Matchday Lab keeps the thread across sessions, matches, training load and sixty-second debriefs, so every recommendation starts from what your team actually did this season.
Free during beta · No credit card required
Respects the MD-2 intensity ceiling · drawn from 125 drills
Accept it and Thursday's plan is on the calendar, reasons included.
Every training event is one lifecycle on one page, and every pass through it makes the next one sharper.
Pick the focus. The planner assembles a full session from the drill library in under a second and cites the debrief signals, match context and season phase that shaped it.
Train. Cut a block, extend another, chase what's working. Run mode logs every change for the debrief.
One screen, sixty seconds. How hard it felt, how it landed, who was there, and keep-or-cut verdicts on every block. Skip what you don't know.
Memory absorbs it. Theme progress updates, drill rotation adjusts, and the next suggestion already knows what happened today.
Every training day is labelled by how far it sits from the next match — MD-2 means two days out — and intensity ceilings follow that countdown. Each session's load comes from a simple formula, how hard it felt × how long it ran, and the week is scored against a target band.
Every day on the strip carries its intensity stripe, its distance from the match, and an estimated load chip — AU is the load unit, effort × minutes. The ~ disappears when the plan locks.
Thu is the lever. Trim the SSG block from 25′ to 20′ and the week lands back in band before Saturday's match.
You set the band. When the week drifts over it, the guardrail points at the day that fixes it.
The schedule · two-week matchweek strip
One screen after training: how hard it was, which blocks worked, who was there. Everything is optional except the save, and every answer goes into season memory.
The effort score is the RPE scale, 0 to 10. Load updates as you drag: that score × actual minutes, next to the figure you planned.
Keep or cut, per block. The changes you made in run mode are already filled in, and your verdicts feed the drill rotation for next week's plan.
The session · plan → run → debrief, one page
A dated ledger for every player: observations routed straight from debriefs, rating snapshots you can lay over each other, and development goals that get set, reviewed and achieved.
“First instinct is now inside-out — took the cutback option twice instead of forcing the far-post cross.”
Beat the first defender 1v1 and deliver — achieved in 78 days.
You type it once in the debrief. It's filed here with the session it came from.
6 of 8 categories shown · rated by the coach
Two coach snapshots, ten weeks apart, on the same axes.
The player ledger · one player, one season
A 46-week season on a single axis: training blocks, planned against actual weekly load, and every theme's journey from introduced to passed.
Late-season push → B7 championship prep
One card holds the block you're in, how closely the plan was followed, and where the curriculum stands.
3 of 21 themes shown · updated from debriefs
Every theme is tracked from its first session. What's working stays in rotation, and a slipping theme gets flagged while there's still season left to fix it.
The season · 46 weeks on one axis
Every drill carries a structured tactical diagram: pitch, players, phases and typed movement arrows. In animation the ball always travels with a carrier, the way the drill actually runs.
Area, players, equipment, phases and seven arrow types (run, pass, dribble, shot, sprint, jog, lofted) on every one of the 125.
Describe the drill you need.
Every draft is scored against a quality gate before you see it
Generated drafts have to clear the same completeness bar as the curated library before they reach your review.
The drill library · ranked for this week's focus
Paste the roster from your group chat and the fixtures from the club site. The parser reads both, you confirm each row, and your first training week is generated before you see a single empty form.
Injuries, position ambiguity, duplicates from the old list: the parser flags them and you decide. About three minutes from paste to a confirmed squad.
First-run setup · two pastes, zero blank forms
Every suggestion names its sources: the sessions, debriefs and results behind it. Anything that came from the memory loop wears a violet tag, so you always know which ideas are the machine's and where they started.
City build through their right half-space — your pressing has held stable across 5 straight sessions. Set the trap there.
"First instinct is now inside-out — took the cutback option twice instead of forcing the far-post cross."
Transition attack is on its 3rd consecutive improving session, and your next opponent concedes most from broken play — keep the thread running into MD-2.
The season memory — every signal feeds the next plan
Bright for the desk, dark for the evening session. Every surface ships in both themes, and you can switch between them any time.
For most AI operations, player names become “Player 1”, “Player 2” and emails and phone numbers are redacted before anything reaches our AI provider. Enforced in code, verified by a dedicated test suite.
We never sell coaching data. Export your whole workspace as JSON from settings, and deletion on request covers backups too. Strict multi-tenant isolation keeps every organization's data its own.
Every recommendation is a starting point with its reasoning attached. You make the coaching decisions.
A real season plan across training and match days — without the hours of admin it used to take.
Consistent curricula across squads, theme tracking that survives staff handovers, and a ledger for every player.
Load management, periodization blocks, and matchweek structure that scales to a 40-match season.
Matchday Lab is free during beta. Paid plans are coming — from volunteer coaches to club academies to professional setups.
Early users lock in founder pricing
The demo is a full season already in motion. Open it and pull on anything you saw above.
Free during beta · No credit card required