How to Track the Time Between Quote Approval and Job Completion
A customer approves the quote on Monday.
The job gets created Wednesday.
Materials are ordered Friday.
Scheduling happens the following week.
Three weeks later, the work is finally completed.
Everyone was busy.
Nothing obviously went wrong.
But how long did that job actually take to move through the business?
If you are not measuring it, you probably do not know.
Start the Clock at Approval
A useful starting point is:
Quote Approved
That is the moment the customer has effectively said:
“Let's go.”
From there, the clock can run until:
Job Completed
The difference gives you the total cycle time.
For example:
Quote Approved: 3 September
Job Completed: 24 September
Cycle Time: 21 Days
One job does not tell you much.
Hundreds of jobs do.
Track the Stages in Between
The real value comes from understanding where those 21 days went.
For example:
Approval → Job Created: 1 day
Job Created → Materials Ordered: 2 days
Materials Ordered → Materials Received: 7 days
Materials Received → Scheduled: 4 days
Scheduled → Completed: 7 days
Now you can see which parts of the workflow are consuming time.
Without those timestamps, everything simply looks like one long job.
Capture Dates Automatically
Your team should not need to maintain another spreadsheet of timestamps.
The system can record dates whenever important events happen.
For example:
Quote Approved → Approved Date saved
Job Created → Creation Date saved
Materials Ordered → Order Date saved
Job Scheduled → Schedule Date saved
Job Completed → Completion Date saved
Those events are already happening.
The system simply remembers when.
Compare Different Job Types
Not every job should take the same amount of time.
A small repair might take three days.
A large installation might take six weeks.
That is why cycle time becomes more useful when grouped by:
- job type,
- branch,
- salesperson,
- technician,
- supplier,
- product,
- or project value.
You can compare similar work instead of treating every job the same.
Find Jobs Taking Longer Than Normal
Once you know the normal cycle time, exceptions become visible.
For example:
Average installation: 18 days
Current job: 34 days
That job deserves attention.
The system could flag:
Job cycle time above target
before the delay becomes even larger.
Management does not need to inspect every job manually.
Look for Repeating Bottlenecks
Patterns may start appearing.
Maybe jobs regularly sit:
Four days before purchasing
or:
Nine days waiting for scheduling
or:
Three days after completion before final paperwork
Those delays can be difficult to notice during day-to-day work.
Cycle-time data turns them into something measurable.
Faster Is Not Always Better
The goal is not simply:
Make every job faster.
Sometimes waiting is legitimate.
Materials need manufacturing.
Customers delay selections.
Permits take time.
Complex work takes longer.
The goal is understanding the delay.
If a 30-day job includes 20 days of necessary supplier lead time, that may be perfectly healthy.
If it includes 10 days where nobody took the next action, that is different.
Measure Improvement
Once you improve a process, cycle time can tell you whether the change actually worked.
For example:
Before automation: 24 days average
After automation: 19 days average
That is much more useful than saying:
“The new process feels better.”
You can see the operational impact.
Start With Twenty Completed Jobs
Take twenty recent jobs.
For each one, record:
- quote approval date,
- job creation date,
- scheduled date,
- completion date.
Then calculate the gaps.
You may immediately find a stage that takes far longer than expected.
At 5M Consulting, we help trade and service businesses connect operational workflows so the time between winning work and completing it becomes visible, measurable and easier to improve.
You already know how much work you are winning.
You should also know how long it takes your business to deliver it.