The Note That Was True When You Wrote It
A handover note, a whiteboard line or a pinned message is correct on the day it is written and wrong a week later. Nobody removes it, because removing it was never anybody's job. Here is how to stop old notes from giving instructions.
Somebody writes on the board: "Room 3 tap not working — use Room 4."
That evening, the tap is fixed. Nobody wipes the board.
⚠️ Three weeks later a new starter reads it and moves a booking out of Room 3. The note was never wrong. It stopped being right, and nothing in the note said when that would happen.
The short version
- Old notes do not look old. They look like current instructions
- The person who writes a note is almost never the person who removes it
- Adding a correction elsewhere leaves the original still giving orders
- Every note needs either an end date or an owner who kills it
- The most dangerous notes are the ones that were useful and accurate
Why a wrong note is easier than a stale one
| Kind of note | How it gets fixed |
|---|---|
| Obviously wrong | Somebody notices and corrects it |
| Vague | Somebody asks |
| Accurate, but out of date | Nobody questions it at all |
⚠️ Staleness is invisible. There is nothing about the writing that distinguishes a note written this morning from one written in spring.
One: how it actually happens
The failure is not carelessness. It is a gap between two jobs.
Writing the note somebody's job, in the moment
Removing the note nobody's job, ever
⇒ The note gets written because there is a reason to write it. It stays because there is never a moment that obviously calls for deleting it.
The specific trigger
The condition ends quietly
The person who wrote it is not on that night
The board is not read by anybody who knew the original problem
⚠️ The quieter the resolution, the longer the note survives. A dramatic fix gets talked about; a tap that just starts working again does not.
Two: the correction that does not correct
Here is the version that catches organised people.
You realise a note is out of date, so you write a new note saying so — in a different place.
The board still says "use Room 4"
The group chat says "Room 3 is fine now"
⚠️ The original is still there, still giving the instruction. Anybody who reads the board and not the chat follows the old note, and they are not being careless — they are reading the thing that was put there to be read.
The rule that fixes it
Correct the note where the note lives.
⇒ Adding the truth somewhere else is not a correction. It is a second source, and now you have two.
⚠️ We did this to ourselves recently. A written record of ours said a batch of billing items had not been touched. Hours later we dealt with them and wrote that up in a new document. Eleven days on, somebody read the first record, saw "not touched," and quite reasonably raised it as an open problem. Both documents were accurate. The first one was just older, and nothing on it said so.
Three: the three lifetimes
Every note is one of these, and it is worth deciding which as you write it.
Permanent a rule, a price, a procedure
Conditional lasts while a condition holds
Dated lasts until a specific day
⚠️ Most notes are conditional and get written as if permanent. That is the entire problem in one line.
Making the difference visible
Permanent goes in the manual, not on the board
Conditional "until the tap is fixed" - written on the note
Dated "remove after Sat 14th" - written on the note
⇒ A conditional note that names its condition can be checked by anybody. A conditional note that does not is permanent by accident.
Four: the board, the chat and the pinned message
Different surfaces rot at different speeds.
Whiteboard wiped often, so staleness is short
Printed sign survives for years
Pinned message survives until somebody unpins it, which is never
Group chat scrolls away, which is its own problem
⚠️ The pinned message is the worst of them, because pinning is an act of emphasis. A stale pinned message is a stale note that everybody has been told is important.
The monthly sweep
Once a month: read every pinned message and every printed sign.
For each: is this still true?
⇒ It takes ten minutes and it is the single highest-value piece of admin most venues never do.
Five: notes that outlive the person
A particular category deserves naming: instructions left by somebody who no longer works there.
"Ask [name] before discounting"
"[Name] handles the Thursday rota"
"Card machine problems - call [name]"
⚠️ These are worse than useless. They send somebody to a dead end and then leave them unsure what the real procedure is.
⇒ When somebody leaves, their name is a searchable thing. Search for it — in the notes, on the board, in the pinned messages, in the shared documents — and replace each one with the person who does it now.
⇒ On the related question of who is actually allowed to make a call: who can say stop.
Six: the handover note specifically
Handover notes are written under time pressure, read once, and never cleaned.
Written at the end of a shift, in a hurry
Read at the start of the next one
Then kept forever, in a book nobody opens
⚠️ A handover book is a log, not a set of standing instructions, and the difference stops being obvious after a few months of entries.
How to keep them separate
Handover book what happened, for the next shift only
Standing notes what to do, kept somewhere else, reviewed
⇒ If an item in the handover book needs to apply beyond tomorrow, it has to be promoted deliberately into the standing notes. Nothing should become permanent by being written down and forgotten.
Seven: dates make staleness visible
The cheapest single improvement is a date on everything.
Undated "Room 3 tap not working - use Room 4"
Dated "14 Mar - Room 3 tap not working - use Room 4"
⚠️ A reader cannot judge a note without knowing when it was written. With the date, a new starter in April can at least ask. Without it, they simply comply.
What a date does not do
It does not make the note current
It does not remove it
It only gives the reader a reason to check
⇒ Which is enough, most of the time. The failure mode is unquestioning compliance, and a date is what prompts the question.
Eight: the same shape in your system
Software has its own version, and it is harder to see because there is no physical board.
A note on a guest record from two years ago
A flag on an account that was set during one incident
A price override that was meant to last a weekend
⚠️ Nobody reviews these, because they are only visible when somebody opens that specific record, which is exactly the moment they are acted upon rather than questioned.
⇒ On settings that keep doing something long after the reason ended: the default that charges money.
Guest notes in particular
"Difficult in March"
"Prefers [staff member who left]"
"Do not seat near the door"
⇒ The first should have expired. The second is dead. The third is probably still true. Only somebody who knows the history can tell, which means the notes need reviewing while that person is still around.
Numbers worth keeping
One How many pinned messages you currently have
Two How many of them are older than three months
Three How many printed signs are up, and who wrote each
Four When you last read the handover book from the beginning
⚠️ Two is usually most of one. The pinned list is where notes go to become permanent without anybody deciding they should be.
The card for the office
────────────────────────
Before you write a note
1. Is this permanent, conditional, or dated?
2. If conditional - write the condition on it.
3. If dated - write the removal date on it.
4. Put today's date on it either way.
Before you correct one: fix it where it lives.
────────────────────────
Common objections
"We'd notice an old note"
⚠️ You would notice a wrong one. A note that was correct when written reads exactly like a current one, and that is the category that causes the errors.
"It's obvious it's old"
⇒ It is obvious to you, because you remember the situation. The new starter does not, and they are the person the note will reach.
"We'll clean up when we do the refurb"
⚠️ The sweep takes ten minutes and the refurb is in six months. Those are not comparable units of effort.
"Nobody reads the board anyway"
⇒ Then either remove it or make it worth reading. A board that is ignored most of the time but obeyed occasionally is the worst possible arrangement — you get the errors without the benefit.
"We put a correction in the group chat"
⚠️ Then you have two sources saying different things, and the older one is in the place people were told to look. Correct it where it lives.
What to do this week
One Read every pinned message. Unpin what is done.
Two Walk round and read every printed sign as if new.
Three Search your notes for the names of people who left.
Four Put dates on everything that survives.
Five Agree who wipes the board, and when.
Summary
- A stale note is indistinguishable from a current one
- Writing a note is somebody's job; removing it is nobody's
- Correcting it elsewhere leaves the original still giving instructions
- Notes are permanent, conditional or dated — write which
- Pinned messages and printed signs are where staleness accumulates
- Names of people who left turn notes into dead ends
Nobody follows a note they know is old. The trouble is that nothing about an old note says so.
Related articles
Who Did It Is Not What They Did
Your records show who made a change and when. They almost never show what the change actually was, or what it replaced. Here is the difference between a log and an audit trail, and the three lines that turn one into the other.
Two Clocks In One System
A scheduled message goes out a day late. A shift lands on the wrong date. A report counts yesterday as today. Usually there is nothing wrong with the schedule — the system is running on two different clocks and only one of them is yours.
The Zero That Meant Something Else
A zero on a report can mean nothing happened, or it can mean nobody recorded anything. Those are opposite situations and most systems show them identically. Here is how to tell them apart before you act on the wrong one.
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