How to Stop Customer Approvals Holding Up Your Jobs
The team is ready.
Materials can be ordered.
The schedule has space.
But the job cannot move.
Someone is waiting for the customer to approve:
- a variation,
- a product selection,
- a revised quote,
- a design,
- a document,
- or a new date.
Three days later, someone remembers to follow up.
Another week passes.
The job is still sitting there.
The problem is not necessarily the customer.
The approval process may simply be too easy to lose track of.
Make “Waiting for Approval” a Real Status
If customer approval is required, the system should show it clearly.
Instead of vague notes like:
“Waiting on customer”
track exactly what is waiting.
For example:
Variation #3 — Awaiting Approval
Window Colour — Awaiting Selection
Revised Quote — Sent 8 September
Installation Date — Confirmation Required
Now anyone looking at the job understands what is blocking progress.
Record When the Request Was Sent
Time matters.
A job waiting one day is very different from a job waiting two weeks.
The system should know:
- what was sent,
- when it was sent,
- who it was sent to,
- when the next follow-up is due,
- and whether the customer has responded.
That makes overdue approvals easy to identify.
Automate the Follow-Up
The system can handle predictable reminders.
For example:
Approval requested → wait three days
No response → send reminder
Still no response after seven days → create staff follow-up
Customer approves → stop reminders
Now somebody does not need to manually review every waiting job.
The system brings the exceptions to them.
Make Approval Easy for the Customer
Sometimes approvals are delayed because the customer experience is awkward.
They may need to:
- find an old email,
- print and sign something,
- reply with specific wording,
- or call the office.
A simpler approach might be:
Approve
Decline
Request Changes
One clear action can dramatically reduce friction.
Let Approval Trigger the Next Step
Approval should not just change a status.
It can continue the workflow.
For example:
Variation approved → update job value
Product selected → create purchasing requirement
Revised quote accepted → create job
Date confirmed → update schedule
The customer decision becomes an operational trigger.
Nobody needs to manually move the job forward afterwards.
Keep Important Decisions Attached to the Job
Approvals should be easy to find later.
That is especially important when they affect:
- pricing,
- scope,
- materials,
- dates,
- or contractual obligations.
Instead of searching through emails and messages, the job should show:
Approved by
Approved on
What was approved
Supporting communication
That gives operations and finance a clearer record.
Give Management Visibility Into Waiting Work
A useful dashboard might show:
12 jobs waiting on customer
4 waiting more than seven days
$86,000 of work currently blocked
That turns customer approvals from invisible delays into something management can actually manage.
Start With the Job That Has Been Waiting Longest
Look at your current pipeline.
Find the oldest job sitting in:
Waiting on Customer
Then ask:
- What exactly are we waiting for?
- When did we request it?
- Has anyone followed up?
- Who owns the next action?
- What happens when the customer responds?
If those answers are unclear, the workflow needs work.
At 5M Consulting, we help businesses build approval workflows that keep customer decisions visible and automatically move jobs forward when those decisions are made.
If work keeps sitting idle because everyone is waiting for a customer response, the approval process probably needs to become part of the system.