Practical workflow guide
Follow one job from completed work to invoice.
Find the hands-on effort, waiting and missing information behind a handoff. Use what you learn to decide whether a process change or system improvement is worth pursuing.
The job is done. What is Finance waiting for?
Explore one illustrative handoff. Select a stage to see the information, owner and next question.
Illustrative job · J-1042
Complete does not yet mean ready to bill.
- Needed
- Approved extras, actual time and the client’s purchase order.
- Next owner
- The coordinator gathers the missing details for Finance.
- What to check
- How often is the handoff incomplete, and how long does it wait?
Separate time spent chasing information from elapsed waiting. Both matter, but they measure different problems.
1. Choose a clear start and finish.
Start when the team marks a job complete. Finish when an accurate invoice is issued. Identify the people involved in that handoff and ask them to walk through recent cases together.
Include ordinary cases and ones that needed correction. A handful of examples can reveal questions to investigate; it does not establish a reliable business-wide average.
2. Capture what actually happened.
Use existing records where possible and note which details are observed, reported or estimated. Record these fields for each case:
| Record | What to capture |
|---|---|
| Start and finish | Job completed, ready for invoicing, and accurate invoice issued: the date and time of each event. |
| Human effort | Minutes spent by each person gathering, entering, checking and correcting information. |
| Waiting | When the job stopped moving, what was missing, and who or what could unblock it. |
| Corrections | What was returned or changed, why, and how much extra work it created. |
| Records and systems | Where the team found each piece of information and where they copied it next. |
| Responsibility | Who owned the next action and whether that was clear to everyone involved. |
3. Keep effort and elapsed time separate.
Add the human minutes across the people involved. Record elapsed time separately: waiting two days for a missing job reference does not mean someone worked on it for two days.
Monthly human effort: monthly case volume × mean human minutes per case ÷ 60.
Show the sample size, period and variation behind that mean. Include corrections and exceptions in their actual proportions before extrapolating to the full workload.
A proposed improvement also needs to include the effort that remains: manual cases, review, correction and ongoing upkeep. Recovered hours represent capacity; cash savings require an actual expense to fall.
A shorter interval before invoicing is a separate outcome. Whether cash arrives sooner depends on payment terms and collection behavior as well.
4. Compare practical changes.
Look first at the cause. Missing ownership may call for an agreed handoff. Repeated copying may call for a shared record or integration. Inconsistent inputs may need a clearer capture process before automation is appropriate.
Compare the cost of implementation, ongoing software and maintenance, and the work required from the team. A smaller change or leaving the process alone can be reasonable if the expected benefit is limited.
5. Write a brief the team can decide on.
- The problem
- Where the work stalls, who it affects and why it matters now.
- The evidence
- The cases observed, the current effort and elapsed time, and the uncertainties still to check.
- The proposed change
- The smallest useful improvement, its alternatives, costs and dependencies.
- The check
- The same measures before and after, with invoice accuracy, completed handoffs and exception handling included.
- The owner
- Who makes the decision, who operates the changed process and who maintains the system.
Give Operations and Finance a chance to correct the picture before making a commitment. The first useful result is a shared understanding of what happens and what would count as an improvement.
Related client work
One repair record the team could build on.
At Secured Tech, repair details, parts, labor and invoicing were spread across systems. The joint delivery combined the repair foundation with practical developer training.
See the work and the team’s next step.
The case study separates USS’s delivery from the customer portal subsequently built by Secured Tech’s own team.
Read the Secured Tech case studyMake the consequences visible
Start with the work. Show the math.
Volume, human effort, waiting and exceptions tell us where to look. A useful estimate makes its assumptions visible.
Manual record entry · one month
Current human effort
800 records × 6 minutes ÷ 60Modeled effort after the change
Includes manual cases, review and upkeepPotential recovered capacity
Time available for other useful workThis is a scenario, not a client result or a savings promise. Recovered time becomes cash savings only when an actual expense falls. Implementation and software costs still need to be included.
See the assumptions and calculation
Assume 75% of the 800 records are eligible and 80% of those use the new process: 480 records. Each takes 2 human minutes, including review and correction. The other 320 still take 6 minutes. Allow another 4 hours for monthly upkeep.
After: (480 × 2 + 320 × 6) ÷ 60 + 4 = 52 hours.
Difference: 80 − 52 = 28 hours.
In a real engagement, we check the volume, observe the work, include exceptions and compare accepted results. Quality and downstream completion must hold up as effort changes.
A practical guide: follow one job from completed work to invoice
Let’s talk
What needs to work better?
What have you inherited, or what keeps getting stuck?
Tell me what is happening, what you have already tried and why it matters now. We’ll talk through the result you need and who will own it with us.
A free 30-minute conversation to identify the problem, separate what we know from what needs checking, and agree a useful next step. You’ll receive a written recap, whether or not we work together.
Included when you choose to email me.