Build a brief you can trace back to its sources, including the places where they disagree.
What you’ll finish with A short briefing with supporting passages, source dates and clearly marked gaps.
AI-generated guide · Content revised · Allow about 15 minutes for the exercise
The walkthrough
Start with a question
Write the decision you need to make before collecting links. For a product launch, ask what changed, who it affects and what is still unknown. This keeps a research session from becoming an endless list of interesting pages.
Collect the original evidence
Prefer the announcement, documentation or research paper behind a claim. Add independent reporting when it provides context. Check what the tool actually imported: a video transcript or webpage text may omit charts, comments and images.
Ask for a claim-by-claim brief
Request a source for each main claim and a separate list of disagreements. Keep published dates beside the claims so an older announcement is not presented as a new development.
Open the supporting passages
Read the cited passage, not just the linked title. A real citation can still fail to support the sentence next to it. Remove unsupported claims and label estimates as estimates before sharing the brief.
Text to start with
Replace the bracketed sections with your own details.
Using these sources, answer: [question]. For each main claim, give the source title, publication date and supporting passage or citation. Separate agreements, disagreements and unanswered questions. Do not turn an absence of evidence into a confirmed fact.
A complete worked example
This fictional source packet demonstrates a disagreement. The source labels are references within the exercise, not real publications.
The question and packet
Question: When can every branch use the new booking system?
[A] Project announcement, September 27: “The pilot starts October 12 in two branches.”
[B] Operations note, September 29: “All branches could join in November if the pilot succeeds.”
[C] Schedule correction, October 2: “No all-branch rollout date is approved. Pilot feedback is due October 19.”
Completed evidence table
Swipe or scroll across the table to see every column.
Completed evidence table
Claim
Evidence
Treatment
Pilot starts October 12 in two branches
A, September 27
Confirmed by the announcement; do not call it a full launch.
All branches join in November
B, September 29; C, October 2
Conditional possibility, followed by a newer statement that no date is approved.
Feedback is due October 19
C, October 2
Stated deadline.
All branches can use it now
None
Remove.
Expected briefing
The pilot is scheduled for October 12 at two branches [A]. A September 29 note suggested November expansion if the pilot succeeds [B], but the October 2 correction says no full rollout date is approved [C]. Feedback is due October 19 [C]. The packet does not establish when every branch can use the system.
Use the pattern on real sources
Keep the source title, date and supporting passage beside each claim. A newer source is not automatically more reliable, but a direct correction matters. Trace two reports back to their original announcement before treating them as independent confirmation. If an import omits a table, open it yourself or leave the dependent claim unresolved.
When it goes wrong
The tool reports November as a committed launch date.
How to correct it
Point to the conditional wording in B and the correction in C. Ask it to separate the pilot date from the unapproved rollout.
Finished when
Every sentence has a supporting reference, and the final answer retains the unresolved question.
Check the result
Does each citation support that exact claim?
Are two reports repeating the same original source?
Did imported text omit a chart or table needed for the conclusion?
Before paying
Try a small source set first. Upgrade only if source limits, research limits or collaboration features prevent a workflow you already find useful.