Turn a long document into notes you can trace and use

1. Prepare a suitable source

Before uploading a file, check that you are allowed to use its contents. Avoid including personal information, confidential contracts or customer data unnecessarily. To test a workflow, use public material or an anonymized version of a document.

Inspect the quality of the input too. Scanned text, missing pages or a broken table may not be read correctly. Give files clear names and distinguish versions so the result is not based on the wrong document.

2. Ask for a map of the document first

Instead of immediately requesting a summary of everything, ask for the sections and the subject of each one. This map shows what the tool has understood and whether it has missed part of the source. Compare its headings and sequence with the original.

Next, define why you are reading. Are you looking for decisions, making study notes or comparing two versions? The same document needs a different output for each purpose, so describe the next step before requesting a detailed summary.

3. Connect answers to passages you can find

Ask for a section heading or another traceable reference with each answer. If the tool provides a citation, open it and read the supporting sentence. If page numbers are unreliable, use a heading and a short searchable phrase to locate the passage.

Ask the tool to separate answers that are not in the document. A summary that mixes general knowledge with the file’s contents is unsuitable as a report of that source unless those contributions are clearly distinguished.

Answer using only the supplied document.
1. Briefly explain its purpose and structure.
2. Extract the points relevant to [my topic].
3. Give a section heading or searchable supporting phrase for each point.
4. Preserve numbers and units exactly.
5. Put information you cannot find under “Not established in the document”.

4. Check figures and tables separately

Spot-checking a few sentences does not verify every calculation. Compare sample table rows with the source, read the units and check that percentages have not been confused with absolute values. If you requested a new calculation, its inputs and method should be explicit.

When comparing documents, record the date and status of each version. A wording change does not always mean the conclusion changed, while a small numerical change can have a substantial effect. Review the meaning as well as the text.

5. Prepare notes for the next step

Shape the final output for its intended use: an action list for a meeting, study questions or a team summary with source links. Keep important references and uncertainties. Shortening a document should not make its conclusions impossible to trace.

Before sharing, read the notes outside the conversation window. Put the document name, version, purpose and review status at the top so another reader knows what the summary refers to and how thoroughly it has been checked.

Your next-step checklist

Review each item before using the result.

Further reading

This guide suggests a workflow. Check the official source and the specific product page for current features and terms.

Related tools in the ElmosGPT catalog

NotebookLMClaudeNotion