Digital Notebook Detectives

Overview

Students now keep a lot of their schoolwork in digital notebooks and drives, and "I can't find it" costs real learning time. In this hybrid lesson, teams open a paper "drive" belonging to a fictional student, Theo, full of files named Untitled document (2) and asdfgh. They race to find one assignment, then build folders and a naming rule, use a printed version history to recover a paragraph a teammate deleted, and compare Theo's field trip notes to an AI summary that sounds complete but drops the most important details. Students leave owning a filing plan they can use tomorrow on a real device.

Objectives

• Students will sort a set of files into subject folders and rename each one with a clear naming rule (Subject – Topic – Date).
• Students will explain how version history helps them recover earlier work and see who changed a shared file.
• Students will compare an AI summary to the original notes and name at least two important details the summary left out or got wrong.
• Students will write a personal filing plan and one rule for when to trust, and when to check, an AI summary.

Step by step

1. 10–5 min

   Hook

   Find it fast!

   Hand each team Theo's Drive envelope. Say: "Theo's teacher needs his bean plant journal right now. You have 60 seconds. Go!" Teams dump out the cards and hunt. Stop the timer. Ask: "Who found it? How did you know which one it was? What slowed you down?" List the slowdowns on the board (no names that make sense, copies of copies, everything in one pile).

   Facilitator noteMost teams have to open (read the preview on) nearly every card. That frustration is the point: the file names gave no clues.

2. 25–15 min

   Explore

   Build Theo's folders

   Teams decide on four folder labels (most will choose subjects: Math, Science, Reading & Writing, Social Studies) and write them on their folders. Then they read each card's preview, decide which folder it belongs in, and write a better name on a sticky note placed over the old name. Challenge: "A new name should tell you what is inside without opening it." Watch for Card 8 (a duplicate) and Card 13 (a list with classmates' phone numbers), and ask teams what they think should happen to those.

   Facilitator noteCard 13 is the digital citizenship moment: other people's phone numbers should not sit in a shared class folder. The right move is to tell the teacher and keep it private, not to rename it.

3. 315–22 min

   Model

   One naming rule for everyone

   Gather the class. Collect a few new names and compare them. Introduce the class rule: Subject – Topic – Date, for example Science – Bean Plant Journal – Oct 3. Ask: "Why put the subject first?" (All the science files line up together.) "Why the date?" (You can tell the newest one.) Then name the second problem on the board: FINAL final REAL and Copy of Copy of poster. Explain: "Instead of making copies, most notebook and drive apps keep a version history, a saved list of every change, who made it, and when. You can go back to an older version without making copies."

   Facilitator noteStay tool-agnostic. Say "look for Version history or File history in the menu" rather than naming a brand.

4. 422–30 min

   Practice

   Version history detectives

   Teams read Part 1 of Handout B, the version history of Theo's shared Owl Report. On Handout C, they answer: Which version still had the owl pellets paragraph? Who deleted it, and when? What should Theo do? Guide teams to the answer: restore the Tuesday 2:15 version (or copy the paragraph back from it) and talk kindly with his teammate. Ask: "Was the teammate being mean, or could it have been a mistake? How does version history help you solve it fairly?"

   Facilitator noteVersion history also shows who did the work in a group project. Some students find that reassuring; others find it surprising. Both are good discussion.

5. 530–39 min

   Apply

   Did the AI summary leave something out?

   Teams read Part 2 of Handout B: Theo's field trip notes, then an AI summary of those notes. Say: "Theo asked an AI tool to shorten his notes. The summary is short and sounds good. Your job: check it against the notes." Teams underline, in the notes, every detail missing from the summary and circle anything in the summary that is not in the notes. Then they rank: which missing detail would cause the biggest problem if Theo only read the summary?

   Facilitator noteKey catches: the permission slip due Friday, bringing a water bottle, the change to a 7:45 bus time, and the allergy reminder are all missing, and the summary adds "bring lunch money," which the notes never said. The summary is not evil; it just picked what sounded important and guessed.

6. 639–45 min

   Reflect

   My filing plan

   Students complete the rest of Handout C: their own four folders, their naming rule, what they will do instead of making copies, and one rule for AI summaries (for example, "I check a summary against my notes before I throw the notes away"). Two or three students share their AI rule. Close with: "Organized files are not about being neat. They are about finding your learning when you need it."

   Facilitator noteLook for AI rules that name a specific action (check, compare, keep the original), not just "AI can be wrong."

Adaptations

Grade 3

Use 8 of the file cards (1, 2, 4, 6, 9, 10, 11, 13) and give teams the four folder labels. Provide a sentence frame for new names: "___ (subject) – ___ (what it is)."

Grade 5 extension

Teams design a folder system for a group project with three people, including who can edit and who can only view, and explain why.

Emergent bilinguals

Add subject icons (a beaker, a book, a globe, a plus sign) to each folder, and allow new file names in English plus the home language.

Students with reading or attention needs

Pre-highlight the key words in each card preview and chunk Handout B so Part 1 and Part 2 are on separate pages.

Pairs well with

• Digital Citizenship Breakouts (K–8)Follow up on privacy and personal information in shared spaces.
• Gen AI Literacy Breakouts (K–8)More practice checking what AI tools get wrong.