Detect stale references in a Google Docs draft with Gemini

A reference freshness report is useful when you need to identify draft references requiring a date or version review. The result should make the underlying records easier to inspect and the next decision easier to explain. This guide develops a specific reference freshness report with a source schema, operating rules, a fictional example, and observable review checks. It is intended for someone who already has the underlying material and needs a dependable way to organize it.

Product references checked: 7 October 2026. The examples and implementation specifications below are original editorial guidance. They illustrate expected behavior and have not been presented as a benchmark or as a completed tool tested inside another product.

Define the deliverable and its scope

This workflow reviews supplied source material. Gemini’s document access and connected-source availability vary; verify the actual source set and paste authorized excerpts if necessary.

Write the acceptance standard before asking Gemini for a draft. A reviewer should be able to identify the claim id, inspect the cited reference, and understand the suggested action without guessing what a blank field means. Decide which records belong in the deliverable, which are out of scope, and who can confirm the final interpretation. Keep those choices visible in the working specification rather than leaving the assistant to supply convenient defaults.

Prepare the source package

Gather a Google Docs draft, its reference list and owner-approved current source copies. Assign source IDs and preserve original wording wherever a small difference could change the outcome. Record the collection date and the version of each source. If two files disagree, keep both references and mark the conflict. Do not replace a disputed value with whichever one produces the cleanest display.

Use a small representative subset for the first draft. Include one ordinary record, one incomplete record, and one record that challenges an important rule. For this task, use the following as the incomplete-record check: A historical source stays appropriate for a historical claim. Preserve the original package separately from the assistant's transformed output. A polished result is easier to audit when its IDs still lead back to the original supplied material.

Define the record schema

Treat claim id as a deliberate part of the data model. Stable draft claim identifier and location. Keep its representation consistent when you sort, filter, or revise the output. The cited reference field has a different job: Source URL, title and cited version. Combining these fields into one sentence can hide the distinction the reviewer needs to inspect.

Pay particular attention to current source and difference. The former means: Reviewed current primary source snapshot and retrieval date. The latter means: Exact dated or versioned change relevant to the claim. Store them separately and label both in the detail view or report. This makes disagreements visible at the exact point where they affect the result instead of burying them in a general note at the bottom.

Apply the task rules

Rule 1. An old publication date alone does not make a reference stale.

Rule 2. Do not treat an inaccessible URL as evidence that its claim is false.

Rule 3. Compare the same product scope and version before proposing a replacement.

Rule 4. Use supplied sources and verify any generated citations against the originals.

Make these rules inspectable alongside the reference freshness report. Ask Gemini to describe how each rule affects a record and what should happen when the supplied data does not establish an answer. A rule written in prose still needs a defined output state. Use an explicit missing, disputed, or not-applicable label where appropriate, and reserve a valid zero or an empty result for cases where it has a defined meaning.

Work through a fictional example

A fictional draft cites a setup page describing menu M1. A supplied current official page describes M2 for the same product version. The report links both records and flags the menu instruction for revision. A second reference is an older research paper describing a historical experiment; its age does not make it stale in that context. A third URL cannot be opened and is marked unavailable for review, not false. The owner updates the first instruction after inspecting the current source, retains the historical paper and investigates access to the third reference separately.

Use the example as a review fixture rather than as real operational data. Before generating the output, write down which fields should be populated and which should remain unresolved. Then compare the generated result with that expectation. If Gemini supplies an unsupported value, correct the underlying instruction or calculation rule instead of merely editing the one visible record. Otherwise, the same error may return when the next record is processed.

Build the first version

Ask Gemini for an extraction table before asking for a polished reference freshness report. Review a few source references against the original material and correct the table first. Then request the reader-facing output using the approved fields. Keep changes to the source document separate from this drafting pass so a mistaken extraction does not automatically overwrite the authoritative record.

The final review should explicitly cover review outcome: Current, stale, uncertain or unavailable with evidence. Also check suggested action: Specific citation or wording correction for owner review. These two fields often establish whether a reader can act on the result. Make missing information visible beside the affected record and ask the owner for the exact evidence needed to resolve it.

A reusable prompt

Create a reference freshness report from the supplied source package. Goal: identify draft references requiring a date or version review. Use these fields: Claim ID: Stable draft claim identifier and location.; Cited reference: Source URL, title and cited version.; Current source: Reviewed current primary source snapshot and retrieval date.; Difference: Exact dated or versioned change relevant to the claim.; Review outcome: Current, stale, uncertain or unavailable with evidence.; Suggested action: Specific citation or wording correction for owner review.. Preserve source IDs. Rules: An old publication date alone does not make a reference stale. Do not treat an inaccessible URL as evidence that its claim is false. Compare the same product scope and version before proposing a replacement. Use supplied sources and verify any generated citations against the originals.. First explain the proposed data model and unresolved inputs. Then build the smallest usable version. Use only supplied facts; label the demonstration fictional. Do not invent approvals, thresholds, owners, or external integrations. Include an empty state and explain the expected result for these checks: A historical source stays appropriate for a historical claim. An unavailable page is marked uncertain without invented replacement content. A changed source must match the claim’s product scope.

Review behavior and edge cases

Check 1. A historical source stays appropriate for a historical claim. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 2. An unavailable page is marked uncertain without invented replacement content. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 3. A changed source must match the claim’s product scope. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Repeat the checks after adding another source record or changing the presentation. A working first example does not prove every record is handled correctly. Pay attention to retained selections, stale derived values, and unexplained changes in the number of displayed records. For reference freshness report work, the reviewer must be able to tell whether a difference comes from new evidence, an edited rule, or merely a changed view.

Maintain the reviewed version

Keep a version label, source cutoff, and short change record with the finished reference freshness report. Record who approved the rules and which demonstration cases were reviewed. When the source package changes, preserve record IDs and revisit the checks affected by the change. Do not treat yesterday's verified result as evidence that today's replacement input is complete.

Before handing the output to another person, review its audience and the material it contains. Use a sanitized demonstration for general feedback when the real source package is confidential. Explain whether changes are saved, whether the output is a preview, and which source remains authoritative. If persistence or sharing is required, verify that behavior in the actual account and intended environment instead of assuming it from a successful preview.

Frequently asked questions

Sources and related reading

Consult the current primary references for account-specific availability and controls: Gemini in Google Docs documentation, Google source-management documentation. The schema, examples, prompts, and review checks here are editorial recommendations rather than documented built-in features.

For broader context, read the related Gemini workflow guide.