Nobody decides to do double data entry. It builds up one tool at a time: a spreadsheet to track contracts, a calendar for the crews, an invoicing program, then a list for reminders. Each addition made sense, but the same address ends up in five places, with no guarantee it is right in all of them. This guide offers a four-part method you can run with a pencil and a one-hour meeting, using a fictional example along the way.
It hides in everyday habits
Double entry rarely looks like a problem, because it looks like normal work. You notice it through its side effects. If any of the following sounds familiar, some information is probably being carried by hand between two tools.
- Someone keeps two windows open side by side and switches back and forth.
- You hear “which one is right?” about a file, a price or a phone number.
- The same typo shows up in several places, or a correction only makes it into one.
- Someone spends time every week or month “getting the lists to match”.
- A sheet printed in the morning is already out of date by noon.
- When the person who makes the copies is away, the other tools stop being current.
A fictional company in Greater Moncton has nine people. Marc, the coordinator (a fictional character), handles contract renewals every spring. He enters each client in the invoicing program, then in a seasonal contracts spreadsheet, then in the crew calendar. Every morning he prints a route sheet for each truck. In the fall, he also keeps a separate list for sending snow removal reminders.
The change-of-address test
To size up the problem without any software, run a thought experiment. Pick a real client and imagine they call to change just one detail: their address, their phone number or their contact person. Count every place where someone would have to update it, then ask how you would know if one was missed.
Do this with the people who actually handle that information. BDC recommends it for any process mapping: they are the ones who know what isn’t working. One sheet per piece of information is enough.
Information trail (one sheet per piece of information)
Information traced (e.g. property address): Where it first arrives (call, email, form, paper): Tool 1 where it is typed, by whom, when: Tool 2 where it is typed, by whom, when: Tool 3 and beyond: Who reads each copy, and what for: How you notice today that a copy is wrong: Last time a wrong copy caused a problem:
A property address lives in five places: invoicing, the contracts spreadsheet, the calendar, the route sheet and the reminder list. Nothing flags a missed copy. Last winter, a crew even showed up at the old address of a client who had moved, because only the invoicing program had been updated.
Give every piece of information a home
Before thinking about tools or connections, decide where each piece of information is the official version. That home is the only place where it gets created and changed. Other tools read it or receive it, but nobody types it again. This is an organizational choice before it is a technical one, and it often solves half the problem on its own.
| Information | Home (official version) | Who changes it | Who only reads it |
|---|---|---|---|
| Client contact details | Contracts spreadsheet | Marc | Invoicing, crews |
| Property address and notes | Contracts spreadsheet | Marc | Calendar, route sheets |
| Contract price | Invoicing program | Owner | Marc |
| Visit schedule | Crew calendar | Marc | Crew leads |
The Government of Canada made this principle one of its digital standards: collect data from users only once and reuse it wherever possible. What works for a federal department works for a nine-person business too: every extra entry is another chance for a mistake.
Five ways to remove a copy, from lightest to heaviest
Once the home is chosen, deal with each remaining copy on its own. Try the options in order, and only move to the next one if the previous one won’t work.
- Drop the copy: if nobody really reads that list or file, stop keeping it.
- Capture it at the start: a form filled in by the client means nobody has to retype it.
- Look it up instead of copying: a link, a filtered view or read-only access to the home often replaces a copied file.
- Import on a schedule: an export from the home, imported weekly into the other tool and checked by a person.
- Connect the tools: an automatic transfer from the home to the tool that needs it, in one direction only.
The reminder list goes away: a filtered view of the contracts spreadsheet (clients with snow removal) replaces it. Route sheets are produced from the calendar instead of being typed. New clients fill in a form that feeds the spreadsheet. Only the link between the spreadsheet and invoicing calls for an automatic connection, and Marc leaves it for last.
What a connection can break
Linking two tools removes a typing step, but it adds a mechanism you have to watch. A mistake that used to be fixed by hand now spreads on its own, and faster. Before you connect anything, look at these points.
- Direction: a one-way transfer from the home to the other tools is much easier to understand and fix than a two-way sync.
- Conflicts: if two people change the same detail in two tools, which one wins? Without a clear home, nobody knows.
- Duplicates: two clients with the same name, or one client entered twice, can be merged or duplicated by mistake.
- Silence: a connection that stops working often tells no one. Decide who gets the alert and what they do next.
- Access: the account the connection uses should only see the information it needs to move.
Measure before and after
To know whether the change is worth it, track two things for a month before and a month after: time spent copying and reconciling lists, and the number of mismatches found between copies. The second number often matters more than the first, because sooner or later a mismatch reaches a client.
Before: about 3 hours a week of typing and reconciling during renewal season, and 11 mismatches found in a month. After the first three options: about 1 hour a week and 2 mismatches, both tied to invoicing, which is still typed by hand. What is left justifies the planned connection, and Marc now knows exactly what it needs to transfer.
Before you connect two tools
- The information has a written home that the whole team knows.
- The lighter options (drop, capture at the start, look up, import) were tried or ruled out for a specific reason.
- The transfer runs one way only, unless there is a documented reason.
- The home has been cleaned up: no known duplicates, no key fields left blank.
- One person gets the alert when the transfer fails and knows what to do.
- The connection’s account can only reach the information it needs.
- You can go back to typing by hand for a week if the connection goes down.
Limits and mistakes to avoid
- The example and its numbers are fictional and illustrative: real savings depend on your volume and your tools.
- Some tools allow neither export nor connection; then you have to choose between keeping a monitored manual copy and switching tools.
- A backup copy isn’t double entry: this guide is about copies typed by hand to get work done.
- This guide isn’t legal advice on your obligations regarding personal information.
Sources consulted
- Government of Canada, “Government of Canada Digital Standards” ↗The principle of collecting data from users only once and reusing it wherever possible (the “Be good data stewards” standard).checked on November 9, 2026
- Office of the Privacy Commissioner of Canada, “PIPEDA Fair Information Principle 6: Accuracy” ↗Keeping personal information as accurate, complete and up to date as necessary, and listing where it is stored.checked on November 9, 2026
- BDC, “What is process mapping?” ↗Documenting who does what, when and how, and involving the people who do the work every day.checked on November 9, 2026
Written with the help of AI tools, then checked and edited by Over U. Examples are fictional. This guide is not legal advice.