4 classic problems with assistant coaches
Problem 1: Information trickles through WhatsApp
The plan runs via WhatsApp. Someone replies late, misses a message, or responds in the wrong chat. On the pitch, everyone has a different version of the plan.
WhatsApp is not built for team coordination. It lacks the structure a coaching team needs.
Problem 2: Unclear responsibilities
Who does what? Who leads the warm-up? Who is responsible for the goalkeepers? Who speaks to the player struggling today?
Without clear assignment, gaps emerge – along with duplication. Both do the same thing; nobody handles the rest.
Problem 3: Inconsistent coaching points
You tell player Jonas: "When pressing, always defend with the outside of your foot." Assistant coach Leon says a week later: "When pressing, put your body between the ball and the goal."
Both are right. But Jonas is confused. Consistency in coaching messages is a fundamental prerequisite for player development.
Problem 4: Assistant coach demoted to a helper
Setting up cones. Collecting balls. Moving goals.
That is not what a good assistant coach can – or wants to – deliver. If you treat an assistant coach as a mere helper, you will lose a colleague and a sparring partner in the medium term.
What good assistant coach integration really achieves
Structured integration of assistant coaches achieves four things:
Shared database. Both coaches have the same information – training plan, player data, attendances and cancellations, development evaluations. No knowledge gap, no information silos.
Clear role allocation. Who does what, when, and how. Defined, documented, visible to both. No more: "I thought you were doing that."
Consistent coaching points. When both coaches see the same training plan, coaching messages delivered to players align. Not always perfectly – but far more consistently than without a shared foundation.
Assistant coaches with their own areas of responsibility. Not a helper – a lead for a defined area. This increases both motivation and quality.
3 building blocks for structured assistant coach integration
Building block 1: Shared database
All information in one place, accessible to everyone:
- Current training plan (with drills, coaching points, timings)
- Squad with player profiles and current development evaluations
- Attendances and cancellations for the next session
- Training history: What did we work on last?
- Team news and announcements
When the assistant coach and head coach access the same database, most back-and-forth communication disappears. Not because you stop talking – but because you no longer need to relay basic information.
Building block 2: Role-based permissions
Not every assistant coach needs the same permissions. Coach OS distinguishes between three roles:
| Role | Can view | Can edit |
|---|---|---|
| Coach | Everything | Everything – squad, plans, evaluations, events |
| Assistant Coach | Everything | Training plan, player evaluations, comments |
| Team Assistant | Squad, events, news | Calendar, communication |
This distinction is not bureaucratic – it is practical. A team assistant accidentally deleting a training plan is a problem. Clear permission management prevents this.
Building block 3: Task allocation within the session
Who leads which phase? Who works on what with which group?
When the training plan is in Coach OS, tasks can be assigned directly:
- Phase 1 (Activation): Assistant coach Leon
- Phase 2 (Technique): Head coach
- Phase 3 (Game form): Jointly
- Cool-down and feedback: Head coach
Both coaches see this allocation before the session. On the pitch, there is no need for a lengthy briefing.
3 workflows: Before, during and after the training session
Before the training session: Automatically synchronised
Coach OS automatically notifies assistant coaches of plan changes. Adjusted the training plan? Leon sees it immediately – without you having to send a message.
Leon can review the plan before the training session, put forward suggestions or ask questions. Not on the pitch where time is tight – but beforehand, while there is still room to adapt.
During the training session: Both on the same app
Both coaches have Coach OS on their smartphones. Both see the current session. If you change a drill on the fly, Leon sees it in real time.
No paperwork chaos. No "Wait, what are we doing now?" Both are synchronised.
After the training session: Dividing evaluations
Player evaluations after the training session do not have to fall solely on the head coach. The assistant coach can observe the group he supervised – and record impressions directly in Coach OS.
This saves time. And it improves the assessment: two observational perspectives are more precise than one.
3 role allocation models
Model 1: Specialisation model
Each coach has their domain:
| Area | Responsible |
|---|---|
| Set pieces (corners, free kicks) | Assistant coach Leon |
| Athletic conditioning and warm-up | Assistant coach Katrin |
| Goalkeeper training | Goalkeeping coach (external) |
| Tactics and game forms | Head coach |
This model works well with larger coaching teams and squads with specialised assistant coaches.
Model 2: Group model
The squad is split into groups A and B – e.g. by skill level, position or age group.
- Group A (older players): Head coach
- Group B (younger players): Assistant coach
With rotation between groups: both coaches work with both groups – but across different phases.
Model 3: Phase model
Each phase of the session has a designated lead:
1. Activation (10 mins): Assistant coach
2. Technical block (20 mins): Assistant coach + head coach together
3. Game form (25 mins): Head coach leads, assistant coach coaches opposing side
4. Cool-down and feedback (5 mins): Head coach
Clear handovers. No gaps. No talking over the other coach's lead.
Coach OS is our own software. What follows is therefore not an impartial market overview, but an illustrative example. The criteria across the rest of this article apply regardless – use them to test any tool, including ours.
3 friction points Coach OS reduces
Friction point 1: "I didn't know that"
The classic phrase following a communication breakdown.
When all relevant information is documented in Coach OS and accessible to all assistant coaches, this phrase virtually disappears. Not because mistakes never happen – but because information gaps are structurally eliminated.
Friction point 2: "You just changed something"
You altered the training plan. Leon didn't notice. On the pitch, an awkward situation unfolds.
In Coach OS, changes to the plan are instantly visible to all assistant coaches. No more surprises.
Friction point 3: "My impression was different"
After the training session: you say Jonas was strong today. Leon says he didn't find Jonas convincing today.
With evaluations in Coach OS – complete with timestamps and optional comments – there is a documented baseline. You can find common ground or record both perspectives.
Assistant coaches in Coach OS: What is technically possible
- Up to 5 assistant coaches and team assistants per team
- Roles: Coach / Assistant Coach / Team Assistant (with differentiated permissions)
- Usable in any browser too – no smartphone required
- Real-time updates when plans change
- Player evaluations can be logged by multiple coaches
- Shared training history accessible
FAQ: Integrating Assistant Coaches in Football
How many assistant coaches can I invite in Coach OS?
Up to 5 assistant coaches and team assistants are possible per team – across different roles with varying permissions.
Does the assistant coach also need the app?
No. Assistant coaches can also use Coach OS in their web browser. All features are accessible via browser as well.
Can the assistant coach plan training sessions independently?
That depends on the assigned role. With assistant coach permissions, he can create and edit training sessions. With team assistant permissions, he only has view access to plans.
Does the assistant coach see the same player data as I do?
Yes. Assistant coaches with appropriate permissions see all player profiles, development evaluations and attendance statistics.
What happens if the assistant coach cancels an event?
Scheduling conflicts within the coaching team become visible on the dashboard. You can communicate directly within Coach OS or plan session coverage.
Can I store coaching points for the assistant coach?
Yes. In the training plan, you can specify coaching points per drill and phase. Assistant coaches see the exact same points – ensuring consistent messages on the pitch.
Can the assistant coach invite players?
That depends on the assigned permissions. With head coach permissions, yes; with assistant coach permissions, this is configurable.
→ Test Coach OS for free: coach-os.com