Back to blog
Guide

The Two Places You Type The Same Thing

A booking gets entered twice, a shift gets written in two places, a figure gets copied across. Double entry is invisible labour with a guaranteed failure mode, and most venues have several.

The booking goes in the system and in the notebook. The shift is on the rota and in the group chat. The takings are in one place and typed into another.

Nobody chose this. It accumulated, and it has a failure mode that is not a matter of if.

What double entry guarantees

The two will diverge. ⚠️ Not might — will. One gets updated and the other does not, and it happens the first busy night.

Nobody knows which is right. The worse half. With one record you have a fact; with two you have a question, and it gets answered by whoever is most confident.

The work is doubled and invisible. It never appears as a task. It is a few seconds, many times a day, forever.

People pick one and abandon the other. ⚠️ Rationally — and the abandoned one is still consulted by someone who does not know it is abandoned.

Where it comes from

A system that did not do something. So a second place was created for that one thing, and then grew.

Distrust of the new system. The old way is kept "just in case", ⚠️ and just in case becomes permanently.

Different people preferring different tools. Both are maintained, badly.

A handover that never finished. ⚠️ Frequently the answer — a migration that stopped halfway, years ago, and nobody declared it over.

Finding them

Ask what people write down twice. ⚠️ They will list them immediately — everyone knows, nobody has been asked.

Watch a shift start and a shift end. The duplication clusters there.

Look for the notebook. ⚠️ There is nearly always a notebook, and what is in it is the list of things the system does not do well enough.

Fixing one

Take the most-duplicated item first.

Ask why the second place exists. ⚠️ The answer is usually a real gap — the system is hard to use at that moment, or does not hold something. Fix that first, or the second place returns.

Then name the single source. Explicitly. Say which one is right when they disagree.

Then remove the other. ⚠️ Actually remove it. Leaving it available means it continues to be used, and you now have three states rather than two.

Watch for two weeks. If it comes back, the gap was not fixed.

The one worth keeping

Not all duplication is waste.

A deliberate backup for something critical is fine — provided it is stated as a backup, not treated as a second source of truth.

⚠️ The test: when they disagree, does everyone know which one wins? If yes, it is a backup. If people have to think about it, it is double entry.

Three to hold

Items entered in more than one place. ⚠️ Ask three people; take the union.

Disagreements found per month. Each one is evidence, and each one cost somebody time to resolve.

Second places removed per year. If zero, the list is growing — every new tool adds one unless something is retired.

Where the record has to sit

The reason a second place exists is nearly always that the first one is hard to reach at the moment the information appears. If the record cannot be updated where the work happens, someone will write it somewhere they can — and they are right to.

tasteck keeps bookings, shifts and takings on the screens staff already use during a shift, so the record is reachable where the information arrives.

Nobody decided to keep two. One of them was added for a reason that may have been fixed years ago, and nobody has been able to say so.

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days