Notebook Operations — Team 2822

Mr. T owns the master template. Each team gets a per-team copy named 2822[X]-Override-Notebook.
Fill the slides as you progress through EDP phases (Identify → Brainstorm → Select → Build → Test → Tournament → Iteration).
For deeper documentation in your area, open the supplement matching your role.
All notebook content must be original student writing — RECF EN4 prohibits AI-generated content.

📖

Master Template — VEX V5RC Engineering Notebook 2026–27 (v3-12)

61 slides · EDP-phase structured · 6-member two-squad roster · iteration cycles built in · 365 KB .pptx — download to your team Drive, rename, then fill

📖Supplements by role

Open the one matching your role

🎯

Supplement 1 — Driver Match Execution

Driver role · match execution detail beyond the base template · 62 KB

💻

Supplement 2 — Autonomous Programming Depth

Programmer role · sensor logs, state machines, tuning iterations · 65 KB

🔧

Supplement 3 — CAD & Fabrication

Engineer role · version logs, build issues, R24/R25 audit · 51 KB

💰

Supplement 4 — Budget & Sponsorship

Budget owner · line items, sponsor outreach tracking · 51 KB

🔍

Supplement 5 — Scouting & Strategy

Strategist role · opponent profiles, alliance theory · 51 KB

🏆

Supplement 6 — Team Ops & Judging

Notebook role + coach · judging prep, ops workflow · 62 KB

⚠Reference exemplar

NOT for submission

📝

Spartan 2822 Engineering Notebook — EXEMPLAR (v3 corrected)

AI-generated by Mr. T as a teaching reference. Fictional team “2822N · Leonidas” — shows what filled slides look like, page rhythm, and EDP phase color use. Do NOT submit any portion for EN4. Visual reference only. 2.5 MB .pptx.

📅 This Week's Workflow

Today highlighted automatically

MON

Sprint plan

Pull sprint goals from Season HQ
List required entries for the week
Brief each role on what you'll collect from them

TUE

Capture day

Practice-side photo capture
Driver log intake during reps
Build photos from any new fab

WED

Mid-week check

Which roles haven't contributed?
Slack/text reminders to laggers
Decision-rationale entry from this week's calls

THU

Sketch + CAD

Capture any CAD locks from this week
Hand-sketch a key mechanism (per warm-ups)
Confirm R24 binder photos for any polycarb fab

FRI

Collection deadline

EOD: all teammate entries collected
Master notebook integrated summary
Sprint reflection entry

SAT

Organize + upload

Photo organization & renaming
Upload to shared folder
Audit: any entry missing photos?

SUN

Prep next sprint

Skim next week's sprint goals
Pre-allocate notebook sections
Rest. The week is over.

✅ Required Documentation Checklist

Per sprint · saves on tap

This Sprint's Required Entries

Per week

Tap to check — persists per-device. Reset at sprint end.

Sprint-goal entry (what we set out to do)Mon
Decision-rationale entries for any architectural calls madeAs made
Build progress per active bot (photos + measurements)Per session
Driver practice log (date, drills, hours, outcomes)Per session
Bench-test results (any test run this week)Per test
CAD lock screenshots (any assembly reaching lock)On lock
R24 compliance evidence (if polycarb fab this week)On fab
Programming milestone summary (1 entry / active bot)Fri
Strategic decisions documented (alliance frame, meta read)As made
Sprint reflection entry (what we learned)Fri EOD

0 / 10

If This Week Includes...

Conditional

Add these to the sprint checklist when the condition fires.

A new mechanism prototyped → full bench-test entry with hypothesis, setup, pass criteria, result, next-iteration
A CAD review → review-meeting entry: who attended, what feedback, what gets changed
A new polycarb piece fabricated → R24 evidence (flat-pattern tracing + piece count update)
A driver scrimmage → head-to-head outcome notes, what worked, what didn't
An event in the next 14 days → trigger the Comp Prep timeline
An EDP phase transition → transition entry: what closes out the prior phase, what the next phase will focus on

📷 Capture Prompts

During practice / events

CAD Image Reminders

Per lock

When: every CAD lock, every assembly milestone, before deleting any iteration.
What: isometric view, exploded view if assembly, dimensioned sketch if a critical part, mate tree if the assembly is non-trivial.
How: 1920×1080 minimum, dark UI for consistency, PNG not JPG (sharp lines).
File: BotName-Assembly-vXX-YYYY-MM-DD.png

OnShape exports: /polycarb-tube-onshape-guide

Testing Log Columns

Per test

One row per bench test. Mirrors the EN4 template structure.

Test name · Date · Bot · Mechanism
Hypothesis — what you expect to happen and why
Setup — rig, mounting, jig description
Pass criteria — the bar (e.g. "0 drops in 50 cycles")
Result — pass / fail / inconclusive
Observations — what surprised you
Next iteration — what changes for v2

EN4 templates: /phase-a-bench-tests

Match Documentation

Event week

Pre-match: photo of bot before, last-minute modifications noted, controller paired confirmed, auto routine selected.
During match: video if possible (someone in the stands), auto result, final score, what failed or surprised.
Post-match: photo of any damage, driver+coach 60-second debrief notes, what changes before next match.
Filing: one entry per match block, NOT one per match — bundle 3-5 matches into one entry to keep the notebook readable.

Driver Interview Prompts

Weekly + post-event

Ask drivers these. Capture their words, not your summary.

Q1What drill did you run? What was your target?

Q2Where did you fall short of target? Why — bot or driver?

Q3What's the next skill you're working toward?

Q4What broke or felt wrong on the bot today?

Q5Best moment of the session? (motivation + good notebook color)

Sprint Reflection Prompts

Fri EOD

End-of-week, in the master notebook. Five-minute team huddle.

R1What did we set out to do this week?

R2What did we actually do? (no editorializing — just facts)

R3What did we learn we didn't know on Monday?

R4What's blocking us next week? Who owns clearing it?

R5What surprised us — bot, team, or game?

📁 File & Upload Organization

Saves chase-down time later

Folder Structure

Shared drive

Mirror this structure in the team's shared folder (Google Drive / OneDrive / etc.). Consistency means anyone can find anything in under a minute.

/season-2026-27/ sprint-[NN]/ build/ # mechanism photos, fab session shots cad/ # OnShape exports, lock screenshots drive-logs/ # driver session photos, drill outcomes tests/ # bench-test data, photos, results decisions/ # decision-rationale entry photos notebook-master/ # the assembled weekly summary events/ [EVENT-NAME]/ matches/ # per-match-block photos & video judge-prep/ # interview practice notes results/ # post-event results + photos r24-binder/ [BOT-NAME]/ flat-patterns/ piece-count/ photos/

Naming Conventions

Predictable filenames

Predictable filenames make finding things easy six months from now. Stick to these patterns.

# CAD locks [bot]-[assembly]-v[XX]-YYYY-MM-DD.png e.g. skimmer-intake-v03-2026-05-11.png # Bench-test photos test-[bot]-[mechanism]-YYYY-MM-DD-[seq].jpg e.g. test-skimmer-cinch-2026-05-12-001.jpg # Match documentation match-[event]-[match-num]-[red|blue].jpg e.g. match-scrim01-Q23-red.jpg # Driver session drive-[bot]-YYYY-MM-DD-[driver-initials].jpg e.g. drive-pelican-2026-05-12-AM.jpg # Decision-rationale entries decision-[topic]-YYYY-MM-DD.png e.g. decision-tube-b-clamshell-2026-05-12.png

Use ISO dates (YYYY-MM-DD) — sorts chronologically by default.

⚙ Engineering Process Tracking

Per active project

EDP Phase by Project

Update weekly

One row per active project. The current phase determines which evidence the notebook needs this sprint.

Skimmer (2822A)

Pin specialist

IDCncDsgBldTstCmpItr

Currently: Build — Tube A fab

Pelican (2822C)

Combo generalist

IDCncDsgBldTstCmpItr

Currently: Build — four-bar PID

Spoonbill (2822D)

Active wrist

IDCncDsgBldTstCmpItr

Currently: Design — rotation gearbox

Osprey (2822E)

Chain bar + pincer

IDCncDsgBldTstCmpItr

Currently: Design — chain bar bearings

Identify Concept Design Build Test Compete Iterate

Evidence per phase: Identify (problem statement + scoring criteria), Concept (sketches + alternatives matrix), Design (CAD lock + decision rationale), Build (fab photos + R24 evidence), Test (50-cycle data + pass/fail), Compete (event match data + judge feedback), Iterate (post-event refinements + v2 design).

🏆 Competition Prep Timeline

Trigger when event ≤ 14 days out

Pre-Event Notebook Checklist

T-14 → T-0

Tap to check — persists per-device. Reset after each event.

T-14: Full EDP audit — every active project has current-phase evidence2 wk
T-14: Identify weakest sections; assign owners to plug gaps2 wk
T-7: R24 binder finalized for each polycarb bot (flat patterns, photos, count)1 wk
T-7: Master notebook printed/bound (or device ready if digital)1 wk
T-7: Cover/identity page current with team photo + season info1 wk
T-3: Judge interview practiced — 60s elevator pitch ready3 d
T-3: Drill 3 standard follow-up questions with the team3 d
T-1: Spare camera/phone charged; storage clear for event photos1 d
Day-of: Notebook + R24 binder + camera + sticky tabs packedEvent
Day-of: Inspector check — binder accessible in < 30 secondsEvent
T+1: Event results entry logged with judge feedback + photos+1 d

0 / 11

Judge Interview Quick-Card

Drill weekly

The 60-second pitch + the 3 questions that always get asked.

Open with the problem: "Override has two scoring elements with non-overlapping diameter envelopes..."
Pivot to your solution: "We solve this with three options: Tube A, Tube B, cup grabbers..."
End with evidence: "Here's the bench-test data showing..."

Likely follow-ups:

FU1"Walk me through how you decided that."

FU2"What's the next iteration?"

FU3"What would you do differently if you started over?"

🔗 References

Cross-links

📚

Role: Notebook

Full role responsibilities

📋

EN4 Templates

Bench-test entry format

⚠

R24 Audit

R24 binder source of truth

📝

Example Entry

Polycarb intake documentation

Common errors + fixes

🧰

Example: Decision Doc

R24 audit framing

🎯

Season HQ

Pull weekly sprint goals

📚

Public Rubric ↗

External judging guide

⚙ MAINTENANCE
Per-sprint setup: Reset the "Required Documentation" checklist Monday morning (or tap the Reset button on the card). Update the EDP phase tracker as projects move between phases — change .edp-phase classes from done → active → done and update the "Currently:" line.
Per-event setup: When an event lands within 14 days, start ticking the Comp Prep checklist. Reset after each event.
Persistence: Both checklists save to localStorage per-device; different scouts/notebook leads on different phones each have their own tracking. Use the team's shared notebook tool (Google Doc / Notion) for the team's actual source of truth.
Today highlight: The weekly timeline auto-highlights the current day of the week on page load — no manual update needed.

Notebook role layer: Role: Notebook · EN4 Templates · R24 Audit

Ops layer: Season HQ · Team Dashboard · Resources · Index