Source-scoping workflow

How to Scope AI Context to Selected Sources

Control the evidence boundary before you ask for synthesis. This workflow keeps a research question, selected sources, verification notes, and the resulting draft visibly connected.

ChatGrid EditorialPublished October 9, 20266 minute readDemand and difficulty unmeasured

Method and ownership note: ChatGrid publishes this workflow. It describes a method that can be used on ChatGrid's visual canvas, where connected sources, chats, and Cards are verified product behavior. It does not claim that source selection makes an AI response automatically correct.

Direct answer

The working method

To scope AI context well, define the question and admissible sources before prompting. Give every source a stable name, ask source-specific questions first, require a page or timestamp locator for material claims, and place unsupported or out-of-scope ideas in a separate lane. Only run cross-source synthesis after the source-level notes pass a manual check. The result is a bounded evidence workflow: the model may help retrieve and organize, while the researcher still decides what counts as support.

01Question
02Sources
03Checked evidence
04Output

Start with an evidence boundary, not a broad prompt

A prompt such as “research this topic” hides the most important editorial decision: which material is allowed to influence the answer. Write a one-sentence research question, then list the sources that may answer it. If you are comparing an explainer video with a policy document, name those two items and exclude background notes, old drafts, and unrelated board material from the first pass.

Give the boundary a purpose as well as a list. “Use Source A for the speaker's explanation and Source B for the formal definition” is more useful than “use both sources.” Google’s Gemini Notebook help makes the same practical distinction: when several sources are selected, naming them in a specific question helps narrow retrieval. Treat that as a workflow technique, not proof that any tool will obey perfectly.

  • Research question: the exact decision the evidence must support.
  • Included sources: stable titles, URLs or filenames, and publication dates.
  • Excluded context: tempting material that is not admissible for this answer.
  • Required locators: page, section, timestamp, or another reproducible pointer.

Create a source inventory before the conversation

Use one small record for each source: source ID, author or publisher, title, date, format, rights or access note, and the question it can answer. The ID can be plain—PDF-1 or VIDEO-1—but it must remain stable in prompts, notes, and the final fact check. A filename such as final-v7.pdf is not a useful identity once several versions appear.

Add a condition field for what the AI actually receives. A PDF may contain selectable text, page images, or both. A video workflow may receive a transcript rather than the visual track. Record that distinction before asking questions, because it changes which claims can be supported. The inventory prevents a transcript-derived answer from being described later as full video analysis.

Ask one source at a time before asking for synthesis

Run a source-specific pass for each item. Ask for the source's answer to the research question, the strongest passage or segment, qualifications, and anything the source does not establish. Do not ask for polished prose yet. The output you want is a compact evidence note that can be checked against the original.

Use the same question structure across sources so differences remain visible. If Source A uses a term differently from Source B, preserve both definitions rather than asking the model to reconcile them immediately. Early reconciliation often erases the exact disagreement that makes a comparison valuable.

  • What does this source explicitly claim?
  • Where is the supporting passage or segment?
  • What conditions, dates, or populations qualify the claim?
  • What would be an overstatement of this source?

Verify the locator, then classify the claim

Open the original at the supplied page or timestamp. Check whether the wording, speaker, and nearby context match the note. For a PDF, inspect tables, footnotes, captions, and page headers when they affect meaning. For a video transcript, replay the segment and look for an on-screen chart, demonstration, or edit that the text does not capture.

Classify each candidate as supported, qualified, conflicting, unsupported, or not checked. “Qualified” is useful when the source supports the core statement only under stated conditions. “Unsupported” means the current source pack does not establish it; it does not necessarily mean the idea is false. This vocabulary keeps absence of evidence separate from contradiction.

Synthesize only accepted evidence

Now ask the cross-source question using only the accepted and qualified notes. Require the synthesis to keep source IDs and locators attached to the statements they support. If two sources disagree, the output should state the disagreement and its likely cause—different scope, date, definition, or evidence—without inventing a winner.

Draft from the synthesis, then run a source-debt pass. Highlight every sentence that contains a checkable external claim. Each should point to an accepted evidence note, be rewritten as analysis, or be removed. The method cannot eliminate model error, but it makes unsupported transitions easier to see before publication.

Copy this seven-line scope block

Place this block at the top of the board or research note: Question; intended output; included source IDs; excluded context; required locators; claim-status vocabulary; and final reviewer. Reuse the block in the drafting prompt so the evidence contract stays visible when the work moves from extraction to writing.

When a new source becomes necessary, add it deliberately. Record why it entered, which gap it fills, and whether it changes any accepted claim. That small change log is more trustworthy than quietly expanding context until the answer sounds complete.

Frequently asked questions

Does selecting sources guarantee a grounded AI answer?

No. Source selection narrows the available context, but the response can still omit qualifications, misread a passage, or supply an inaccurate locator. Material claims still need manual verification against the original source.

How many sources should one AI research question use?

Use the smallest set that covers the decision. Start with source-specific passes and add material only when you can name the evidence gap it fills. A larger source count is not automatically better.

What should happen to useful information outside the scope?

Move it to an out-of-scope or follow-up lane with its source attached. It can seed another question without silently influencing the current answer.

Primary sources

  1. Add or discover new sources for your notebook

    Google Gemini Notebook Help

    Primary documentation for selecting sources and the transcript-only treatment of YouTube imports.

  2. View video transcripts

    YouTube Help

    Primary documentation for transcript availability and jumping from transcript lines to video moments.

  3. Artificial Intelligence Risk Management Framework 1.0

    National Institute of Standards and Technology

    Public primary document used as a reproducible PDF example.

  4. Mastering AI Risk: NIST's Risk Management Framework Explained

    IBM Technology

    Public captioned video used as the paired-video example in ChatGrid's mixed-source workflow.

Continue the workflow