A case can contain four hours of work and still take six weeks to finish. Both numbers are true. They describe different operating problems.
Working time is the hands-on effort. Waiting time is everything that happens between arrival and delivery. A team can reduce one without moving the other, so each needs its own measure and its own plan.
Where elapsed time goes
Waiting rarely appears in a cost report. It sits between activities: behind a missing document, in an external inbox, at a handoff, or in a review queue. Nobody looks idle. The person waiting for the result still experiences every day.
- External records. Another organization holds the evidence and works to its own schedule.
- Repeat requests. Each new request to a client creates another round trip.
- Mixed queues. Difficult cases and routine cases block each other when they share one path.
- Batched review. Grouping senior review may save reviewer time while adding days to delivery.
- Intake and completeness
- Obtaining the source record
- Verification with the issuer
- Analysis and drafting
- Senior review and release
- Questions, corrections, outcome
A useful improvement depends on the goal
Cutting an hour of expert work from a four-hour case creates real capacity. If the case still waits a month for an outside response, the client may see no change in turnaround. The improvement still matters, but it should be described accurately.
The reverse is also possible. Better intake, earlier document requests, and clearer queue rules can shorten delivery without changing hands-on effort at all. That can be valuable even when unit cost stays flat.
Measure the file
Start with stage timestamps. Record when a case enters and leaves each stage. Then sample hands-on effort separately. This shows where time passes and where staff attention is used.
Keep the measurement attached to the case rather than the individual. Experienced people often receive the hardest work, so personal speed is a poor quality measure. The operating question is where cases stop and what they are waiting for.
Cost follows working time. Experience follows elapsed time. A good operating plan pays attention to both.
Once the two measures are visible, priorities become easier to defend. The team can decide whether it needs more capacity, shorter turnaround, fewer handoffs, or a better exception path. Those are different goals, and they lead to different changes.