Independent re-check — detecting vendor oversights and overreactions

01Re-verification is not "doing the same work twice"

Treat independent re-verification as retracing the vendor's check and you get pure duplication. The load-bearing word is "independent." Set the vendor's conclusions aside — what they fixed, what they cleared — and have the owner re-draw the regulatory line on the asset from a blank sheet. Only then compare the two lines.

Read while anchored to the vendor's verdict and you unconsciously wave past anything the vendor called clean. That anchoring bias is the single biggest source of misses. Independence is a procedural device for psychologically cutting that anchor.

02Two error types: false negatives and false positives

A vendor check can miss in two directions. A false negative passes something that should have been stopped; a false positive stops something that should have passed. Internal review tends to fixate on FNs, but leaving FPs untouched does real harm too.

FNs surface as regulatory risk, FPs as business risk. Independent re-verification looks both ways at once. A one-sided check that only "finds the dangerous stuff" can never rescue an asset the vendor over-trimmed.

03The re-verification flow

For an asset that has cleared formal receipt (Vol. 3), run this content check.

1. Blind read: Close the vendor's change log, comments, and checklist. Read only the finished asset and flag, independently, whatever feels off.
2. Norm mapping: Tie each claim to a specific provision — Act §66/§68/§68-2, the Advertising Standards, the MSA Guidelines, the JPMA Code.
3. Reconcile: Only now open the vendor's verdicts and extract the deltas against your own flags.
4. Classify deltas: Sort into match / owner-only flag (FN candidate) / vendor-only flag (FP candidate).
5. Finalize: Resolve each delta against the criteria below and record it.

04Catching false negatives

FN detection runs on the posture "suspect precisely what the vendor cleared." Hit the categories where misses cluster first.

Data drift is especially common when the vendor worked off a copy instead of the original source. The owner opens the primary source and reconciles in person. A citation being attached is not a substitute for verifying it.

05Catching false positives

FP detection runs the other way: "did the thing the vendor cut or weakened actually have a basis?" Vendors lean to the safe side to deflect liability, dropping lawful claims along the way.

• Lawful comparisons gone: Comparisons grounded in objective data are permitted when conditions are met. Did the vendor cut them on the false belief that "all comparisons are banned"?
• In-label efficacy thinned: Did the vendor blur efficacy that the package insert states plainly, "just in case"?
• Excess hedging: Have unnecessary notes and disclaimers piled up until the claim can no longer be read?
• No reason for deletion: Spots marked only "removed to be safe," with no provision cited as the basis for cutting.

Accept an FP silently and you have decided to abandon a substantiated claim. The owner demands a textual basis for deletions too, and reconsiders restoring any FP cut whose basis cannot be shown. Leaning to the safe side is not always the right call.

06Resolving deltas: who decides

Resolve each delta between owner flags and vendor verdicts by these rules. The owner is a decider, not the vendor's sounding board.

The owner must not unilaterally call gray areas black or white. The job of re-verification is to settle what is decidable and route the gray into escalation correctly — not to replace internal asset review (Vol. 8 (in preparation)). The owner's independence is independence from the vendor, not from internal governance.

07Guaranteeing independence by process

Leave re-verification to an individual's diligence and it hollows out exactly on the tightest timelines. Force independence through process.

• Codify the blind: At receipt, split the vendor's verdict file out and write into the SOP that it stays closed until the independent read is done.
• Double-check threshold: High-risk assets (new products, comparative claims, patient-facing) pass a cross-check by a second reviewer, not the owner alone.
• Mandatory delta log: Record FN/FP/match counts every time. A vendor chronically high on FN becomes a corrective-action target under the Production Quality Management series.
• Signed verdicts: Record by name who did the re-verification. Align the record format with the documentation policy in Vol. 10 (in preparation).

08The record format: the re-verification summary

Capture the result on a single sheet attached when the asset goes to internal review. The requirement: every verdict traces back to a provision.

With this sheet, internal review starts from "what the owner independently confirmed and what was raised unresolved," not "what the vendor said." Whether the owner "just passed it through" or "re-drew the line independently" is now distinguishable in the record — the final latch that turns the owner's moral and regulatory responsibility, set out in Vol. 2, into something verifiable.