Designing the Monthly Hospital MIS Report for the Board

Build the pack from the front page backwards. The first page should carry between eight and twelve numbers, each with the current month, the prior month, the same month last year, the budget or target, and a direction indicator. Occupancy, admissions, OPD footfall, average length of stay, revenue, EBITDA or operating margin, collection days, and one or two quality indicators will cover most hospitals. Nothing on this page should require explanation to a non-clinical trustee.

Every number on the front page must be a link to a supporting page, and every supporting page must trace to a front-page number. This simple rule kills the accretion problem permanently: a page that no front-page number points to has no reason to exist. It also gives the board a navigation model — see something odd, turn to its page.

Colour should carry meaning and nothing else. If a cell is red, it is materially off target and there is an action against it later in the pack. Decorative colour, gradient fills, and charts that dress up a single number all reduce the page's information density and slow the reader down. The front page of a board pack is one of the few documents where austerity genuinely helps.

Most board packs are almost entirely lagging: revenue, occupancy, margin, collections. These describe what already happened and are essential, but by the time they move, the decision window has usually closed. A pack made only of lagging indicators produces a board that reacts competently to last quarter and cannot see the next one.

Leading indicators point at the same outcomes before they materialise. Booked appointments for the coming fortnight lead OPD revenue; the surgical booking pipeline leads theatre utilisation and IPD admissions; referral volume from partner clinics leads admissions; open consultant vacancies and notice periods lead capacity constraints; empanelment and claim submission lag lead cash collection. Each of these is visible weeks before its lagging counterpart moves.

Aim for roughly a third of the front page to be leading. Label them as such, because a board that does not know which numbers are predictive will treat a soft booking pipeline as a minor operational detail rather than as an early warning about next month's revenue. Operational systems that hold booking, theatre scheduling, and claim status — HealUDoc among them — make these leading indicators available without a manual compilation exercise, which is usually why they are missing.

Both comparisons are needed and they answer different questions. Variance against budget tells you whether the plan is holding, which is the governance question. Variance against the prior year tells you whether the business is growing, which is the strategic question. A month can be simultaneously well ahead of last year and well behind budget, and reporting only one of these gives the board a false picture.

Decompose material variances rather than reporting them as a single line. Revenue below budget because volume was low is a completely different problem from revenue below budget because the payer mix shifted towards scheme patients at lower realisation, or because a high-earning consultant was on leave. Price, volume, and mix decomposition takes a modest amount of work and converts an alarming number into a specific, addressable one.

Set a materiality threshold and apply it consistently, so that only variances above it get narrative treatment. Without a threshold, the pack explains every wobble and the board loses the ability to distinguish noise from signal. With one, a variance appearing in the narrative is itself informative.

The commentary is where board packs most often go wrong, because it is the one part that is written rather than generated. Useful commentary follows a fixed structure: what happened, why, what we are doing, by when, and who owns it. Anything that does not fit that structure — background, context that has not changed, restatement of the number in words — should be cut.

Ban the phrases that carry no information. Performance was impacted by market conditions; we continue to monitor the situation; efforts are ongoing to improve collections. Each of these occupies a line and communicates nothing. Replace with the specific: collections slipped because two corporate accounts moved to ninety-day terms in February, and finance is renegotiating both by the end of the quarter.

Give the narrative a length limit — a paragraph per material variance, no more. The constraint is what forces the writer to identify the actual cause rather than surveying possibilities. It also makes month-on-month comparison of commentary possible, which is how a board notices that the same explanation has now appeared four times without the number moving.

The most damaging thing that can happen in a board meeting is two numbers for the same thing. Operations reports 1,240 admissions; finance reports 1,196 billed admissions; someone asks which is right and the meeting is lost for twenty minutes. The numbers are usually both correct under their own definitions — operations counts admissions on the admission date, finance counts on the discharge or billing date, and one excludes day-care while the other does not.

Fix this before publication with a standing reconciliation. Each month, before the pack is finalised, operations and finance compare their core counts, identify the differences, and either agree a single figure or document the definitional gap in a reconciliation note that travels with the pack. Ten minutes of preparation removes the single most common source of lost board credibility.

Longer term, the reconciliation should shrink as definitions converge. Where both functions draw from the same warehouse with one agreed definition per metric, the difference disappears entirely. Where they cannot converge — because a regulatory or accounting definition genuinely differs from the operational one — publish both with their labels and stop pretending they should match.

Cutting is politically harder than adding, because every page has a sponsor. The technique that works is to move rather than delete: shift the page to an appendix or a separate operational pack, announce that it remains available, and see who asks for it. Most pages are never requested, and the ones that are can return with a named reader attached.

Run this review annually and treat it as a fixed obligation rather than a project. Ask each recurring page three questions: who reads it, what decision does it inform, and what would change if it stopped. A page that cannot answer all three moves out of the board pack. This is the same discipline that keeps a metric set useful, applied to the document that carries it.

The end state is a pack of perhaps ten to fifteen pages that the board reads properly, plus an operational appendix that management uses. That is a smaller document that takes less time to produce and generates more decisions than the forty-page version it replaced — which is the only measure of a management report that matters.