Somewhere in your business, a person is reading something on one screen and typing it into another. It might be a customer's address from an email into a CRM. It might be quantities from a supplier's PDF into an order system. It might be yesterday's figures from one report into a spreadsheet.
It never appears in a budget. It is one of the most expensive things a business does.
Why it is worth taking seriously
It is pure loss. Most work in a business produces something — a decision, a product, a relationship. Re-typing data produces nothing that did not already exist. It is the clearest example of effort with no output.
It introduces errors at a known rate. Any manual transcription has an error rate. It is small per field and large in aggregate, and the errors are the expensive kind: a transposed digit in a quantity, a wrong email address, a date entered in the wrong format. These do not fail loudly. They fail three weeks later, in front of a customer.
It scales linearly with growth. Doubling your order volume doubles the re-typing. Every other part of the business gets some efficiency from scale; this part does not. It is a direct tax on growth, and it is usually the reason a business "needs another admin" at a certain size.
It creates disagreement between systems. Two copies entered by hand will diverge. Once they diverge, nobody knows which is right, and you inherit the scattered information problem on top of the entry cost.
Sizing it
The estimate is straightforward, and it is worth doing properly because the result usually changes the conversation.
Pick one instance. Count the fields being re-entered. Time one occurrence honestly, including finding the source and switching windows — it is generally longer than people assume, because the switching is not counted. Multiply by frequency per week, then by fifty, then by the number of people who do it.
A four-minute task done twenty times a day by two people is roughly six hundred and sixty hours a year. That is a third of a full-time role, spent producing nothing.
Then add the error cost. If one in fifty entries contains a mistake, and a mistake costs an hour to discover and fix plus some customer goodwill, that is a second, larger number sitting underneath the first.
Where it hides
The obvious cases are visible. These are the ones that get missed:
- Copying between two tabs of the same spreadsheet, or between a spreadsheet and a system.
- Re-entering into a portal. Customer or supplier portals are a classic. A person enters the same order into your system and into the customer's system.
- Reformatting. Downloading a report and reshaping it by hand every month is re-entry with extra steps.
- Reading a PDF a machine generated. If a supplier sends a computer-generated PDF and a person types its contents into your system, information that was structured has been deliberately destroyed and manually reconstructed.
- Asking a customer for information you already have. The version customers experience. Filling in a form, then repeating it on the phone.
- Re-keying handwritten notes. Field staff write on paper, office staff type it up. Extremely common and usually the largest single instance in a service business.
Fixing it, in order of preference
1. Do not collect it twice. The cheapest fix is often to stop asking. If the information is already in a system, the second form should look it up rather than request it.
2. Connect the systems. Where two systems each need the data, they should exchange it directly. This is the standard integration case and is usually less work than people expect for common business software.
3. Import instead of type. If a connection is not available, a file import beats manual entry. A spreadsheet template that the supplier or customer fills in, imported once, removes the per-record cost.
4. Extract rather than read. Where the source is unstructured — a PDF, an email, a photograph of a job sheet — extraction with a confirmation step is a good fit, and one of the clearest cases where AI genuinely saves time rather than creating it. The person checks six fields against the source instead of finding and typing them.
5. Capture it once at the source. For handwritten field notes, the real fix is usually giving field staff a way to enter it directly, on a phone, at the job. This is a bigger change and often meets resistance; it is also the only fix that removes the entire second step rather than speeding it up.
Two cautions
Do not automate a form nobody should be filling in. Before connecting two systems, ask whether the destination record is used for anything. A surprising amount of duplicate entry feeds a report nobody reads.
Do not remove the human's eyes without asking what they were catching. Sometimes the person re-typing is also, incidentally, the only quality check in the process — noticing that the address looks wrong or the quantity is implausible. If you remove them, put a validation rule where their judgement was.
Duplicate entry audit
- Listed every point where a person reads from one screen and types into another
- Timed one real occurrence including window switching and finding the source
- Calculated annual hours: duration x frequency x people x 50
- Estimated the error rate and what a typical error costs to fix
- Checked whether the destination data is actually used by anyone
- Identified what the person was implicitly validating while typing
- Ranked fixes: stop collecting, connect, import, extract, capture at source
This is unglamorous work with an unusually reliable return. It requires no strategy, no vision, and no new category of software — just someone counting the places where the business pays a person to move information from one box to another.