Overdue Maintenance - Managing Late PM and Urgent Repairs

Overview

A maintenance task becomes overdue when its scheduled date has passed and no completion has been recorded. In small numbers, overdue tasks are a normal operational friction. In large numbers, they become a liability.

Organizations that let overdue maintenance accumulate face a predictable set of problems. Equipment degrades faster because service intervals are missed. Regulatory inspections expose gaps in compliance records. Failures happen at the worst possible times — during peak production, in safety-critical environments, or when a key asset is already under repair. And when an incident occurs, the lack of a completion record becomes evidence of negligence.

The risks are not hypothetical:

A generator that missed its last three quarterly inspections fails during a power outage.
A forklift with an overdue brake inspection injures an operator.
A refrigeration unit with a deferred compressor service spoils inventory overnight.
An annual equipment certification lapses because no one tracked the renewal date.

Overdue maintenance is a warning signal, not just an administrative gap. Managing it well means identifying what is late, understanding why it slipped, resolving it systematically, and preventing the pattern from repeating.

How it Works in UniAsset

UniAsset tracks every maintenance task against a due date. When that date passes without a completion record, the task is automatically flagged as Overdue. This happens without any manual intervention — the system evaluates task status continuously.

Overdue Detection

UniAsset marks a task overdue based on its scheduled due date. This applies to:

Scheduled preventive maintenance generated by PM rules (time-based or usage-based)
Manually created maintenance records with a specific due date
Recurring tasks that have not been closed before the next cycle begins

When a task goes overdue, it appears with an Overdue status indicator and surfaces in the maintenance dashboard. Assets with overdue tasks are also visually flagged in asset listings, so you can spot problem assets without running a separate report.

Notifications and Alerts

UniAsset sends notifications when tasks approach and pass their due dates. These can be configured per PM rule:

Advance warning: X days before due date (e.g., 7 days before)
On due date: Reminder when the task becomes due
Overdue alert: Notification after the due date passes

These notifications go to the assigned technician, team managers, or any user subscribed to maintenance alerts. Early warnings are what separate proactive teams from reactive ones.

Maintenance Dashboard

The maintenance dashboard gives you a filtered view of all tasks by status. For overdue management, the relevant filters are:

Overdue — tasks past their due date with no completion
In Progress — tasks started but not closed
Scheduled — upcoming tasks not yet started

You can filter further by asset category, location, assigned user, or date range. This lets a facilities manager see all overdue HVAC tasks, or a fleet manager see all vehicles with missed oil changes.

Asset-Level Visibility

On any individual asset, the Maintenance tab shows the full task history including overdue items. This is useful for understanding how chronically a specific asset is being deferred — a pattern that often indicates a resource problem, a difficult-to-schedule vendor, or an asset that has become operationally unreliable.

Overdue in Context of PM Rules

When a PM rule generates a recurring task and that task goes overdue, the next cycle does not begin until the overdue task is either completed or explicitly dismissed. This prevents the schedule from drifting forward while the backlog remains unresolved. If you complete the overdue task today, the next task is scheduled from today's completion date — not from the original due date — unless you specify otherwise.

Reviewing and Working Through Overdue Tasks

Use this process when you need to audit your backlog and systematically close or reschedule overdue maintenance.

1. Open the Maintenance Dashboard

Go to Maintenance from the main navigation. This is your central view for all task activity across the organization.

2. Filter for Overdue Tasks

Apply the Overdue status filter. You can combine this with additional filters:

Category: Limit to a specific asset type (e.g., Vehicles, HVAC, IT Equipment)
Location: Limit to a building, floor, or site
Assigned To: See what a specific technician or team has pending
Date Range: Identify tasks that have been overdue the longest

Sort by Due Date (Oldest First) to start with the most critical backlog.

3. Triage Each Overdue Task

For each overdue task, decide on one of three actions:

a) Complete it now (or record past completion) If the work has already been done but was never logged, mark it complete with the actual date the work occurred. Do not use today's date if the work happened earlier.

b) Reschedule it If the work is genuinely delayed (vendor not available, part on order, scheduled for next week), update the due date to the next realistic date. Add a note explaining why it was pushed. This removes it from the overdue list temporarily and sets a new expectation.

c) Dismiss or cancel it In rare cases, a task may no longer apply — the asset was disposed of, the maintenance type changed, or the requirement was eliminated. Cancel the task with a clear note. Do not leave ghost tasks accumulating for assets that no longer exist.

4. Prioritize by Risk

Not all overdue tasks carry equal risk. When triaging a large backlog, prioritize by:

Safety-critical assets (vehicles, lifts, pressure vessels, fire suppression)
Compliance-driven tasks (regulatory inspections, certifications with expiry dates)
High-value or high-dependency assets (production equipment, servers, primary HVAC units)
Assets already showing symptoms (noises, performance drops, error codes)

Lower priority: cosmetic maintenance, deferred cleaning tasks, optional upgrades.

5. Assign and Communicate

If overdue tasks are unassigned, assign them to a specific person with a deadline. An unassigned overdue task is likely to stay overdue indefinitely. Make the assignment explicit and set a new due date that reflects the current reality.

6. Complete and Document

When the work is done, complete the task with:

Actual completion date
What was performed
Who did the work
Any findings or follow-up actions needed
Actual cost (if known)

See Completing Maintenance Tasks for full field-by-field guidance.

7. Review the Overdue List Weekly

After the initial cleanup, build a habit of reviewing the overdue list weekly. A list that stays at zero or near-zero is a sign of a functioning maintenance program. A list that grows week over week is a signal that capacity, scheduling, or prioritization needs attention.

Best Practices

Set realistic due dates from the start. Overdue tasks that are always rescheduled once or twice usually indicate the original frequency was too aggressive for your team's capacity. Adjust PM rule frequencies to match what you can actually execute.

Distinguish between overdue and deferred. If you deliberately push a task because a vendor is scheduled next month, update the date and write a note. This keeps the overdue list meaningful — it should reflect genuine gaps, not planned deferrals.

Use the overdue count as a KPI. Track the number of overdue tasks at the end of each week. Share this with team leads. A rising number signals a workload or resourcing problem before it becomes a failure.

Complete tasks with the actual date, not today's date. If a technician serviced a unit last Thursday but you are recording it on Monday, use last Thursday's date. This preserves accurate PM cycle calculations and audit records.

Pair overdue tasks with asset health context. Before closing a long-overdue task, check the maintenance history for that asset. If it has missed multiple consecutive PMs, the first completion should include a full inspection — not just a routine service — to assess whether the deferred maintenance caused any secondary issues.

Never delete overdue tasks to make numbers look better. Canceling a task without a reason, or changing its due date indefinitely, undermines the integrity of your maintenance data. Auditors, insurers, and compliance reviewers may examine this history.

Common Mistakes to Avoid

Using today's date for work that was done days or weeks ago. This skews PM cycle calculations. A task completed on March 15 but recorded on March 30 will generate the next PM task 15 days later than it should. Over time, this erodes the schedule.

Leaving tasks as "In Progress" indefinitely. In Progress is a transitional state that means work is actively happening. If a task has been In Progress for two weeks, it has become overdue in practice. Review stuck In Progress tasks as part of your weekly audit.

Not assigning overdue tasks to a specific person. Shared ownership means no ownership. Every overdue task needs a named person responsible for resolution and a date by which it will be addressed.

Rescheduling the same task repeatedly without investigation. If a task has been pushed three times in a row, something structural is wrong: the technician does not have access, the part is on backorder, the vendor is unreliable, or the task frequency needs adjustment. Investigate instead of rescheduling a fourth time.

Ignoring overdue tasks on inactive or low-use assets. An asset that sits in storage or is used rarely still has compliance and safety requirements. A rarely-used fire extinguisher still needs its annual inspection. Low-use does not mean no maintenance.

Completing overdue tasks without recording what was found. If a motor overdue by 90 days finally gets serviced and the technician finds early bearing wear, that finding needs to be in the record. An overdue task that gets closed with "Done" and no notes is a missed opportunity to document the consequence of the delay.

Pro Tips (UniAsset Advantage)

Spreadsheets do not flag overdue tasks automatically. A team managing maintenance in a spreadsheet depends entirely on someone manually checking what is past due. Dates do not turn red. Nothing pings the responsible person. In UniAsset, overdue detection is automatic and continuous.

Overdue count across your whole fleet in seconds. With the maintenance dashboard filtered to Overdue, you can see every late task across every asset, site, and category at once. A facilities team managing 200 assets across three buildings can triage their full backlog in minutes, not hours.

Notification chains catch tasks before they go overdue. PM rule notifications can be set to fire 14 days before, 7 days before, and on the due date. A task that receives three advance warnings before going overdue is far less likely to slip. Spreadsheets and generic task tools rarely offer this layered alerting tied directly to asset and maintenance context.

Overdue history is part of the asset record. If a vehicle has been overdue on its brake inspection three times in the past year, that pattern is visible on the asset's maintenance tab. It can support a decision to replace the vehicle, change the vendor, or escalate to a supervisor. That operational intelligence is only possible because the system preserves the record of what was missed, when, and for how long.

Incident and compliance risk is traceable. If an asset causes an incident and its maintenance was overdue, UniAsset's history shows exactly when the gap started and who was responsible for closing it. This is not just useful for internal accountability — it matters in insurance claims, regulatory inquiries, and workforce safety reviews.

Need Help?

If you have questions not covered in this article, our support team is here to help.

Contact Support