Advanced · Work and documents · module 106 of 155
Processing long documents in parts
Summarise a long document without losing exceptions or references.
After this lesson
You process a long document in clearly defined parts, with a location for each point and a check on what was lost.
In view · Step by step
Processing a long document in parts
Divide by chapter, section or appendix and keep the original.
Main points, conditions and exceptions, each time with where they are found.
Show contradictions separately and check points in the original.
Part 1 of 3 · Split logically
Your preference for less movement is on. Choose each part yourself.
Why one big question falls short
A long report or set of regulations does not always fit completely into the context window. And even if it fits, details in a long input are sometimes overlooked, especially in appendices or in the middle. If you ask for a summary of eighty pages in one go, you will not know afterwards what each point is based on. So split the document into logical parts: chapters, sections or appendices. Work with a document you are allowed to share and keep the original with page numbers.
Summarise each part, with its location
Give each part the same instruction: main points, conditions, exceptions, figures and open questions, each with a reference to the page, article or section. That way every point remains traceable. Ask for a fixed format, for example a table with the columns point, type and location. Have the model state explicitly when a part contains nothing relevant, instead of filling something in. Because each part was given the same instruction, you can then merge the results fairly.
Merge and check back
Merge the partial summaries into one overview and ask for contradictions between parts to be shown separately. A rule in chapter 4 may be restricted by an appendix. Then spot-check: look up three points in the original and see whether the exceptions came along. Always check important conclusions in full. Note which parts you processed, so that it is clear what the summary does and does not cover.
New practice example
From explanation to a usable result.
You process a long document in parts, each time with the same instruction. Every point gets a source reference and exceptions stay visible.
Fictional practice situationFictional: the rules of use of a municipal sports hall run to 40 pages. Article 4.2 says the hall is open until 22:00; annex B says the hall closes at 18:00 on Sundays.
View a possible solution
This is how it can be done
Chapter 4 gives: open until 22:00 (article 4.2). Annex B gives: closing at 18:00 on Sundays. When merging, I put them together: open until 22:00, on Sundays until 18:00. Without annex B the summary would be wrong for Sunday.
Why this works
The source reference for each point shows where a rule comes from. When merging, you then also see which exception limits a general rule.
Make it slightly more difficult
Add a third part with a rule that contradicts the previous one. How do you show that contradiction without making a choice yourself?
Extra practice, at your own pace. You do not need to submit anything. This does not count towards an automatic assessment.
Your workplace · learning by doing
Make something. See what changes.
Checking the AI connection… You can already view the written example.
Present your assignment to Ende.
Read the answer, change one thing, and compare.
Previously held
New version
You remain in control
What do you want to improve in your next attempt?
On this device only. AI answers remain only in this page memory. This is self-review, not a grade.
Why this approach works
The source reference for each point shows where a rule comes from. When merging, you then also see which exception limits a general rule.
A step further
Add a third part with a rule that contradicts the previous one. How do you show that contradiction without making a choice yourself?
Try & discover · no obligation
Fill the context window
Make your input longer. Then reserve more space for the answer. Where is the limit?
Blue: inputGreen: answer spaceGrey: free space
The specified input and reserved output fit together in this window.
Practice model, not a real tokenizer or product limit. Input also includes instructions and history. Fictitious rate: € 0,002 per 1.000 input tokens and € 0,006 per 1.000 output tokens. Actual rates and calculation rules differ.
This trial works locally with fictitious data and does not count towards your lesson completion. It starts anew with a new lesson or reload.
A prompt to get you started
Below is section 3 of fictional hire regulations for a municipal hall. Make a table with the columns point, type (rule, condition, exception, amount or open question) and location (article number). Always include exceptions. If this section says nothing about a topic, write “not in this section”. Do not summarise the whole set of regulations yet. [Paste section 3 here]
Apply it
You had a 60-page report summarised in one go. An exception from appendix C is missing from the result.
Which approach best fits this situation?
- Ask for the same summary again, but shorter.
- Process the report section by section and appendix by appendix with the same instruction, noting where each point is found, and check the exceptions in the original.
- Leave out appendices from now on, because a summary is about the main text.
With JavaScript, you can check your approach and receive immediate feedback.
Test your insight
You summarise a long set of regulations in parts. What makes the end result easiest to check?
- One short summary without references, because that reads most smoothly.
- A reference to the article or page for each point, with exceptions and contradictions listed separately.
- Only process the first and the last section; that is usually where the core is.
Extra practice
Choose a fictional or public document of at least five pages. Process two sections with the same prompt and merge them. Then check three points in the original.
Section 3, article 3.2: the hall is available until 23:00 (rule). Article 3.4: associations from the municipality pay half (exception). Deposit: not in this section. When merging, it turns out that article 5.1 limits the hall to 20:00 on Sundays. I put that contradiction separately in the overview.
