A color-coded Google Slides notebook built around the EDP. This guide covers first-time setup, keeping entries in order, maintaining the table of contents, adding clickable navigation, and the mistakes that cost teams before competition.
Mr. T keeps one master template — a blank Google Slides file with the color system, divider slides, and placeholder prompts. Your team gets its own copy. That copy is the only place you write.
Your notebook's file name must follow this format exactly:
2822A-Notebook-2026-27If Mr. T named it for you, do not rename it. If he asks you to rename it, use exactly this format.
EDP: Identify the Problem
EDP: Brainstorm & Research
EDP: Select Best Solution
EDP: Build & Program
EDP: Test & Evaluate
EDP: Tournament Prep & Reflect
[TeamNumber]-Notebook-2026-27. If it is not, do not rename it yourself — ask Mr. T first.Every entry must be added in the order it happened. Do not go back and insert slides between existing entries. If you missed documenting something, add a catch-up entry at the current date that explains what happened earlier — do not backdate it or insert it out of order.
Every entry slide must have a date. Use the entry header format on every slide:
Google Slides does not add automatic slide numbers to content slides. Use one of these approaches:
Add a small text box in the bottom-right corner of every entry slide. Type the slide number manually (e.g., 14). Update the TOC to match these numbers.
In Google Slides: Insert → Slide numbers. Choose to show numbers, set the starting number if needed. This adds numbers to all slides automatically. Note that divider slides will also get numbers.
Your Table of Contents slide uses a four-column table. Keep it on Slide 2 and update it every session.
| Slide # | Entry Title | EDP Phase | Date |
|---|---|---|---|
| 1 | Cover Page | — | 08/29 |
| 8 | ■ Game Overview | Identify Problem | 09/08 |
| 14 | ■ Concept Brainstorm | Brainstorm | 09/19 |
| 18 | ■ Drive Decision Matrix | Select Solution | 10/01 |
| 23 | ■ Build Log — Drive v1 | Build & Program | 10/12 |
The template has 37 slides. Your finished notebook will have more — every build log entry, test protocol, and competition reflection is a duplicate of a template slide. When you add slides, two things break: page number footers and TOC slide numbers. Here is exactly what to do about each.
The template uses manually typed footers like 21 / 37. Every time you add a slide before an existing one, every footer after it is wrong. The fix is permanent and takes 2 minutes:
21 / 37 text boxes in the bottom-right. Once you have automatic slide numbers on, find and delete those manual boxes so they don’t conflict. You can select-all on a slide (Ctrl+A) and look for the number text box.When you add a slide at position N, every TOC entry for slides N and above shifts by +1. That means you need to update those row numbers. Here is the workflow teams that keep clean notebooks follow:
The updated template (v3) has 20 blank rows at the bottom of the TOC table as a buffer for entries added during the season. When you fill those, right-click any existing TOC row in Google Slides and choose Insert row below to add more. The blank rows are already formatted to match the existing entries.
In Google Slides, you can link any text or shape to a specific slide. Here is the step-by-step process for making your TOC interactive:
Ctrl+K (Windows) or Cmd+K (Mac).Each entry slide should have a small “Back to TOC” button in the bottom-left or top-right corner. This lets a judge jump back to the TOC after reading any entry.
Every entry appears in version history with a timestamp. A notebook where 80% of the entries were created in one editing session does not demonstrate a season-long engineering process.
Someone cannot find the team notebook, so they start their own Google Slides file and work there. Now there are two notebooks. Neither is complete. Neither is the official record.
The notebook has 45 slides but the TOC only references 20. A judge looking for the decision matrix cannot find it and assumes it does not exist.
Every “Written By” field shows the same name. Judges assume the other team members do not understand the work. They will direct interview questions at the members who have no entries.
A slide with a robot photo and a date but no written explanation of what it shows does not score rubric points. Judges cannot read your mind from a photo.
The matrix table is filled in with scores — but there is no written paragraph explaining why the winning option was chosen and what the team gave up by not choosing the others.
A team member makes the notebook 'Anyone with the link can edit' so a friend can help. Now an unauthorized person has edit access to the official team record.
Placeholder text like '[Write your problem statement here]' appears in slides submitted to judges.
Four columns. Color-coded EDP Phase. Every entry hyperlinked. Updated after every session.
Full-width color slide marking each EDP phase and each new iteration. Makes section starts visible without reading.
Written By / Witnessed By / Date on every entry slide. Colored left border or background matching the EDP phase.
Small linked shape on every entry slide. Consistent position. Links to Slide 2.
Bottom-right corner of every entry slide. Matches TOC slide numbers exactly.
Before every competition, do a visual scan of the slide panel (the thumbnail column on the left in Google Slides). You should see a clear pattern:
If your event uses remote judging (digital submission), follow these steps:
[TeamNumber]-Notebook-2026-27.pdf