TEAM 2822[X]

v[X.X]

ACTIVE BUILD

[ROBOT NAME]

Lift: [LIFT TYPE] · Manipulator: [MANIPULATOR] · Toggle: [TOGGLE TYPE]

C: [CAPTAIN NAME] [MEMBER 2] [MEMBER 3] [MEMBER 4] [MEMBER 5]

Updated

[MON DD, YYYY]

Overall

Competition Readiness

Build

Code

Drive

Notebook

Match Prep

🔥 Sprint & Daily

Sprint = weekly · Daily = morning

This Week's Sprint

Week [N]

°[SPRINT GOAL 1][OWNER]
°[SPRINT GOAL 2][OWNER]
°[SPRINT GOAL 3][OWNER]
°[SPRINT GOAL 4][OWNER]
°[SPRINT GOAL 5][OWNER]

0 / 5 done

Today's Priorities

[DAY MON DD]

→[PRIORITY 1 — what gets worked on first][TIME]
→[PRIORITY 2][TIME]
→[PRIORITY 3][TIME]

Reset every morning · If you skip a day, leave yesterday's content

⚙ Build · Code · CAD

Update weekly

Build Progress

°
[BUILD ITEM 1]0%
°
[BUILD ITEM 2]0%
°
[BUILD ITEM 3]0%
°
[BUILD ITEM 4]0%

Programming Progress

°
[CODE MILESTONE 1]0%
°
[CODE MILESTONE 2]0%
°
[CODE MILESTONE 3]0%
°
[CODE MILESTONE 4]0%

CAD Progress

°
[CAD ASSEMBLY 1]0%
°
[CAD ASSEMBLY 2]0%
°
[CAD ASSEMBLY 3]0%

OnShape link: [ONSHAPE DOC URL]

🎮 Drive · Auto · Notebook

Drive after each rep · Auto after each test · Notebook weekly

Driver Reps

0.0 hr / wk

MON

0.0

TUE

0.0

WED

0.0

THU

0.0

FRI

0.0

SAT

0.0

Skill Targets

°[SKILL TARGET 1 — e.g. 5 consecutive pin pickups]
°[SKILL TARGET 2]
°[SKILL TARGET 3]

Target: 4 hr / driver / week

Autonomous Testing

0 / 3 routines

Pass / fail per attempt — aim for ≥ 8/10 to commit

[AUTO A]

0/10

[AUTO B]

0/10

[AUTO C]

0/10

Notes: [latest tuning observations — what's working, what's not]

Notebook Updates

EDP Phase A

°This week's design entryDue Fri
°Driver practice log entriesPer session
°CAD lock screenshotsOn lock
°R24 compliance evidence (if polycarb)On fab
°Decision rationale (architectural choices)As made

Guide: notebook rubric →

📋 Testing Logs

Prepend new entries at top

Recent Tests

Last 7 days

°[TEST NAME] — [OUTCOME / NOTES][DAY MON DD]
°[TEST NAME] — [OUTCOME / NOTES][DAY MON DD]
°[TEST NAME] — [OUTCOME / NOTES][DAY MON DD]
°[TEST NAME] — [OUTCOME / NOTES][DAY MON DD]

Protocol reference: /phase-a-bench-test-protocols

Active Blockers

0 open

✖[BLOCKER] — [DESCRIPTION + WORKAROUND][DATE OPENED]

If empty, the team has zero open blockers — ship it.

⚡ Strategy & To-Do

Strategy ad-hoc · To-Do continuous

Match Strategy Notes

[STRATEGY THEME 1]: [the play, the rationale, when to use it]

[STRATEGY THEME 2]: [the play, the rationale, when to use it]

[STRATEGY THEME 3]: [the play, the rationale, when to use it]

Alliance role: [combo bot / pin specialist / cup specialist / flexible]
Strongest pairings (per matrix): [partner names]

Reference: /fleet-manipulator-matrix

To-Do List

0 / 0 done

[TODO ITEM 1] HIGH

[TODO ITEM 2] HIGH

[TODO ITEM 3] MED

[TODO ITEM 4] MED

[TODO ITEM 5] LOW

Sort high → low · Move to "done" don't delete · Clear every Friday

⚙ HOW TO USE THIS TEMPLATE

FIRST-TIME SETUP (~10 minutes per team):
1. Copy this file to team-dashboard-[robotname].html (e.g., team-dashboard-skimmer.html).
2. Find & replace every [BRACKETED PLACEHOLDER] with your team's value. Search for [ in your editor to catch them all.
3. Set the data-pct attribute on each .r-row in the readiness gauge (Build, Code, Drive, Notebook, Match Prep). Overall % auto-computes on page load.
4. Link the new file from /index.html and /season-hq.html (under Quick Links).

WEEKLY UPDATES (Monday AM, ~15 minutes per team):
• Update the five data-pct values in the readiness gauge.
• Rewrite the Sprint Goals card with this week's goals.
• Update Build / Code / CAD sub-item progress percentages.
• Update notebook entry status.
• Update the "Updated" date at the top right of the identity strip.
• Clear the To-Do list (move done items off or delete).

DAILY UPDATES (morning, ~2 minutes per team):
• Today's Priorities card: replace tasks. If you skip a day, leave yesterday's content (don't go stale).
• Driver Reps: log hours per day after practice.
• Auto Testing: update routine cell classes (pass / fail / untested) after each test session.
• Testing Logs: prepend a new entry at the top after each bench test.
• Active Blockers: open or close as they appear.

STATUS COLOR LEGEND (consistent across all sections):
✓ done / on track · ◯ in progress · ⚠ at risk · ✖ blocked · ° not started

READINESS GAUGE COLOR TIERS (assigned automatically by JS based on percentage):
80–100% green · 60–79% cyan · 40–59% gold · below 40% red

SECTIONS NOT TO REORDER: the identity strip and readiness gauge must stay first — team members open this on their phone in the morning and the readiness % is the headline number. Sprint and Daily must be the next visible block (above the fold on laptop).

WHAT TO DO IF A SECTION DOESN'T APPLY: hide the card with style="display:none;" on the .card div rather than deleting — makes it easy to re-enable later. The Active Blockers card especially: keep it on the page even if zero open, so the "zero blockers" state is visibly affirmed.