Measure active handling time separately from waiting time

Where the extra work starts

Separate handling from waiting so you buy or build around the time you can actually reduce.

Invoice rekeying is a bounded task you can test today. Use the same invoices to compare your manual method with ParseMill, including source checks, corrections and export. The monthly plan costs $49 USD for 500 PDF processing pages and one user; judge it against the work it actually removes for you.

Define the start and finish of the task before measuring. For example, start at the first inspection of a submission and finish when the required administrative review is recorded. Retain receipt time separately if you also want total turnaround.

A practical way to get it right

Give every case a reference and record each active touch with start, stop, person and purpose. Pause the effort clock while waiting for a reply or doing unrelated work. Record waiting intervals by their cause without adding them to handling minutes.

Sum active touches across staff for each case. Two people working for ten minutes each contribute twenty person-minutes, even if the elapsed interval is only ten minutes. Do not double-count the same person's overlapping timer entries; resolve overlaps before totaling.

For a bounded diary, record all cases selected by the stated method, including those still open at the cutoff. Report their effort so far and incomplete elapsed duration separately. Use full dates and times when intervals cross midnight, and keep the time zone consistent.

Microsoft: Calculate the difference between two times demonstrates elapsed-minute arithmetic. With full datetime values in A2 and B2, =(B2-A2)*1440 computes one interval; classification still determines whether it is active work.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

The five completed synthetic cases total 55 active minutes, eight queue-wait hours and 84 client-wait hours. Mean active effort is 55 divided by five, or 11 minutes. The waiting totals describe accumulated case-hours, not staff capacity. Copy the table and retain the underlying touch log so the summary can be checked.

Catch the cases that create rework

Do not infer active effort from a task's creation and completion timestamps. Those timestamps can include nights, weekends and waiting. If a timer was left running, mark the observation uncertain and reconstruct it only from reliable evidence; do not silently replace it with a convenient average.

If multiple waiting reasons overlap, choose a defined primary reason or record overlapping intervals explicitly. Adding all labels as separate durations would exaggerate turnaround.

Microsoft: Excel functions by category describes SUMIFS and COUNTIFS. Use case and activity criteria to total the relevant touches rather than summing every recorded interval.

Decide whether the change is worth keeping

Recalculate two cases from their touches and confirm that the summary excludes waiting. Then choose the improvement target: fewer active checks, a shorter internal queue or clearer client requests. Use measured active minutes in the capacity calculator only after checking that its task definition matches your diary. Faster turnaround alone does not establish that staff hours were released.

The workflow audit checklist can help record the observed friction before considering a change.