Gemini Notebook table export: inspect the Sheets copy

A Gemini Notebook table export starts with a source-based Data Table, followed by row checks and Export to Sheets. After this exercise, you can extract three short programme descriptions, inspect the spreadsheet copy and check a citation tab where citations exist. The result is a reviewed practice extract, not a real event catalogue.

A Data Table arranges source information into rows and columns. Export creates an output you can use in another file. A sheet tab is one page inside the spreadsheet file. AI means artificial intelligence; it helps separate fields from prose, but it does not confirm facts missing from the source.

Content checked: 15 October 2026. Google's current help uses Gemini Notebook for the product previously known as NotebookLM. This desktop exercise assumes a working account and Data Tables access. All programme descriptions are fictional author-created material. No live account run, measured generation speed or actual event offering is reported.

What belongs in your first extraction?

Imagine a small arts centre whose workshop descriptions use different wording. One lists materials before duration, another omits duration altogether. Your task is not to recommend a workshop. It is to put matching fields in a consistent structure and preserve the gaps for the person who will investigate them.

Define a row before asking the assistant for a table: one row represents one programme. Two materials in a description do not create two programmes.

The AI data analysis guide concerns calculations and business comparisons. This exercise is different: extract a bounded source into a Studio artifact, export it and inspect the separate file.

Which source should you paste into the notebook?

Copy the block below, including its version and P labels. These are ordinary source references for your review, not special software commands. The text is not a real service offer. You need no customer details, payment records, registration list or confidential lesson plan to practise extracting these fields.

FICTIONAL SOURCE: Arts centre practice descriptions, version 01. P1: Poster layout practice lasts 90 minutes. The organiser supplies sample paper. P2: The duration of the introductory bookbinding session is not specified. Participants bring their own sample notebook; other equipment provision is not stated here. P3: Exhibition caption practice lasts 45 minutes. The organiser supplies a sample text. Dates, fees and registration arrangements are absent from this document. This is teaching material, not an actual programme catalogue.

Open notebook.google.com on your computer and sign in with an appropriate account. Create a notebook. In Add sources, choose the pasted-text route, insert the block and name it Arts practice 01. Once imported, open the source and confirm that P1, P2 and P3 appear in full.

Google documents copied text as a source and lets you name it. Use only this source in the exercise. If a previous notebook already contains unrelated documents, create a separate practice notebook instead of deleting that material. Do not assume another notebook's sources are automatically available to this one.

The source maintenance guide addresses changing an outdated source and checking a fresh answer. Here, keep the input fixed while reviewing the generated artifact and export. Correcting a spreadsheet cell does not establish which original source version is authoritative.

How do you request a useful Data Table?

In Studio, find Data Tables and open its pencil customisation control. Google's current instructions describe choosing a language and using the prompt box to specify rows and columns. A prompt is the written instruction you send the assistant. It defines your requested structure, not a guarantee that the output will have exactly the intended shape.

Use only Arts practice 01 to create an English table. Make one row per programme. Columns: Code, Programme, Duration, Materials and supplier, Missing information, Source label. Preserve P1 through P3. Keep the duration unit given in the source; write not specified when it is absent. Invent no dates, fees, registration rules or equipment. Preserve who supplies each material. Retain supporting source citations where available. This is a practice extract, not a real catalogue.

Start generation and open the result when it is ready. Count the rows and inspect the labels. Three visible rows are not sufficient if P1 appears twice and P2 is missing. Each programme must be represented once, with any general explanatory note kept separate from the programme records.

If Data Tables is absent, check the account and notebook and leave that stage unresolved. Producing a normal table in chat does not prove that the Studio Data Table exists. This article makes no promise about subscription entitlement, generation limits or a fixed waiting time. Do not buy a plan simply to resolve an unexplained missing control.

This is not the Ask Gemini workflow inside a spreadsheet. The Gemini in Sheets guide covers that separate route. Here the artifact begins in Gemini Notebook and is exported afterward. Keep those two starting points distinct when describing what you completed.

Which fields must survive before export?

Read all three rows beside the source. P1 must retain 90 minutes and organiser-supplied paper. P2 must retain the unknown duration and the participant-supplied notebook. A missing duration is not zero minutes. Zero would look like a measured value rather than an unresolved field.

This table is the author's checking key, not an observed generated answer. With a different source, write your own expected facts before reviewing the output. A cell saying paper provided loses useful information if it removes who provides it. Shorter wording and faithful extraction are not automatically the same thing.

Where a citation appears, open it and inspect the supporting passage. Very short sources may be cited as a whole. In that case, locate the P label manually and record a manual comparison. If there is no citation, do not fabricate one. A Source label column helps traceability but is not a replacement for an actual product-generated reference.

For each row, record acceptable, needs correction or untested. If a field is wrong, describe its difference from the source before attempting a repair. Do not resolve an unknown by inventing a plausible class duration.

How do you inspect the spreadsheet and its citations?

Open the three-dot menu beside the generated Data Table in Studio and select Export to Sheets. Google's current guide says the table content fills the first tab of a new spreadsheet, while any citations populate a second tab. This is the specific Data Table route, not a claim that every report or note exports in exactly the same structure.

In the new file, inspect the first tab. Confirm the column headings, P1 through P3 and the not-specified duration. Make sure the programmes did not lose or exchange facts during export. Then inspect the tab labels. Where a citation tab exists, open it and check whether you can identify the relevant source reference.

An absent or empty citation tab is not evidence of a fully cited export. Record its actual condition. You can still compare the table with the original source manually, but that is a different observation from successful citation transfer. Do not silently combine those two statuses in the review record.

Do not share the practice file. Google states that notebook sharing permissions do not carry over to exported files. That does not mean every export is automatically public or automatically private. Before any real sharing, inspect the new file's own access settings rather than relying on the notebook's previous audience.

Changes made in the exported spreadsheet do not synchronise back to the original notebook content. A repaired cell in Sheets is therefore not proof that the Studio artifact was repaired too. Record the source, generated table and exported copy as separate objects. This exercise does not create an automatically updating report.

What should remain after fifteen minutes?

On Windows, open Start, search for Notepad and open the app. Start a blank note with headings for notebook name, source version, row decisions, citation status and exported file address. In the spreadsheet's browser tab, press Ctrl+L and Ctrl+C to copy its address, then paste it into your note. This is your private retrieval reference for the fictional practice file.

Press Ctrl+S, choose Documents and save as table-export-review-01.txt. Close the note and reopen it from Documents. Copy the saved spreadsheet address. In your browser, press Ctrl+T for a new tab, press Ctrl+L, paste the address and press Enter to reopen the exported file. Confirm that P2's duration remains not specified. Then return to Studio and locate the original Data Table as a separate retrieval check.

1. First three minutes: add and inspect the source. Output: P1 through P3 visible.
2. Next four minutes: generate the Data Table. Output: a structured draft.
3. Next five minutes: check the rows and export. Output: a spreadsheet with an explicit citation status.
4. Final three minutes: save the record and reopen the file. Output: retrievable artifacts.

This is a planning allowance, not a measured generation promise. If creation or export takes longer, leave that stage open. In my earlier essay about effectiveness and perfection, I described projects delayed while pursuing every detail. Applied here, that principle means checking three rows and their exported copy before attempting an entire catalogue. It is not a claim that I performed this account trial or measured a gain.

The mind-map guide inspects visual topic branches, not a spreadsheet extract. The artificial intelligence guide offers other starting tasks. Close today's exercise with separate statuses for source, Studio table and export; a successful download or new file alone does not validate all three.