The Two Places You Type The Same Thing

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.

Two copies do not stay equal

Day one   identical
Week two   one of them is more current, and nobody agrees which
Month three  they are used for different questions, and both are wrong

⚠️ Divergence is not a risk, it is a certainty. The only variable is how long it takes and who finds out first.

Which copy wins an argument

⇒ ⚠️ Usually the one that is easier to open, not the one that is correct. Accessibility beats accuracy every time there is a guest waiting.

---

Where the second one always comes from

Someone needed a view the system did not offer
Someone needed it faster than the system allowed
Someone was never given access to the first one

⚠️ All three are reasonable. The duplicate is not laziness — it is a sign that the first record failed somebody, and it will keep coming back until that failure is fixed.

Which is why deleting it does not work

⇒ ⚠️ Delete the spreadsheet and it reappears within a fortnight, under a different name, on someone's phone.

---

Finding them without an audit

Ask "where do you look when you need X?"  the answers will differ
Watch a handover           you will see the second copy

⚠️ Do not ask whether anyone keeps their own list. Ask what they open first — the question is not accusatory and it gets a true answer.

---

Fixing one, in order

One Why does the second one exist  what does it do that the first cannot
Two Make the first one do that   or accept the second one deliberately
Three Then, and only then, remove it

⚠️ Skipping step one is why most of these fixes fail. Removing the symptom leaves the reason intact, and the reason is what generates copies.

When the first one cannot be fixed

⇒ ⚠️ Name the second one the record for that one purpose, in writing. A deliberate second copy with a stated scope is safe; an undeclared one is not.

---

Which duplicates are worth keeping

A working note that is thrown away nightly  harmless
A view that is generated, not typed     harmless
Anything re-typed by hand          not harmless

⚠️ The test is whether a human retypes it. Generated copies inherit corrections; typed copies inherit typing.

The one to fix first

⇒ ⚠️ Whichever one a guest can be told a wrong answer from. Internal disagreement is expensive; telling a guest the wrong price is worse, and it is always the hand-typed copy that does it.

---

---

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.

---

Read next

• The Thing You Stopped Doing
• The Change They Think They Made
• The Second Time Something Breaks
• The Setting Nobody Remembers Changing
• The Thing Somebody Said Once
• The Night The System Was Down