SPARTAN 2822 — Internal Team Resource Public reference site →
📝 ROLE HUB · NOTEBOOK

The Notebook

Owns engineering documentation, the Engineering Design Process rigor, and judge-interview readiness. The notebook is the team's defense at inspection and the team's case for awards — both need to be ready before the event.

CurrentCompetitionPracticeResourcesCoordinationSkillsWeekly
01 / 07
Current Responsibilities
Ongoing
  • Maintain the team notebook for the current sprint — template adherence, EDP coverage, weekly entries.
  • Collect entries from teammates — driver logs, engineer build notes, programmer milestones, strategist analyses.
  • Photo & sketch documentation — clear, well-lit, labeled.
  • Maintain the R24 compliance binder for any polycarb bot.
  • Chase down stragglers each Friday before the weekly summary.
02 / 07
Competition Responsibilities
Event day
  • Bring it: physical notebook + R24 binder, current through the prior week.
  • Inspector ready: R24 evidence (flat patterns, photos, piece count) accessible in < 30 seconds.
  • Capture event-side: photos of matches, judge interactions, awards presentations — for next entry.
  • Judge interview prep: drill the team on the 60-second elevator pitch and standard followup questions.
  • Post-event: log results, judge feedback, what to refine before next event.
03 / 07
Practice Responsibilities
Every session
  • Daily entry: what got built, coded, practiced, decided.
  • Weekly summary entry (Friday) integrating all teammates' contributions.
  • Cross-team coordination: which entries are due, who owes what.
  • Maintain template adherence (Spartan Design system, Perrybotics-style structure).
  • Photograph any new mechanism, CAD lock, or fab session as it happens.
05 / 07
Team Coordination
Cross-role
w/ EngineerBuild photos, R24 evidence (flat patterns, piece count), CAD-lock screenshots by Friday.
w/ DriverPractice log entries: date, drills, hours, outcomes.
w/ ProgrammerCode milestone summaries with pseudocode and tuning rationale.
w/ StrategistStrategic decision rationale documented — judges score reasoned decisions highly.
w/ Whole teamJudge interview practice once weekly. Everyone takes turns answering.
06 / 07
Skill Development
Quantified
  • EDP fluencycite phase from memory
  • Photography for docsclear, well-lit, labeled
  • Hand sketching5 isometric / wk
  • Technical writingno rambling, no hedging
  • Judge interview60s elevator pitch
  • R24 complianceinspection-ready any day
07 / 07
Weekly Expectations
Mon → Fri
  • All teammates' entries collected by Friday EOD — chase the stragglers.
  • Master notebook updated with the week's integrated summary.
  • 1 R24 compliance audit against the binder — photos current, piece count tracked.
  • Cross-team check: every team deliverable from the sprint is documented somewhere.
  • 1 judge interview run-through with at least one teammate.
Other roles: Driver · Engineer · Programmer · Strategist

Back to ops: Season HQ · Team Dashboard · Index