Copy, paste, repeat

Move the sliders to match a normal week. Then flip the switch.

31
Working days a year
£5,060
A year

31 working days a year of copy and paste: all of January and most of February. Karen would like them back.

Rough sums. 46 working weeks of 7.5 hour days. "Typed once" keeps three-eighths of the time, as on the agricultural services job (eight hours a week of retyping became three). Nobody misses retyping.

How this works

Count the things that get typed in one place and then typed again somewhere else: an order into the order sheet and again into the accounts, a new customer into the inbox and again into the CRM. Each one is counted once, as one retype.

Hours a year = things a week × minutes each ÷ 60 × 46 working weeks

Days are those hours over a 7.5 hour day, and the cost is those hours at the hourly cost you set (wages plus what goes on top, so never under the minimum wage). Under two days it shows hours; past a whole working year, it counts in working years.

"Typed once" keeps three-eighths of the time, because that is what the real job kept: eight hours a week of office retyping became three, with the unusual records left in a check queue. The rest is what comes back. Under about £500 a year back, it says so: not worth a Build. The year is drawn as 230 working days, about 19 a month, and the lost days fill from January onwards so they show as one block.

It leaves out the cost of the mistakes retyping makes (the £18,400 that became £18,040), which is often the bigger bill.

We did one like it

The work · Build

Written in the field. Typed again in the office.

A family agricultural services business typed paper records, photos and messages into the office systems. A seven-week Build put the records on the field team's phones, working without signal, straight into the office schedule.

8 hours a week to 3

Read the job
More on operations

Run on spreadsheets nobody else understands?