Gemini Notebook: check reports after a source changes

Google describes two behaviors here with Gemini Notebook.

• You can have a Drive source which is auto-updating.
• You have a pre-generated Studio report which retains the content.

So when a user is reading from a pre-saved report they have to check the content of that report against the source they want to be reading from.

In our browser test, we had a fake workshop doc to work with. We edited the date and capacity in Google Docs.

• The new facts appeared in the notebook source viewer.
• The new facts appeared in the answer to a new question within the existing chat.
• The old facts remained in the pre-change report.
• The new facts appeared in a second doc report.

Google, Google Docs and Gemini Notebook are trademarks of Google LLC. HoldMyTwist is not affiliated with or endorsed by Google.

Before you start

Use Gemini Notebook (opens in a new tab) from a desktop browser, with a Google Account. The practice document needs to be something you have permission to use. We used a private, made-up Google Doc and one source. We made Document reports without having to do the paid upgrade. The account display did not establish its exact plan label. Check what features and usage allowance you have available in your account. This test does not establish a fixed number of reports.

Don't put private stuff in the exercise. It might be faster to just check the source itself for a short document, instead of using AI. The made-up example doesn't have many facts, so it's easier to see the difference. There is no need to upgrade for this exercise.

1. Set facts you can check independently

We had one Google Doc file for a fake workshop. It was our practice file.

Revision A of the doc had a date of 12 November 2026, capacity of 18 people and venue of Cedar Room.

Then we updated that doc into revision B.

It had a date of 19 Nov 2026, capacity of 24 people and venue of Cedar Room.

No real event happened.

Make a Google Doc file with the title Fictional workshop source.

The text of revision A in that file should be:

For the test use a separate notebook. In the source search control use Drive. Search for the exact title of the document, while it still contains revision A. Confirm the result. Import only this one file. In the source viewer look at the document text. Note that Source guide is a separate AI summary, not the document text.

Before editing the Google Doc, create a baseline report via Studio > Reports > Document > Create your own. Use the same exact request for both reports in section 4. Call this first report Report A.

2. Confirm the changed source reached the notebook

Replace the Google Doc text with revision B below:

Wait for Saved to Drive. Then reopen Gemini Notebook. Check the date, capacity and venue in the source viewer. Our source viewer displayed revision B after a freshness check. We did not sync manually or measure the sync delay. According to Google help, automatic Drive source updates are available in Gemini Notebook. The help also describes the manual Click to sync with Google Drive option. If revision A still appears, use the available sync controls. Re-inspect the source before comparing reports. Remember to look at the actual source text. Don't just rely on an AI response that it's up-to-date.

3. Reopen the existing report

Open the same Report A (within Studio) after you've verified revision B (source viewer). Select only Fictional workshop source.

Say in the existing chat:

Click on the source's citation in the answer. See the source, chat answer, and Report A. See if they have the same revision, date, capacity and venue. In our case, Report A still held on to 12 Nov, 18 attendees. In both source view and a new cited chat answer we see 19 Nov, 24 attendees. Both source versions have Cedar Room.

As per Google, updating or deleting a source doesn't affect existing Studio outputs. A fresh chat answer doesn't update an old report. You need to see what's in your saved artifact.

Enlarge image

Gemini Notebook source and fresh answer show revision B, 19 November and 24 attendees, while retained Report A shows 12 November and 18 attendees.

×

Open full-size image

4. Generate and check a new document report

For the 2nd report, you'll use the same source and request as for the 1st report. Select only that source in the notebook. You'll be on the Studio side doing Reports -> Document -> Create your own. Then enter this request:

If you still have generation allowance available, click Generate now.

To check whether all the facts you asked for line up with the source, open up the newly generated report. Our second report showed revision B, 19 Nov 2026, a capacity of 24 attendees and Cedar Room. Make sure to give the new report a unique title. Remember or stash away the old reports, if there are any, as you're checking. The new report generation doesn't mean the old one's disappeared.

Enlarge image

The regenerated Gemini Notebook report shows revision B, 19 November 2026, 24 attendees and Cedar Room.

×

Open full-size image

Correct numbers do not clear the rest of a report

Report A was good for that date and capacity in revision A. The AI added extra comments about governance and official documentation standards. Those weren't part of our four-line source. The request excluded made-up details, but the AI added them anyway. Read every sentence carefully in the report.

Report 2 has a header: 'Compliance & Final Constraint Verification'. That's generated text. It's not a separate verification result. We checked the requested fields against the source.

We only tested one pretend Google Doc, two Document reports and one new question in the existing chat. We did not test other Studio formats, uploaded PDFs, shared-notebook permissions or future edits.

Current window usage jumped from 0% to 3%. But weekly usage stayed at 0%. Non-exact percentages aren't a way to pin down a usage number per report. If you have no remaining generation allowance in your account, don't upgrade for this exercise. Wait for the reset as shown.

Before you send the report, you want to confirm the source version and facts. If you see an unsupported claim, check the original doc and then fix or remove it from the report. The same applies to regenerated reports. Validate the claims.

Sources

• Google: source types, Drive syncing and existing Studio outputs (opens in a new tab)
• Google: generate document reports (opens in a new tab)
• Google: automatic Drive syncing announcement (opens in a new tab)