Bodies Project committee (COPROJ)
The project committee, or COPROJ, is the operational body of a project: weekly or every two weeks, short, focused on what is blocked. The web very often confuses it with the steering committee, and this confusion damages both bodies at once. Here is what sets them apart, and why the distinction is not a quarrel over vocabulary.
Project committee, n.
That last sentence is the whole definition. A project committee that starts accepting scope changes, moving milestones or granting delays is no longer a project committee: it is a steering committee that does not know it, without the people who should have been there to decide.
Names vary from one organization to another: follow-up committee, project check-in, operational committee, weekly review. The name matters little; what matters is the scope of decision.
Steering committee and project committee, point by point.
Four criteria are enough to tell which of the two bodies you are in.
| Criterion | Steering committee | Project committee |
|---|---|---|
| Frequency | Monthly, sometimes quarterly on long projects. | Weekly or every two weeks. |
| Participants | Sponsors and decision makers on both sides, project management. | Project managers, business leads, sometimes the team. |
| Decisions | Scope, deadline, budget, acceptance of major risks. | None that commits the contract. Prioritization, unblocking, alerts. |
| Deliverable | Minutes submitted for approval, and a frozen status of the project. | An action log, updated continuously. |
The steering committee is covered in detail on its own page, and its main artifact on steering committee minutes.
The internal project review, always forgotten.
There is a third body, and it is rarely named: the internal project review, on the supplier side, without the client. It looks at what the other two do not look at, because it is not shown to the client: the real margin, the team's workload, human tensions, the staffing of the coming weeks.
Its absence produces a recognizable symptom. A project can be green at the steering committee, smooth at the project committee, and heavily deteriorating from the point of view of profitability or of the team. Nobody lies: simply, neither of the two visible bodies is meant to see it.
The three are therefore told apart by what they look at: the steering committee looks at the commitment, the project committee looks at execution, the internal review looks at cost and teams.
The latter is also the easiest to sacrifice when the schedule tightens, precisely because no client asks for it. Yet it is the only one of the three where you can say that a consultant is disengaging, that a workload is becoming untenable or that a margin is eroding, before these three facts become visible from the outside in the form of a delay.
Why the three get confused in mid-sized organizations.
It is neither laziness nor ignorance. It is a mechanical consequence of the number of people available.
The same people everywhere
When the project manager is also the project director and sometimes the salesperson, holding three distinct bodies amounts to meeting with yourself.
The single meeting that absorbs everything
You merge, and the monthly session deals with today's blocker before the scope decision. The urgent topic chases out the important one.
The client always present
Without an internal review, everything is said in front of the client. What should be said there, margin and workload included, is then said nowhere.
The way out is not to add meetings. It is to separate the agendas even when the people overlap, and to make the project status available continuously, so that each session starts from the data rather than reconstructing it.
What each body holds, rather than what it is.
Project governance describes the bodies: who decides, at what pace, on what agenda. Operational commitment management describes what these bodies hold: what was promised, by whom, by what date, and on what dated proof. One is the frame. The other is the substance.
Seen this way, the question "should the COPROJ be weekly or every two weeks?" becomes secondary. What decides the usefulness of a session is that it opens on an up-to-date status that everyone could read beforehand, and that it leaves behind actions whose owner will be known, the next time. This is what we call operational commitment management.
In pylotik.
The project committee with the client is held on the tracking screen. Nothing has to be re-entered afterwards.
The session starts from the real status
Progress, milestones, risks and open actions are already there. There is no deck to produce for a weekly meeting.
Actions are logged on the spot
Each with an owner, a due date and a requester. The list lives between two sessions instead of being born again at each one.
What goes up to the steering committee is flagged
A point that goes beyond the scope of the project committee is identified as such, and ends up on the agenda of the body that can decide it.
The internal review stays internal
Margin, workload and team signals are visible only to the supplier. The client never sees them, whichever body is meeting.
The overall frame is described on project governance. The complete tour is on the product page, and the contractual modes on the commitment levels.
What we are asked about the COPROJ.
What is the difference between COPIL and COPROJ?
The steering committee decides what commits: scope, deadline, budget, major risks. The project committee follows execution, clears blockers and prepares what the steering committee will have to decide. The first is monthly and decision-making, the second weekly and operational.
How often should a project committee be held?
Weekly when the project is dense or the team distributed, every two weeks otherwise. Beyond two weeks, blockers pile up and the session becomes an inventory. Within a week, it replaces the team's normal communication.
Who takes part in the project committee?
The project managers on both sides, the business leads concerned, and depending on the topics part of the team. Sponsors are not there: their presence turns the session into a decision body.
What goes on the agenda of a follow-up committee?
Ongoing actions and their status, progress since the last session, blockers, new risks, and what must go up to the steering committee. Nothing that calls for a scope decision.
Do you need minutes for a project committee?
An action log is enough, kept up to date rather than written up. Formal minutes, submitted for approval, belong to the steering committee: it is the one that produces decisions to rely on.
Can the two bodies be merged on a small project?
It is often done, and it can hold if the agenda stays split into two distinct parts: first the operational, then the decisions, with the right people present for the second part. What does not hold is mixing the two in the same discussion.
Going further.
- Project governance: bodies, roles, artifacts, and what they hold.
- The steering committee: the body that decides.
- Committee minutes: the structure that holds, and who approves it.
- Operational commitment management: the definition of the category.