How to Stop Jobs Sitting in “Waiting” With No Clear Owner
The job is not cancelled.
It is not complete.
It is not really progressing either.
It is simply:
Waiting.
Waiting for a customer.
Waiting for materials.
Waiting for finance.
Waiting for approval.
Waiting for someone to do something.
Then two weeks pass.
The real problem is often not what the job is waiting for.
It is that nobody clearly owns what happens next.
“Waiting” Is Not a Useful Next Action
A status like:
Waiting
tells you almost nothing.
Instead, the system should explain exactly what is happening.
For example:
Waiting for Customer Approval
Waiting for Deposit
Waiting for Materials
Waiting for Site Survey
Waiting for Internal Review
That makes the blocker visible.
But there is still one more question:
Who is responsible for moving it forward?
Every Blocked Job Needs an Owner
A useful workflow should connect the blocker to someone.
For example:
Waiting for customer selection → Sales
Waiting for deposit → Finance
Waiting for materials → Purchasing
Waiting for technical clarification → Operations
Waiting for site information → Survey Team
Now the job has somewhere to go.
It is no longer sitting in a shared pipeline hoping someone notices it.
Give the Owner a Specific Action
Ownership works better when the next action is clear.
Instead of:
Owner: Sarah
use:
Sarah → Follow up customer selection
or:
Purchasing → Confirm supplier delivery date
or:
Finance → Check deposit payment
The difference is small.
But now the person knows what they actually need to do.
Add a Follow-Up Date
Waiting jobs also need time attached to them.
For example:
Customer approval requested today → follow up in three days
Supplier delivery delayed → check again Friday
Deposit outstanding → reminder tomorrow
Without a date, the job can sit indefinitely.
With a follow-up date, the system knows when it should become visible again.
Let the System Surface Overdue Waiting Jobs
Managers should not have to manually scan every job.
The system can highlight:
Waiting longer than expected
Follow-up overdue
No owner assigned
No next action
Blocked for more than seven days
Now management only needs to investigate the exceptions.
Stop Shared Responsibility Becoming No Responsibility
A common operational problem is assuming:
“Someone will handle it.”
Sales thinks operations owns it.
Operations thinks admin owns it.
Admin assumes the customer is going to respond.
Nobody is deliberately ignoring the job.
The responsibility is simply unclear.
A workflow should remove that ambiguity.
Measure Where Work Gets Stuck
Once waiting reasons are structured, the business can start learning from them.
For example:
18 jobs waiting on customer selections
9 jobs waiting on materials
6 jobs waiting on internal approval
4 jobs waiting on deposits
That can reveal much larger bottlenecks.
Maybe customer selections need to happen earlier.
Maybe purchasing lead times need attention.
Maybe one approval process is slowing everything down.
Automatically Resume the Workflow
Where possible, the event you are waiting for should move the job forward.
For example:
Deposit received → Ready for Purchasing
Materials received → Ready to Schedule
Customer approves → Continue Job
Manager approves → Create Purchase Order
The job does not need someone to notice that the blocker disappeared.
The workflow responds automatically.
Start With Your Oldest Waiting Job
Open your pipeline.
Find the job that has been sitting still the longest.
Ask:
- What exactly are we waiting for?
- Who owns the next action?
- When were they supposed to follow up?
- What happens once the blocker disappears?
If any of those answers are unclear, you have found the reason the job can disappear into the pipeline.
At 5M Consulting, we help trade and service businesses build workflows where every blocked job has a clear reason, owner and next action.
If jobs keep sitting in “waiting” until someone remembers them, the workflow needs more than a status.
It needs ownership.