What Is Your Team Still Copying, Chasing or Remembering Manually?

A customer fills in a form. Someone copies the details into a spreadsheet. Another person enters them into the CRM. A colleague sends a message asking whether anyone has replied. Later, somebody remembers that a follow-up was due.

None of these actions looks especially serious on its own. They look like work.

But when a team spends each day copying information, chasing updates and remembering what should happen next, people may be doing more than their actual jobs. They may also be holding a disconnected process together.

The useful question is not whether every manual task should disappear. It is which tasks still need human judgement and which exist only because information, ownership and next steps are not properly connected.

Manual does not automatically mean inefficient

Some work should remain manual. A sensitive customer conversation, an unusual request, a quality check or a decision involving judgement should not be pushed through an automated process simply because technology can do something with it.

Manual work becomes more revealing when it is repetitive, predictable and necessary only to move information from one place to another.

If a person has to copy the same name, email address and requirements from a form into a spreadsheet and then into a CRM, the value is not in the copying. The person is acting as the connection between systems that do not exchange information.

The task may take only a few minutes. Repeated across enquiries, customers and team members, it becomes part of the working day and another opportunity for information to be missed, duplicated or changed.

Copying is usually an information problem

Copying often appears wherever the same information is needed in several places but has no reliable route between them.

A team might copy an enquiry from a website email into a spreadsheet. Customer details may then be entered into accounting software, a CRM or a project board. Notes from a call may be copied into an email so somebody else knows what happened.

The person doing this is not necessarily working badly. They may have created a practical workaround that keeps the business moving.

The risk is that each copy becomes another version. A phone number is corrected in one place but not another. A requirement changes during a call, but the original spreadsheet remains untouched. Two colleagues update separate records and both believe theirs is current.

Repeated copying is therefore not just an administrative inconvenience. It can be a sign that the business has not decided where the reliable customer or operational record lives.

Chasing is usually a visibility problem

Chasing happens when the person waiting cannot see the status of the work or who owns the next step.

Has the quote been sent? Did the customer provide the missing document? Has somebody called the new lead? Is the work ready to invoice? Did anyone respond to yesterday's complaint?

When the answer is not visible, people create visibility through messages, emails, meetings and reminders. The chase becomes the system.

UK workplace research reported in 2025 found that employees spent an average of nine hours a week locating information. It also reported that 53% believed asking a colleague or arranging a meeting was the only way to obtain what they needed, while 55% experienced delays because they were waiting for information from others.

Those figures came from a broad employee survey rather than a study of small businesses alone, so they should not be treated as a measurement of every SME. They do, however, reflect a familiar pattern: when progress is not visible, work becomes dependent on interruption.

A colleague may answer quickly, but the business has still used two people's attention to establish one piece of status information.

Remembering is usually a process problem

Remembering is the quietest of the three because it often looks like experience.

One person knows that new enquiries should be followed up after two days. Someone else remembers which documents a customer still needs to send. A long-serving employee knows that a particular task must happen before the monthly invoice run.

That knowledge is valuable. The risk appears when memory is the only place the process exists.

People take annual leave. Busy days interrupt routines. Team members change roles or leave. A task without a visible trigger, owner or due date can disappear without anybody deliberately deciding to ignore it.

A business can therefore look organised while depending heavily on a few people carrying its operating instructions in their heads.

Why these tasks accumulate without anyone noticing

Disconnected work rarely arrives as one large failure. It develops through small, reasonable decisions.

A spreadsheet is created because the current system does not show a useful view. A WhatsApp group is started because it is quicker than finding the information elsewhere. A team member keeps a personal checklist because the official process misses important details. A manager asks for a weekly update because progress is difficult to see.

Each workaround solves something in the moment. Over time, the workaround becomes normal work.

This is why asking people whether a process is broken does not always reveal much. They may not describe it as broken. They have learned how to make it work.

A more useful question is: what do people have to do manually to stop this work from being lost, delayed or misunderstood?

A simple way to examine one process

Choose one piece of work that happens regularly. It could be responding to a new enquiry, preparing a quote, onboarding a customer, collecting documents, completing a job or raising an invoice.

Follow it from beginning to end and record three things:

1. What is copied? Note every detail that is retyped, pasted, downloaded, uploaded or recorded again.
2. What is chased? Note every message, email, call or meeting used to ask for an update, missing information or confirmation.
3. What must be remembered? Note every follow-up, deadline, exception or next action that depends on somebody recalling it.

Do not tidy the process while you are mapping it. Include the unofficial steps, personal spreadsheets, paper notes and quick messages. They often show where the formal process has stopped supporting the real work.

Then ask what would happen if the person who normally holds it together was unavailable for a week.

What should be connected first?

The answer is not necessarily to automate the longest list of tasks.

Start with the point where disconnection creates the greatest consequence. That may be a customer waiting without an acknowledgement, a team member working from outdated information, an invoice not raised, a document not collected or a follow-up that can quietly disappear.

A useful first improvement might be:

• one agreed place for the current customer record;
• a form that sends information directly to the right system;
• a clearly assigned owner and next action;
• a shared status that removes the need to ask for updates;
• a reminder triggered by a real event rather than personal memory;
• an automated handover that preserves the information already collected.

The right technology may be a CRM, a workflow, an integration, automation or AI. It may also be a clearer process and better use of a system the business already owns.

Automation should remove repetition, not judgement

A connected process does not remove people from the work. It stops using people as the cable between disconnected tools.

A system can capture an enquiry, create a record, assign a task and send an acknowledgement. A person can then focus on understanding the customer's situation, deciding what is appropriate and handling anything unusual.

AI may help summarise notes, prepare a response or identify missing information. It should not be introduced simply because a manual step exists. The business still needs to decide what information the AI can use, what it is allowed to do, when a person checks the output and when the work must be handed over.

Good automation makes responsibility clearer. Poor automation can move confusion faster.

The manual work is giving you useful evidence

Copying, chasing and remembering are frustrating, but they are also clues.

Copying shows where information stops moving. Chasing shows where progress and ownership cannot be seen. Remembering shows where the process has not been made visible or dependable.

The people doing these tasks are often the best source of insight because they know exactly where the official process needs help. The aim is not to criticise their workarounds. It is to understand why those workarounds became necessary.

When you can see that clearly, technology becomes easier to judge. You can connect the part that needs connecting without replacing the human work that genuinely matters.

What is your team quietly holding together?

Look at one ordinary working day. Notice what is copied more than once, what has to be chased and what somebody is expected to remember.

Those small actions may reveal more about the business than a list of software features ever could.

The Davina Connect Business Review helps you step back and see how people, information, systems and processes are working together now. Your Business Insights Snapshot identifies what appears connected, where friction may be forming and which areas deserve a closer look.

No recommendation begins with a tool. It begins with understanding the business.