On-Track, Due-Soon, Overdue: Reading Fleet Health at a Glance

The Spreadsheet That Doesn't Tell You What's Wrong

It's a Monday morning. You have 60 assets in the plant. A vendor wants to know whether Asset 34 — the hydraulic press — is current on its PM. You open the spreadsheet, scroll to row 34, check the last-service date, mentally subtract today's date, compare it to the interval column two screens to the right, and conclude: probably fine, maybe due this week, hard to say.

Now imagine doing that for every asset before the shift starts.

No maintenance manager has time for that arithmetic every morning. And the consequence of skipping it isn't a missed column in a spreadsheet — it's a press that runs three weeks past its PM due date because the number was never visible, and a repair bill that arrives instead of a service record.

PM status indicators exist to collapse that morning arithmetic into a single, scannable color. By the end of this article, you'll understand exactly how On-Track, Due-Soon, and Overdue are calculated, why the thresholds matter, and how a persistent status layer across your entire fleet makes fleet health readable in seconds rather than minutes.

---

How PM Status Is Calculated

Every PM status indicator reduces to a single number: days remaining until the next PM is due (or days past due, if negative). The formula is straightforward:

Days Remaining = Next PM Due Date − Today's Date

Where Next PM Due Date = Last PM Date + PM Interval (in days).

A worked example with three illustrative assets:

Asset	Last PM Date	Interval	Next PM Due	Days Remaining	Status
Hydraulic Press	Mar 1	90 days	May 30	42	On-Track
Air Compressor	Mar 15	60 days	May 14	26	Due Soon
Conveyor Belt	Feb 10	45 days	Mar 27	−15	Overdue

The conveyor belt's next PM due date passed 15 days ago. That negative number is the Overdue signal. The air compressor has 26 days left but is inside the Due-Soon window. The press has 42 days — safely On-Track.

For a deeper look at how Next PM Due Date is derived — including hour-based and cycle-based intervals alongside day-based ones — see Next PM Due Date Calculation Explained.

---

Defining the Three Status Bands

The thresholds that separate On-Track from Due-Soon from Overdue are a design choice, not a universal standard. What matters is that they're consistent, visible, and set relative to each asset's own interval — not a fixed calendar window applied uniformly to a mixed fleet.

On-Track (Green) Days remaining exceed the Due-Soon threshold. The asset is current, no immediate action required.

Due Soon (Amber) Days remaining are within a defined look-ahead window — often 20–30% of the interval, or a fixed number of days such as 7, 14, or 30, depending on your planning cycle. An asset in this band needs a work order created or a technician scheduled before the window closes.

Overdue (Red) Days remaining is zero or negative. The PM due date has passed. The asset is running without its scheduled maintenance — which means the failure probability is increasing in a way the interval was designed to prevent.

The practical value of Due-Soon is that it gives you a planning horizon. A weekly planning meeting needs to see what's due in the next 14 days, not just what's already overdue. A fleet with no Due-Soon band is a fleet that only surfaces problems after they've arrived.

---

Why Fleet-Level Status Matters More Than Per-Asset Status

A single asset's status is useful. A fleet-level status view is what a maintenance manager actually needs.

When you can see all 60 (or 100, or 500) assets simultaneously, grouped by status, two things happen:

1. Pattern recognition becomes possible. If 18 assets show amber in the same week, that's a resource-planning signal — you may not have enough technician hours to clear them all before they turn red. If an asset turns red repeatedly, its interval may be set too wide for its actual operating conditions.

2. Prioritization becomes automatic. Instead of manually ranking your to-do list each morning, the status board does it for you. Red assets get immediate attention. Amber assets go into this week's planning queue. Green assets are confirmed current — no action needed.

This is the core limitation of using a spreadsheet for PM tracking. A spreadsheet can hold the dates and the intervals, but it recalculates nothing automatically. Every morning you're the calculation engine — and past roughly ten assets, that cognitive load compounds into errors and omissions. A persistent status layer recalculates every asset's position every day, without anyone running the formula manually.

---

Reading PM Status Indicators in Practice

A well-designed PM status dashboard surfaces three numbers at the fleet level:

• Count of Overdue assets — the immediate action queue
• Count of Due-Soon assets — the planning queue for this week or this sprint
• Count of On-Track assets — confirmation that the majority of the fleet is current

Some teams also track a PM compliance rate: the percentage of scheduled PMs completed on time within a rolling period (typically 30 or 90 days). That rate doesn't come from the status indicators alone — it comes from combining status with PM history. But the status board is the daily operational surface; compliance rate is the management reporting metric. Both matter, and they inform each other.

For how PM compliance tracking connects to documentation requirements in regulated environments, see PM Compliance Tracking for OSHA.

For a calendar-based view of the same data — which assets are due in which week across the next 12 months — see Annual PM Schedule: Calendar View.

---

Setting Due-Soon Thresholds That Fit Your Planning Cycle

There's no single correct Due-Soon window. The right threshold depends on two things: how long it takes to plan and execute a PM task, and how much lead time your procurement and scheduling allow.

A simple rule of thumb: set the Due-Soon window to cover at least one full planning cycle. If your team plans maintenance weekly, a 14-day Due-Soon window ensures every task surfaces at least one planning meeting before it goes overdue. If your cycle is monthly, extend to 30 days.

For assets with long procurement tails — where a PM task requires a part that needs three weeks to arrive — a wider Due-Soon window (45 days, or 30–40% of the interval) prevents the situation where a part isn't ordered until the asset is already red.

For short-interval tasks (weekly lubrication, bi-weekly filter checks), a narrower window (3–5 days) avoids flooding the amber band with tasks that are easily completed on short notice.

The interval itself is the foundation. If the interval is wrong — too wide for a high-duty-cycle asset, too narrow for a rarely-used one — status indicators will either fire too late or too often. Setting PM intervals correctly is the upstream work that makes status indicators meaningful downstream.

---

From Status to Action: Closing the Loop

A PM status indicator that nobody looks at does nothing. The workflow that makes status indicators operational is:

1. Daily or shift-start review of the fleet board — scan for new Overdue assets; confirm Due-Soon assets have work orders open.
2. Weekly planning meeting — use the Due-Soon count to match available technician hours against upcoming tasks; escalate any Overdue assets that haven't been addressed.
3. Post-PM update — once a PM is completed, log the completion date so the system resets that asset's Next PM Due Date and its status returns to On-Track. Without this step, an asset stays red even after service.
4. Interval review — if an asset repeatedly enters the Overdue band because technicians can't get to it in time, that's often a scheduling or resource signal, not an interval signal. But if an asset fails before its Due-Soon window opens, the interval itself may be too long.

The checklist work that supports each PM task — the step-by-step verification that a technician actually completed each item — is a separate layer from the status indicator. The PM Compliance Checklist Pack provides ready-to-use task checklists organized by asset type, so the work behind each status reset is documented and repeatable.

---

Making Fleet Health Readable Without Building It Yourself

Calculating status for three assets takes a few minutes with a formula. Calculating it for 60 assets, every day, across a mix of day-based, hour-based, and cycle-based intervals, while tracking PM history and compliance rates — that's what breaks the spreadsheet model. It's not that the math is hard; it's that the math needs to run continuously, on every asset, without anyone having to remember to run it.

A persistent, multi-asset status engine does exactly that: it recalculates every asset's days-remaining, assigns status, and surfaces the fleet-level count — so the maintenance manager can spend Monday morning looking at the dashboard, not building it.

If you're ready to see what your fleet's PM status looks like in a single view, explore the features or start a 14-day free trial — no setup required beyond entering your assets and their last PM dates.

If you're earlier in the process and still working out intervals and cost estimates in a spreadsheet, the PM Compliance Checklist Pack is a practical starting point for structuring the task-level work while you decide on tooling.