When a family takes on the administrative load around cancer care, the schedule tends to be built from half-remembered promises: “the office said a week”, “the insurer usually approves quickly”, “someone will be at the desk on Saturday”. This checklist is an audit tool for those promises. It is meant for paperwork, appointments and payments only. It offers no medical guidance and takes no position on any treatment; those conversations belong with the treating team.
What the audit is for
An assumption audit asks a narrow question of every plan: what are we taking for granted, and what would change if it turned out to be false? The audit does not make a plan safer by itself. What it does is convert vague trust into specific, inspectable statements. A statement such as “pre-authorisation takes about a week” can be tested by a phone call; the feeling that “it will probably be fine” cannot.
Run the audit once at the start, and again whenever something material moves, such as a new appointment date or a change of insurer contact. Each pass takes about twenty minutes if you keep the sheet short.
Step 1: Collect the plan’s moving parts
Write the plan as a plain list of events with dates: the registration visit, the insurer submission, the date a signature is needed, the billing settlement, the follow-up appointment. Leave out anything clinical. If a line is about care itself, strike it and leave it to the care team.
- Is every event attached to a date, even a rough one?
- Is every event attached to a person’s role, such as the patient’s relative, the desk, or the insurer’s helpdesk?
- Does each event depend on another event finishing first? Draw an arrow if so.
Step 2: Extract the assumptions from each event
For each event, ask what must be true for it to go ahead. Be literal. If the registration visit is on Tuesday, what do you need to believe? That the desk opens at the time you think, that the identity papers are acceptable, that the person accompanying you is free, that the route takes the time you allowed.
- Have I written each belief as a full sentence, not a keyword?
- Could a stranger reading the sentence tell what to check?
- Have I separated confirmed facts from unconfirmed beliefs? Only the second group belongs on the audit sheet.
Step 3: Score each assumption
Give every line two ratings. The first is how likely you think it is to hold. The second is how much it would disrupt the plan if it failed. Keep the scale crude: low, medium, high. A line with low likelihood and high impact is the one to work on first, and a line with high likelihood and low impact can wait.
- Is my likelihood rating based on something I actually know, such as a past visit, rather than on hope?
- Have I marked impact honestly, including knock-on delays for later events?
- Do the top three lines have a named check beside them?
Step 4: Attach a check and an owner
A rating with no follow-up is decoration. Beside each high-priority line, write the cheapest action that would confirm or kill the assumption. Usually this is a phone call, an email, or a look at posted hours. Then add who will do it and by when.
- Is each check small enough to complete in one sitting?
- Does each have an owner who has agreed to it, not merely been assigned it?
- Have I recorded the answer, along with the role of the person who gave it and the day it was given?
Step 5: Look for clusters
The most useful discoveries from an audit are shared dependencies. Two assumptions that look unrelated may both depend on the same person’s availability or the same office’s turnaround. When you see a cluster, treat it as one larger risk and consider a backup for it.
- Do any two assumptions rely on the same person, desk or document?
- If that shared dependency slipped by a day, which dates would move?
- Is there a plain fallback, such as an alternate signer, and is it written down?
Step 6: Review after each milestone
Reopen the sheet when an event passes. Mark each assumption as held, partly held or failed, and add a short note about why. Failed lines are the valuable ones, because they show where your information was weakest. After two or three cycles, patterns emerge: perhaps a particular office always takes longer than quoted. Those patterns can then feed straight into the next plan’s ratings.
- Have I updated the likelihood ratings using what actually happened?
- Have I deleted lines that became confirmed facts?
- Have I added new lines raised by the latest developments?
Where to read around the subject
Families often tell us that the hardest part is knowing what to ask. For that, our guide to the practical questions people bring to the care team after a diagnosis makes a useful pairing, and the article on money, support services and seeking another view once a diagnosis is known covers the financial side at a general level. They are general background pieces, not endorsements of any provider or course of care.
An aside from the technology world
Writing assumptions down is hardly unique to healthcare administration. Software teams record them in design notes and tickets so that the reasoning behind a decision survives staff changes. A training website based in India, NoOpsSchool, which describes its pages as covering certification courses, consulting and services for IT people, sits in that technical world. The family-paperwork version is simpler: a single printed page and a pencil will do.
A short example of the audit in motion
Suppose the plan includes submitting forms to an insurer on Monday and settling the first invoice on Friday. Extracting assumptions gives four lines: the insurer’s portal accepts the file format we have, a reply comes before Friday, the invoice will match the estimate we were given, and the billing counter is open late that day. Scoring them shows that the reply-before-Friday line is low likelihood and high impact, because everything downstream hangs on it.
The check is a call to the insurer’s helpdesk on Monday morning, asking what the present queue looks like and writing down the answer. If the answer is “ten working days”, the Friday settlement is already at risk, and you can ask the hospital’s billing desk about a later date while there is still time. The audit did not change the insurer’s speed. It changed how early you learned about it, and that gap is where most of the value sits.
Quick reference: ten questions to keep on the sheet
- What am I counting on that I have not confirmed?
- Who would tell me if it were wrong?
- How soon would I find out?
- What would I do differently if it failed?
- Which other line fails with it?
- Whose time does the check require?
- Have I written the date I last confirmed it?
- Is this a fact that has crept into the list?
- Does anyone else need to read this line?
- Is there a fallback written next to it?
Final word
The aim of the audit is modest: fewer surprises in the paperwork, so that attention stays free for the people involved. Keep the sheet short, honest and current. If you take only one habit from it, take this one: whenever you hear yourself say “it should be fine”, write the sentence down and attach a way to check it.
