Four steps, not a setup project. Register your equipment, set an interval, log each service, and let the status take care of itself.
Sign in on the first day and you can be logging services before lunch.
Sign in with Google and set up your organization in seconds. Your workspace is scoped to your org, so everything you add stays organized and private to your team.
Takes less than a minute.Register all equipment you need to track: HVAC units, vehicles, generators, machinery. Give each one a name, location, and maintenance interval so the system knows when to expect the next service.
Maintenance interval is set in days. You decide the cadence.After each maintenance visit, log what was done, who did it, and when. Build a complete service history for all equipment without chasing down paper records or spreadsheets.
Each log entry is timestamped and tied to the technician.Your equipment list shows the health of everything at a glance: green for good, amber for due soon, red for overdue. No mental math, no missed services.
Status updates automatically as time passes.One entry per visit, filled in once, readable by everyone on your team.
Every piece of equipment carries one of three states, derived from its interval and the date of its last service.
Serviced recently. Nothing due inside the interval you set.
The interval is nearly up. Book the visit before it slips.
The interval has passed with no service logged. Fix this one first.
The workflow you already run, minus the parts that lose records.
Binder in the back office
One shared log, open on any phone
"When did we last service this?"
Date, work, and technician on the record
Calendar reminders nobody owns
Due dates derived from the interval
Scrambling the week before an inspection
Filter the history, export the CSV
Creating your organization takes under a minute, and each piece of equipment takes about as long as typing its name, location, and service interval. Most teams have their fleet in and are logging services the same day.
The number of days between services for one piece of equipment. A fryer you clean every 30 days gets an interval of 30. The next due date is the last service date plus that interval, so logging a service moves the date forward automatically.
No. Register the equipment and enter the date it was last serviced, and the status is accurate from that point on. History builds itself as your team logs new visits. Older paper records can be added later as backdated entries if you want them in one place.
Yes. Everyone signs in with their own account and works inside the same organization, so in-house staff and managers all write to the same history. Each entry is attributed to the person who wrote it.
Status is derived from the interval and the last service date, so it changes on its own as time passes: good while the interval has room left, due soon as it runs out, overdue once the date has passed with no service logged. Nobody has to remember to update it.
Yes. Filter the service history by equipment and date range, then export it as a CSV for an inspector, an insurer, or your own records.
Set up your organization in under a minute.