If review cycles keep drifting—or you’re shipping “final” files that boomerang for changes—you don’t have a talent problem. You have a cadence and criteria problem. Today’s post gives you both: a simple 2d/2d/1d review timetable and a QA rubric your team can apply at Concept, Draft, and Final.
What you’ll get
- A crystal-clear 2d/2d/1d review cadence
- A QA rubric (copy-paste) that separates must-change from nice-to-have
- A practical escalation path so work doesn’t stall
Related: build the intake/brief foundation first (see Intake → Brief → Review), then add role clarity (RACI for Creative Teams) so there’s exactly one Approver at each gate.
The 2d/2d/1d cadence (what it means)
- Concept/Direction — feedback due in 2 business days
- Draft — feedback due in 2 business days
- Final — approval due in 1 business day (or written risks)
If feedback is late: Ops/PM pings the Approver (single person) → Approver decides within 24 hours. No more slow-motion threads.
The QA rubric (use at every stage)
Scoring key: 3 = Ready to ship · 2 = Minor tweaks · 1 = Major revisions · 0 = Not acceptable
| Criteria | What good looks like | Must-change triggers |
| Meets Brief | Delivers the stated objective for the named audience; reflects the core message and “definition of done.” | Drifts from objective; wrong/undefined audience; core message missing; acceptance criteria unmet. |
| On-Brand & Voice | Tone/visual style match brand examples; consistent terminology; accessible reading level. | Off-voice/visual; banned phrases; inconsistent style; accessibility violations. |
| Accuracy & Compliance | Facts/claims supported; legal/privacy requirements satisfied; required disclosures present. | Unsupported claims; missing disclosures; privacy/legal risks. |
| Channel Fit & Specs | Correct format, dimensions, duration, safe zones; follows platform best practices. | Wrong specs/file types; crop/layout issues; ignores platform constraints. |
| Accessibility & Inclusivity | Alt text/captions provided as needed; sufficient contrast; inclusive language/imagery. | Missing alt/captions; low contrast; exclusionary or insensitive content. |
| Quality & Craft | Clean layout; grammar/links correct; version control followed. | Typos, broken links, layout errors; wrong assets; version confusion. |
Feedback rules
- Be specific (what/why).
- Prioritize: must-change vs nice-to-have.
- Make it actionable (suggest fixes/examples).
- Keep comments in the source of truth (doc/ticket)—no side-channel decisions.
Decision SLAs & escalation
- Concept: 2 days → If late, escalate to Approver → Approver decides within 24h
- Draft: 2 days → same
- Final: 1 day → same
Tip: At Concept, score Meets Brief and On-Brand heavily; at Draft, score all criteria; at Final, zero tolerance on Accuracy/Compliance and Channel Fit/Specs.
How to run a review (10-minute flow)
- Open the brief and restate the objective in one line.
- Apply the rubric, starting with Meets Brief and On-Brand.
- Capture must-change items first; then nice-to-have if time permits.
- Confirm the decision (approve / approve with tweaks / revise & resubmit) and the owner + due date for any changes.
- Update the source of truth and move the work to the next step.
Common failure modes (and quick fixes)
- Endless opinions: Use the brief and rubric to anchor decisions. Ask: “Does this change help us meet the brief?”
- Late feedback: Enforce 2d/2d/1d. If late, escalate and decide within 24h.
- Committee approvals: Name one Approver per gate in your RACI; others are Consulted or Informed.
- Spec misses at Final: Add a pre-flight checklist for Channel Fit & Specs.
Next steps
- Get the Creative Ops Playbook — map the cadence and rubric into your tool (Asana, Monday, Wrike, Jira, Smartsheet, Notion).
- Download the QA Rubric — copy the table above into your doc/ticket template so every review uses the same criteria.
Leave a Reply