Lesson 3: Verification as a Team Habit — Roles, Not Worksheets

Purpose: Give teachers a quick, consistent overview of PLC roles before the next PLC meeting so Lesson 4 time stays focused on team discussion and real work.

Step 1: Upload the Roles PDF to NotebookLM (2 minutes)

1. Open NotebookLM
   

2. Create a new notebook
   

3. Upload the PDF linked below into the notebook’s Sources/Knowledge bank
   

4. Keep web access OFF (if available)
   

Step 2: Generate a Studio Video Overview (2–3 minutes)

1. Go to Studio
   

2. Select Video Overview
   

3. Use a prompt like this:
   

Prompt (copy/paste):
“Using only the uploaded PDF, create a short Video Overview explaining our PLC roles (Driver, Source Checker, Skeptic, Recorder), what each role does, and how roles help us verify outputs without anyone feeling called out.”

Step 3: Verify Before Sharing (5 minutes)

Before you send the video to staff:

• Watch the full video once
  

• Compare key points back to the PDF
  

• Confirm it accurately describes each role
  

• Remove or correct anything that is unclear, missing, or incorrect (regenerate if needed)
  

Verification check:

• Does it match the PDF language?
  

• Are the role responsibilities accurate?
  

• Does it reinforce: “outputs are drafts” + “verify against sources”?
  

Step 4: Share With Teachers (1 minute)

Send the verified video to teachers prior to the next PLC meeting with one sentence of framing:

Message to staff (copy/paste):
“Please watch this short video before our next PLC meeting—this previews the roles we’ll use to keep verification consistent and low-pressure during our Studio activity.”

Teacher-Facing Preview (What the video should cover)

Teachers should walk in knowing:

• Driver: navigates NotebookLM and generates the chosen Studio output
  

• Source Checker: anchors the team in the uploaded text (“Where is that in the text?”)
  

• Skeptic: flags overconfidence, gaps, or missing nuance
  

• Recorder: captures I Notice/I Wonder patterns + team decisions (Use/Revise/Skip), next step, and guardrail
  

• Team norm: Treat outputs as drafts; verify before use/share; roles keep verification non-personal
  

Quick Bridge to Lesson 4 (PLC Activity)

In Lesson 4, teams will:

• Upload an instructional text
  

• Generate a Studio output
  

• Use I Notice / I Wonder to discuss usefulness
  

• Use Source Checker + Skeptic to verify and flag gaps
  

• Decide Use / Revise / Skip, name a next step, and commit to one guardrail