TL;DR. A Treasury Board submission is not a grant application with bigger margins. It is a decision document written for a committee of ministers, in a fixed analytical vocabulary, where the quality of the reasoning — not the ambition of the idea — determines whether a file advances. Most proposals stall not because the idea is weak, but because the document doesn't speak the language the decision is made in.

There is a moment, common to almost every federal file, when a good idea meets the page it has to be written on. The idea survives or dies there. Treasury Board submissions are where that happens for a large share of federal spending and authority decisions — and they are written to a standard that is unforgiving of imprecision.

The standard is not stylistic. It is structural. A submission is expected to answer a specific set of questions, in a specific order, to a specific level of evidence: what is being proposed, why now, what it costs, what it risks, how success will be measured, and how it aligns with existing authorities and government priorities. Each of those is a discipline. Underbuild any one of them and the file does not read as "promising but early" — it reads as not ready.

The vocabulary is the gate. Central agencies evaluate hundreds of proposals against a shared analytical frame. A submission that uses that frame — that frames cost in the terms the costing analysts use, risk in the terms the risk reviewers expect, results in the terms the performance framework requires — is legible. A submission that doesn't, however strong its underlying case, forces the reader to do the translation. Readers under volume do not translate. They defer.

This is why we treat the operational vocabulary of government as a prerequisite, not a polish step. Before a single line of a submission is drafted, the questions are: which authority is actually being sought; which framework governs it; what evidence standard applies; and what the decision-maker needs to be true in order to say yes. The document is then built backward from that — every section earning its place by moving the reader toward a defensible decision.

Three failure modes we see repeatedly:

  • The narrative submission. Compelling prose, thin on the structured evidence the frame requires. It persuades a general reader and loses the specialist one — and the specialist one decides.
  • The everything submission. Every benefit, every contingency, every stakeholder. Length is read as a lack of judgment, not a surplus of rigour. The strongest files are ruthlessly scoped.
  • The mismatched-authority submission. A strong case for the wrong instrument. The single most expensive error, because it isn't fixable by editing — it's fixable only by starting again.

None of this is about writing well in the ordinary sense. It is about writing to a standard that was designed to make decisions defensible to Parliament and to the public. The firms and organizations that move files reliably are the ones that internalize that the document is the strategy — not a record of it. Strategy lives in the text. We build submissions to that standard, not slide decks about them.

If you're preparing a submission and want a structural read before it goes up the chain, start a conversation.