productivity

11 Manual Data Entry Statistics for 2026

this+that team
11 Manual Data Entry Statistics for 2026

What the research says about the hours spent moving information from one place to another

Nobody was hired to retype things. But somewhere in most working weeks there is a stretch spent copying a name from an email into a CRM, a date from a message into a calendar, a decision from a thread into a document. It rarely appears on anyone’s job description and it rarely shows up in a plan. The statistics below try to size it. Workflows in this+that exist to remove that stretch: the message arrives, and what somebody would have retyped is already where it needed to go.

Key Takeaways

How Much of the Week Goes to It

1. 60% of time goes to “work about work”

Asana’s Anatomy of Work Index puts 60% of knowledge-worker time into coordination rather than production: chasing updates, sitting in unnecessary meetings, switching between tools, and moving information between them.

2. Only 27% of time goes to skilled work

The Anatomy of Work Index’s US findings put 27% of time on the skilled work someone was actually hired to do, and 12% on strategy. The thing you are paying for is the smallest slice.

3. More than 40% of workers lose a quarter of the week to repetitive tasks

Smartsheet’s research found over 40% of workers spending at least a quarter of the working week on manual, repetitive tasks. Email, data collection and data entry were the three largest categories.

4. Nearly 20% of the week goes to finding information

The McKinsey Global Institute puts nearly 20 percent of the workweek into “looking for internal information or tracking down colleagues,” which covers finding information rather than retyping it. Worth pairing with the numbers above because the two are the same loop: information is hard to find partly because it was never captured properly in the first place.

What Workers Say About It

5. 83% say too much of their time goes to work that could be automated

83% of knowledge workers report spending too much time on manual data entry they believe could be automated. Rare near-consensus, and it matters because the people saying it are the ones who would know.

6. Reps spend 70% of their time not selling

Salesforce’s State of Sales, Sixth Edition found reps selling just 30% of the time, leaving 70% for everything else. Their workweek breakdown puts 9% into manually entering customer and sales information and another 9% into administrative tasks. Admin, internal meetings and manual entry take the rest.

7. Estimates put annual data-entry losses in the hundreds of hours per rep

One widely repeated figure is 546 hours a year, about 27% of productive time, spent on data entry and chasing inaccurate records. Treat it as an estimate rather than a measurement, but even heavily discounted it describes weeks per person per year.

What Automation Gives Back

8. Broader automation estimates reach 15 to 20 hours a week

More expansive analyses, covering a full set of repetitive tasks rather than data entry alone, put recoverable time at 15 to 20 hours per employee per week. This is a vendor estimate of a best case and should be read as a ceiling, not a forecast.

9. Email is consistently the largest single category

Across the studies above, email is named more often than any other task as the largest consumer of repetitive time. Smartsheet lists email, data collection and data entry as the three biggest categories, in that order. Not writing it, but processing it: reading, sorting, extracting what matters and moving that somewhere else.

Why It Persists

10. The work is invisible in every plan

None of this appears in a project plan, a job description or a sprint. It is the connective tissue between systems that do not talk, and it is absorbed by whoever is holding the information at the time. Work nobody schedules is work nobody optimizes.

11. The payoff is delayed and the cost is immediate

Entering a record takes thirty seconds now and pays off in six months, if at all. That trade loses to whatever is urgent, every time, which is why data entry is both universally disliked and reliably skipped, and why the systems that depend on it are reliably incomplete.

The Pattern Underneath

Read together, the numbers describe a category of work with three properties: it is large, it is disliked by the people doing it, and it is structurally invisible. Those three combine badly. Large and visible work gets optimized. Large and invisible work gets absorbed.

The usual response is to buy a system that makes entering data faster. That helps at the margin and leaves the shape intact, because the underlying problem is not typing speed. It is that the information already exists, in a message somebody sent, and a person is being asked to transcribe it into a second place.

Which is the argument for reading the message stream directly. When a supplier confirms a delivery date, the date exists. When a customer gives a new phone number, the number exists. Nothing needs entering, only routing. That is what workflows do here, and it is the same bet behind contacts that build themselves: capture as a byproduct of communication rather than as a separate task.

How We Sourced This

Asana’s Anatomy of Work Index and Salesforce’s State of Sales are the two pieces of primary research here, both large-sample industry surveys, and they carry most of the weight.

The Smartsheet survey figures are also primary. The automation-recovery numbers, the 546-hour estimate and the 15-to-20-hour ceiling come from vendors selling automation and should be read as interested estimates. We have linked the best available source in each case and said which is which. Ranges are reported as ranges.