Check an AI summary against its source document
Every claim in a summary needs a location in the source. Here is a repeatable way to mark them.
Turn documents and rough notes into work you can check.
Writing work on this site starts from a document you already have: a contract, a report, a long thread, or a draft an assistant produced in a hurry. The pages below treat the assistant as a first pass and the source as the authority. Each one walks through a single job — checking a summary against the document it came from, summarising something long in sections that can be verified, or rewriting an email without moving a date, a price or a promise.
What the four pages share is a habit rather than a tool: write the claim down, write down where it came from, and keep both until the work is sent. The claim ledger is the browser version of that habit, and each guide explains the reasoning behind a column you would otherwise fill in from memory. If you are unsure where to begin, start with the summary check; the three kinds of drift it looks for turn up in almost every draft, and the same reading habit carries into the research brief workflow at the end of the collection.
Every claim in a summary needs a location in the source. Here is a repeatable way to mark them.
Section-by-section work costs a little more time and removes most rewrites.
A warmer sentence should not quietly become a new deadline.
Every material sentence in the brief should point back to a source register row.