Working with long documents
This is where these tools are genuinely strong and where the failure mode is most expensive: a fluent summary of a document it skimmed.
- Say what the document isOne line of context before the question. A lease, a tender, a clinical guideline and a board paper are read differently, and the tool cannot tell which it is holding.
- Ask a question, not for a summaryA summary of a sixty-page document is a document you still have to read. Ask the thing you actually need to know, which is usually narrower and always more checkable.
- Make it point at the sourceAsk for the clause, the section or the page behind every claim. This is the single habit that separates useful work from a confident invention, because it makes the answer verifiable in seconds.
- Verify the two that matterNot all of it — that defeats the point. Check the two answers the decision actually rests on, against the section it cited. If the citation is wrong, stop trusting the rest of that session.
The work this covers
- A contract or bundle where the question is narrow and the reading isn't.
- A ruling, standard or Practice Standards revision where you only need what changed.
- A strata report, tribunal document or scope of works you have to price against.
- Your own notes, minutes or transcripts turned into a document with a structure.
Ask a question, don't ask for a summary
“Summarise this” is the weakest possible instruction: it has no criteria, so you get the average of what summaries look like. “What obligations fall on the tenant, and where does each one appear” has criteria, and it can be checked.
Everything in this module comes back to that: named questions, in your own words, with a requirement to point at where the answer came from so you can verify it in seconds.
The habits that stop the expensive mistake
- Require a location for every claim — clause, page, heading. Unverifiable answers get thrown out.
- Ask the same question twice in different words. Inconsistent answers mean it hasn't actually found the thing.
- Ask what's missing or unclear, not only what's there. This is where these tools earn their keep.
- Spot-check two answers against the document by hand. Every time, not just the first week.
Long is not unlimited
Very large documents still get truncated or handled in pieces depending on tool and tier, and a tool that has quietly dropped half the input will still answer confidently. Knowing how to detect that is part of the module.
Why Claude usually, and when not
Long input with one careful answer is the shape Claude handles best, and it is the default we teach for this module — see Claude for long documents. Short documents at high volume are the opposite shape and go the other way.
What this module covers
Work where the input is long: a contract, a bundle of reports, a tender pack, a year of meeting minutes. The failure mode here is specific and easy to miss — a summary that's accurate for twelve pages and subtly wrong for the last three.
- Summarising against your own checklist rather than accepting a general summary.
- Asking questions of a document instead of asking for its contents.
- Keeping the source open beside the output, and which parts always get checked against it.
- Comparing two versions of a document and getting the differences that matter rather than every changed comma.
- Working with scans and photographs of documents, and when that goes wrong.
What someone can do afterwards
Gets the three facts they needed out of a forty-page document in minutes, with a defensible account of what was checked and what was taken on trust.
Where it sits in the order
Anywhere after the first module. It's the highest-value module for legal, conveyancing, accounting and NDIS documentation work, and often the reason those teams book at all.
Where this module stops
It does not make anyone a reader of contracts. Where the document carries a regulated judgement — advice, a clinical decision, a tax position, a sign-off — the judgement stays with the qualified person, and no amount of careful summarising moves that line.
Get a training plan built for your business. Nine questions about how your business actually runs. You get a plan ordered for your work, a reading on where you're exposed, and one clear place to start. No account needed. Build your plan.
Start an enquiry