Editorial Review and Quality Assurance

Proofreading Signoff

Complete and record the final text, display, punctuation, formatting, link, metadata, and asset checks on the exact version scheduled for publication.

Free editable Markdown · Proofreaders, editors, and publishers · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Release candidate

Asset title and URL/path: [Enter]
Release candidate version: [Enter stable version or commit]
Proof environment: [Preview URL, device, and browser]
Structural review complete: [Yes / No / Not required]
Fact and subject review complete: [Yes / No / Not required]
Copyedit complete: [Yes / No]
Content freeze owner and time: [Name, date, time zone]

Text and consistency pass

Names, product terms, dates, figures, units, and quotations match approved sources.
No words, sentences, list items, or sections are accidentally duplicated or missing.
Spelling, grammar, punctuation, capitalization, and hyphenation follow the style guide.
Headings, labels, buttons, list items, and table entries are parallel and consistent.
Cross-references, section numbers, footnotes, and visible dates are correct.
Placeholder text, internal comments, and unfinished markers are absent.

Rendered page and asset pass

Page title, description, H1, canonical, and social preview refer to the correct asset.
Internal, external, email, anchor, and download links open the intended destination.
Images, video, charts, captions, credits, and alternative text are present and paired correctly.
Tables, code, quotations, and callouts remain readable on narrow and wide displays.
Keyboard-operable controls have clear labels, focus, states, and error feedback.
Structured data and visible content do not contradict one another.
The not-found, sign-in, or error state was checked where it matters.

Correction log

Duplicate for every defect.

Issue ID and location: [Enter]
Observed problem: [Describe exactly]
Severity: [Blocking / Important / Minor]
Correction: [Write the approved change]
Applied by and version: [Name and version]
Verified by: [Name, date, environment]
Status: [Open / Fixed / Accepted exception]

Signoff and live check

Open blocking issues: [List or None]
Accepted exceptions and owner: [List or None]
Proofreader decision: [Approve / Return / Approve with named exception]
Proofreader and timestamp: [Name, date, time zone]
Publisher and release version: [Name and version]
Live URL: [Enter after release]
Live checks repeated: [Links / Assets / Metadata / Main action]
Post-publication issue owner: [Name/team]

How to use this template

Freeze and identify the final candidate after substantive editorial and factual review.
Proofread the text in separate passes for meaning-sensitive details and surface consistency.
Test links, assets, metadata, controls, and layout in the intended environment and viewports.
Log every correction and verify it on the same release candidate.
Record conditional signoff, publish, and complete a focused live-page check.

Enter proofreading only after substantive decisions are closed

Proofreading is the final quality pass, not the moment to solve a weak argument or rebuild the page. Confirm that structural editing, fact-checking, subject review, and copyediting are complete and that one version is designated for release. Ask the author and stakeholders to stop making parallel edits during the pass. Reviewers miss small errors when they are also evaluating whether whole sections belong. Record any late substantive issue separately and return the page to the appropriate stage; when it comes back, begin a new signoff on a named version rather than carrying an approval forward.

Inspect both language and rendered behavior

Read slowly for omissions, duplicated words, names, punctuation, capitalization, heading consistency, list parallelism, and accidental changes to numbers. Then test the page as a user would: open links, use controls, view downloads, inspect captions and alternative text, and check narrow and wide displays. Confirm that the title, description, canonical URL, breadcrumb, publication date, and visible heading describe the same page. Dynamic components, line wraps, and copied text can introduce problems that are invisible in a document editor. If the content has localized versions, each locale needs a qualified pass in its own rendered context.

Make approval traceable and conditional

Use a correction log rather than changing the final version silently. For each defect, record its location, correction, owner, and verification status. Distinguish blocking errors from acceptable known limitations and require explicit ownership for any exception. The signoff should name the version, environment, proofreader, approver, time, and scope. After release, perform a short live check because deployment, caching, redirects, or missing assets can produce issues that were not present in preview. A signature means the listed checks passed on that version; it is not a permanent claim that the page will remain correct.

See the fields in context

Fictional example: downloadable event guide

Northbridge Week is invented. The dates, URL, and corrections below demonstrate a signoff record only.

Candidate: Fictional event guide RC-3, checked in preview at desktop and mobile widths.
Blocking issue: The registration button linked to last year's imaginary form; it was corrected and reopened successfully.
Minor issue: One heading used “Check-in” while the approved event term was “Arrival”; the label was aligned.
Decision: Approved RC-4 after both fixes, with no open exceptions.
Live check: Title, primary button, PDF download, and hero image were verified immediately after the fictional release.

Frequently asked questions

Should the author proofread their own work?

The author can run a pass, but a fresh reviewer often sees omissions and display problems the author has learned to overlook. Higher-risk assets benefit from independent signoff.

Is a spellchecker enough?

No. Automated checks can flag patterns but cannot reliably verify names, numbers, links, intended wording, asset relationships, or rendered interaction.

What invalidates a signoff?

Any change outside the approved correction log may require rechecking. The scope depends on the change, but a different release candidate should never inherit approval automatically.

What should the live check include?

Prioritize elements that deployment can change: the URL, title, main action, key links, downloads, assets, redirects, and access or indexing state.