How to Turn a Location Scout Voice Memo Into a Shoot-Day Brief With NotebookLM

The problem this solves and who it is for

This workflow is for creators, producers, and content leads who walk through a location once, say a lot of useful things out loud, and then lose half of it before the actual shoot day. A good voice memo often contains the real production value: room order, sound issues, light direction, prop constraints, parking problems, and easy pickup shots. The problem is that the memo stays messy.

NotebookLM is a strong fit because this is a source-grounded planning job. You want the brief to stay anchored to what you actually said during the scout, not drift into generic production advice.

Prerequisites

• A phone with a voice memo app
• A Google account for NotebookLM
• A quiet place to record the memo or a willingness to record in short segments
• Optional: a simple text note for addresses, access codes, or contact names that you do not want buried inside the memo
• If your voice memo app saves in a format NotebookLM does not accept cleanly, export the file as MP3 or WAV or create a transcript first

How to capture or gather the source material

1. Walk the location once and narrate what matters in order: entrance, best background, windows, noise sources, props, power outlets, likely b-roll corners, and any restrictions.
2. Keep one memo per location. Do not mix two venues into the same audio file.
3. Say concrete things instead of vague ones. Better: The west wall has clean morning light until about 10 AM. Worse: Lighting seems okay.
4. Add a short companion note with exact logistics such as address, arrival time, parking, permissions, or building access.
5. If you also took photos, keep them in the same folder. You can add them later as extra sources if the audio memo is not enough.

Step-by-step workflow

1. Export or upload the scout memo in a NotebookLM-friendly format. NotebookLM supports audio files as sources, along with copied text and other files. If your phone saves a tricky format, export it to MP3 or WAV or use a quick transcription step first.
2. Create a dedicated notebook for that shoot. Add the audio memo first. Then add your logistics note and any key reference photos only if they clarify the plan.
3. Ask NotebookLM for a source-grounded planning summary. The first response should extract sequence, setup opportunities, risks, and missing information from your memo only.
4. Convert the summary into a shoot-day brief. Ask for a clean brief with arrival checklist, room sequence, shot opportunities, audio watchouts, prop reminders, and pickup shots.
5. Generate one extra artifact only if it helps. A briefing document is useful for email. A slide deck or infographic is useful if you need to hand the plan to a crew quickly.
6. Do a human cleanup pass. NotebookLM can structure the information, but you should still correct anything time-sensitive, permission-sensitive, or ambiguous.

Tool-specific instructions

Primary recommendation: Notebooklm

NotebookLM is the centerpiece here because Google's documentation shows that NotebookLM accepts uploaded sources, including audio files, copied text, and many document types, and it can turn source material into grounded reports and other outputs. The mobile app also supports adding sources and using generated artifacts on the go.

Practical setup:

• Create one notebook per shoot or client job.
• Upload the voice memo first.
• Add a short logistics note as a second source.
• Ask for a summary before asking for the final brief.
• Use a briefing document when you need a clean shareable plan; use a slide deck only if other people really need a visual handoff.

Alternative: Gemini

Gemini is a workable fallback after you transcribe the memo or turn it into a plain text note. Use Gemini when you want a faster one-off result and do not need NotebookLM's source workspace. Upload the transcript or paste the text, then ask for a shoot-day brief.

Alternative: ChatGPT

ChatGPT is also a good fallback once you have a transcript or written scout note. Projects in ChatGPT are useful if you repeatedly plan shoots for the same client and want the brand context, prior notes, and new brief in one place.

Copy and paste prompt blocks tailored to the workflow

NotebookLM summary prompt

{
  "role": "production coordinator",
  "task": "summarize a scout memo into source-grounded planning notes",
  "goal": "extract only what is supported by the uploaded scout memo and notes",
  "instructions": [
    "Use the uploaded sources only.",
    "Organize the response into location sequence, usable setups, risks, props or gear reminders, and missing information.",
    "Separate direct source-backed observations from open questions.",
    "Do not add generic production advice unless it directly solves a source-backed issue."
  ],
  "output_format": {
    "location_sequence": [],
    "usable_setups": [],
    "risks_and_constraints": [],
    "props_or_gear_reminders": [],
    "open_questions": []
  }
}

NotebookLM shoot-day brief prompt

{
  "role": "shoot planner",
  "task": "draft a compact shoot-day brief",
  "goal": "turn the source-backed summary into a practical plan for the actual production day",
  "instructions": [
    "Create a brief with arrival checklist, room or area order, priority shots, pickup shots, sound and lighting watchouts, and a final pre-roll check.",
    "Keep it concise enough for a small team to use from a phone.",
    "Do not invent timings or access details unless they are in the sources.",
    "Flag anything that still requires confirmation."
  ],
  "output_format": {
    "arrival_checklist": [],
    "location_order": [],
    "priority_shots": [],
    "pickup_shots": [],
    "watchouts": [],
    "needs_confirmation": []
  }
}

Quality checks

• Confirm the brief uses the same room order or setup order you described in the memo.
• Check that each risk or watchout is source-backed instead of generic.
• Make sure the final brief is short enough to use during the actual shoot.
• Keep the raw memo in the notebook so you can trace a line back to the source if someone questions the plan.

Common failure modes and fixes

Failure mode: The memo is too rambling.
Fix: Add a short typed logistics note and ask NotebookLM to prioritize only actionable production details.

Failure mode: Important details are buried in background noise.
Fix: Re-record a two-minute clean recap or create a quick transcript before uploading.

Failure mode: The brief invents times or access info.
Fix: Tell NotebookLM to mark unknown logistics as needs confirmation instead of filling gaps.

Failure mode: The output is too long for field use.
Fix: Ask for a phone-friendly checklist version after the first full brief.

Sources Checked

• https://support.google.com/notebooklm/answer/16215270?co=GENIE.Platform%3DDesktop&hl=en (accessed 2026-03-25)
• https://support.google.com/notebooklm/answer/16206563?hl=en (accessed 2026-03-25)
• https://support.google.com/notebooklm/answer/16296687?co=GENIE.Platform%3DiOS&hl=en (accessed 2026-03-25)
• https://support.google.com/notebooklm/answer/16212820?hl=en (accessed 2026-03-25)
• https://help.openai.com/en/articles/10169521-projects-in-chatgpt (accessed 2026-03-25)
• https://support.google.com/gemini/answer/14903178?co=GENIE.Platform%3DDesktop&hl=en (accessed 2026-03-25)

Quarterly Refresh Flag

Review by 2026-06-23 to confirm the live product interfaces and supported file, image, audio, project, or notebook behaviors still match the current tools.