Session builderU19 · Tue 19:00 · Pitch 2
Template — pressing wk- 01Rondo 6v2Technical12′1.4
- 02Pressing triggersHigh intensity18′2.6
- 03Small-sided 4v4Conditioning20′2.4
- 04Corners — walkthroughSet pieces8′0.8
Selected work / 02
LKRM Team Management
LKRM runs the working week of a student-athlete team. Voortgang designed and engineered the platform end to end — from the board-capture flow that turns a photographed whiteboard into a structured session, to the readiness board that watches every practice, data-gated selection, and the live matchday run sheet every role reads.
LKRM — board capture · LK-01
Photograph the board.
LKRM builds the week.
01 — Capture
Tuesday is drawn the way it has always been drawn — in marker, on the board, ten minutes before everyone goes home.
02 — Structure
LKRM reads it: routes become drills, marks become players, and the scribble becomes a session with minutes and load.
03 — Ship
The session is on every phone before the coach leaves the room — and the console shows who has seen it.
LKRM Team Management — coach consoleBoard LK-01 · U19 · captured Tue 18:47Voortgang — strategy · design · engineering
- 4 minfrom board photo to published session — traced, structured, and on every player's phone.
- 87%squad readiness by Friday — check-ins, treatment, and install reps rolled into one number the depth chart can act on.
- 30 sfor a player to log a post-practice check-in — soreness, sleep, strain — read by the coach before breakfast.
- 0group-chat threads needed to run a matchday. The run sheet is the source of truth.
The engagement
A season is a thousand small Tuesdays.
LKRM came to us as a sentence: running a team is a full-time job that nobody is paid for. The plan lives on a whiteboard, the squad lives in a group chat, and Saturday runs on memory. The brief was to move the whole working week — plan, prep, run, review — onto one platform without losing the whiteboard's speed.
So we kept the whiteboard. LKRM's defining move is board capture: the coach photographs what they drew, and the platform turns it into structured, publishable work. Everything else hangs off the same spine — record the plan, and watch it become real.
- CapturedThe training board, photographed — traced into drills, players, and a session plan.
- PreppedCheck-ins and install reps build the readiness picture by Friday — flags raised while there is still time to adapt.
- RunSaturday reads from one live run sheet — arrival, warm-up, kickoff, planned subs.
- ReviewedMinutes and load flow back into the ledger that shapes next week's plan.
The platform — one working week
Plan it. Prep it. Run it.
The coach console, room by room: a Tuesday session assembled from drill blocks against a load budget, a readiness board filling as the week's practices land, and a Saturday that runs off the sheet. It advances on its own — or click through the rooms. Synthetic data throughout.
Load budgetWeek 34
7.2of 8.0
DistributionSquad · 18 players
Publish session
Published Tue 18:42 · 18 deliveredThe surfaces
Every job the touchline actually has.
- Squad
The roster is the database
Positions, numbers, guardians, documents — one squad record that availability, selection, and dues all read from. Nothing is retyped twice.
- Sessions
Built from blocks
A drill library where every block carries minutes and a load value. A session is a sum; the week is a budget; a spike is a flag before it is a strain.
- Readiness
Practiced, treated, cleared
For a student athlete, attendance is not the question — condition is. Post-practice check-ins, physio status, and rep counts on every installed play roll into one readiness picture by Friday.
- Selection
Only the eligible
The lineup board can only field players the data allows. Fitness flags, suspensions, and lapsed clearances are visibly parked, with cover suggested from the depth chart.
- Matchday
One run sheet, every role
Arrival to final whistle as visible states — warm-up, team talk, kickoff, planned subs at the hour. Changes broadcast to the bench and the touchline alike.
- Travel & kit
The Saturday logistics
Meet times, venue pins, kit color, and lift manifests attached to every fixture — the forty questions that used to be forty messages, answered before they are asked.
Pitch-side
Built for the sideline,
not the back office.
Matchday surfaces are designed for where they are actually used: a floodlit touchline in November. Dark by default, readable at arm's length, and honest about connectivity.
- Offline-first run sheet — cached before kickoff, reconciled after
- Tap targets sized for gloved thumbs and one-handed use
- Dark by default under floodlights; print-clean for the clubhouse door
The system
Decisions that made it feel inevitable.
A few of the calls that shaped the build — open one to see why it was made.
The board is an input deviceCapture · trace · structure
Why
Coaches already have a fast, expressive planning tool: the whiteboard. LKRM does not replace it — it reads it. A photograph becomes routes, players, and drill blocks the coach confirms in one pass, so the plan exists as data without anyone learning a diagram editor.
Readiness is measured, not assumedCheck-ins · treatment · install reps
Why
A student athlete doesn't choose Saturday — the fixture list does. What varies is the shape they arrive in. So LKRM reads the week itself: rep counts on every installed play, a thirty-second wellness check-in after each practice, treatment status from the physio — rolled into a readiness picture the depth chart can act on by Friday.
Load is a budgetEvery drill carries a cost
Why
Sessions sum their drills against a weekly budget per squad, and matchday minutes feed the same ledger. The platform flags the spike while it is still a plan on a screen — not a strain on a Tuesday.
Selection sees only the eligibleRules live in the database
Why
Suspensions, fitness flags, and lapsed academic clearance gate the picker at the data layer, not in the coach's memory. The lineup board shows who is parked and why, and suggests cover from the depth chart.
The run sheet survives the signal shadowOffline-first matchday
Why
Every phone caches the run sheet before kickoff and reconciles when the signal returns. A north-stand dead zone does not get a vote in how Saturday runs.
- Strategy — Voortgang
- Product strategy, program design
- Design — Voortgang
- UX/UI, design system, motion
- Engineering — Voortgang
- Architecture, front-end & backend, realtime sync
- Surfaces
- Coach console · player app · club admin