Mechanic inspecting an excavator engine beside a field-service truck

Fleet Maintenance

Give every machine issue an owner and a record.

Connect field issues, repair work, routine visits, and service history. Add the module to Core or Growing with one mechanic/oiler seat, or use it as part of Full.

Request a walkthrough See pricing

What it does

From field issue to completed service.

Report the problem against the machine. Assign the repair and keep the completed service in its history.

Eligible foremen can report issues. Mechanics and oilers use fleet seats to run the work.

A field issue report becomes an assigned repair work order, then a completed entry in the excavator’s service history. — A field report becomes owned repair work, then a service record that stays with the machine.

Report the machine issue.
Assign and manage the repair.
Record the completed service.

Inside the module

The machine’s history stays with the machine.

Issues

Keep the reported problem and job context together.

Repairs

Assign work and track its recorded status.

Routine visits

Record fuel, fluids, meter readings, and service notes.

History

Find previous work before diagnosing the next problem.

How it helps

Keep routine service with the job visit.

Oilers record visits to machines on a job. Fuel, fluids, readings, and notes stay in service history.

A visit list for the job.
Additions and readings per machine.
Service notes and supporting photos.

An oiler records fuel, DEF, and a meter reading on an excavator visit inside a North Ridge job service session. — Routine service has its own path: a job service session, a machine visit, and the fuel, fluids, and readings recorded at that stop.

Open the job service session.
Record the machine visit.
Keep additions and readings in service history.

Issue: what someone noticed: An operator or foreman reports the machine problem, with notes or photos for context. The issue lets the office or shop review the report before deciding what work is needed.
Work order: who handles the next step: Create owned repair or preventive work, including the field or shop location. Keep diagnosis, waiting-on-parts updates, and completion context with that work instead of leaving the next step in a text thread.
Service entry: what was done: Record the completed work on the machine’s history. A routine service visit or work already performed should have its own record without inventing an unresolved breakdown.
Readiness: review the operating context: Check the issue, work, and recorded equipment state before planning the next assignment. A completed entry is evidence of recorded work; it is not independent certification that a machine is safe or ready for every task.

One job service session: An oiler person or crew starts the job stop, records the machine visits underneath it, and closes the session. Field changes after close require reopening with a reason.
A record for each machine visit: Keep fuel and fluid additions, readings, notes, and visit photos with the machine. Review open issues or report a new issue during the visit; repair ownership stays with the maintenance work queue.
Supply equipment and deliveries: Record refills on the fuel trailer, service trailer, or oiler truck that received them. Supply entries record additions and sources; they do not claim an automatic stock balance from estimated usage.

Can a foreman report an issue without a fleet seat?

With Fleet Maintenance enabled, eligible foremen can report issues and add context. Mechanics and oilers use specialized seats to run the work.

What does the module include?

Fleet Maintenance includes one mechanic/oiler seat. Additional fleet seats can be added as needed. Full Operations includes the module; Core and Growing can add it.

Does routine fueling or service need an issue first?

No. Routine service can be recorded on its own. Fleet Maintenance keeps job service visits and the machine service history alongside issues and work orders, without treating every fuel or fluid entry as a breakdown.

What should we demonstrate for the shop?

Use one reported field problem and one routine visit. Follow the issue, owner, field/shop location, work updates, and completed service entry. Then find the machine history and discuss how your team confirms operating readiness.

Walkthrough

Walk one down machine through the queue

Bring one current job and the records your team uses. We’ll demonstrate the relevant workflow and confirm scope, seats, and price.

We’ll use these details to respond and focus the walkthrough on your operation.