What structure reveals about an engagement
A consulting proposal is the best-behaved document the firm will ever send you: written to win, reviewed by partners, polished for signature. Whatever is vague in it will not become clearer under delivery pressure. That is why structural gaps are diagnostic: a proposal that avoids naming its delivery team, its assumptions or its end state is describing, accurately, how the engagement intends to behave.
Where proposals most often go soft
Across engagement types, the same three checks fail most often. Client responsibilities are omitted because quantifying them makes the price look bigger. Implementation ownership is left open because the recommendation phase is the profitable one. And exit criteria are absent because the strongest predictor of next year's revenue is an engagement without an ending. None of these is scandalous, but each shifts risk quietly from the firm to you.
Who should run the checklist, and when
- Sponsors comparing proposals from two or three firms before down-selection.
- Procurement and legal teams preparing the contract questions that follow.
- Executives inheriting an engagement mid-flight who want to know what was actually agreed.
How the checklist is scored
Twelve items, ten points each, normalised to 100. There is no partial credit: an item stated verbally, promised in a covering email or implied by past behaviour is unticked until the proposal says it in writing. The bands describe the structural clarity of the document, not the ability of the firm behind it.