Check a text before publication or client delivery

Return to the brief first

Confirm the audience, format, tone and required information before polishing the language. A perfectly corrected text can still be wrong if it no longer answers the brief. If the content contains names, numbers or technical strings, check those separately before keeping the resulting version.

Verify factual details against sources

Check names, dates, figures, quotes and links against their source. If something cannot be verified, flag the uncertainty instead of presenting it as established fact. Keep the original nearby whenever the change could alter how a passage is read or how several elements relate to one another.

Review language after the content is stable

Run spelling and typography checks after substantive changes. Inspect any correction involving names, approved wording or domain-specific vocabulary. Check names, numbers and technical strings separately. If the content contains names, numbers or technical strings, check those separately before keeping the resulting version.

Inspect the delivered format and files

Open links and attachments and view the actual exported or published format. File names, version labels and visible metadata can also matter to the client. Review the affected passage in its real context so the change still fits the rest of the text rather than looking correct in isolation.

Keep a record of what was delivered

Save the exact version sent to the client so later revisions start from a known reference rather than a parallel draft. Check names, numbers and technical strings separately. If the content contains names, numbers or technical strings, check those separately before keeping the resulting version.

Frequently asked questions