How to Find Jobs That Have Not Changed Status in Too Long
The job says:
Waiting for Materials
It said that yesterday.
And last week.
And twelve days ago.
Nobody has technically missed a deadline.
But the job has stopped moving.
That is the problem with relying only on statuses.
A status tells you where something is.
It does not tell you how long it has been there.
Track When the Status Changed
Every time a job changes stage, the system can record the date.
For example:
Quote Approved – 3 September
Materials Ordered – 4 September
Waiting for Materials – 6 September
If today is 19 September, that job has been sitting in the same stage for:
13 days
Now the delay is visible.
Define What “Too Long” Means
Different stages should have different expectations.
For example:
New Enquiry: 1 day
Quote Preparation: 3 days
Waiting for Internal Approval: 2 days
Ready to Schedule: 5 days
Completed but Not Invoiced: 2 days
A job can then be compared with the normal time expected for its current stage.
Surface Stale Jobs Automatically
Instead of managers scrolling through every open job, the system can create a view such as:
Jobs With No Status Change for 7+ Days
That might immediately reveal:
- forgotten jobs,
- missing follow-ups,
- supplier delays,
- customer blockers,
- incomplete handovers,
- or work with no clear next action.
The team sees the exceptions instead of hunting for them.
Separate Legitimate Waiting From Stalled Work
Some jobs are supposed to sit.
For example:
Manufacturing lead time: 4 weeks
That job may be completely healthy.
So the system should also understand why the job is waiting.
Compare:
Waiting for custom manufacture – expected 28 days
with:
Waiting for internal review – unchanged for 12 days
Those are very different situations.
Give Every Stale Job a Next Action
Once the system identifies a stale job, someone needs to own it.
For example:
Materials delayed → Purchasing to contact supplier
Customer approval missing → Sales to follow up
Job ready but unscheduled → Operations to book
Completed but uninvoiced → Finance to review
The goal is not just to flag the problem.
It is to create movement.
Escalate Based on Time
You can also make the warning stronger as the job ages.
For example:
5 days unchanged → highlight
10 days unchanged → notify owner
15 days unchanged → escalate to manager
Now forgotten work becomes increasingly difficult to ignore.
Measure Where Jobs Commonly Stall
Once stage duration is tracked, you can look across the whole business.
For example:
Average time waiting for materials: 8 days
Average time ready to schedule: 6 days
Average time waiting for approval: 2 days
If one stage consistently takes much longer than expected, you may have found a process bottleneck.
Look Beyond Due Dates
Due dates are useful.
But many operational problems happen before anything is technically overdue.
A job might have a completion date three weeks away while already sitting untouched for ten days.
Stage-ageing gives you another signal.
It tells you:
This job has stopped moving.
That can be enough to investigate early.
Start With Your Oldest Unchanged Jobs
Open your current job list.
Sort by:
Last Status Change
Then look at the oldest ten.
Ask:
- Why is this still here?
- Is the delay expected?
- Who owns the next action?
- Has anyone followed it up?
- Should the system have surfaced this earlier?
You may find jobs that nobody realised had stalled.
At 5M Consulting, we help trade and service businesses build workflows that show not only where work is sitting, but whether it has been sitting there for too long.
A job does not need to miss its final deadline to be in trouble.
Sometimes the first warning is simply that nothing has changed.