How to Stop Staff Re-keying Data Between Systems

Why re-keying persists

Most organisations add systems one at a time: an HR platform, then payroll, then an IT service desk. Each is bought to solve one problem, and the gaps between them are filled by people copying data from one screen to another. This is often called swivel-chair work. It survives because each hand-off looks small, but across a team it adds up to hours a week, and every manual copy is a chance to introduce an error that surfaces later in payroll, billing or a report.

Step 1: Find every double entry

• Ask the people who do the work which fields they type into more than one system. They know; managers usually underestimate it.
• For each hand-off, note the source system, the destination, the trigger (a new hire, an invoice, a closed deal), the monthly volume and the minutes per item.
• Note the errors: duplicates, mismatched names, wrong cost centres. Rework often costs more than the original typing.
• Rank the hand-offs by hours per month and by the cost of a mistake.

Step 2: Choose the lightest fix that works

Step 3: Fix one hand-off and prove it

• Pick the top-ranked hand-off and agree the measure: hours per month, items touched by hand and error rate.
• Decide which system is the source of truth for each field, so the integration never overwrites good data with bad.
• Build the fix with a review queue for anything the automation is unsure about, rather than letting it guess.
• Run it alongside the manual process for a few weeks, compare the results, then switch over.
• Move to the next hand-off. Each one gets cheaper as the connections already built are reused.

Mistakes to avoid

• Replacing systems to remove re-keying. A new all-in-one platform is a much bigger project than connecting the ones you have.
• Automating a hand-off that should not exist. Sometimes the second system does not need the data at all.
• Syncing without ownership. If nobody owns the integration, it breaks quietly when one system changes and people go back to typing.

Frequently Asked Questions

What is swivel-chair work?

It is the manual work of reading information in one system and typing it into another, named after the image of someone turning between two screens. It is a symptom of systems that are not integrated.

Do we need an integration platform to stop re-keying?

Not always. Native connectors handle many common pairs. An integration platform earns its cost when you have many hand-offs, need error handling and monitoring, or have to connect systems without native connectors.

When is an AI agent better than an integration?

When the input is unstructured, such as an email, a PDF or a scanned form, and someone has to interpret it before entering it. Integrations move structured data reliably; agents handle the reading and judgement, and should hand uncertain cases to a person.