Editorial Review and Quality Assurance

Revision Priority Matrix

Rank requested changes by factual harm, reader value, compliance exposure, dependency, confidence, effort, deadline, and consequence if unresolved.

Free editable Markdown · Editors, writers, and project managers · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Revision item

Item ID: [Durable identifier]
Location: [Section, paragraph, screen, or asset]
Problem: [Observable issue]
Source: [Fact check, policy, review, research, stakeholder, or another]
Desired outcome: [What should improve?]
Reader consequence: [If unchanged]
Change risk: [What could be damaged?]
Decision owner: [Role]

Gate and priority

Mandatory gate: [Yes / No, with authority]
Factual or compliance risk: [Critical / High / Moderate / Low]
Reader value: [High / Medium / Low, with evidence]
Evidence confidence: [High / Medium / Low]
Dependency: [What must happen before or after?]
Reach: [Affected audience or surfaces]
Effort: [Small / Medium / Large, with estimate]
Deadline: [Date and reason]
Reversibility: [Easy / Costly / Difficult]

Decision

Disposition: [Do now / Test / Defer / Decline / Escalate]
Rationale: [Why this priority]
Sequence: [Order]
Owner: [Person or role]
Due date: [YYYY-MM-DD]
Acceptance evidence: [How completion is verified]

Required re-review is included.
Deferral has a trigger, not an indefinite backlog label.
Declined feedback receives an accountable explanation.

Revision plan

Batch or milestone: [Group]
Shared root cause: [If several items]
Reviewers affected: [Who must return?]
Final checks: [Facts, links, accessibility, proof, or another]
Status: [Planned / In progress / Complete / Blocked]
New evidence: [Change to priority]

How to use this template

Normalize feedback into specific issues with locations, evidence, consequence, and desired outcome.
Mark mandatory gates and remove duplicates, contradictions, and requests outside the approved scope.
Assess reader value, factual or compliance risk, evidence, dependency, effort, deadline, and change risk.
Sequence accepted work, assign owners and acceptance checks, and record deferred or declined decisions.
Reassess after major revisions and reserve final validation for every affected quality control.

Convert comments into revision decisions

Rewrite each request as a location, observed problem, reader or organizational consequence, and desired outcome. “Improve the intro” is not ready for prioritization. Identify its source and authority: verified correction, required policy, reader evidence, editorial judgment, stakeholder preference, or experiment idea. Combine comments that describe the same root cause and separate requests that hide several changes. Confirm whether an issue blocks publication, belongs in a later iteration, or falls outside the content’s purpose.

Prioritize consequence and dependency

Apply hard gates first. Then compare reader value, evidence strength, reach, reversibility, deadline, and effort. A one-minute correction to a misleading date may outrank a large stylistic rewrite; a structural fix may precede dozens of sentence comments because later wording depends on it. Use descriptive ratings with written reasons instead of false mathematical precision. Include the consequence of not changing and the risk of changing. A proposed improvement with weak evidence and high disruption may deserve a small test rather than full revision.

Protect scope and accountability

Create a sequenced revision plan with owners, decision dates, dependencies, and acceptance evidence. Reserve capacity for rechecking facts, links, accessibility, and layout after changes. When time is limited, explicitly defer lower-priority work instead of silently ignoring it. Communicate declined requests with a reason tied to audience, brief, or evidence. If a late stakeholder tries to bypass the matrix, use the governance escalation path. Revisit priorities when new evidence or a changed deadline alters consequence.

See the fields in context

Fictional example: registration guide revisions

Hillpark Courses and its feedback are invented.

Item A: Correct an outdated fictional registration deadline; mandatory factual gate, small effort, do now.
Item B: Move eligibility before the form link; high reader value and prerequisite for later line edits, do next.
Item C: Replace every sentence with a more playful voice; weak evidence and high disruption, decline.
Item D: Add a worked example requested by interviews; useful but not blocking, schedule after A and B.
Final check: Revalidate links and rendered dates after the structural change.

Frequently asked questions

Should effort lower the priority of a serious issue?

Effort affects planning but does not cancel a mandatory or high-harm problem. Delay publication, narrow scope, remove the claim, or allocate more resources when necessary.

Can priorities be calculated automatically?

Automation can organize inputs, but written reasoning and authority remain necessary. Hard gates, dependencies, uncertain evidence, and unequal harms do not reduce safely to one formula.

How should conflicting feedback be ranked?

Resolve what each reviewer is protecting, compare authority and evidence, and escalate material conflicts. Do not assign both contradictory changes to the writer.

What makes a deferral responsible?

Record why it can wait, who owns it, what triggers reconsideration, and any interim control. An unowned item with no condition is abandonment, not planning.