Get Free Quote

A Pre-Launch Audit: Is Your Plan Hiding Fast, Cheap and Good?

Healthcare IT

Hospitals and clinics regularly launch small administrative improvements: a new way of handling referrals, a revised discharge paperwork pack, a tidier filing system, a digital appointment tool. Most of these start with the same hopeful brief: finish soon, spend little, and make it work flawlessly. What follows is an audit to run before work starts, or mid-way if a project is wobbling. Its purpose is to expose which of fast, cheap and good the plan quietly relies on all at once, and to force a conscious choice. It concerns administration only. Clinical practice, patient care decisions and anything medical lie outside it and stay with qualified staff.

How to run it

Go section by section with the project owner and one future user of the result. Score each question yes, no or unsure. Count only the honest yeses. Any unsure answers are tasks for this week. The audit is analytical rather than emotional: it looks at what the plan states and what the evidence supports, and it produces a short written decision at the end. Allow forty minutes. Do it with the document in front of you, not from memory.

Section A: the promises

  • Is there a written finish date, and who set it?
  • Is there a written budget figure, covering staff hours as well as cash?
  • Is there a written statement of the standard the result must meet?
  • Do all three exist at the same time? If so, mark the plan as overpromised until proven otherwise.
  • Has anyone written down what happens if one of them cannot be met?

A no on that final question means you have found the most common gap. The plan has three promises and no rule for choosing between them when pressure arrives. That is where unhappy surprises start, and it is the single most valuable item to fix.

Section B: the evidence for the date

  • Is the date based on how long similar tasks took before, or on when someone hoped to finish?
  • Have absences, holidays and busy seasons been counted?
  • Does the date include time for testing and for staff to learn the new way?
  • Is there a spare week, or at least a few spare days, before any external deadline?

A date supported by history is worth far more than one supported by enthusiasm. If the evidence is thin, treat speed as the likely casualty and say so openly.

Section C: the evidence for the budget

  • Does the figure include internal time, which is easy to forget because nobody invoices for it?
  • Are recurring costs, such as subscriptions or supplies, listed separately from one-off costs?
  • Is there a small reserve for surprises?
  • Would a simple itemized estimate, laid out in plain lines, make the total easier to trust? Our general reading on how itemized hospital estimates tend to be laid out illustrates the idea of reading a total line by line.

Section D: the standard

  • Is “good” defined in observable terms, such as “no missing fields on any form in the first month”?
  • Who inspects the result, and how soon after launch?
  • Which requirements come from regulation or hospital policy? Mark them fixed. They never enter the trade.
  • Are there extras above the fixed minimum that could be dropped if time or money runs short?

The fourth point matters most. Quality is not one lump. A fixed core must always be met, and there is usually an optional layer above it. The optional layer is where a real trade-off can happen without harm.

Section E: the choice

  • Which two corners will the project protect? Write them in one sentence.
  • Which corner is being relaxed, and by how much, expressed in days, money or features?
  • Who approved this choice, and when?
  • Who has been told, and has everyone affected seen the same sentence?

If you can answer all four with a straight face, the plan is in better shape than most. If you cannot, resolve it before spending more.

Section F: early warnings

  • What specific signs would show the plan is slipping, such as two missed milestones or a spending overrun of a set percentage?
  • Who looks at those signs, and how often?
  • What is the first action when one appears: pause, reduce scope or call a meeting?
  • Is there a short log where changes to the plan are recorded with dates?

Section G: the people

  • Do the people doing the work agree that the plan is realistic?
  • Is overtime part of the hidden plan? If yes, name it and cost it.
  • Has anyone been given a task with no time allotted to do it?
  • Is there a named person who can say no to extra requests?

A worked example of the audit in action

Consider an outpatient office replacing its paper referral tray with a shared digital list. The brief says: live in four weeks, no extra spend, nothing is ever lost. Running Section A shows all three promises present and no rule for choosing between them. Section B reveals that the four weeks include a staff holiday and a busy month-end, so the date rests on hope. Section C finds that internal hours were never counted. Section D shows that “nothing is ever lost” has no measurable form. Section E is blank.

The owner and a colleague then write the decision: protect cost and the fixed core, which is that every referral is logged with its date and recipient, and move go-live to eight weeks. Optional extras, such as automatic status notices, go on a later list. Section F adds two warning signs: a missed milestone and more than two untraced items in a week. The whole conversation took about forty minutes, and the plan looked sturdier at the end of it, with no new money spent.

Findings that turn up again and again

  • Unwritten standards. Teams assume that everyone shares one idea of good. They rarely do, and the disagreement appears at the worst moment.
  • Uncounted internal time. The cheapest project on paper is often the one that quietly consumed the most hours.
  • Dates set by someone far from the work. A date handed down without evidence invites a quiet sacrifice of quality.
  • No stop rule. Without agreed warning signs, drift continues until a crisis forces a meeting.
  • The fixed core mixed with the optional layer. Once separated, many apparent conflicts disappear.

Scoring the audit

Count the honest yeses out of the roughly thirty questions. There is no pass mark, because every project differs, but the pattern is revealing. If most of your yeses sit in Sections A to D and the nos sit in E to G, you have a well-described plan with no decision about trade-offs. If the nos cluster in A to C, the plan lacks basic numbers. Either way, the first fix is a sentence: which corner we relax. Write it, date it and share it. For people who like a smaller, personal version of the same discipline, a short article on tracking a monthly allowance with a simple routine shows the habit at household scale, and it is general reading only.

A reference from the technology side

The idea is hardly unique to hospitals. A cloud operations site, cloudopsnow.in, titles itself A CloudOps Blog and shows brief, readable pieces, and technical teams in that space weigh the same three corners whenever a change is planned. It is cited as a parallel and nothing more.

After the audit

  1. Write the one-sentence decision on the project page.
  2. Convert every unsure answer into an action, with one named owner and a due day.
  3. Book a half-hour review in three weeks.
  4. At the review, rerun only the sections where answers changed.
  5. Keep the finished audit with the project records for next time.

A project that survives this audit is not guaranteed to succeed, but it is far less likely to fail through a surprise nobody agreed to. That is a modest promise, and in office work a plain, honest promise beats a grand one that will not hold.