A Recap Document is the structured, readable result Recap creates from one source. It keeps the useful details grounded in the original material, then makes three next steps visible: send time-based information to Calendar, export the document to Workspace, or start question-driven Learning.
The source can be a message, screenshot, webpage, PDF, document, video, saved post, or note. Recap starts with what you already have instead of asking you to begin from an empty prompt.
Why a source needs more than a summary
A short summary can tell you what something says, but it often leaves the next piece of work to you. You still need to identify dates, organize decisions, rewrite useful details, decide where they belong, and move them into another tool.
Recap treats readability as the first result rather than the final result. The document gives you enough structure to review the source and decide what should happen next without losing the original context.
How Recap turns a source into a document
The workflow has three parts:
- Bring in one source. Add or share the message, screenshot, link, PDF, document, video, saved post, or note you want to use.
- Review the Recap Document. Recap organizes the material into a structure that fits its purpose while keeping the source available for verification.
- Choose the next step. Send relevant details to Calendar, export the result to Workspace, or start Learning. The three choices remain available together.
You do not need to classify the source before adding it. Recap prepares the readable result first, so the choice is based on the actual content rather than an upfront form.
Four document modes
Recap uses four document modes to make different sources easier to inspect.
| Mode | Best for | What it emphasizes |
|---|---|---|
| Action | Notices, meetings, requests, and deadlines | What needs to happen, when, and what to check |
| Decision | Reviews, recommendations, and competing options | Options, trade-offs, evidence, and the decision to make |
| Understanding | Explanations, articles, and complex ideas | Main ideas, supporting evidence, and important relationships |
| Reference | Documents and material you may revisit | A readable structure that preserves detail and context |
These modes are not separate tools. They are different ways of presenting the same foundation: one source becomes one source-grounded Recap Document.
Send time-based details to Calendar
When a source contains a strong time signal, Recap can surface a Calendar Sheet. This is useful for appointments, meetings, classes, events, deadlines, reminders, and similar information that belongs in a time system.
The Calendar Sheet is reviewable. You can confirm, edit, or cancel before sending anything to your calendar. Recap prepares the details; it does not replace your calendar or remove your control over the final action.
Even when Calendar is surfaced, Workspace and Learning remain available.
Export useful material to Workspace
Some sources are worth keeping rather than scheduling. A Recap Document can be exported to the notes, documents, tasks, or workspace tools you already use.
For example, a meeting message may become an Action document, a product review may become a Decision document, and a detailed PDF may become a Reference document. The useful structure moves with the result, reducing the need to reread and manually reformat the source.
Recap is the preparation layer before your workspace, not a replacement for it.
Start PBL Learning when a source deserves more attention
Learning is for sources you want to understand rather than simply save. Recap turns the document into a question-driven PBL session with different perspectives, concise answers, evidence, explanation, reflection, and follow-up questions.
The source remains the foundation. Learning starts after the Recap Document, so questions and answers stay connected to the material that prompted them.
Example: a workshop invitation
Imagine receiving a workshop invitation as a screenshot.
Recap first creates a readable document containing the topic, organizer, date, location, requirements, and useful context. Because the source includes a clear date, Recap can also prepare a Calendar Sheet for review.
You can then choose to:
- send the confirmed workshop details to Calendar;
- export the Recap Document to a project workspace; or
- start Learning if the workshop topic deserves deeper preparation.
The source is processed once, but the result can support more than one next step.
What Recap does not replace
Recap is not another calendar, notes app, task manager, read-later queue, or open-ended chatbot. Those tools are useful destinations or alternatives for specific jobs.
Recap focuses on the missing step immediately after capture: turning raw incoming information into something readable, reviewable, and ready for the system or activity that comes next.
Questions about Recap Documents
Does every source become a Recap Document?
Yes. The structured document is the default result and the foundation for Calendar, Workspace, and Learning.
Does Recap automatically send information to other tools?
No. Calendar details are presented for review, and you choose whether to send or export a result. Recap keeps the next step visible without taking irreversible action for you.
Is Learning required?
No. Learning is one of three parallel next steps. Use it when a source deserves deeper understanding; otherwise, you can send time-based details to Calendar, export the document, or simply keep the readable result.
Can one source use more than one next step?
Yes. Sending a Calendar Sheet does not remove Workspace or Learning. The options remain available because one useful source can support scheduling, saving, and understanding at the same time.
Continue in Recap
Turn this source into a Recap Document
Make it easier to read, then send time-based details to Calendar, export it to Workspace, or start PBL Learning.