The gap assessment is the most important deliverable in consulting that nobody teaches you to write. It's usually your first paid work for a client, it sets the roadmap for everything that follows, and — whether you frame it this way or not — it's the sales document for the rest of the engagement. And yet the standard-issue gap assessment is a 40-row spreadsheet of clause numbers and terse verdicts that exactly one person at the client will ever read, and only once.
The gap between a gap assessment that gets filed and one that gets funded is mostly structure. Here's what a decade of watching clients' faces while they read these things teaches.
Write findings as evidence, not opinion
The weakest sentence in any assessment is "The company does not have an adequate corrective action process." Adequate according to whom? The client's production manager was solving problems before you arrived; you've just called their work inadequate in a document their boss will read.
The strong version has three parts, in order: what the requirement asks, what you observed, what's missing between them.
ISO 9001 clause 10.2 requires that when a nonconformity occurs, the organization evaluates the need for action to eliminate its cause, and retains documented information on the nature of nonconformities, actions taken, and results. The shop maintains a rework log (reviewed: May–July) that captures what was fixed; it does not capture cause evaluation or verification of the action's effect. Two repeat occurrences of the same dimensional issue appear in the reviewed period.
Nobody argues with that paragraph. It contains no adjectives to disagree with — just a requirement, an observation with its evidence base, and a distance between them. The two repeat occurrences do the persuading, which brings up the real rule: let the client's own records make your argument. You're not the critic; you're the mirror.
Assess in clause order, report in people order
The perpetual structural tension: standards are organized by clause, businesses are organized by process. Solve it by using both, in different layers.
Assess against a clause-ordered register — a fixed, versioned list of requirements you apply the same way to every client. This is what makes your assessments consistent, defensible, and comparable across visits (and it's what lets a reassessment next year show movement, which is the single most persuasive artifact in consulting: nothing renews an engagement like a chart of findings going green).
Report in the client's order. The executive summary and action plan should read in the language of their operation — "Purchasing," "The floor," "Training," "When things go wrong" — with clause references attached rather than leading. The owner doesn't think in 8.4; they think in "our supplier problem." Your register keys the findings; their org chart presents them.
Score honestly, or don't score
Clients love a number. Numbers are also where assessments quietly rot: a "73% compliant" headline computed from an opaque weighting is a number nobody can defend when the owner asks why 73? — and someone always asks.
Two honest options. Either skip the aggregate and report counts by severity (conformity / minor gap / major gap / not assessed — with "not assessed" as a first-class category, because pretending you covered everything in two days is its own credibility leak). Or score transparently: every point traceable to a specific finding, arithmetic a client can redo themselves, and no invented precision. A score that decomposes to its findings is a communication tool; a score that doesn't is a liability with a percent sign.
The action plan is the actual product
The findings prove you looked; the action plan is what the client is buying. Three properties separate plans that get executed from plans that get laminated:
- Sequenced, not just listed. Document control before training records (the training points at documents). Corrective action before internal audit (the audit will generate CARs and needs somewhere to put them). A findings list sorted by clause number is a data export; a plan sorted by dependency is consulting.
- Sized honestly. "Establish management review" is an afternoon of design and a recurring calendar entry. "Establish traceability" might be a capital project. Clients budget from your plan — a plan where every item looks the same size produces a budget that's wrong in both directions.
- Owned by names, not departments. The moment a finding has a person attached, it has a probability of closure. "Production" never closed a finding in the history of the profession.
Close the loop, visibly
The assessment that transforms a client relationship isn't the first one — it's the second one. Same register, same method, findings carried forward with their history: closed, in progress, unmoved. That before/after is your effectiveness made visible, and it converts a one-time diagnostic into a standing relationship measured in years.
Which imposes a discipline on the first assessment: it must be reassessable. Ad-hoc Word documents with this-visit-only structure can't be diffed against next year. A versioned register, applied consistently, with findings sealed at completion — that can. (Structuring exactly that — versioned registers, carry-forward reassessment, findings that keep their history — is the core of what we're building for consultants in Norma.)
One last thing, since the deliverable will outlive the visit: the assessment report ends up in front of people who weren't in the room — the owner, the OEM's supplier-quality auditor, sometimes the CB. Write it to survive that audience. A gap assessment that impresses the client is good. One that impresses the client's customer is marketing you didn't have to pay for.