Treasury Board isn't grading your idea

Here's something I keep coming back to on federal files: the idea is almost never the problem. It's the page the idea has to be written on.

A Treasury Board submission is where a big share of federal spending and authority actually gets decided, and it's a different animal from a grant application. It's a decision document, written for a committee of ministers, in a fixed analytical vocabulary. What's being graded isn't how ambitious your idea is — Cabinet already decided the idea was worth doing. It's the quality of the reasoning: whether a costing analyst, a risk reviewer, and a Chief Financial Officer can all put their names under it.

I've watched strong files stall, and it's rarely because the work wasn't good. It's because the document didn't speak the language the decision gets made in. A submission has to answer a specific set of questions, in a specific order, to a specific standard of evidence: what you're proposing, why now, what it costs on both a cash and an accrual basis, what it risks, how you'll measure success, and which authority you're actually asking for. Underbuild any one of those and the file doesn't read as "promising but early." It reads as not ready.

The part I think founders miss is that the vocabulary is the gate. Central agencies run hundreds of these against a shared frame. Frame your cost the way the costing analysts do, your risk the way the risk reviewers expect, your results the way the performance framework wants them — and you're legible. The reader can say yes. Get it wrong, however strong the underlying case, and you've handed them a translation job. Readers under volume don't translate. They defer.

Three ways I see it go sideways, again and again:

• The narrative submission. Beautiful prose, thin on the structured evidence the frame needs. It wins a general reader and loses the specialist — and the specialist is the one who decides.
• The everything submission. Every benefit, every contingency, every stakeholder. Length reads as a lack of judgment, not a surplus of rigour. The strongest files I've seen are ruthlessly scoped.
• The wrong-authority submission. A strong case for the wrong instrument. The most expensive mistake on the list, because you can't edit your way out of it. You start again.

None of this means you have to become a drafter. It means knowing what the document has to do, and who's actually reading it, before anyone writes a word — so the people building it inside government build the right thing, and you can speak to it yourself when it counts. That's the part worth getting right: the document is the strategy, not a record of it. The strategy lives in the text.

If you want the full mechanics — who reads it first, the CFO attestation gate, the quality screen that bounces an incomplete file before anyone really reviews it — I wrote them up in what a Treasury Board submission actually has to do. And if you've got federal money sitting between an announcement and a cheque, and you'd rather carry that file yourself than hand it off, book a scoping call. I'll give you an honest read on what it has to do to move.