You have ten minutes on the board agenda and a database risk that needs a decision. Here is the one page that gets it.
Most technical people lose the room by explaining the problem. The board does not need to understand the problem. They need to decide about it. So structure the page around their decision, not your diagnosis. Four lines. That is the whole page.
The risk, in business terms. Not “untested backups”. “Our billing database has not been proven recoverable this year.” One sentence, in money or compliance or downtime.
The exposure, sized. What happens if it goes wrong, and roughly what it costs. A range is fine. “An outage of our claims system costs around X an hour, and recovery today would realistically take Y.” The board lives in numbers. Give them one.
The ask, specific. What you want, by when, for how much. “Approve a fixed-scope assessment this quarter.” Vague asks die in committee. Specific asks get a yes or a no, which is all you need.
The evidence, external. One line: an independent, plain-English assessment is attached. Nothing moves a board faster than a finding they did not have to take on faith from their own staff.
Risk, exposure, ask, evidence. One page, four lines, ten minutes. If the missing piece is the evidence, that is the part we can hand you. We run a free, read-only health check and give you the report in language a board reads, so the one page writes itself and the decision lands on their side of the table, not yours.
Want to know if this is sitting in your estate? We run a read-only check and hand you a graded report in plain English.
Get your free health check