Practical guide
How to build a focused topic briefing
Define the topic as a bounded question with a population, geography, timeframe, and decision. Select sources for distinct evidence roles, then group every item by the claim it changes.[1][2]
Why this gets difficult
A topic briefing becomes vague when the topic is a label instead of a question. Broad intake encourages background repetition and makes it hard to tell which evidence is genuinely new.[1][2]
A practical way through
- Rewrite the topic into a question that can be answered or updated.[1][2]
- Choose primary, specialist, and independent sources with different evidence roles.[1][2]
- Separate new facts, interpretation, disagreement, and unchanged background.[1][2]
- Review the source list when a recurring blind spot appears in the excluded trail.[1][2]
An example
The situation: A briefing labeled 'AI policy' gathers hundreds of items but cannot tell a product team what changed for a planned feature.[1][2]
What changes: The boundary becomes a named jurisdiction, product use, and launch window; official dockets lead and commentary is grouped by the obligations in question.[1][2]
What you get: The team receives a small set of relevant changes and an explicit list of unresolved policy questions.[1][2]
What to watch for
Sources worth keeping
How Scottie helps
Scottie can rank chosen sources against topic-specific priorities, combine shared coverage, and show excluded items when the boundary needs correction.[3]