Skip to main content
All resources

Workflow guide

How to read a vehicle maintenance roadmap

Connect vehicle history, mileage, inspections, recommendations, due context, and internal follow-up without turning guidance into an automatic estimate or customer action.

Subject owner
VehicleDesk Product
Last reviewed
2026-07-31
01

Start from the vehicle record

The roadmap is meaningful only when ownership, identifiers, mileage, service history, inspections, and open recommendations can be traced back to the vehicle and source evidence.

02

Treat due context as guidance

Maintenance groupings help staff review what may deserve attention. They do not replace technician judgment, manufacturer guidance, an inspection, or a current quote.

03

Create the next internal action

Staff can turn review findings into a task, reminder, or opportunity while preserving the reason and vehicle context. That action does not contact the customer by itself.

04

Keep provider writes controlled

Publishing estimate content back to Shopmonkey is a narrow controlled write path and is disabled by default. The roadmap remains useful as an internal planning surface without that write enabled.

Related product detail

See how this guidance appears in VehicleDesk.

Open related workflow