Turn scattered files into an answer you can check.

Start with a source register

Google documents grouped sources and direct citations for Gemini in Drive. For a specific project, we also recommend a short source register: document, owner, approval status and effective date. Do not remove superseded drafts indiscriminately; mark them clearly and keep them out of the source set used for decisions.

A summary is not evidence of complete coverage

Google explicitly notes that folder summaries can omit files. For tenders, contract versions or project handovers, compare the result against your source register. Ask not only what the sources say, but which of the specified documents support the answer. A critical file with no evidence of consideration remains an open review item.

Example: a clear project handover

A project lead hands an engagement to the delivery team. Sources include the approved proposal, scope boundaries, schedule and confirmed change requests. Gemini prepares a table of deliverables, commitments, deadlines, sources and uncertainty. The accountable reviewer compares conflicting dates and fills missing decisions. Only then does the summary become the team’s agreed working reference.

Check access rights and source quality separately

Google describes Gemini as unable to access Workspace content the user is not allowed to see. Owner restrictions can further limit access. Your review therefore needs two questions: may this role read the document, and is the document authoritative for the task? A correctly authorised user can still choose an outdated or incorrect file.

Working template: an answer with an evidence boundary

A suitable instruction is: “Answer [question] using only the selected documents. Give the source and date for every commitment. Separate current requirements, conflicting statements and missing information. Do not interpret absence of a statement as approval.” Add the source register prepared beforehand. Use the answer only after opening and checking its decision-critical references.

• Expected conflict case: explicitly distinguish the old deadline from the new one.
• Expected knowledge gap: identify the missing appendix and leave the review open.

Test conflicts before rollout

Include an older proposal version, a missing appendix and conflicting dates deliberately in the test set. A useful answer makes these conflicts visible. It should not silently choose the most convenient version. If this test fails, improve source organisation and instructions first. The System Check assesses whether curated Drive sources suffice or a dedicated knowledge solution is required.