Book Appointment

A Records Audit Checklist: Known Facts, Working Assumptions, Hunches

Healthcare Careers

On Monday morning, a records clerk at a mid-sized hospital opens a folder and finds a note: “Transfer paperwork complete.” Nothing about the note looks wrong. It is typed, it is initialled, and it sits in the right place. By Wednesday, the same folder has caused three phone calls, two apologies and a family waiting longer than anyone intended. The paperwork was not complete. Somebody had assumed it was, because it usually is by that stage.

This checklist is for exactly that situation. Its scope is the administrative corner of a hospital and nothing clinical, and it contains no medical advice. The goal of a records audit checklist is to help you sort every statement in a file into what the documents confirm, what staff are assuming and what is only a hunch, and to label each one before anyone acts.

The story behind the checklist

The clerk in this story, whom we will simply call the clerk, decided to rebuild the Monday folder from scratch. She laid out every line of the note as a separate card. For each card she asked one question: could I point to a page that shows this? Two cards had a page behind them. Three did not. One of those three turned out to be a verbal update from a colleague who was off that day. That was the moment she began to treat unlabelled statements as unfinished work.

The checklist

Before you open the file

  • Decide what question the audit must answer. “Is this ready?” is too vague; “Which of these five documents are in the folder today?” is better.
  • Prepare three labels: confirmed, assumed, guessed. Paper stickers or three columns in a spreadsheet both work.
  • Note the time. Facts have a shelf life, and your audit does too.

While you read

  • For every statement, point to the page, screen or message that supports it. No pointing, no confirmed label.
  • Mark anything that rests on memory, such as “I think the family was told”, as assumed.
  • Mark anything nobody has looked at as guessed, and resist the urge to round it up to assumed.
  • Watch for borrowed confidence: a line copied from an earlier note carries the old author’s certainty but not their evidence.

Before you close the file

  • Pick the single assumed item whose failure would create the largest tangle, and check it first.
  • Test any guess that can be tested safely, such as searching the shared inbox or opening the portal, before sending an alarm to someone else.
  • Write the next action beside each item that is not confirmed, with an owner and a time.
  • Leave the labels in the file so the next person sees how sure each line is.

Three questions that settle most doubts

When a line refuses to fit neatly into a label, the clerk falls back on three questions. Who wrote this, and could they see the underlying record themselves? When was it last true, and has anything happened since that could change it? And what is the smallest harmless step that would turn this line into something I have actually seen? Most lines are settled by the third question alone, and that is a satisfying discovery for anyone who dreaded a long afternoon of detective work. Opening a portal, scrolling to the right page or sending a one-line message costs almost nothing, and it replaces an argument about who remembers what with a screenshot.

She also learned to distrust summary words. “Complete”, “cleared”, “sorted” and “all set” each hide a list of smaller steps. Whenever one appeared, she asked for the list, and she was often handed a shorter and more honest sentence in return.

What the clerk found

By Tuesday afternoon the clerk had labelled every line in nine folders. About a third of the statements in them were confirmed by a document. Many more were assumptions that were probably right but had never been checked. A handful were pure guesses dressed as facts. None of this meant her colleagues were careless. It meant the folders had no vocabulary for uncertainty, so everything sounded equally solid.

The checklist gave the office that vocabulary. In the following weeks, people began adding “assumed” to their own notes unprompted. Nobody had asked for it; they simply found it more honest than writing “done” when they meant “probably done”.

Reading outside sources with the same labels

Patient-services staff also read public information to prepare for questions, for example an overview such as this article on the options people usually look at before surgery is considered. Apply the same three labels there. What does the article state as a general fact, what is it assuming about the reader’s situation, and what would you only be guessing about how your own hospital handles the matter? An article can describe a typical pathway while your local process differs, and that is worth knowing before you promise anything to a family.

Likewise, when a guide such as a comparison guide to choosing among fertility clinics describes what a patient might ask a clinic, read the list as a source of questions to ask, never as a description of how one particular organisation works.

A parallel from engineering teams

Engineers who keep websites and apps running rehearse the same sorting whenever a service misbehaves: monitoring output goes in one pile, the team’s working theory in another, and loose speculation in a third. DevOpsSchool, an online platform for people studying DevOps and neighbouring engineering fields, offers courses, certification tracks and reading material, which you can browse via this engineering learning site if you are curious how professionals are trained to reason that way. The vocabulary differs from a records office; the logic does not.

Running the audit weekly

The clerk now runs a short version of the checklist every Friday on a sample of folders. It takes about the length of a coffee break. She keeps a simple tally of confirmed, assumed and guessed statements, and the point of the tally is to notice the direction of travel, not to score anybody. When the share of guessed statements falls, she knows the labels are working.

If you adopt the checklist, start small. Pick a single type of folder, such as discharge paperwork or referral letters, and audit five of them. Share the findings kindly. Nobody enjoys finding out that a trusted note was an assumption, so present the results as something the system produces, not a flaw in any one person.

One last reminder

The checklist will not tell you what a document should say, and it will not replace a policy, a supervisor or the hospital’s own procedures. What it does is bring uncertainty to the surface where it can be handled calmly. A guess that is labelled as a guess is harmless. A guess that looks like a fact is how Monday’s tidy folder becomes Wednesday’s crisis.