Guides

How to measure business process time before automating it

A copyable spreadsheet template to estimate the hours, variability and operating cost of a recurring workflow.

Updated on 4 min
A person records timings in a notebook beside a stopwatch and a laptop with a spreadsheet open.

What does it cost the team to move incoming requests from email into the CRM each month? To measure the time a business process takes, pick one workflow, count how often it runs and track the minutes people actively spend on it. That gives you a starting point for deciding where to make a change.

Define where the process starts and ends

Choose something the team already does and give it an observable start and finish. For example, the workflow starts when a request arrives in a shared inbox and ends when its CRM record is complete and assigned. In between, someone reads the request, searches for an existing record, fills in the fields and checks the result.

Write down who handles each step, where they get the information and where they record it. If team members follow different paths, ask a colleague to walk through a real case with you. The LuCz guide to writing a business procedure includes an example of documenting and testing a task this way.

Record active work, waiting time and exceptions

Choose an observation period that reflects normal work. If the volume changes at month-end, track that period separately. For each run, record the date, case type, step, active minutes, waiting minutes and any exception. Keep the totals separate. Active work tells you what the team spends on the process. Waiting time helps explain why a request stays open.

  • Count the time spent verifying data, correcting errors or picking a request back up. If two people work on it, add both people’s active minutes.
  • Record cases that follow a different path as exceptions. For example, a duplicate may need checking or a required field may be missing.
  • If a measurement is missing, leave it blank and mark it for follow-up. Enter zero when you have verified that the step took no time.

Calculate the hours for the period

For each case type, multiply the number of runs in the period by the average active minutes per run, then divide by 60. Add the hours for all groups. If you timed every run, you can add all the active minutes directly and divide by 60. If you use a sample to estimate the average, note how many runs you timed.

To estimate a range, repeat the calculation using the shortest and longest times recorded for each group. The endpoints describe two scenarios based on your observations. If you measured only a few cases or the periods vary substantially, update the range before using it to make a decision.

A worked example for the email-to-CRM workflow

Hypothetical example. A team receives 40 requests in a week. Thirty follow the standard route and take 7 minutes of active work on average. The other 10 need an extra check and take 14 minutes on average. The workload is 30 × 7 + 10 × 14 = 350 minutes, or 5 hours and 50 minutes.

Illustrative example for one week
Case typeRunsMinimum minutesAverage minutesMaximum minutesEstimated active minutes
Standard30678210
Exception10121416140
Total40350

Using the observed extremes, you get (30 × 6 + 10 × 12) / 60 = 5 hours and (30 × 8 + 10 × 16) / 60 = 6 hours and 40 minutes. If you know the hourly cost, multiply it by the estimated hours. At €30 an hour, this example comes to €175 in operating cost for the week. To estimate savings, measure the checks, corrections and ongoing work after the change as well.

A template you can copy into your spreadsheet

Paste the block below into cell A1. If it goes into a single column, use your spreadsheet’s text-splitting tool and choose tabs as the separator. Enter one row per case type. Replace the example numbers with yours and copy the formulas into any additional rows. Enter formulas only once you have the relevant input measurements.

Case type	Runs	Minimum minutes	Average minutes	Maximum minutes	Estimated hours	Minimum hours	Maximum hours
Standard	30	6	7	8	=B2*D2/60	=B2*C2/60	=B2*E2/60
Exception	10	12	14	16	=B3*D3/60	=B3*C3/60	=B3*E3/60
Total	=B2+B3				=F2+F3	=G2+G3	=H2+H3

Choose a step for your first trial

Group the minutes from the same period by step. If copying information into the CRM takes 170 of the 350 minutes in the example, start by examining that step. If incomplete requests cause the longest delays, try clarifying the form fields first and measure again.

Decide how you will test each change. If you try pre-filling the CRM, check the values shown, who approves exceptions and what happens when a field is missing. Repeat your measurement across the same workflow, including standard cases and exceptions.

LuCz can help you test a specific workflow, connect the tools you already use and check where human review is still needed. See how we work on business integrations and automation.

Sources

Tags

#business processes#automation#time measurement

Written by

Matteo Lucrezio

Matteo Lucrezio

Startupper | Lead Software Engineer

Book 30 minutes with Matteo

Leave your contact details, then choose a day and time for a free 30-minute initial conversation. Any technical assessment and subsequent work are agreed separately.

How can we help?

Enter your contact details to continue to the calendar.

We use it to follow up on your request and manage the booking. This does not subscribe you to promotional messages.

We save your details immediately to handle your request. They also stay in this browser for 24 hours, so you do not have to type them again if you reload the page.

No suitable time or prefer to write? Email me at matteo.lucrezio@lucz.dev.