How to Stop Jobs Falling Through the Cracks
A customer says yes.
The job gets created.
Then nothing happens.
Or the job is waiting for someone to call the customer.
Or materials were meant to be ordered.
Or a technician finished the work, but nobody told finance.
Eventually someone asks:
“What happened with that job?”
That is what people mean when they say work is falling through the cracks.
Usually, the problem is not that nobody cares.
The problem is that the next step is unclear.
Every Job Needs a Clear Status
If a job can only be understood by asking someone, the system is not giving the team enough visibility.
A simple workflow might use stages like:
- New
- Awaiting Approval
- Ready to Schedule
- Scheduled
- In Progress
- Waiting on Customer
- Ready to Invoice
- Complete
The exact stages do not matter as much as everyone understanding what they mean.
A manager should be able to look at the system and immediately see where every job is sitting.
Every Stage Needs an Owner
A status alone is not enough.
Someone also needs to know:
“This is mine.”
For example:
Ready to Schedule → Operations
Waiting on Payment → Accounts
Site Information Missing → Field Team
Quote Follow-Up → Sales
When ownership is unclear, people assume somebody else is handling it.
That is when work gets forgotten.
Create the Next Task Automatically
One of the easiest ways to prevent missed work is to make the next step automatic.
For example:
Quote approved → create scheduling task
Job completed → create invoicing task
Customer has not responded for five days → create follow-up
Required document missing → notify admin
The system does not need to complete the work.
It simply makes sure the work appears in front of the correct person.
Use Deadlines, Not Memory
A task without a deadline can quietly sit there forever.
Important workflow steps should have clear due dates.
For example:
- new enquiry follow-up within one business day,
- quote follow-up after three days,
- completed job reviewed within 24 hours,
- invoice issued after completion,
- overdue job escalated after a defined period.
Once those rules exist, the system can identify what is late automatically.
Make Exceptions Easy to See
Not every job will follow the happy path.
Some jobs will be waiting on:
- customer approval,
- materials,
- access,
- payment,
- additional information,
- or another team member.
That is fine.
The important thing is being able to see those exceptions without manually searching for them.
A dashboard or filtered view can show:
Jobs overdue
Jobs with no owner
Jobs waiting more than five days
Jobs missing required information
Now managers can focus on actual problems instead of checking every job manually.
Stop Managing Work Through Messages
Messages are useful for communication.
They are not a reliable workflow.
If a task only exists because someone sent:
“Can you remember to do this tomorrow?”
there is a good chance it eventually gets missed.
Important work should exist as a task, status or workflow step inside the system.
Messages can support the process.
They should not be the process.
Start With the Jobs That Get Forgotten Most Often
Look at the last few jobs that were delayed or missed.
Ask:
- What was supposed to happen next?
- Who was responsible?
- Was there a deadline?
- Could the system see that it was stuck?
- Did someone have to remember manually?
Those answers usually reveal the missing workflow.
At 5M Consulting, we help businesses build clearer job workflows so work moves from one stage to the next without relying on memory, inboxes or someone constantly checking what is missing.
If jobs keep falling through the cracks, the solution is usually not more reminders.
It is a better system.