SoW conformance verification

01Is "What I Ordered" the Same as "What Arrived"?

Most material defects are not the visible kind — typos or color shifts. They come from quiet drift between what the owner intended and what the vendor delivered. A vague request to "make the efficacy look a bit stronger" passes through the vendor's interpretation and becomes a claim beyond the approved range. Material meant "for healthcare professionals" gets repurposed into something patients can see. The source document to be cited was never updated from an old version. None of these surface in proofreading. They appear only when you compare the deliverable against the record of what was actually ordered — the SoW.

Even when production is outsourced, responsibility for material sent up for internal review and into the world stays with the owner. That principle from Part 2 becomes concrete work at the verification stage. Instead of "passing the vendor's output straight to internal review," the owner "confirms alignment with their own intent before sending it up." The reference for that confirmation is the SoW.

02Four Elements of a Verifiable SoW

A SoW is a contractual scope document, but in material verification it reads as the document defining "what to collate against." A verifiable SoW contains at least these four elements. Without them, there is no way to decide where in the deliverable to look.

Each element answers a verification question. Claim intent: "did it overstate?" Target media: "right audience, right place?" Source materials: "is the basis correct and current?" Regulatory premise: "which ruler do we measure with?" Drop one of the four, and verification cannot answer the matching question.

03How a Vague SoW Breeds Drift

Most drift is planted at the ordering stage, not at delivery. Hand over an unverifiable SoW and the vendor fills the blanks with their own reading — a reading that exceeds the approved range. The contrast below shows the same request as a vague version and a verifiable version.

With the right-hand SoW, any "works better than competitors" wording in the deliverable is immediately a drift. With the left-hand one, you cannot even judge whether that wording is drift. Writing a verifiable SoW is an investment that lowers the owner's own verification cost.

04The Alignment Verification Flow

Once a deliverable is received (after Part 3's intake flow), collate it against the SoW in this order — a stacked process where what fails an earlier stage does not pass to the next.

1. Media & audience match — Do the deliverable's format and the SoW's target media/audience agree? Check first. If this is off, all downstream claim verification is moot.
2. Claim-range match — Does the wording stay inside the claim intent (approved range)? Prioritize headlines, taglines, and figure captions; drift surfaces most in emphasized spots.
3. Source identity — Do cited figures, charts, and efficacy statements match the SoW-specified version and page? Did the vendor reference a different version or a secondary source?
4. Regulatory premise compliance — Any drift against the SoW-specified standards (Ad Standards, MSA-GL, etc.)? Only here do you apply the judgment criteria.
5. Elements outside the SoW — Has any unrequested claim, figure, or note crept in? The vendor's well-meaning "additions" are the most overlooked source of drift.

Do not slight item five. Owners check "is what I ordered present" but miss "is something I did not order present." A claim absent from the SoW sits outside the ordering intent even if its content is accurate. The owner should remove it before internal material review.

05Separating Drift by Severity

Treating every detected drift as a "send-back" makes operations unworkable. Sort by severity and vary the response. The owner makes the call, but the severity threshold derives from the SoW's regulatory premise.

The point of sorting by severity is to reliably stop the critical ones. Examine everything with equal intensity and the drift that truly must be stopped gets buried under trivial notes. With a clear regulatory premise in the SoW, which drift is critical can be told almost mechanically. Here too, a verifiable SoW pays off.

06A Judgment Template

Do not let verification results dissolve into spoken remarks or email bodies. Keep them in a fixed judgment record — the starting form for the documentation covered in Part 10 (in preparation). A minimal layout follows.

The heart of this form is the "Basis" field. Whether you can write the send-back reason as "exceeds the approved range in SoW clause ◯, may constitute exaggeration under Pharma Act §66" rather than "feels too strong" changes both the dialogue with the vendor and the explanation at internal review. Never confuse the articles: exaggeration is §66, pre-approval advertising is §68, and the duty of effort for information provision is §68-2.

07When the SoW Is Missing or Stale

In reality there are orders with no documented SoW, and cases where verbal changes piled up until the SoW and the actual state diverged. With the deliverable arriving in that state, there is no reference for collation. You must rebuild the reference before verification can begin.

• No SoW — Before verifying, retroactively document the ordering intent. Write up memory and verbal agreements into the four-element form from Section 2, then collate. Verification without a reference is only impressionism.
• Stale SoW — Fix a version reflecting the verbal changes and record who changed what, when. A missing version history is itself a breeding ground for drift.
• SoW–vendor mismatch — If a gap is found before delivery, the owner decides whether to update the SoW as the authoritative text or adopt the vendor's reading, and records it. Do not accept delivery while the gap is unresolved.

Maintaining the SoW is the owner's responsibility and cannot be dumped on the vendor. The vendor produces the deliverable; the owner defines what should be produced. The sister series "Production Quality Management" (/production-qm/) handles the vendor's quality control, but the accuracy of the SoW that underpins it is held by the owner.

08Making Verification a System

Leave alignment verification to individual skill and its depth will vary by person. To embed it as a system, build three things into operations.

1. Standardize the SoW template — Provide an ordering template with the four elements from Section 2 as required fields. Make it impossible to order with blanks, and unverifiable SoWs structurally decline.
2. Fix the verification checklist — Turn Section 4's five lenses into a checklist operated together with the judgment record. Do not rely on individual attention to avoid a missing lens.
3. Accumulate send-back cases — Stockpile critical-drift cases linked to their SoW clauses and feed them back into sharper SoWs for the next order. Do not let the same drift be made twice.

Verification sits downstream of the intake flow (Part 3) and upstream of documenting the judgment record (Part 10, in preparation). Alignment verification is placed at the very fork where the owner moves from "passing the vendor's output straight through" to "owning responsibility for their ordering intent." To skip verification is to abandon that responsibility. The norms underlying the judgment criteria are the Pharma Act (/compliance/01-pharma-act.html), the Ad Standards (/compliance/03-ad-standards.html), and the MSA Guidelines (/compliance/04-msa-guidelines.html).