How to run a football club technical meeting (4-step method)

You come out of your technical meeting feeling like you have wasted an hour and a half. The coaches listened politely, no one really exchanged ideas, and in three weeks, nothing that was said will have changed on the pitch. If this scene sounds familiar, you are not alone: it is the lot of the majority of technical meetings in amateur football.

The problem almost never comes from the content discussed. It comes from the lack of structure.

A well-run technical meeting can, conversely, become the real engine of progress for a staff, far more effective than an accumulation of documents sent by email.

This article presents a concrete method, in 4 stages, to transform your technical meetings into real drivers of collective training.

Why the technical meeting is an underused tool

In many amateur clubs, the technical meeting has slipped into a purely administrative format: match calendar, reminder of schedules, disciplinary points. These subjects have their place, but they do not, on their own, justify bringing together an entire staff for an hour.

A technical meeting has a different objective: to help coaches progress collectively in their practice. It is the only moment in the week when the whole staff is gathered in the same place, without players, without pitch constraints. Not using this time for pedagogy means depriving yourself of a free continuous training tool that is already scheduled in the club's calendar.

A staff that regularly exchanges views on its practices progresses faster than a staff that only receives top-down instructions. The most experienced coaches pass on their knowledge, the younger ones ask questions, and the club gains in pedagogical consistency from one age group to another.

The frequent mistakes that drain a technical meeting of its value

Before detailing the method, it is useful to identify what makes the majority of meetings fail.

A vague or non-existent agenda.

Without an announced structure, the meeting goes in all directions. Everyone brings up whatever comes to mind, out of order, and time runs out before the essentials have been addressed.

A single person monopolizing the speaking time.

The technical director or the head coach talks for 45 minutes, the others listen. No interaction, no feedback from the field coaches, who are nevertheless best placed to observe what really works with the players.

Too many subjects covered superficially.

Wanting to cover everything in a single meeting: the game project, the weekend results, the tournament organization, a pedagogical point, leads to nothing being explored in depth. One subject well handled is worth more than five subjects skimmed over.

The absence of decisions acted upon.

The meeting ends on a soft consensus: "we all agree," without any precise action being assigned to someone, with a deadline. Result: nothing changes concretely.

A frequent mistake is confusing an information meeting with a technical meeting. The first serves to pass on instructions; the second must serve to help the staff progress on the substance of the coaching profession.

The 4-stage method to structure an effective technical meeting

Here is a simple framework, transferable to any club, whatever the size of the staff.

Stage 1, The quick collective review (about 10 minutes)

Each coach present shares, in one or two sentences, a success and a difficulty encountered in their age group since the last meeting. The objective is not to recount the weekend in detail, but to give everyone a structured space to speak.

Concretely, during your meeting, time this round table: two minutes maximum per person. This prevents a particular subject from taking up all the space, and it makes it possible to identify, by omission, the themes that come up among several coaches; often, that is where the real subject to address next is hidden.

Stage 2, One pedagogical subject explored in depth (about 15 minutes)

Choose a single theme for the meeting, and go deep.

For example: playing out from the back under pressure in U11s, managing defensive transitions in U15s, or communication with parents.

Let us take the example of a group of U13s that systematically loses the ball when playing out from goal under opposition pressure. Rather than listing generalities about playing out from the back, the meeting can serve to dissect precisely: what solutions to offer the players, what reference points to give them, what exercise to set up from the following week. The coach can then observe a real change in their team's play, because the subject was addressed with depth rather than on the surface.

This key moment of the meeting can be based on a video, a tactical diagram, or simply a structured oral exchange around specific questions.

Time 3: The exchange of practices between coaches (about 15 minutes)

This is often the richest time, and the most neglected. One coach presents an exercise or a situation that worked well in their session, and the others question it, challenge it, propose variations.

This horizontal exchange has a value that top-down transmission does not have: it values the field expertise of each coach, including the least experienced, and it creates a culture of sharing within the staff rather than a fixed hierarchy. On the field, this can translate into better pedagogical consistency between age groups: an exercise tested and validated in U11 can be adapted in U9 the following week.

Time 4: The decisions made (about 10 minutes)

This is the time that makes all the difference between a useful meeting and a meeting for nothing. Before closing, concretely list what has been decided: which action, carried by whom, with what deadline.

A meeting without a decision made at the end is a meeting that will change nothing on the field. A simple table, even handwritten, is enough:

Test the build-up exercise under pressure | U13 coach | Tuesday session

Harmonize the tactical vocabulary U9-U11 | Technical lead + U9/U11 coaches | Next meeting

Prepare communication to parents | U15 coach | Before the next match

This table can be shared in writing after the meeting (email or staff WhatsApp group), so that everyone keeps a clear record of their commitments.

Example of a ready-to-use agenda

To concretely visualize this method, here is an example of an agenda for a typical 50-minute meeting, with the timing of each time and a decision-tracking table to fill in.

You can use it as is for your next meeting, or adapt it to the usual format and duration of your staff.

Practical tips to anchor this method over time

Set a total duration and stick to it.

An effective technical meeting lasts between 45 minutes and one hour. Beyond that, the staff's attention drops, whatever the quality of the content.

Rotate who leads.

Entrusting time 2 (pedagogical topic) or time 3 (exchange of practices) to a different coach at each meeting strengthens the commitment of the whole staff, and prevents the meeting from resting only on the technical lead.

Keep a written record.

A simple half-page report, sent after each meeting, makes it possible to track the evolution of decisions from one meeting to the next, and to avoid returning to the same subjects without progress.

Start small if your club does not have this culture.

If your current meetings are only administrative, do not try to apply the 4 times all at once. First introduce time 4 (decisions made): it is the simplest change to put in place, and the one with the most visible impact from the first meeting.

FAQ

How long should a technical meeting last?

Between 45 minutes and one hour is enough when the meeting is structured. A longer duration often reflects a lack of framing rather than a real need for additional time.

How often should a technical meeting be organized?

A monthly frequency is a good starting point for most amateur clubs. Some more structured clubs operate on a twice-monthly meeting, especially during a busy season period.

Who should lead the technical meeting?

Most often the technical lead, but rotating the leading between coaches, at least for certain times of the meeting, strengthens the involvement of the whole staff.

How to manage a coach who does not participate in the exchanges?

The framing of time 1 (timed round table) helps to give everyone an equal chance to speak, including the most discreet coaches, without putting them in difficulty in front of the group.

Should administrative topics be dealt with during the technical meeting?

It is preferable to separate them, for example by sending them in writing before the meeting, to devote the collective time to pedagogy and exchange between coaches.

Conclusion

A technical meeting has value only if it changes something on the field. The 4-time method, collective review, pedagogical topic explored in depth, exchange of practices, decisions made, makes it possible to structure this moment without complexity, and to transform an agenda constraint into a real tool for continuing education for your staff.