A meeting pre-read should give participants the evidence needed for a decision without burying them in every linked file. Use Gemini to prepare a packet from approved documents, preserving versions, decision relevance, conflicting evidence, and links that participants can actually open.
Primary product documentation checked on 8 October 2026. The worked examples are fictional editorial examples, not claims of hands-on testing inside Gemini or Perplexity.
Start with the meeting decision
Write the decision the meeting should make and the questions participants need to answer. Select documents because they help those questions, not because they are nearby in Drive. Record who approved each source for this purpose. A document shared broadly may still be a draft or an outdated reference.
Define the audience and review time. A technical annex can remain available without becoming mandatory reading for everyone. Keep that distinction explicit so the packet supports preparation instead of imposing an undefined reading burden.
Build the approved source manifest
Record file identity, title, version or snapshot date, owner, approval state, and the relevant section. Check participant access before distributing links. A pre-read that cites inaccessible material creates unequal preparation. If access cannot be restored, arrange an authorized summary or replacement source rather than copying sensitive material casually.
Ask Gemini to use only the selected source package and identify any source it could not assess. Google’s source controls help constrain context, but the reviewer must still verify the coverage and relevance of the output.
Create a decision-oriented packet
Request a short decision statement, essential facts, options, disputed points, open questions, and a reading order. Link each consequential fact to its exact source location. Keep proposed options distinct from documented commitments. Do not describe a recommendation as approved merely because it appears in a draft document.
Include a disagreement section when sources conflict. A useful packet should expose that conflict before the meeting. Ask what information or authority could resolve it, and identify the participant expected to provide that input if documented.
Work through a fictional review
Suppose a team must choose a release date. Approved sources include a readiness checklist, a support staffing plan, and a customer commitment register. An old planning deck proposes an earlier date but has no current approval. The packet should lead with current readiness and staffing constraints, while treating the deck as historical context.
If the commitment register conflicts with the staffing plan, show both. Do not average the dates or select the more recent-looking document without authority. The meeting’s purpose may be to resolve that conflict, and hiding it would undermine the decision.
Check usefulness before distribution
Ask a colleague to identify the decision and locate evidence for the main facts using only the packet. Fix missing context and broken links. Label essential and optional reading, and preserve the source manifest with the packet version. Distribute only through the authorized channel.
If a source changes before the meeting, flag the affected section and update the packet date. After the meeting, connect the recorded decision to the reviewed packet version. This helps later readers distinguish what participants knew at the time from information that arrived afterward.
Validate the evidence and hand over the result
Run the review in two passes. First, check the source records without reading the generated conclusions. Select a small but representative sample: a clear record, a contradictory record, an incomplete record, and a record that changed after the review began. Write down the expected treatment of each. This gives you a reference for judging the output instead of accepting a plausible narrative because it looks organized.
Then inspect the generated result against those expectations. Open every source supporting a consequential conclusion. Check the surrounding paragraph, the relevant table heading, and any qualifying note. A link to the correct document is only the beginning of verification. The document may support a narrower claim, describe a different version, or use a different unit. Record a correction beside the affected item rather than quietly changing its meaning.
Count the inputs and outputs where a one-to-one relationship is expected. Explain every omitted record and every merged record. When several source items become one conclusion, retain the individual references so the reviewer can reverse that grouping. When one source item produces several actions, preserve the connection so a later source correction can update all affected actions. Never interpret an empty output as evidence that there are no problems until you have checked source coverage.
Keep proposed wording separate from approved wording. An AI system can suggest how to express a finding, but the source owner still needs to confirm the underlying facts when records disagree. Use explicit states such as supported, disputed, missing evidence, and awaiting owner confirmation. Avoid a single confidence score that disguises those different reasons for uncertainty. A disputed statement with two strong sources needs a different next step from a statement with no accessible source.
Before handover, ask a colleague to use the result without your explanation. Can they locate the original evidence, identify unresolved items, and understand what changed since the last version? Fix the places where they need to guess. Save the source manifest, the prompt, the reviewed result, and the correction history together. A useful deliverable should remain understandable after the conversation that produced it has ended, and it should make the next review cheaper because the evidence trail is still intact.
Frequently asked questions
Should every linked document be included?
No. Include approved sources relevant to the decision, with optional background clearly separated. A long link list is not a useful reading plan.
What if participants cannot open a source?
Resolve access or provide an authorized alternative. Do not assume that access available to the preparer is available to every participant.
Can Gemini choose the winning option?
It can organize evidence and compare documented options. The decision remains with the authorized participants and should preserve unresolved tradeoffs.
How should conflicting evidence appear?
Show both sources, their versions, and the question requiring resolution. A concise summary should not erase a material disagreement.
What happens when a source changes?
Update affected sections and notify readers through the approved process. Preserve the prior packet so the meeting’s evidence context remains traceable.
