01
Glossary
Weekly Cockpit.
An online coach's ranked roster surface — sorted by who needs the coach this week, with the signal that flagged them next to each row.
Weekly Cockpit
This week · 24 clients
02
Definition
What Weekly Cockpit means.
A Weekly Cockpit is the home surface a coach opens at the start of the week to see where the roster actually stands. Not a dashboard with widgets. Not a CRM pipeline. Not a project management board. It is a single ranked list of every active client, sorted by who needs the coach right now and why — at-risk, missed check-in, PR, past-due payment, plateau, and other signals that change the week. The week starts as triage, not catch-up. The term exists to replace “open the app and try to remember” with a surface that does the remembering for you.
03
The job
One screen. Triage, not stack.
The job of a Weekly Cockpit is to compress the operational decisions of a coaching week into one ranked surface. This is what separates it from a generic dashboard.
- Every active client in one ranked list — not alphabetical, not grouped by tag.
- A status flag per client — at-risk, missed check-in, PR, past-due, plateau.
- A reason next to every signal, so the coach reads context, not raw labels.
- The check-in queue, showing whose week is waiting on the coach.
- Quiet clients pushed down — no news is good news, treated that way.
- A clean read on the week that doesn't expand into a dozen inboxes.
Anything that does fewer of these is a dashboard. Anything that does more without ranking by what needs a decision is a database.
04
Adjacent surfaces
Categories that look similar, but aren't the same thing.
A Weekly Cockpit is often confused with surfaces that look superficially similar. Each does part of the job. None does the whole job.
- A dashboard. A widget grid showing metrics is a dashboard. A Weekly Cockpit ranks clients by what needs the coach next, with a reason.
- A CRM. Sales pipelines manage prospects through stages. A Weekly Cockpit manages active coaching relationships on a weekly cadence.
- A project board. Kanban columns and tickets are built around tasks moving through statuses. Coaching lives at client level, across multiple signals at once.
- An inbox. Notifications and DMs pull a coach into whoever messaged most recently. A Weekly Cockpit pulls a coach into who needs them most, regardless of who has the loudest thumbs.
The word matters: cockpit, not dashboard, because the surface is for an operator deciding the next move, not a viewer reading a chart.
05
When you need one
When the roster is too big for memory and the inbox stops being a coaching surface.
A coach with three clients does not need a Weekly Cockpit. The roster fits in memory, the inbox is a fine signal layer, and Monday morning is not a triage problem. The trigger comes later, and it looks like operations starting to leak through the cracks.
- The roster is past five active clients and growing.
- Mondays start by scrolling messages to remember what each client said.
- Renewals are running on whatever cadence you happen to remember.
- Adherence drift shows up at the cancellation email instead of in time to act.
- The loudest clients are setting your priority more than the slipping ones.
- What it replaces: spreadsheet triage, WhatsApp memory, Notion rosters nobody opens, and the "I'll remember" cadence that lets renewals slip.
A Weekly Cockpit does not replace coaching judgement. It replaces the back-of-the-mind cost of holding the whole roster in your head.
06
TrainedBy and the term
TrainedBy's Weekly Cockpit.
Inside TrainedBy, Weekly Cockpit is the home surface — the first screen a coach sees inside the product. Not a tab to navigate to; the surface the product opens on. It is opinionated by design: ranked by what needs a coaching decision this week, with reason text on every row, and quiet clients pushed down. Outputs from across the product land here as cockpit rows — check-ins, payments, AI Body Scan reads, plateau detection, anomaly detection, and PR auto-detection.
- The first screen on web and in the coach app — not a separate tool to remember to open.
- Opinionated and zero-config — works out of the box, with the signals wired in across the product.
- Connected to the rest of TrainedBy — every signal lands here, not in a separate notifications tab.
- See /features/weekly-cockpit for the full product surface.
Weekly Cockpit is one of the six surfaces in a coach operating system. For the deeper product view, go to /features/weekly-cockpit.
07
FAQ
Common questions on the term.
What is a Weekly Cockpit?
An online coach's ranked roster surface — a single screen that sorts every active client by who needs the coach this week, with the signal that flagged them visible next to each row.
Why is it called a cockpit?
Because the surface is built for an operator deciding the next move, not a viewer reading a chart. The job is closer to flying than displaying.
How is a Weekly Cockpit different from a dashboard?
A dashboard shows numbers. A Weekly Cockpit ranks people by what needs the coach next, with a reason. The output of a dashboard is metrics. The output of a cockpit is priority.
Is "Weekly Cockpit" an industry-standard term?
Not yet. It's TrainedBy's framing for the surface that replaces inbox-first and spreadsheet-first coaching at scale.
Do I need a Weekly Cockpit if I have a small roster?
Probably not. At very small scale, memory and the inbox are often enough. A cockpit pays off once the roster is past memory and the inbox stops being enough of a signal layer.
What does TrainedBy's Weekly Cockpit look like?
See /features/weekly-cockpit for the full product surface — the ranked roster, the signals that land there, and how it sits at the centre of the coaching week.
08
Final CTA
See how TrainedBy's Weekly Cockpit works in practice.
See the surface, the signals, and how the week starts already triaged.