How to Turn Project Emails and Notes Into a Running Client Decision Log With Gemini Notebook (Formerly NotebookLM)
Turn emails, call notes, and approvals into a dated, verifiable client decision log with current Gemini Notebook source handling.
Workflow summary
Quote this workflow accurately
- Best for
- Freelancers, consultants, and client service teams with an active engagement that accumulates approvals, revisions, and unresolved requests. The outcome is a living, reviewed decision log with source references, not a...
- Input
- Access to Gemini Notebook and permission to use the relevant client communications in that environment. A project identifier and authoritative contract or approved scope. Selected emails, call notes, comment summaries...
- Primary tool
- NotebookLM
- Output
- Turn emails, call notes, and approvals into a dated, verifiable client decision log with current Gemini Notebook source handling.
- Main risk
- Tentative comments appear as final: Require an approver and direct evidence; label all others proposed.
- Verification step
- Every approved decision points to a message, signed document, or other authorized approval evidence. Tentative comments remain separate from approvals. Superseded decisions remain discoverable with their original dates.
Continue from this article
A project decision log should answer three questions quickly: what was approved, what changed, and what still needs a decision. When evidence is scattered across emails and meeting notes, Gemini Notebook (formerly NotebookLM) can assemble a cited first draft, but it should not be the only place the project's official decisions are stored.
Who this is for
Freelancers, consultants, and client service teams with an active engagement that accumulates approvals, revisions, and unresolved requests. The outcome is a living, reviewed decision log with source references, not an automatic approval detector.
Prerequisites
- Access to Gemini Notebook and permission to use the relevant client communications in that environment.
- A project identifier and authoritative contract or approved scope.
- Selected emails, call notes, comment summaries, and change approvals with dates and sender or approver context preserved.
- A shared document or project system to store the official decision log and manage version history.
How to capture or gather the source material
Export only decision-bearing email threads and important notes, not the entire mailbox. Paste them into dated documents with clear headers for sender, recipient, date, subject, and source channel. Preserve the exact approval language. For documents whose comments hold decisions, export the comments into a separate text source: Google says importing a Google file may omit footnotes and comments. Remove irrelevant sensitive side conversations. Keep the original communication available for audit and dispute resolution.
Use a controlled Google Drive document as your current source pack when permitted. Gemini Notebook now documents automatic syncing of eligible Google Drive imports when a notebook is opened; manually uploaded files and pasted text should not be presumed to update after the underlying originals change. Always check the last imported version before declaring the decision log current.
Step-by-step workflow
1. Create a project decision notebook
Open Gemini Notebook, start a notebook for the project, and add the current signed scope and dated communication sources. Choose the most relevant sources in the Source panel when analyzing one phase. Avoid mixing former clients, unrelated phases, or private internal discussions.
2. Extract candidate decisions
Run the first prompt below. Ask for decisions, explicit approvals, tentative suggestions, rejected options, reversals, owners, and pending confirmation. Require a supporting source and quoted or closely paraphrased approval evidence. Do not assume that silence or a meeting summary establishes consent.
3. Check the sequence against primary messages
Verify who approved a change and when. A later note may reverse an earlier direction, but it must be traceable. If the evidence conflicts, mark the entry disputed. If two sources summarize the same decision, do not create two entries.
4. Create the dated running decision log
Use the second prompt to produce a concise table: date, decision, approved by, status, impact, source, and next action. Preserve the history of superseded choices rather than overwriting old rows. If an exact date is missing, mark it unknown.
5. Store the controlled record and update deliberately
Copy the reviewed output to your official project document or tracker. Add an owner and version date. For new client decisions, import the updated source pack, regenerate only the affected period, verify against the prior log, and append or amend entries with an audit trail. Never let a regeneration erase earlier accepted decisions.
6. Resolve missing approvals
Send a focused confirmation request for any change that affects scope, cost, timeline, or deliverables but lacks express approval. File the reply and then update the log. An AI-generated decision log is not proof that the client agreed.
Tool-specific instructions
Gemini Notebook: Use cited notebook chat to extract and compare decision sources. Imported Drive files can auto-sync, but verify changed sources and permissions. The standalone notebook chat is designed to answer from notebook sources; the Gemini app can use additional tools and web information, so it is not the same evidence boundary.
- Fallback: If notebook access is unavailable, consolidate the source pack into one dated document and use an approved assistant to extract a decision table with source references. Keep your original threads as the authority.
Copy/paste prompt: decision extraction
{
"task": "Identify client project decisions and open questions from the selected source pack",
"instructions": [
"Use only selected signed scope, email messages, notes and approved changes",
"Classify each item as approved, proposed, rejected, superseded, disputed, or open",
"Identify the actual approver; do not treat silence as approval",
"Cite the exact source document and date where possible",
"Flag competing interpretations and absent approvals",
"Do not infer decisions from sentiment or informal brainstorming"
],
"output": {
"candidate_decisions": [
{
"decision": "",
"status": "",
"approver": "",
"decision_date": "",
"source": "",
"effect_on_scope_cost_or_schedule": "",
"unresolved_question": ""
}
],
"conflicts": [],
"missing_source_material": []
}
}
Copy/paste prompt: running log
{
"task": "Prepare an updated running decision log from the human-verified extraction",
"input": "Use the reviewed decision candidates and previous official log",
"instructions": [
"Maintain a chronological record and do not delete superseded entries",
"Consolidate duplicates only when the underlying decision is the same",
"Show changed direction and its approval evidence",
"Use Unknown when no date or approver is confirmed",
"List pending client confirmations separately",
"Report what changed since the prior official log"
],
"output": {
"updated_decision_log": [],
"changes_since_previous_version": [],
"outstanding_confirmations": [],
"source_versions_checked": []
}
}
Quality checks
- Every approved decision points to a message, signed document, or other authorized approval evidence.
- Tentative comments remain separate from approvals.
- Superseded decisions remain discoverable with their original dates.
- No client changes were fabricated from a paraphrased summary or omitted email chain.
- The version date and source cutoff are explicit, especially after adding new material.
Common failure modes and fixes
Tentative comments appear as final: Require an approver and direct evidence; label all others proposed.
Imported source pack is stale: Reopen the notebook, verify eligible Drive-source sync, and replace manually uploaded sources as needed.
Email comments are missing: Export approval-bearing comments as their own dated source because Google-file import does not necessarily include comments.
A later change erases earlier context: Preserve the old row with a superseded status and link the new approval.
The log becomes enormous: Keep one sentence per decision, with details and context in the original communication source.
Sources Checked
- https://workspaceupdates.googleblog.com/2026/07/notebooklm-now-gemini-notebook.html (accessed 2026-10-14). Google Workspace Updates, official NotebookLM to Gemini Notebook renaming, July 16, 2026.
- https://support.google.com/gemininotebook/answer/16215270?hl=en (accessed 2026-10-14). Google Help, supported sources, audio transcription, Google Drive automatic sync and limitations.
- https://support.google.com/gemininotebook/answer/17003757 (accessed 2026-10-14). Google Help, Notebook vs Gemini app differences and source grounding.
- https://support.google.com/gemininotebook/answer/17004255?hl=en (accessed 2026-10-14). Google Help, data handling and account-dependent privacy terms.
Quarterly Refresh Flag
Review by 2027-01-12 to recheck the Gemini Notebook name, source import and syncing, Studio controls, plan availability and permissions.
Related Workflows
How to Turn a Signed Proposal and Kickoff Notes Into a Client Onboarding Checklist With NotebookLM
Use NotebookLM to turn a signed proposal, kickoff notes, and client questionnaire into a first-week onboarding checklist with confirmed and unresolved setup items.
How to Turn a Freelance Project Into a Zero-Loss Handoff Packet With Claude
Turn a freelance project into a zero-loss handoff packet for a collaborator, subcontractor, or future restart with Claude.
How to Turn Client Emails and Revision Notes Into an Upsell Opportunity Map With NotebookLM
Turn client emails, revision notes, and meeting recaps into a source-grounded map of upsell opportunities that actually match what the client needs.
Help keep PromptedWork sharp
Share a broken step, outdated prompt, or general feedback. This is only for improving this specific workflow.