How do I decide what belongs in a quick-reference handout and what belongs in a full guide?
Quick answer
Put information in the handout when readers need it to act, choose, or check something quickly. Put background, reasoning, examples, exceptions, and detailed explanations in the full guide. For each item, ask what the reader needs at the moment of use, whether it can be understood without extra context, and what happens if it is omitted. Make the handout useful on its own, not just a list of links.
The question, the details, the next step.
I’m making both a one-page quick-reference handout and a longer guide about preparing for a community book discussion. How do I decide what goes where without just shrinking the guide?
Start with the reader’s task, not the page limit. The handout should help someone take a next step while preparing or participating. The guide should help them understand how to do that step, make choices, and handle complications.
For every piece of draft content, ask:
- Does the reader need this at a glance to act or check something?
- Can it make sense without a paragraph of explanation?
- Would leaving it out make the reader less able to complete the task?
If it is brief, immediately usable, and clear on its own, it is a handout candidate. If it needs a reason, example, alternatives, or qualification, it likely belongs in the guide. Some information can appear in both, but serve different purposes: the handout gives a short cue; the guide explains it.
What should I do with important information that needs context, like how to choose discussion questions?
Keep the usable cue in the handout and put the method behind it in the guide. For example, the handout might say, “Choose two open-ended questions; leave room for follow-up.” That is a prompt someone can use quickly. The guide can explain what makes a question open-ended, show a weak and stronger example, and suggest how to adapt questions for different group sizes or reading experiences.
A short note can point readers toward the fuller explanation, such as “For examples and ways to adapt questions, see the section ‘Choosing questions’ in the guide.” Make the pointer specific, so readers know what they will find. Don’t use the handout as a dumping ground for every detail that did not fit elsewhere.
Can you show how you would sort a few items for this book-discussion example?
Here is a hypothetical sorting example, not a prescribed format:
- “Bring the book and a way to take notes.” Handout: yes. It is a short reminder the reader can act on. The guide may explain optional preparation, but need not repeat the reminder at length.
- “Write down one passage you want to discuss.” Handout: yes. The guide can explain how to choose a passage and offer an example if readers need help.
- “Start with questions that invite more than a yes-or-no answer.” Handout: short cue. Guide: explain the idea and demonstrate how to revise a closed question.
- “If the conversation stalls, return to a specific passage.” Handout: brief fallback. Guide: describe how to invite observations without putting someone on the spot.
- “The group may use different discussion styles.” Guide: explain possible approaches and how to choose one. Handout: include only a short label or reminder if the reader needs it during the meeting.
The test is not whether a sentence is important. It is whether the reader needs its full explanation at the moment they use the handout.
How do I keep the handout useful on its own while still making the guide feel worth reading?
Give the handout a complete, small job: orient the reader, show the few actions or prompts they need, and provide a next step when useful. Avoid unexplained abbreviations, vague references like “see below,” or instructions that only make sense after reading the guide.
Make the guide valuable through depth rather than repetition. It can explain choices, show examples, address common snags, and offer optional approaches. Review the pair side by side: each handout line should either help with immediate use or point to a clearly named explanation. Each guide section should add understanding or support a decision, not merely restate the handout in longer sentences.
Try this sorting worksheet: Item | Reader’s task | Handout cue | Guide explanation | Reason for keeping it here. Fill in one row per idea, then read the handout by itself. If a cue is unclear without the guide, rewrite it or add a brief clarification.
A practical checklist
Name the specific task the reader will use the handout to complete.
List each idea separately before assigning it to a format.
Keep short, self-explanatory actions and prompts in the handout.
Put reasoning, examples, alternatives, and complications in the guide.
For content used in both, give the handout a cue and the guide a fuller explanation.
Read the handout by itself and replace unclear references with explicit wording.
A few more useful answers
Should the handout include every key point from the full guide?
No. Include what readers need for the handout’s immediate task, not a miniature version of every section. A specific pointer can direct readers to relevant detail.
What if a handout instruction could be misunderstood without an explanation?
Rewrite it so the action is clear on its own, or add a very short clarifying cue. Put the fuller reasoning or examples in the guide.
How can I tell whether I have repeated too much between the two?
Compare each overlapping item’s purpose. If both formats provide the same wording and detail, decide which is the better home. If one gives a cue and the other explains or demonstrates it, the overlap serves different needs.