In brief

Double handling often grows from sensible quick fixes: a separate list, an extra spreadsheet, or a workaround that keeps work moving. Repeated every day, those steps can waste time, introduce errors and make information harder to trust. The starting point is to understand why the extra handling exists. Then reduce what is unnecessary, reuse reliable information and automate where it helps — without replacing tools that still work well.

Entering the same information more than once wastes time. It also increases the opportunity for errors. Every time information is copied, retyped or transferred manually from one place to another, something can be missed, changed or entered incorrectly.

Double handling rarely starts as a deliberate process. It usually develops gradually, through a series of small decisions that make sense at the time — quick fixes, shortcuts, time savers or ways of bypassing a bottleneck. The problem appears when those small steps become the normal way the business works.

A few minutes here and there may not seem like much. But when the same information is repeatedly entered, searched for, checked and corrected across many jobs, those minutes add up.

So do the opportunities for mistakes.

How double handling creeps into everyday work

A spreadsheet might be created to solve one particular problem. Later, someone needs additional information, so another column is added. Another person needs the information presented differently and creates a second spreadsheet.

A customer starts sending details by email. A job sheet is introduced because it makes the work easier for the people doing it. Perhaps another piece of software is introduced for accounts, scheduling or reporting.

Each change can be perfectly sensible.

The difficulty begins when people have to keep moving the same information between these places by copying, retyping or reworking it.

Customer details from an email are entered into a spreadsheet. Some of those details are copied onto a job sheet. When the work is finished, another spreadsheet or system is updated. The same information may then be entered again for invoicing or reporting.

Before long, people are not just doing the work. They are also spending time moving information from one place to another so that everyone else can do theirs.

Each individual step may only take a few minutes. The cost comes from repeating those same few minutes every day, across many jobs, by several people.

Signs double handling has become part of the process

The warning signs are often familiar:

  • Several versions of the same information are maintained, and staff have to reconcile one list against another.
  • Details are copied between systems, or the same information has to be searched for and extracted repeatedly.
  • Reports are assembled manually from several sources, or information is reworked before somebody else can use it.
  • A change in one place has to be remembered and repeated elsewhere.
  • Important information lives in someone's inbox, personal folder or private spreadsheet.
  • A formula, process or sequence of updates is understood by only one person.

None of these things necessarily looks serious on its own. But some can also become constraints. Work may have to wait until the right file can be found, the right person is available, or someone with the necessary knowledge can take the next step.

When access to information or knowledge holds up the work, it becomes a bottleneck in its own right. The difficulty is that both the repeated handling and the waiting can gradually become accepted parts of everyday work.

The cost is more than the time spent entering data

If the same information exists in several places, those copies can start to differ. A customer changes an address, a job date moves, or a quantity is corrected in one place but not another.

Someone then has to work out which version is right. That can lead to more checking, more questions and more interruptions:

“Has this been updated?” “Which spreadsheet should I be looking at?”

“Does this match what was sent to the customer?” “Has accounts got the new information?”

Over time, this can affect confidence in the information itself. If people are never quite sure whether the data is current, complete or accurate, they begin to treat it cautiously. They double-check it, compare it with another source, ask someone who might know, or keep their own copy for reassurance.

Even when the information is correct, the lack of trust still creates work.

Information needs to be current, complete and accurate enough for the work it supports. People also need good reason to feel comfortable relying on it.

Double handling can also create delays. The next person may not be able to continue until somebody else updates a spreadsheet, sends a file, or transfers information from one system to another.

Scattered information also makes it harder to see what is actually happening. If details about the same customer, job or project are held in different places, getting a clear picture may require somebody to bring those pieces together first.

People can also become responsible for remembering the process itself — update this spreadsheet, then change that document, then tell someone else that something has changed.

A process can appear to work well simply because the people using it have become very good at working around its weaknesses.

The original few minutes of double handling can therefore create another layer of work: searching, checking, correcting and waiting before people feel able to take the next step.

Why we create workarounds around bottlenecks

A bottleneck is a point in the process that holds up the work that needs to follow.

Sometimes the reason is obvious. A person may be overloaded. Information may arrive too late. A system may not provide what is needed. Approval may depend on one person. Two systems may not share information properly.

When that happens, people look for a way to keep the work moving. They create a spreadsheet, keep a separate list, copy information into another system, send themselves reminders, or introduce an extra step.

In the short term, that can be exactly the right thing to do.

The difficulty comes when the workaround remains after the immediate problem has passed, or when more workarounds are added around it. The bottleneck may still exist, but now the business also has another process to maintain.

The workaround itself may introduce new problems. It may leave out information somebody else needs, depend on one person remembering what to do, create another version of the data, or add a step that has to be checked and maintained.

Over time, a temporary shortcut can become part of the normal workflow — and another place where information has to be entered, checked or remembered.

Alongside asking where information is being entered twice, it is worth asking:

“What problem were we trying to get around when we started doing it this way?”

“Is the workaround missing something or creating a problem of its own?”

Look at the work around the spreadsheet

The spreadsheet itself is often only part of the process. When the same information is being entered in several places, it can be tempting to blame the spreadsheet, the software, or even the people doing the work.

But the duplication is often a symptom rather than the real problem. Those extra steps may be meeting a genuine need or compensating for something the existing process does not provide.

So before replacing anything, look at the work happening around the spreadsheet — and between the other systems, documents and people involved.

Ask the people doing the work to show you what happens, including the extra steps they take when the usual process does not meet their needs.

Where does the information first come from, and who needs it?

Where is it entered or reworked again, and why?

What happens when something changes? Does the information genuinely need to exist in both places?

What would happen if this step disappeared tomorrow?

These questions help distinguish information that needs to be shared from handling that does not need to be repeated. They can also show where a workaround is compensating for a problem elsewhere.

That is why it is worth understanding the process before removing the workaround.

Removing double handling is not really about getting rid of spreadsheets. It is about understanding how information needs to move through the business, then finding where unnecessary handling can be reduced, simplified or avoided.

Capture information once, then reuse it

A useful starting point is to avoid re-entering information that already exists.

If customer, job, product or project details have already been captured, they should be reused wherever practical rather than typed again somewhere else.

That means being clear about which information is current, where changes should be made, and how those changes reach the people who need them.

The same information might be used to prepare a job sheet, update a status, create an invoice or produce a report.

The benefit is not just saving a few minutes of data entry. It can also reduce the number of separate copies that people have to keep consistent when something changes. If a customer updates an address, a job date moves, or a quantity changes, there should be less need for someone to remember every other place that also needs updating.

The aim is not to force everything into one system. It is to reduce unnecessary handling while preserving the parts of the process that genuinely serve a purpose.

This can also make everyday questions easier to answer. What work is waiting? What is overdue? Who is responsible for the next step? What happened with a particular customer or job? What still needs to be invoiced?

The answers should not depend on searching several places, finding the right spreadsheet, or asking the person who happens to know.

When information can be reused reliably, it becomes easier to keep it consistent, easier to see what is going on, and easier to remove some of the repetitive work surrounding it.

Automate the repetitive parts

Once information is being captured and reused more effectively, some of the repetitive work around it can often be reduced further.

A system might generate a document from information that already exists, update a job status, prepare a report, send a notification, or pass information to another system without somebody having to copy and paste it first.

The important point is not to automate for the sake of automation. A poor process does not necessarily become a good one just because it happens faster.

It is usually better to first understand where the duplication and unnecessary handling occur, then decide which parts can be done reliably by the system.

The aim is not to remove people from the process. It is to reduce the manual repetition without losing the useful result. That leaves people to deal with the work that needs judgement, experience, communication or decision-making.

And reducing repetitive work does not necessarily mean replacing the tools that are already doing their job well.

You may not need to replace every spreadsheet

Spreadsheets are still very useful tools. They are excellent for calculations, analysis, planning, modelling and one-off tasks. In many cases, a spreadsheet is exactly the right solution.

The spreadsheet itself is not necessarily the problem.

There is a difference between a spreadsheet being used by the business and a spreadsheet quietly running the business.

If several people depend on it, consider what is needed to keep it useful. Information may have to be copied in and out, different versions may need to be reconciled, or one person may have to remember how everything fits together.

Those are reasons to look more closely at the process, not automatically to replace the spreadsheet.

Sometimes the answer may be a better-designed spreadsheet. Sometimes it may be connecting existing systems. Sometimes a small internal application or database may remove the repeated handling.

Man with pencil reading document

The goal is not to replace something simply because it is old, familiar or imperfect. The goal is to reduce unnecessary work and make the process easier to manage.

Start where the extra work begins

Improving the process does not have to mean redesigning everything at once.

Choose one everyday task where the same information is handled repeatedly. Follow it from the person who first records it to the people who need it next. Look for the copying, searching, checking and waiting — and ask what purpose each step serves.

Once you understand that part of the process, choose a useful change. Then check with the people involved that it has reduced the work rather than simply moved it somewhere else.

What matters is not how sophisticated the technology is. It is whether the change reduces unnecessary work and gives people information they can rely on.

Double handling rarely announces itself as a major problem. More often, it is a collection of small tasks that have gradually become normal.

Each one may only take a minute or two. The real cost appears when those minutes, searches, checks, corrections and interruptions are repeated every day.

So the useful question is not:

“How do we get rid of our spreadsheets?”

It is:

“Why are we doing this more than once?”