What does a project manager do? Roles and responsibilities

A project manager is the person accountable for delivering a project. They agree what it will produce, plan the work, lead the team, keep stakeholders aligned and deal with the risks and changes that come up along the way. They rarely do the hands-on work themselves. Their job is to make sure it gets done, on time, within budget and to the standard agreed.

This guide lists those responsibilities in full, using the job study PMI runs to build the PMP exam, then shows what they look like in a real week and in a worked example.

Where this list of responsibilities comes from

PMI runs a job task analysis: a study of what practising project managers actually do and which tasks matter most. The result is the PMP Examination Content Outline, the document every PMP exam is built from. The current version, revised in August 2026, describes its tasks as "the underlying responsibilities of the project manager".

It lists 26 tasks in three groups, which PMI calls domains: People (8 tasks), Process (10) and Business Environment (8). That is the closest thing there is to an official job description for a project manager, so we use it here and put each task into plain English.

The same study found that today's project managers work across predictive, agile and hybrid approaches, and PMI fed newer trends such as AI and sustainability into it. It also reflects a wider view of success: a project succeeds when it delivers value worth the effort and expense, not only when it hits its schedule, budget and scope.

People: leading the team and the stakeholders

PMI's eight People tasks are about leadership. In plain English, a project manager:

• Builds a shared vision of what the project is for, with the key stakeholders, and keeps it current.

• Manages conflict, starting from its source, and sets ground rules the team agrees to keep.

• Leads the team: sets expectations, gives people room to decide, solves problems and agrees clear roles.

• Identifies the stakeholders, analyses them and tailors communication to each group.

• Aligns stakeholders' expectations with each other and with the project's objectives.

• Manages what internal and external customers expect, and responds when satisfaction slips.

• Makes sure the knowledge the project depends on is captured and shared.

• Plans and manages communication, including the reports that sponsors and governance boards need.

People questions make up 33% of the PMP exam. In our experience, this is the part of the job new project managers most often underestimate: the plan rarely fails on its own, and the conversations around it usually decide the outcome.

Process: planning and delivering the work

The ten Process tasks are the technical core of the role. A project manager:

• Builds the integrated project plan, recommends the approach (predictive, agile or hybrid) and keeps the plan current.

• Defines the scope, gets stakeholders to agree to it and breaks it down into manageable work.

• Delivers value: prioritises work by the value it brings and checks there is a way to measure the benefits.

• Plans and manages resources, meaning the people, equipment and materials the work needs.

• Plans and manages procurement: contracts, vendors and negotiations.

• Plans and manages the money: the budget, contingency reserves and spend tracking.

• Plans quality, runs quality reviews and drives continuous improvement on the deliverables.

• Builds the schedule, baselines it and manages variation against it.

• Tracks status with metrics and reports progress.

• Closes the project or phase: formal approval, handover to operations and lessons learned.

Process questions are 41% of the exam, the largest share. Our guide to project deliverables shows how the output of all this work is defined and signed off.

Business environment: governance, risk and change

The eight Business Environment tasks connect the project to the organisation around it. A project manager:

• Sets up governance: decision rules, reporting, success metrics and escalation paths.

• Plans and manages compliance, such as security, health and safety, and regulatory requirements.

• Runs change control: assessing proposed changes, getting them approved and updating the documents.

• Removes obstacles and manages issues, including risks that have turned into issues.

• Plans and manages risk: identifying and analysing risks, keeping a risk register and acting on it.

• Feeds lessons learned into continuous improvement.

• Supports organisational change, reading the culture the project's result will land in.

• Watches the outside world, such as regulation, technology and the market, for changes that affect the scope.

These make up 26% of the exam. Our guide to project risk management goes deeper on the risk task.

What does a project manager's week look like?

The 26 tasks do not arrive in order. A typical week on a mid-sized project mixes all three groups. This is an illustrative week, not a PMI schedule:

1. Monday: a planning session with the team to agree the next two weeks of work and who owns each piece.

2. Tuesday: a call with a supplier about a late delivery, then updates to the schedule and the risk register.

3. Wednesday: a conversation with two team members who disagree about a design, and an agreed way to settle it.

4. Thursday: a status report for the sponsor, with the budget position, the top risks and one decision needed.

5. Friday: a change request reviewed at the change board, then a short retrospective with the team.

Most of that week is conversation, decisions and follow-up rather than hands-on work.

A worked example: one late supplier

Say you are managing the rollout of a new booking system for a chain of 12 clinics, due to go live on 1 June. In April, the hardware supplier says the front-desk tablets will arrive three weeks late, and the clinics cannot train their staff without them. One problem touches all three groups of responsibility:

1. Process: you check the schedule and confirm the go-live date is now at risk. You price two options: rent tablets for three weeks, or train staff on desktop computers first and move them across later.

2. Business environment: the late delivery was on your risk register as a risk, and now it is an issue. You raise a change request with both options, their cost and their effect on the date, and take it to the project board.

3. People: before the board meets, you brief the sponsor so there are no surprises. Afterwards, you tell the clinic managers what is changing and why, in terms of their front desks rather than your project plan.

The board chooses the rental. It is paid from the contingency reserve and protects the date. None of that needed technical expertise. It needed someone who knew the schedule, the budget, the change process and the people, and that is the project manager's job.

What a project manager is not

Three roles often get confused with the project manager's:

• The sponsor. The sponsor owns the business case and funds the project. The project manager is accountable for delivering it.

• The technical lead. A project manager on a software project does not need to be the best developer. They need to understand the work well enough to plan it and spot the risks.

• The line manager. Many project managers lead people who report to someone else, which is why influence matters as much as authority.

For how project managers work alongside a project management office, see our guide to what a PMO does.

Project manager roles at different levels

Titles vary by employer, but the usual path looks like this:

• Project coordinator: supports a project manager with schedules, meetings and documents. A common first role.

• Project manager: accountable for one project, or for several smaller ones.

• Senior project manager: larger, riskier or more visible projects, often mentoring other project managers.

• Program manager: a group of related projects managed together for benefits none of them would deliver alone. PMI's credential for this level is the PgMP.

• Portfolio manager: decides which projects and programs the organisation funds, and in what order. PMI's credential for this level is the PfMP.

Our guide to whether the PgMP is worth it covers the step from project to program.

How do you become a project manager?

Most project managers did not start with the title. They led projects inside another job, in engineering, IT, operations or finance, and moved into the role once they could show the results. Two PMI credentials mark the usual path:

• The CAPM needs no work experience, so it suits people starting out or moving in from another field.

• The PMP is for people who already lead projects. With a bachelor's degree, PMI asks for 36 months of experience leading projects and 35 hours of project management education. Our guide to PMP eligibility covers the other routes.

Because the PMP exam is built from the same 26 tasks listed above, preparing for it is also a structured way to learn the whole job. Our PMP course is live weekend training over 7 Saturdays, in person in Mississauga or online, from a PMI Authorized Training Partner (ATP #4456).