NotebookLM Tutorial: Check Sources in Gemini Notebook

Updated September 8, 2026 · Published by FarsiVid

If you are looking for a NotebookLM tutorial and now see Gemini Notebook, you are looking at Google’s renamed research product. Google announced the change on July 16, 2026. The useful starting point remains the same: add sources, ask a focused question, and inspect the evidence behind the answer.

This guide uses two short, fictional documents to show how to catch a source conflict. You can repeat the exercise without uploading private notes or buying access to advanced features. The expected result below is our analysis of the sample documents, not a claimed output from a hands-on product test.

First, distinguish the product name from the workflow

The official rename announcement says Gemini Notebook remains a standalone product and describes deeper integration with Google’s other tools. Availability of newer features can depend on the account and rollout. The exercise here needs only sources and chat, so an absent advanced feature does not prevent you from learning the source-checking method.

Use the product link in Google’s announcement rather than an advertisement for a similarly named browser extension. Create one notebook for one question. Mixing unrelated research into a single notebook makes it harder to tell whether a retrieved sentence belongs to the decision you are making.

Prepare two sources with an intentional disagreement

Copy the following original examples into two separate plain-text documents, keeping their titles. They describe an invented community workshop. The dates and prices are exercise data, not a real event.

Source A: workshop plan, version 1

Fictional workshop plan — version 1 — 1 September 2026
The photo-organizing workshop is planned for 18 September 2026.
It has 20 seats. The proposed fee is $12 per attendee.
No room has been assigned.
This is a draft plan, awaiting organizer approval.

Source B: organizer update

Fictional organizer update — 5 September 2026
The photo-organizing workshop is confirmed for 19 September 2026.
The capacity remains 20 seats. The approved fee is $10 per attendee.
This update replaces the date and fee in the 1 September draft.
The room will be announced later.

Add both documents as sources and give them distinct names. Google’s source documentation covers supported import formats and source selection. Small text files make this first exercise easier to inspect than a scanned PDF with uncertain text recognition.

Ask a question that requires evidence, not just a summary

Use this prompt with both sources selected:

Using only these two workshop sources, make a table of the final date, fee, capacity and room. Cite the evidence for each field. Identify disagreements and explain which source resolves them. If a fact is missing, mark it “Not stated.”

The table below is the answer key. Compare the tool’s actual response with it field by field.

Field	Expected interpretation	Reason
Date	19 September 2026	Source B explicitly replaces the draft date.
Fee	$10 per attendee	Source B gives an approved replacement fee.
Capacity	20 seats	Both sources agree.
Room	Not stated	Neither source assigns a room.

A newer timestamp alone is not the reason to prefer Source B. Its explicit replacement statement and confirmed status resolve this particular conflict. If that sentence were missing, the honest result could be “conflicting sources” rather than a quietly chosen date.

Open the citations and audit one claim at a time

Google’s chat instructions describe inline citations that let you inspect quoted source context. Open the citation for the date, then check that it supports the date actually written in the response. Repeat for the price and room. A citation’s presence is not proof that the sentence is supported.

With very short sources like these, Google notes that a citation may reference the whole document rather than an individual passage. In that case, open the named source and compare the relevant sentence yourself. A whole-document reference does not remove the need for that check.

1. Match the source: is the citation pointing to the draft or the confirmed update?
2. Match the scope: is it discussing this workshop, rather than an unrelated event in a longer file?
3. Match the claim: does the source actually state the answer, or is the response adding an assumption?
4. Check omissions: did the response acknowledge the missing room and the superseded date?

Now deselect Source B and ask the same question. The tool no longer has evidence for the confirmed September 19 date. This variation tests whether you understand the source boundary, rather than whether the first answer sounded polished.

Handle updated sources deliberately

Current Google documentation says eligible imported Google Drive sources can sync automatically every few minutes while the notebook is open, with a manual sync option when needed. Other uploaded source types can require replacement when the original changes. Check the current behavior for your source type in the source guide; do not assume every imported file is either permanently frozen or always live.

For consequential research, keep a dated copy of the evidence you used and record the source’s version. If a source changes after you save a conclusion, repeat the relevant questions. A beautifully organized notebook can still preserve an answer based on an earlier policy.

Turn the answer into a reviewable note

Use a short template: question, source names and dates, answer, unresolved points, citations checked, and date checked. Google’s chat help describes saving answers to notes while preserving formatting and clickable citations. Add your own review comments rather than treating the saved response as a completed fact-check.

For our sample, a useful note would read: “Date and fee resolved by the September 5 update; capacity agrees across both files; room still missing. Do not send venue instructions yet.” That final action follows from the evidence and its gap. It adds more practical value than another paragraph describing what a research assistant can do.

Where this method stops

Source-grounded answers inherit source problems. An outdated manual, a fabricated report or an incomplete document can produce a well-cited but misleading result. Use sources you are entitled to upload, consider account privacy settings, and verify important conclusions against the underlying material.

If documents must stay on your computer, our local AI setup and evaluation guide explores a different workflow. For code, use the coding assistant test checklist, where running the code supplies evidence that a citation alone cannot provide.