PM Compliance Tracker (Mini)
A lightweight preventive maintenance tracker you can embed in Webflow. Track vehicles, PM intervals (miles and/or days), see who’s overdue, and export a clean CSV for your ops team.
PM due by miles or days
Overdue + due soon
CSV export
Add / Update a Vehicle
Used to determine due/overdue by miles.
If set, the tool estimates “days until due (miles)”.
Set to 0 to ignore mile-based PM.
Set to 0 to ignore time-based PM.
Data is stored locally in the browser (localStorage). For a shared team tracker, you’d wire this to your backend.
PM compliance
—
Compliant / total
Overdue
—
Needs PM now
Due soon
—
Within threshold
Policy
—
Filter
| Status | Unit | Next PM | Due in | Actions |
|---|
—
How to use a PM compliance tracker
Pick an interval (miles and/or days). Keep your “last PM date” and “last PM odometer” updated. Your compliance score improves when you complete PM before vehicles go overdue.
Common PM policies
- Light-duty: 5,000–7,500 miles or every 90 days
- Severe duty: shorter intervals and stricter “due soon” windows
- High utilization: focus on miles-based PM, and estimate due date from miles/day
PM Compliance FAQ
What counts as “compliant”?
A vehicle is compliant if it is not overdue by miles or days. If you track both, the earliest due trigger wins.
Can I use miles-only or days-only?
Yes—set the other interval to 0. Example: set days to 0 to use miles-only PM.
How do I make this shared across a team?
This mini tool stores data in the browser. To share, connect it to a database (or your existing fleet system) and require login.
Disclaimer: This tracker is for planning and workflow. Always follow OEM guidance and your internal safety requirements.