Ask people from a hospital front desk or a coordination office and many will recall hearing “I thought that was already done.” It is rarely said with bad intent. Somebody carried an assumption from one shift to the next, it sounded like a fact by the time it was repeated, and an administrative step quietly slipped. What follows covers only the office side of that problem, meaning how to tell confirmed records from administrative guesses. It is general information about office process, not medical advice of any kind.
The idea behind confirmed records versus assumptions is simple. Before acting on any statement, put it into one of three buckets. Known means a record, a timestamp or a signed form confirms it. Assumed means it is likely, since cases like it normally turn out that way. Guessed means nobody has looked. The eight habits below are ways of making that sorting automatic rather than heroic.
1. Name the source of every statement
A note that says “insurance cleared” is not a fact until you know who cleared it, when, and where that appears. Make it a habit to attach a source to each line in a handoff: “per the scanned approval letter”, “per the front-desk list”, “per what the family mentioned”. When a source cannot be named, the line moves to the assumed bucket automatically.
2. Put dates on everything
Records go stale. A bed list that was accurate at breakfast may be wrong by the afternoon round. Stamp each fact with the time you last saw it confirmed. A statement that was checked this morning is a different animal from one that was checked last week, even if the words are identical.
3. Use three visibly different labels
If your handoff sheet uses one font and one tone for everything, readers cannot tell the difference. Pick three markers that look different at a glance: a tick for confirmed, a tilde for assumed, a question mark for guessed. Some teams use colour; others use a short prefix such as “C:”, “A:” and “G:”. The format matters less than the consistency.
4. Treat “usually” as a warning word
The words “usually”, “normally” and “always” are almost always signs of an assumption. A coordinator who writes “reports usually arrive by noon” is describing a pattern, not a state of the world today. That is useful context, but it belongs in the assumed bucket until today’s report actually shows up in the system.
5. Ask what would change your mind
For each assumption that matters, write one line: “If X turns out to be different, we would do Y.” This tiny exercise exposes which guesses are load-bearing. If nothing would change your plan, the guess does not need checking. If a wrong guess would derail a discharge-paperwork step or a referral, check it now. The same discipline is useful when reading about topics such as how telehealth fits into follow-up care after cardiac procedures, where administrative arrangements vary from one provider to the next, which invites guessing.
6. Check the cheapest facts first
Some questions take ten seconds to settle: is the form in the folder, does the name on the booking match the name on the identity record, is the referral letter dated. Others take a phone call. Settle the cheap ones immediately so your remaining uncertainty is concentrated in the few items that need real effort. It is a good use of a quiet minute and it shrinks the list you carry into a busy hour.
7. Test the guess before you act on it
An assumption you cannot verify can sometimes still be tested safely. If you suspect a transfer request is stuck in a queue, you can search the queue before calling anyone to demand an explanation. If you suspect a form is missing a field, open it. The point is to turn a guess into an observation using the smallest, most reversible action available, and only then decide what to do about it.
8. Hand over the labels, not just the conclusions
The most common failure happens at shift change. The outgoing person writes “all documents ready”, and the incoming person reads it as fully confirmed. Pass along the labels too: “documents ready (ticked: two of three; the third assumed from the earlier file)”. Passing on the doubt is not weakness; for an office it is inexpensive protection.
A short worked example
Imagine a coordinator preparing materials for a family comparing recovery programmes, such as the ones discussed in this overview of how families approach choosing a heart failure recovery programme. The coordinator writes three lines. Known: the family’s preferred language is recorded on the registration form. Assumed: an interpreter is needed at the appointment, because the family said they were more comfortable in that language. Guessed: the visiting relative will attend. Only the first is a fact. The second needs a question to the family, and the third needs nothing yet, because nothing depends on it today.
Without the labels, all three lines would have been presented as logistics and the office might have booked an interpreter for a visitor who never came, or skipped one for a family that wanted it. With the labels, the next action for each line is obvious.
Where engineers learned the same lesson
Software and operations teams who run live services have long practised a close cousin of this habit during outages: jot down what dashboards confirm, what the team currently believes and what is a stab in the dark, and poke the belief gently before changing anything. Readers who wonder how that mindset gets taught can look at the online engineering school DevOpsSchool, whose pages list certification tracks, courses and reading material for engineers. The parallel is worth borrowing even if you never touch a server.
Making the habits stick
Adopting every habit simultaneously is a recipe for fatigue, so stage them. Begin with the source and date habits, because they cost nothing and change what people write. After a few weeks, add the three-label system to the handoff sheet. Reserve the “what would change your mind” question for the two or three items per week that would create the biggest mess if mistaken.
Expect some friction. People may feel that labelling a statement as “assumed” sounds like an accusation. Frame it as a courtesy to the next reader instead. Everybody carries assumptions; the useful part is that they are visible.
Common mistakes to avoid
- Labelling everything as confirmed because it is quicker.
- Treating a colleague’s confidence as evidence.
- Leaving guesses unlabelled because they feel too small to mention.
- Checking low-stakes facts at length while skipping the one that gates the next step.
Administration in a hospital setting runs on trust between colleagues, and trust is easier to keep when everyone can see how sure a note really is. The sorting habit takes a few minutes to learn and pays back every time a handoff survives a busy day without a surprise.