Best practices for an effective steering committee

Updated May 6, 2026

In short : The steering committee (COPIL) is the body that strategically steers a large-scale project. It brings together 5 to 7 decision-makers around three missions: monitoring progress, arbitrating deviations, anticipating risks.

On cross-functional projects that involve several departments, a significant budget and a duration of more than three months, governance is rarely played out in team meetings. It is played out in the steering committee. It is the body where strategic decisions are made, where budget-time discrepancies are arbitrated, where major risks are escalated. An effective copil moves the project forward; A poorly animated copil slows him down by diluting the responsibilities of all the participants.

This guide summarizes what an effective copil should do: who to invite, how often to meet, how to structure a relevant agenda, and the four mistakes to avoid so as not to turn it into a sterile debriefing meeting. It also offers a concrete example of a standard agenda over 1h30.

Steering committee: definition

The steering committee is a series of regular meetings that bring together the decision-makers of a project to steer its strategic progress. It is different from a simple team meeting: it does not deal with the day-to-day operations (this is the role of the project committee), it validates the main orientations, arbitrates critical deviations and anticipates risks likely to compromise the success of the project.

Synonyms: copil, steerco, steering committee

The terms copil, steerco and steering committee refer to the same body in French-speaking organizations. Copil predominates in the administrations, the IT Services and consulting firms. Steerco is used more in large international groups and subsidiaries of Anglo-Saxon groups. The difference is a matter of use, not function.

For teams juggling between French and English speakers, the following table maps the five project instances and their equivalents:

A cross-functional team called upon at regular intervals

The COPIL brings together a cross-functional team on a regular basis. Responsible for monitoring the progress of the project, this team arbitrates and makes strategic decisions.

As a result, the steering committee is essential to good project management.

Differentiate between steering committee, project team and project governance

Like project governance , which deals with the overall organization of the company, the steering committee ensures the overall management of a project.

The project team (COPROJ) also makes it possible to manage a project, but on a micro scale. It deals with the day-to-day operations, whereas the steering committee covers the strategic dimension.

When does a project need a copil?

Not all projects justify a steering committee. The creation of a copil becomes relevant from a threshold of complexity that combines three criteria: a project that mobilizes at least three distinct departments or businesses, a committed budget of more than 50,000 euros, and a provisional duration of more than three months. Below this threshold, a weekly project committee is usually enough — setting up a copil on a simple team project amounts to over-governance that dilutes responsibilities more than it structures them.

For cross-functional strategic projects — redesign of an information system, mergers and acquisitions, opening of a subsidiary, organizational transformation — the copil is not optional: its absence is paid for in budget drifts and deadlines that far exceed the cost of 1h30 of monthly meetings.

What is the role of a steering committee?

Present the status of the

The role of the steering committee is to monitor and present the progress of the project. He ensures that all the elements are in place to achieve the objectives. This presentation is not just a raw report: it exposes the milestones achieved in relation to the provisional schedule, the budget consumed in relation to the allocated budget, the resources mobilized in relation to the capacity, and the associated variances.

The COPIL thus guarantees the transparency of information and the alignment of all stakeholders on objectives, tasks and deadlines. In the event of a discrepancy, it is within this framework that corrective actions are decided, based on the progress reports produced by the project manager if necessary.

Arbitrating important topics

In fact, the main objective of the steerco is to make strategic decisions on blocking issues. This meeting serves to gather the opinions of the various stakeholders; It must lead to recorded decisions, not to a shared observation.

It is during the steering committee that any changes in strategy are usually made.

Raising the alert in case of risks

Project risks remain unavoidable. The steering committee, by allowing regular monitoring, alerts in the event of deadlines, budgets, or any other risk threatening the success of the project.

In the event of an alert, the COPIL measures the probability that these risks will occur and anticipates solutions.

What are the challenges of a COPIL?

Determine the strategic direction of the project

The steering committee aligns the project's objectives with the company's strategy. This may require structuring decisions such as:

• the mobilization of a new project budget,
• recruitment or resource modification,
• the postponement or even cancellation of certain deadlines.

Provide support to the project manager

The project manager, who is responsible for the smooth running of the project, does not bear the decision-making burden alone. The steering committee distributes this burden with other, generally experienced, profiles.

These profiles bring their perspective and experience to unblock complex situations, and contribute to setting up a well-thought-out risk management to anticipate solutions.

Keeping the project on track

The steerco also makes it possible to monitor the execution of missions. This prevents project drift and ensures that all elements remain aligned with achieving goals. The COPIL also takes stock of the expected deliverables and those ready to be delivered.

In the event of discrepancies or difficulties (significant delays, changes to deliverables), the steering committee can influence the allocation of resources, the extent of the scope, or even opt to abandon the project.

Define the resources needed to carry out the project

The steering committee is responsible for the optimal allocation of resources to achieve the objectives: additional budget if the drift is justified, business reinforcements on sensitive phases, arbitration between competing projects for rare profiles. This arbitration exercise is made possible by the composition of the committee: only decision-makers with authority over resources can make these choices, which justifies the systematic presence of the sponsor and the business departments concerned.

If necessary, the COPIL acts on the allocation and planning of resources, whether financial, human or material.

Establish transparent communication

Finally, the steerco ensures good communication between all project stakeholders. The steering committee ensures that this communication is regular and transparent, and offers a homogeneous level of information to all stakeholders.

Regular and clear reporting must be established. Producing summary reports after each meeting ensures that all participants are aligned by discussing:

• a summary of the important points,
• advancement,
• the problems encountered,
• decisions made.

Stafiz aggregates all your project data

 

Discover our reporting tool

Copil, cotech, coproj: the project governance triad

On a large-scale project, three bodies rarely coexist by chance: the steering committee (copil), the technical committee (cotech) and the project committee (coproj). Each has a distinct mandate, its own cycle and a specific composition. Confusing them — or worse, using only one out of the three — is one of the most common causes of project drift.

Steering Committee (copil): the strategic body

The copil is the highest body of the system. It meets monthly, lasts about 1h30, and brings together five to seven decision-makers: the sponsor, the project manager, two to four representatives of the business departments concerned, and a member of the executive committee on strategic projects. Its deliverable is a report of decisions made, enforceable, which commits the participants beyond the meeting.

Technical Committee (cotech): the operational expertise body

The cotech brings together technical experts who validate the proposed solutions before they are sent to the copil. It generally meets every two weeks, for a duration of about one hour. Its composition varies according to the project: for an information system redesign, there will be the IS architect, the security manager, the referent business expert and the project manager. The cotech does not decide alone — it prepares the decisions of the copil by shedding light on the technical arbitrations.

Project Committee (coproj): the day-to-day coordination body

The coproj is the operational body. It is held weekly, lasts 30 to 45 minutes, and brings together the client's project team and that of the service provider. This is where the tasks in progress are managed, the immediate blockages and the feedback that will feed the next cotech or copil. The coproj executes, the cotech advises, the copil decides.

Differential table of the three instances

The role of the project manager is not the same everywhere: he leads the coproj, contributes to the cotech as a coordinator, and reports to the copil without being the facilitator. On highly complex projects, the coordination of the copil is the responsibility of the sponsor or a dedicated PMO, never the project manager (who must be able to concentrate on operational management). The role of a copil facilitator can be based on the skills of a PMO, especially in mature organizations where project governance is formalized.

How to lead a steering committee?

The 4-phase method

Leading an effective copil consists of four phases:

1. The preparation phase, which starts five to seven days before the meeting, consists of building the agenda with the sponsor, gathering the appendices (progress report, budget dashboard, risk map) and distributing it to the participants 48 hours before the session.
2. The opening phase opens the meeting with five minutes: reminder of the objectives of the project, validation of the agenda, update on the actions of the previous copy.
3. The animation phase lasts about 1 hour and 15 minutes: each point of the OdJ is reviewed in the scheduled time, the moderator reframes when the debate drifts, solicits tacit opinions and acts on decisions as they go.
4. The closing phase takes ten minutes to recap the decisions made, formalize the next steps and set the date of the next copy.

A golden rule structures these four phases: no meeting without an agenda validated beforehand by the sponsor, and no meeting that exceeds 1h30. Beyond that, attention drops and decisions become blurred. The report must be sent within 24 hours so that the decisions made remain enforceable and that the project remains on track. Finally, the facilitator must know how to decide when consensus is delayed: collective disempowerment is the number one pitfall of a poorly animated copil.

Who to invite to a COPIL?

The composition of a copil depends on the structure of the company and the nature of the project. A copil generally brings together five to seven decision-makers: the project sponsor (who finances and arbitrates), the project manager (who reports without leading), two to four representatives of the impacted businesses (IT, finance, HR, client business depending on the project), and sometimes a member of the executive committee on strategic projects.

Beyond eight participants, the decision-making dynamic deteriorates: arbitrations tend towards soft consensus, and real divergences are no longer expressed.

COPIL meeting: how often should it be organised?

The frequency with which the steering committee is organised depends on the scope of the project.

In all cases, it must be regular, and each member present at each meeting in order to avoid imbalances of information.

Generally, steercos take place on a monthly basis and at important stages of the project:

• at the beginning of the project,
• at each key phase,
• exceptionally in case of difficulty.

How to prepare and structure a COPIL?

Don't neglect preparation

The planning phase is decisive for the progress of the steering committee. The time allotted, often limited to 1h30 or 2h, leaves little room for improvisation.

It is therefore essential to inform the participants in advance of the agenda and the objectives to be achieved so that everyone can prepare. The agenda should be anticipated and sent to the participants, ideally 48 hours before the meeting.

All annexes and documents that facilitate decision-making must be prepared: planning, report and activity report, minutes of previous committees, analyses.

Send invitations

Invitations should be sent at the beginning of the project for the coming months, so that participants can block slots in often overloaded agendas.

In invitations, clearly indicate the points to be addressed so that everyone understands the issues to be prepared.

Be predictable

Forget the element of surprise. All the information shared during the COPIL must have been discussed, or even validated with the project sponsor.

It is not a question of announcing news but of solving problems that are already known. The surprise effect generates live settling of scores; A well-prepared copil avoids it.

The steering committee is used to make decisions and obtain validations.

Be concise and effective

It is essential to respect the time allotted while discussing all the subjects to be covered.

To avoid overflows, provide a time master in charge of reminding the agenda in case of deviations.

Take care of the presentation

To facilitate the sharing and assimilation of the information communicated, prepare a careful support. Focus on synthetic and visual information, such as dashboards and graphs.

Send the report within 24 hours

The minutes of the steering committee must be sent within 24 hours of the meeting. It ensures that everyone has the same level of information and confirms the status of decisions made.

The report also serves as a basis for the preparation of the next steering committee.

To be relevant, it must be based on the notes taken during the steerco and include:

• the topics discussed,
• the subjects that could not be addressed,
• the decisions made,
• the actions required.

Four common mistakes to avoid

Four recurring pitfalls transform a decision-making body into a sterile review meeting.

Error 1 = Confusing copil and coproj

The most frequent mistake is to deal with in copil what is settled in coproj. A weekly schedule, a redistribution of tasks, a question of coordination between developers have nothing to do in a steering committee: they mobilize decision-makers on subjects that do not require strategic arbitration, and they stretch an already short body to the detriment of the real subjects.

The cost is not only operational, it is also political, because decision-makers stop responding to a copil from which they no longer expect anything structuring.

The weak signal can be read in the agenda: when more than a third of the items are related to team coordination, the meeting is no longer a copy. It is up to the facilitator to filter the points that fall under the COPIL and those that fall under the COPROJ: each COPIL point must ask for either a decision, or a budgetary arbitration, or represent a strategic direction. Everything else must be switched to coproj.

Mistake 2 = Seeking consensus at all costs

The primary role of a copil is not to produce unanimity but to act on a decision on the basis of the objectives of the project. The quest for consensus at all costs produces the opposite: decisions postponed from one committee to the next, dilution of responsibility, project that drifts while the discussion is turning.

This error is reflected in the minutes when the same items come back on the agenda for two or three successive meetings, without any decision being taken.

The practical rule: decide as soon as the debate goes in circles. For example, after fifteen minutes of debate, the sponsor decides, and the arbitration is recorded — even if it displeases some of the participants.

Mistake 3 = Keeping quiet about a risk for fear of conflict

This error is the most costly in the long run, and the most difficult to diagnose because it does not leave a trace in the report. The reasons are often the same: not daring to name a difficulty for fear of weakening the customer relationship, of being perceived as alarmist, or of putting an internal sponsor in difficulty.

Each time the risk is postponed to the next copil it weighs more and more heavily, until it materializes in a proven exceedance — even though it has been documented for a long time.

Error 4 = Postponing the sending of the report for more than 48 hours

Beyond 48 hours, the memory of decisions erodes, the commitments made in meetings fade away, and the copil loses its enforceability. A report sent five days after the meeting no longer serves as a reference: each participant has reconstructed his or her own version of what has been decided, and the arbitrations must be taken up in the next copil.

The discipline that changes everything: appoint a dedicated secretary who writes the CR during the copy. Ideally, this report should contain the on-the-spot validation of the decisions by the participants.

Example of a typical agenda over 1h30

A well-constructed agenda follows a logic of balanced distribution of time: one third devoted to advancement, one third to decisions to be taken, one third to anticipation. The following structure proposes a division into eight points over 1h30, which can be adapted to the reality of the project: short one-hour copil for cruising projects, long copil of two hours for structuring milestones.

This division respects the attentional rhythm of the participants: the most difficult points to address come before cognitive fatigue, and the trade-offs are made at a time when collective energy is still mobilized. For milestone projects (transition to production, critical acceptance), it may be relevant to extend the "strategic decisions" block to 20 minutes by compressing blocks 1 and 8.

How to articulate committees without meetingitis?

Project comitology refers to the articulated organisation of all the committees that steer a project. When the articulation is clear, the coproj (weekly, operational), the cotech (bi-monthly, expertise) and the copil (monthly, strategic) form a coherent cycle: the feedback from the coproj feeds the cotech, which prepares the decisions of the coproj, which sets the course for the next cycle. When it is not, committees multiply without logic, duplication sets in, responsibilities are diluted and participants become demobilized.

Typical sequence diagram

On a monthly cycle, the articulation follows a funnel logic:

• D-7 cotech (validation of technical solutions),
• D-2 preparation by the sponsor and the project manager (consolidation of the points to be arbitrated),
• D0 copil (decisions recorded),
• D+1 sending the report, then weekly cycle of coproj until the next cotech.

This rhythm ensures that each committee receives material prepared by the committee below, and that decisions go up from the operational to the strategic level without short-circuiting.

How many committees depending on the complexity of the project?

The structure of comitology must be adjusted to the complexity of the project, not the other way around. A simple project with a single team, a modest budget, and a short duration works great with a weekly coproj.

• A project of medium complexity, which involves two or three members of management and lasts from 3 to 6 months, justifies a coproj plus a monthly cotech.
• A cross-functional strategic project — an overhaul of the IS, a company merger, a multi-country launch — calls for the complete copil/cotech/coproj triad.
• Beyond that, some very complex projects (multi-year transformation program) add a program committee or a governance committee that oversees several copies.

Each addition of a committee must be justified by a mandate that is separate from the existing committees, otherwise it is a question of over-governance.

The COPIL is a project governance mechanism

The steering committee becomes essential from a certain threshold of project complexity: beyond that, its absence is paid for in budget drift and deadlines that far exceed the cost of 1h30 per month. But below this threshold, creating a copil is an over-governance that dilutes responsibilities more than it structures them. Project maturity is knowing when to implement it and when to do without it. For organizations that manage a portfolio of cross-functional projects (consulting firms, IT Services, transformation teams), the challenge is shifting: it is no longer a question of deciding whether the COPIL is useful, but of standardizing its preparation, animation and operation so that it systematically produces decisions rather than reports.