Why most consulting reports nobody reads — and how to fix that

A breakdown of the structure I use for client audits so the recommendations actually get acted on.

The problem with most reports

Most consulting reports are written for the consultant, not the client. They document what was found, not what should be done — and they bury the most important recommendation on page 47 after 46 pages of context nobody asked for.

Lead with the decision, not the discovery

The structure I've landed on after several audits: open with the single most important thing the client needs to do, then provide the evidence that supports it. Invert the traditional report structure entirely.

If your executive summary requires the full report to make sense, it isn't a summary — it's a table of contents.

Make the action clear enough that a non-technical stakeholder can assign it

Every recommendation needs an owner, a timeline, and a definition of done. A recommendation without those three things is a suggestion, not a recommendation.