Home›Blog›Project controls and project management: two acts, not two jobs
FundamentalsBeginner
Published September 12, 2026 · By Vincent KENNEL
Project controls and project management: two acts, not two jobs
Project controls or project management: the phrase sets two things against each other that no referential puts on the same plane. What the standards separate is three acts, and which one is under way decides what a meeting is for.
In brief
No referential defines project controls as a term. The standards define three acts: controlling compares actual performance with planned performance, reporting provides the current status, the forecasts and the analysis, and directing decides on that basis and can stop the work. NF ISO 21502:2021 places the three at three levels of one chain.
On a large programme under contract, one monthly pack does two things at once. It informs a committee, and it settles something. Nothing in the document says which of the two acts is under way, and the English-speaking market states the problem in a shape of its own: project controls on one side, project management on the other, as though the question were which team owns what. The referentials do not sort them that way.
Three acts, not two job families
None of the referentials quoted in this article defines project controls as a term. What they define is acts, and there are three of them.
Controlling is a comparison. ISO 21506:2024, the vocabulary standard, defines control at 3.13 as the "comparison of actual performance with planned performance, analysing variances, and taking appropriate corrective action and preventive action as needed". Nothing in that sentence decides anything. It measures, it explains the gap, it proposes the correction.
Reporting is a transmission. NF ISO 21502:2021 gives the purpose of project reporting at 7.15.1: to provide the current status, the forecasts and the analysis of the project. The same clause carries a note that is worth keeping, because it is the one most articles on the subject skip: reports are distinct from communications. A report is not a conversation about the project, it is a delivered state of it. ISO 21506:2024 names the object at 3.60, progress report, "report of current status and work accomplished during a specified time period".
Directing is a commitment. NF ISO 21502:2021 at 6.4 makes its object the continued justification of the project, up to and including the work being stopped when the justification for the organisation is no longer supported. That is not an assessment. It is a decision with consequences for money, for people and for contracts.
Three acts, and what separates them is what each one produces: a corrected measurement, an informed recipient, a commitment. Defining them by their product rather than by their name matters more than it looks, and the reason appears further down. The names themselves are not stable.
The French normative pair cuts the same territory in two functions instead of three acts, and lands on the same frontier. NF X50-115:2017 at 5.3.3 holds that project management covers two distinct and complementary functions. Direction de projet is the decision function for all the operational aspects of the project, and it reports to project governance. Gestion de projet is the aid-to-decision function, and it reports to the direction de projet. Its stated mission is to bring the decision function a set of analysed information, so that its decisions are relevant and timely.
Where the line runs: three levels, two directions of travel
NF ISO 21502:2021 does not set the three acts side by side. It sets them at three levels, in three separate clauses, each with its own carrier. Clause 6.3, overseeing, belongs to the sponsoring organisation. Clause 6.4, directing, belongs to the project sponsor, supported by the project board. Clause 6.6, controlling, belongs to the project manager, whose stated objective is to monitor and measure performance against an agreed plan.
The bottom of that structure is where the information is manufactured. Clause 6.6.3 asks the project manager to collect and analyse progress and performance data. NF X50-115:2017 says the same on the French side and goes one step further at 5.5.3: gestion de projet supplies the information that feeds the project's periodic and specific progress reports.
What travels upward is not the raw data. NF X50-115:2017 at 5.3.3 speaks of analysed information, and at 5.5.3 assigns the levels of synthesis matching the needs of the different stakeholders. The distinction is not cosmetic. A sponsor who receives raw progress data has been sent the wrong object.
The route is normed as well. NF ISO 21502:2021 at 7.15.3 describes a cascade in three steps: work package leaders report to the project manager, the project manager reports to the sponsor and the project board, the sponsor reports to the other stakeholders. Set that against the three levels above and the picture closes. Information travels up, decisions travel down. Two flows in one chain, and confusing them amounts to believing that an upward arrow makes a project advance.
Reports travel up, decisions travel down.
One institution has drawn that line inside its own organisation, and it is the institution whose function carries the disputed word. NASA/SP-2016-3424 defines project planning and control at 2.1 as "a set of inter-related functions that supports developing the plans for executing a project and subsequently assesses and evaluates progress against the plan", and it lists seven of them: PP&C integration, cost estimation and cost assessment, resource management, scheduling, acquisition and contract management, risk management, and configuration and data management. The scope is wide. The stopping point is explicit. The fundamental focus of the integration activity is "to gather, analyze, and assess project information to enable effective decision making in support of project success", and "the culmination of PP&C is the integrative activities and subsequent assessment and recommendations". Assessment and recommendations, not decisions.
There is one point on which the referentials disagree, and it deserves to be named rather than smoothed over. NF ISO 21502:2021 at 6.4 and the AFITEP Dictionnaire de management de projet, 3rd edition (1996) place directing at the level of the sponsor and the board, AFITEP describing it as indirect and discontinuous decision-making activity. NF X50-115:2017 at 5.3.2 places it lower, calling le management du projet the operational body that conducts the project, and FD X50-105:1991 already spoke at 4.2 of the decision level assumed by the project manager. The mechanism that reconciles the two is named by the standard itself: NF X50-115:2017 at 5.5.2 founds the project manager's authority on an explicit mandate validated by the empowered bodies, a delegation of authority to take decisions and make trade-offs within the field that delegation specifies, and it reserves to the governance or portfolio level alone the power to confirm or overturn the orientations that follow. PRINCE2 7 carries the same mechanism in English, through tolerance: an exception is a forecast deviation beyond the tolerance levels agreed between the project manager and the project board, and the exception report exists to "seek direction from the project board". Two readings, two heights on one ladder of delegation. Who directs is answered by reading the mandate, not by choosing a referential.
One last observation on the vocabulary, and it explains the method used here. NF X50-115:2017 employs the word pilotage at two levels: at 5.3.2 for the body that conducts the project, and at 5.3.4 for the loop that measures progress and variances and defines corrective measures, which is what ISO calls controlling. The word is not a stable label, in usage or in the standards. Defining by the act rather than by the word is not a stylistic preference. It is the only thing that holds.
What each one produces, how often, and for whom
Reporting produces named reports. The AFITEP Dictionnaire de management de projet, 3rd edition (1996) lists three of them, the progress report, the financial report and the project report, and observes that French has no single word for the activity of preparing and presenting them. PRINCE2 7 sorts them by trigger in table 11.2: checkpoint and highlight reports are time-driven, exception and issue reports are event-driven. One of the four settles the question on its own. The exception report exists to "seek direction from the project board", and a report whose stated purpose is to obtain a decision marks precisely where reporting stops.
Directing produces a decision that commits. NF ISO 21502:2021 at 6.4 puts continuation and termination in that category. NF X50-115:2017 at 5.5.2 adds the trade-offs made within the delegation, the allocation of resources, the clarification of objectives and the choice of the solutions retained. The report is defined by that same finality seen from the other end: in the PMBOK Guide, 6th Edition (2017), a work performance report is "intended to generate decisions or raise issues, actions, or awareness".
The cadence is derived, not customary. PRINCE2 7 at 11.2.4 holds that the frequency of reporting should reflect the level of control required, and that it is likely to vary during the project, the example given being an experienced team that justifies less frequent reporting. The consequence is uncomfortable and easy to check: a cadence that has not moved since the kick-off was not derived from a need.
The recipient is a governance decision, not a habit either. NF ISO 21502:2021 at 7.15.2 plans reporting within the governance of the project, and what gets planned is the content, the author, the recipients, the frequency, the confidentiality and the format. A distribution list that grew by forwarding is not a plan.
Under contract, the same logic is written into the agreement. NF X50-115:2017 at 5.5.2 has the direction de projet answer the requests for information formulated by the client and by the organisation's governance, towards which it performs reporting activities. On the client side, the DoDI 7000.10, in its edition of 3 December 1979, bounds contractual reporting to what management control actually requires, and accepts that the contractual reports derive from the contractor's own internal reports. A contractual report is a deliverable with a purpose, and the purpose is set by the party that asks for it.
One point runs against intuition and is worth holding on to. NF X50-115:2017 at 5.5.3 makes gestion de projet the party that anticipates possible drifts, that alerts and proposes, and that is also the guarantor of the traceability of information and of decisions, in particular the exchanges between the contracting parties. The decision is taken at the top and traced at the bottom. Any formula of the kind "directing produces a traced decision" has to say who does the tracing, or it contradicts the standard it leans on.
Where the reporting function came from
The project report was born already split, and the date can be given to the month. Supplement No. 1 to the DoD and NASA Guide, PERT COST Output Reports, of March 1963, normalises eleven output reports. Two sentences carry the whole point. On the Management Summary Report: "The report is prepared at several levels of the work breakdown structure [...] depending upon the needs of management", then "the report is usually divided for distribution to appropriate government and contractor managers". On the Program/Project Status Report: "whereas the Management Summary Report highlights information for a manager, this report retains detail for an analyst".
From 1963, two reports drawn from the same data are separated by their recipient, and the report's structure follows the work breakdown structure. The question "for whom" is not a late refinement of the discipline. It is in the first specification.
The separation was then written into two distinct instructions. DoDI 7000.2, in its edition of 10 June 1977, states the criteria a contractor's management control system has to satisfy. DoDI 7000.10, in its edition of 3 December 1979, states the reports to be delivered. One instruction for the system that measures, another for the reports it feeds.
The warning against confusing the two acts is older than either. Fayol, in Administration industrielle et générale (1917), chapter 5, defines control at page 153 as verifying that everything happens in conformity with the adopted programme, the orders given and the accepted principles, its purpose being to signal faults and errors so that they can be repaired and prevented from recurring. At page 155 he names the danger: the interference of control in the direction and the execution of services, an encroachment he calls a duality of direction in its most formidable form. At page 156 he closes on the balance, holding that control, done well, is a precious auxiliary of direction.
A little over a century later the instruction has not changed. Verifying and deciding are two acts, and keeping them apart is what makes the first useful to the second.
Asked in the usual way, the question opposes a part to its whole. ISO 21506:2024 defines project management at 3.65 as "coordinated activities to direct and control the accomplishment of agreed objectives", and pairs the same two verbs again at 3.57 and 3.48. Controlling is one of the acts that project management coordinates, not a discipline standing beside it. What can legitimately be told apart is directing on one side, controlling and reporting on the other, which is the separation the referentials actually make.
In short
The test is not the job title on the invitation, it is what leaves the room. Information transmitted to someone is a report, whatever it is called and however senior its audience. There is direction only where a decision has been taken inside the field of a delegation, and traced.
The test applies to an object as readily as to a meeting. A monthly pack that changes nothing but the shared level of awareness is a report, and a good one may be exactly what the project needs. A pack that carries a trade-off made within a mandate is the trace of a decision, and it belongs to the other act.
The criterion stops there, deliberately. It says which of the two acts is under way. It does not say what to keep, what to shorten or what to abandon, and the referentials give no ground for that judgement. Before the next pack goes out, the question worth asking is the smaller one: at the end of it, what leaves the room, information or a decision, and if a decision, under whose delegation.
Stop guessing. See the real impact.
Frequently asked questions
Q.Is a dashboard project controls or project management?
NF X50-115:2017 files progress reports, dashboards and indicators under a reporting heading in its annex. The name comes from steering, the function is restitution.
Q.Does a small project need a separate person for each of the two functions?
No. NF X50-115:2017 at 5.3.3 states that, depending on the complexity and scale of the project, these functions may be carried by one or several persons, and FD X50-105:1991 at 4.2 said the same for small projects. Two functions, not necessarily two people, never a single act.
Q.Is monitoring the same as controlling?
Not in the PMBOK Guide, 6th Edition (2017), which separates them. Monitoring collects performance data, produces performance measures and reports and disseminates the information. Controlling compares actual with planned performance, analyses variances and recommends corrective action.
References
AFNOR - NF X50-115 - Management de projet et de programme, présentation générale - Décembre 2017
AFNOR - FD X50-105 - Le management de projet, concepts - Fascicule de documentation, août 1991
AFNOR - NF ISO 21502:2021 - Recommandations sur le management de projet - Juin 2021
AFNOR, AFITEP - Dictionnaire de management de projet français-anglais-espagnol - 3e édition, 1996
