// PATTERN B · OPERATIONS DASHBOARD · POST-MATCH

Match Analysis

Post-match review workflow: capture what scored, what didn't, what opponents did, and what to drill before the next event. One entry per match, every match, every event. The drill prescription is the whole point — analysis without drill assignment is just storytelling.

Last updated: 2026-05-12 · Sprint Week 2 of 42 · Owner: Strategist (per bot) + Driver (sign-off)

Matches reviewed

0 / 0

No comp matches yet — pre-season

Drills queued

From scrimmage observations

Open issues

Tracked at bottom of page

Next comp

TBD

Schedule confirms post-kickoff

Match log Review template Sample filled entry Drill prescription matrix Trend tracker Open issues

01Match log

Reverse chronological. Most recent at top. Click a match row to expand the full review (or scroll to find its entry below). Empty until first comp.

Date	Event · Match	Alliance	Opponents	Score	Result	Reviewed	Drill assigned
No matches logged yet. First entries will appear here after the first competition.

Workflow: within 24 hours of each event, the Strategist owns filling out one review entry per match the team played. The Driver signs off on the "what worked / what didn't" sections (they were in the seat). Drill prescription rolls into /role-driver and /role-strategist for the next week's practice plan.

02Per-match review template

Copy this template for each match. Fill it in within 24 hours while memory is fresh. The Strategist drafts; the Driver reviews and adds/corrects from their POV; the Coach signs off if the drill prescription touches a major architectural decision.

// MATCH REVIEW TEMPLATE · ONE PER MATCH

Match ID

[Event · Q/F/SF/F-N]

Date / Time

[YYYY-MM-DD HH:MM]

Driver / coach

[Name / Name]

Bot used

[Skimmer / Pelican / Osprey / Spoonbill]

Alliance partner

[Team number + best subsystem]

Opponents

[Team numbers + observed strengths]

Final score

[us]-[them] · result (W/L)

Our scoring breakdown

[Pins scored where / Cups scored where / AWP achieved?]

Their scoring breakdown

[Same structure from opponent side]

Auton outcome

[Pass/fail + AWP if scored + which routine ran]

What worked

[2-3 specific things — not "we played well"]

What didn't

[2-3 specific things — identified root cause if known]

Opponent moves

[Defensive plays we hadn't seen, novel scoring patterns]

Mechanical issues

[Failures, near-failures, anything to inspect post-match]

Drill assigned

[Link to drill in section 04 + name]

Driver sign-off

[Initials + date when reviewed]

03Sample filled entry

Hypothetical example showing what a filled-in entry looks like. Use this as the bar for detail. Generic "we did our best" entries are useless — specifics are everything.

// EXAMPLE FILLED ENTRY (HYPOTHETICAL) · FOOTHILLS SCRIMMAGE Q-12

Match ID

Foothills Scrimmage · Q-12

Date / Time

2026-09-15 11:34

Driver / coach

[Driver-A] / Coach-T

Bot used

Pelican (2822C)

Alliance partner

5588B — strong cup scorer, weak on tall goal

Opponents

9610X (heavy claw, slow cycles) + 2587C (fast intake, but no autoaim)

Final score

122-87 · WIN

Our scoring breakdown

5 pins on tall (50), 4 cups on alliance goals (32), 4 cups on neutrals (24), AWP secured = 16. Total 122.

Their scoring breakdown

Mostly mid-tier pin scoring; no AWP. 9610X locked us out of midfield in last 30s but we'd already cleared.

Auton outcome

Routine "right-side-3pin" ran clean. AWP scored. 2 pins + 1 cup placed.

What worked

(1) Cup orientation detection nailed all 8 cups; no rotation needed. (2) Tall-goal queue with 5588B alliance was clean — we pre-staged, they shot. (3) Last-30s lockout from 9610X didn't matter because we'd already converted.

What didn't

(1) 2587C beat us to the center-field pin stack twice; lost 2 pins to them. (2) Pneumatic pincer cycle felt slow when we had a cup queued behind a pin pickup; pin-then-cup transitions are 600ms vs our 200ms target.

Opponent moves

9610X used corner pinning — novel for us. They committed a full robot to denial. Worth practicing how to break a corner-pin (back-out + 180 turn).

Mechanical issues

Right drive wheel feels loose post-match; inspect screw torque. Pincer cylinder shows minor seal weep — not urgent but log it.

Drill assigned

drill-pin-cup-transition-cycle · 4 sessions before next comp

Driver sign-off

[Driver-A] · 2026-09-15 19:00

04Drill prescription matrix

When a match review identifies a weakness, prescribe a specific drill rather than a vague "we need to practice more." Drills live here; assignments rollup into /role-driver weekly practice plan.

Drill	Targets weakness	Reps / session	Status	Assigned to	Due before
cup-orientation-pickup	Slow cup pickup when orientation needs correcting	10	DRILLING	Driver-A (Pelican)	Next comp
pin-cup-transition-cycle	Pin-then-cup transitions slower than 200ms target	15	READY TO RUN	Driver-A, Driver-C	Next comp
corner-pin-escape	Defensive corner-pinning (novel from Foothills sample)	8	DRAFTING	Strategist (write protocol)	Mid-October
Add new rows here as match reviews identify drillable weaknesses.

05Trend tracker (across matches)

Patterns across multiple match reviews. Updates after every event. The point: catch a problem that's recurring before it costs us a final.

Pattern	Matches affected	Root cause hypothesis	Status
Patterns emerge after 3+ matches reviewed. Empty until then.

06Open issues

Things noted in match reviews that haven't been resolved yet. Each one has an owner and a target date.

Issue	From match	Owner	Status	Target
Pneumatic pincer pin-to-cup transition timing (~600ms vs 200ms goal)	Foothills Q-12 (sample)	Engineer + Programmer	INVESTIGATING	Pre-next-comp
Corner-pin escape protocol — no rehearsed response	Foothills Q-12 (sample)	Strategist	UNWRITTEN	Mid-October

07Using this page

This dashboard supports a closed-loop competition feedback workflow:

Match occurs → Driver captures rough notes in scouting-center during the event.
Within 24 hours → Strategist fills in the per-match review template (section 02).
Driver signs off → Reviews the entry; corrects or adds from their POV.
If weakness identified → New drill in drill matrix (section 04) OR new issue (section 06).
Drill rolls into practice plan → /role-driver shows assigned drills for the week.
Recurring pattern after 3+ matches → Trend tracker (section 05) flags it; may require architectural change.

This page is private operations. Match data — especially the "what didn't work" and opponent observations — is competitive information. Don't share screenshots; don't paste content into public channels. The post-comp public summary lives elsewhere (notebook + match-day briefing).