How do I summarize without losing exceptions?

Watch the briefing

Watch the full video on YouTube

The short answer

Require exceptions alongside the main rule.

Worked example

FICTIONAL EXAMPLE; outputs ILLUSTRATIVE, not model-generated

What this does not establish

Original fictional inputs, mock outputs and editorial diagrams; no personal records, borrowed screenshots or actual model tests.

Full briefing transcript

A borrower collects equipment on Friday. Your short summary says return it the next day. But the original policy makes Friday loans due on Monday. The summary is shorter and less useful because it removed the condition that changes the answer. Start by keeping each important exception next to the rule it modifies, rather than treating it as optional detail.

This fictional policy has five clauses. Equipment is due by five in the afternoon on the next calendar day. Friday collections are the exception: they are due by five on Monday. Collection is allowed Monday through Friday, from nine until four. Renewals need staff approval before the deadline. Missing parts must be reported when equipment is returned. These are invented rules for an exercise, not an actual lending service.

Now define what the summary must preserve. We want three borrower facing bullets, but not at the cost of the return deadline, Friday exception, collection window, renewal condition, or missing parts instruction. Put that list in the request. Also prohibit adding holiday rules, fees, grace periods, or weekend collection arrangements. A length target is useful only when the essential meaning can still fit inside it.

Here is our deliberately flawed illustrative summary, not a captured model response. Return equipment by five the next day. Collect during weekday opening hours. Renew if you need more time. It loses Monday's exception, replaces exact hours with a vague phrase, and makes renewal sound like the borrower's choice. Read against the original clauses and mark those three losses. They are meaning changes, not merely differences in style.

The corrected version says return by five on the next calendar day; Friday collections are due by five on Monday. Its second bullet gives weekday collection from nine until four, and renewal only with staff approval before the return deadline. Its third says report missing parts at return. Three bullets still work because the exceptions and conditions remain attached to the relevant instructions. Concision comes from grouping, not deleting constraints.

Test the summary with two simple cases. A Wednesday collection is due Thursday by five. A Friday collection is due Monday by five. Both answers must match the original. Then check the remaining conditions separately: could a reader mistakenly assume a Saturday collection is allowed, or a renewal is automatic? Nothing here establishes a holiday procedure. If a real policy is silent on a case you need, ask its owner rather than invent an answer.

Require exceptions alongside the main rule. Before using a summary, compare the rule, exception, trigger, and consequence with the source. Scenario checks help expose omissions, but two passing examples do not establish that every possible case is covered. Keep the original available for questions beyond the summary. Next, we will separate a long message into requests, background, and unanswered questions without losing their dependencies.

Disclosures

AI-assisted production and synthetic narration. Original teaching examples and diagrams; linked third-party sources retain their respective rights.