An audit that begins with a spreadsheet tends to inherit the spreadsheet’s blind spots. An audit that begins with a drawing begins with the work as it moves. This checklist is for administrative teams that want to review a hospital paperwork process, such as how consent forms, referral letters and billing documents travel between desks, by sketching it first. The scope stays administrative, so please do not read any of it as direction for anyone’s treatment.
The principle is straightforward: put a rough version on paper before you change the process, because a pencil line costs almost nothing to move. Use the sections below in order. Each item is phrased so that you can mark it done or not done.
Before you pick up the pencil
- Name one flow to audit. “Paperwork” is too wide; “how an outpatient referral letter reaches the scheduling desk” is the right size.
- Name one owner who can approve changes to that flow.
- Gather one real, anonymised example of the document, with all identifying details removed, so the sketch follows something concrete.
- Set a time limit of one working session. A sketch that takes longer is probably trying to be a finished diagram.
Stage one: draw the flow as it really runs
- Draw a box for every desk, office or tray the document touches.
- Draw an arrow for every handoff, and write on it who carries the document and how, for example by hand, by internal post or on screen.
- Mark each point where the document waits, with a rough duration in plain words.
- Use a second colour for steps you saw yourself, and pencil only for steps you were told about.
- Walk the route once, if the building allows, and correct the sketch where reality differs.
The distinction between observed and reported steps matters. A flow built entirely from descriptions will reflect the policy. A flow built from observation will reflect practice, and an audit exists to find the distance between the two.
Stage two: test the sketch against the questions
- Is there a step that nobody can justify in a single sentence?
- Does any detail get written down more than once by different people?
- Is there any document produced that no later step reads?
- Does any step depend on an item that is created after it?
- Is there any single desk through which every exception must pass?
- Where does a missing page get noticed, and how far has the document travelled by then?
Record each yes as a finding with a location on the sketch. Findings without a location tend to drift into general complaints.
Stage three: draw the untidy cases
- Add a path for the document that arrives incomplete.
- Add a path for the document that arrives at the wrong desk.
- Add a path for the document that must be corrected after it has moved on.
- Add a path for a busy day, when the usual person is absent.
Compare the size of the tidy-case sketch with the size of the untidy-case sketch. If the second is larger, the written procedure describes the exception rather than the norm, and the audit should say so.
Stage four: sketch the proposed change before building it
- Redraw only the part of the flow you plan to alter, on a fresh sheet.
- Count the touches per document in the old and new sketches. If the count has not fallen, say why the change is still worthwhile.
- Check that the change does not push work onto a desk that is already crowded.
- Identify who must be told and who must be trained before the change goes live.
- Write down how you would undo the change within a day if it misbehaved.
The last bullet is the one teams most often skip. A change you can reverse is a change you can try; a change you cannot reverse needs a longer look first.
Stage five: decide what to record
- Photograph the original sketch with the date written on it.
- Photograph the proposed sketch and link it to the decision.
- Note the findings in a short table: location, finding, owner, next step, review date.
- Store the table where the next auditor can find it.
Records are not decoration; they let a later team judge whether an improvement lasted. A sketch dated before the change is the most credible baseline you will ever have.
Examples worth practising on
Public pages from cancer-focused hospital sites describe journeys that imply long administrative chains. A page about why accreditation is a topic when looking at hospitals abroad raises questions of documentation and recognition that each involve paperwork. A guide on what people ask in the earliest conversations following a diagnosis hints at the volume of information that flows to patients and families. You do not need to assess the medical content to use these as practice material. Pick one, imagine the front-desk and records steps behind it, and sketch them.
A note on reading outside your field
Structured how-to material from outside medicine can sharpen your eye. Osnivo, an independent site for consumer gadget owners, groups its pages into ordered ownership stages and offers troubleshooting flows beside a reader forum. Reading anything laid out that cleanly is a low-cost way of training yourself to draw stages in order.
Questions to put to each desk during the walk
When you walk the route with your sketch in hand, a short script keeps the conversation useful and polite. Ask the person at each desk what arrives, in what form and at roughly what time of day. Ask what they do when something arrives incomplete, and who they tell. Ask what they hand on, and whether they have ever been asked to send it somewhere it did not need to go. Finally ask what they would remove if the choice were theirs. Write every answer on the drawing in the observed colour, even when it contradicts the policy manual. Contradictions are the lines worth most on the sheet, because they show where the written process and the lived process have drifted apart, and an audit that records only the manual has audited nothing.
Common audit errors
- Auditing the document instead of the journey. The form may be perfect while the route is poor.
- Auditing once. A flow changes as staff change; schedule a light review at a sensible interval.
- Skipping the people at the desks. Hand the sketch to the person who actually carries the folder and ask what is missing.
- Combining the audit with the fix. Finish the findings first, then propose changes. Mixing the two makes people defensive.
- Letting the sketch become a presentation. If someone is formatting it, stop and return to pencil.
One-page summary for the audit file
When the work is complete, the audit file should hold four things on a single page: the original sketch, the list of findings with locations, the proposed redraw, and the rollback note. A reader who opens it a year later should be able to see what the process looked like, what was wrong with it, what was changed and how it could be undone, without asking anybody.
Final word
Precision in an audit does not require precision in the drawing. A crooked box with an honest arrow beats a beautiful diagram that records what the manual says. Work through the stages in order, mark each item, and keep the pencil sketch. Whatever you change later, you will be changing it with your eyes open, at the stage where changes are still nearly free.
