Maintenance rarely ends in front of a computer. “Log maintenance” now appears directly on every Equipment card on the phone. It remains available for preventive work and becomes more prominent when the item has reached its threshold. Recording does not depend on a network connection.
A short action with no invented choice
The button opens a field-friendly sheet. You explicitly choose Inspection, Repair, Replacement, Cleaning, or Other. The app never preselects a type on your behalf. The date starts at today but remains editable; cost and notes are optional.
An invalid cost no longer disappears silently. The phone keeps the sheet open and asks for a valid value of zero or more. It then stores the maintenance fact and its sync operation together in the local database. Losing connectivity between those steps cannot leave a visible record that has no way to reach the server.
Three actions close the cycle; two only enrich history
An inspection, repair, or replacement resets the service cycle. The “Maintenance due” badge disappears on the phone immediately, before any connection returns. The server also closes reminders that are still pending when the operation syncs.
Cleaning and Other remain useful historical facts, but they reset neither distance nor time. This distinction prevents a wash from making worn runners appear serviced.
The badge follows your thresholds, not a hidden rule
MushMate no longer applies an annual maintenance default. The badge appears only when you entered a distance interval, a day interval, or both for that item. With no threshold, the app invents no schedule.
“Worn” and “Damaged” remain visible in the condition badge, but they do not trigger “Maintenance due” by themselves. That may look less automatic. It prevents a repair logged in the field from leaving an alert that cannot close until someone also edits the web inventory.
The phone and server count the same calendar days. An outing completed on the service day belongs to the cycle that was just closed; the first following day starts the new cycle.
What remains visible, and what does not
A reminder already sent remains history. The app closes pending or failed reminders, but it cannot recall an email that left just before maintenance was logged. Maintenance for another sled and reminders for another kennel remain untouched.
This delivery does not create or edit inventory from the phone. Thresholds, condition, assignment, and photos remain managed on the web. It also does not infer a cost, maintenance type, or interval from the equipment. The phone captures what you actually did and syncs it when connectivity returns.