Content Review Severity Rubric: Block, Fix, or Note

A practical creator content severity rubric can use three outcomes: Block for content that cannot proceed, Fix for a required correction that can stay within the current production path, and Note for optional guidance or information. The labels are a recommended house model, not a legal or industry standard. Their value comes from definitions that lead reviewers to the same action.

Define severity by release action

Severity should describe what happens next, not how strongly a reviewer feels.

| Level | Release action | Typical owner | |---|---|---| | Block | Stop publication or paid activation until resolved | Decision owner or specialist | | Fix | Return the current version for a required correction | Creator ops or brand reviewer | | Note | Do not hold release; record optional or future guidance | Reviewer |

A missing disclosure, unsupported objective claim, absent contracted deliverable, or expired usage permission may be a blocker, depending on facts and applicable rules. A misspelled product name could be a required fix. A subjective preference that the brief never required should usually be a note, not a hidden requirement.

Fit these actions into the creator content approval workflow so the label controls queue state, notification, and authority.

Write a complete finding

Every finding should contain five pieces:

1. Observation: what the reviewer can see or hear.
2. Rule: the brief, policy, contract, or source the observation conflicts with.
3. Severity: Block, Fix, or Note.
4. Action: the smallest change that can resolve it.
5. Evidence location: timestamp, frame, caption line, or landing-page field.

Weak: “Disclosure issue. Block.”

Useful: “At 0:02 the partnership disclosure is partly hidden by the caption background. Block paid activation. Move the disclosure above the caption area and keep it visible during the opening endorsement.”

The second version lets another reviewer verify the issue and lets the creator act without guessing.

Build category-specific examples

Do not publish one generic example and expect reviewers to infer every boundary. Create a small example set for claims, disclosures, offer details, rights, brand requirements, and production quality.

For claims, the FTC’s advertising guidance says advertisers need a reasonable basis for objective claims before dissemination. That supports a hard stop for an unsupported objective claim in U.S.-directed advertising. It does not mean every creative adjective is automatically an objective claim or that the same evidence standard applies to every product.

Example calibration set:

• Block: The video says a supplement cures a disease, outside approved language and support.
• Fix: The approved offer is 15 percent, but the on-screen text says 20 percent.
• Fix: A required product demonstration is missing from the submitted cut.
• Note: The reviewer prefers a tighter opening, but the existing opening meets the brief.
• Note: Suggest storing a clean background plate for future paid variations.

Use actual company examples only after removing sensitive information.

Prevent severity inflation

Reviewers often escalate a preference because a stronger label gets faster attention. That makes creators redo acceptable work and makes genuine blockers harder to see.

Require a rule reference for Block and Fix. If the reviewer cannot identify an agreed requirement or real risk, the feedback belongs as a Note or a proposed brief change. The RACI matrix for creator approval should identify who can accept a risk, add a requirement, or reverse a blocker.

Also prohibit severity from being based only on effort. A two-second text correction can still be a blocker if the ad would otherwise mislead. A difficult reshoot can remain a preference if the brief did not require it.

Calibrate and govern the rubric

Give reviewers the same five sample clips and ask them to classify the findings independently. Discuss differences in cited rules and release actions, not just labels. Update examples where reasonable reviewers diverge.

Track overrides and reopened findings. A high override rate in one category may indicate an unclear rule, missing authority, or a training need. It does not prove that an individual reviewer is poor.

Define who can downgrade a Block, what reason must be recorded, and which issues cannot be waived internally. An exception process cannot override applicable law, platform rules, contract limits, or the need to substantiate claims.

Give creators action-first feedback

Creator-facing notes should begin with the requested change, followed by the reason and location. Internal legal analysis or risk scoring can remain in the decision record when it would confuse the action.

Group duplicate findings, identify the version reviewed, and send one consolidated response. The severity model should reduce ambiguity, not expose creators to the organization chart.

The takeaway

Define severity by release action, require evidence and a rule for mandatory changes, and calibrate with realistic examples. Block, Fix, and Note work only when reviewers use the same boundaries and creators receive a precise next step.