Memuat
Memuat
Want to go deeper?
Join one of our courses or ask us directly on WhatsApp.
Picked from the software, topic, and level of “Claude from Zero to Expert Class #14: Summarizing Long Documents and Articles”.
Other ways we can help with Claude.
Learn with a mentor
Scheduled AI & Machine Learning courses with live guidance and a certificate.

Midjourney Course: Create Stunning AI Images from Text
★ 4.9

DALL-E Course: Creating Professional AI Images from Text
★ 4.9

Stable Diffusion Course: AI Art from Beginner to Professional
★ 4.9
Have it built for you
No time to learn Claude? Our team can do the project for you.

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production
★ 4.9

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business
★ 4.9

AI Image Creation with Midjourney — Cinematic AI Art for Business
★ 4.9
Get notified about new Claude classes
At most one email a week. Unfollow anytime with one click.
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Hi, and welcome back. After plenty of writing, we now learn the opposite: reading fast with Claude's help. In this episode we summarize long documents and articles: setting the purpose of a summary, writing a safe prompt, making layered summaries, turning an article into teaching material, and checking whether the summary is right.
If we only write, summarize this document, Claude gives a general summary. It's not wrong, but it's often not very useful, because Claude doesn't know who will read it. One document can have many summaries that are all correct. A warehouse report read by the director, the warehouse head, and the finance team needs a different summary for each. So before asking for a summary, answer two questions: who is this summary for, and what decision does it support? The first type is the gist in one sentence. It suits a quick message to your team or a boss who only needs the big picture. Second, key points, usually the three to seven most important ones. This is the type we use most often. Third, a section-by-section summary, for example by report chapter or meeting agenda item. It works well when each section has a different owner. Fourth, a summary for a specific reader. Claude picks what matters most for that reader's role, such as costs for the finance team. You can combine these types in one request, for example a one-sentence gist followed by five key points.
Let's practice with Dewi. The first block is the data: the third-quarter warehouse evaluation report, twelve pages long, pasted straight into the chat box. The purpose block names the reader, the director, and the decision: whether to hire more warehouse staff. The format block asks for one gist sentence, three findings, two risks, and one recommendation, one hundred fifty words at most. The limits block matters most. Claude may only use the report, and must write not in the report if something really isn't mentioned. This limit reduces the risk of Claude filling the gaps with guesses that sound convincing. Dewi sends the prompt. Notice that she doesn't just send the report on its own, but with its purpose and limits. While we wait, notice that the twelve-page report didn't need tidying first. Text copied from an office document is usually good enough for Claude to read. Claude gives a summary in the requested format: one gist sentence, three findings with numbers, two risks, and a recommendation to add one part-time warehouse worker. Ninety-five hours of overtime feels like a lot. Before reporting it to the director, Dewi asks Claude to quote the original sentence. Claude shows the quote from section three point two. Dewi opens the original report, matches the sentence, and now she's sure the number is right. This is the most important habit when summarizing: for numbers and facts that will drive a decision, ask for the original quote and match it yourself.
The next technique is the layered summary. Start with a one-sentence gist to get the big picture. If the document is important, ask for five key points. At this stage, you already know whether the document is worth reading further. For the sections relevant to your work, ask for a section-by-section summary. You can skip the rest. Finally, questions and answers. Ask something specific, such as: according to this report, what do I need to do this week? This way, you don't need to read twelve pages to find out that only two of them really matter to you. From the same report, Dewi needs another version for Andi, the warehouse head. Andi doesn't need the director's recommendation. He needs to know what to prepare. Claude writes four action points in casual language, ready to send on WhatsApp. One document, two summaries, and two readers who are both well served. Before sending, Dewi still reads all four points. If something isn't in the report, such as the two-hour overtime limit, she checks first whether it's an office decision or Claude's suggestion.
Now an example from education. Mr. Hendra, a science teacher at Cerdas Tutoring, pastes a long article about acid rain. He asks for four key points, three difficult words, and two comprehension questions for eighth graders. The right panel shows tidy teaching material. The summary uses language for junior high students, the difficult words get simple meanings, and the questions can be answered from the summary. Mr. Hendra just prints or shares this page. Preparing material that usually takes an hour is done in a few minutes. But Mr. Hendra still rereads every point. For lesson material, the scientific facts must be right, and the source article itself must come from a trusted website. Mr. Hendra knows not all his students are comfortable reading long texts. He asks for an easier version: sentences of ten words at most, plus one everyday comparison. Claude makes an easy version with short sentences. Acid rain is compared to weak lemon juice, something close to the students' own experience. From one article, Mr. Hendra now has two levels of teaching material. Fast readers get the full version, students who need help get the easy version, and both learn the same lesson.
Now the limitations. First, a summary can miss small but important details, such as exceptions, conditions, or footnotes in a contract. Second, meaning can shift. A sentence that originally said maybe can turn into definitely in the summary. For important decisions, that difference is huge. Third, very long texts are best split into sections, then the summaries of each section combined. How much Claude can read at once differs by plan, so check Anthropic's official documentation. Fourth, don't paste company secrets or personal data. Delete or mask the sensitive parts before summarizing. Fifth, a summary of someone else's article still comes from their work. Use it for learning, credit the source, and don't share it as your own work. None of these five points is a reason to stop summarizing with Claude. In fact, knowing them tells us which parts we can trust as they are, and which parts we need to check. To deal with this, keep three checking questions. First: what did you leave out of the summary? This question often brings up details that turn out to matter. Second: which part is the least certain? Claude will flag sentences that were originally estimates or possibilities. Third: quote the original sentence for a specific point. Then match it yourself against the original document, just as Dewi did earlier. In this episode we pasted text straight into the chat box. In the next session we learn to upload PDF files and ask about their contents. The screens in this video are simulations, so menus may differ slightly.
We've learned to set the purpose of a summary, write a safe summary prompt, make layered summaries for different readers, turn an article into teaching material, and use three checking questions. In the next episode, the last one in the writing session, we learn to translate and adapt the tone of writing for different readers. See you there!
Try these on your own after watching to lock in what you learned.
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
Notes are saved with the current video time and are only visible to you.
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.

Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
See our clients →