Project Manager Roles and Responsibilities: Who Owns What

At 8:40 a project manager opens three things before email: the risk log, yesterday's status notes and the calendar for the sponsor check-in. None of that is writing code or laying bricks. A project manager owns the plan, the schedule, the budget, the risks and the communication that keep a team pointed at one agreed result. The sponsor owns the reason and the money, and the team owns the craft.

That split sounds tidy and rarely is, which is why "what are a project manager's roles and responsibilities?" keeps being asked in every office that runs projects. This guide answers it in four cuts: a single working morning, the five phases of a project, the line between the manager, the sponsor and the team, and the way the job grows from junior to senior. The IAPM Certified Project Manager (CPM) appears near the end, because that exam tests exactly this division of duties.

What does a project manager actually do on an ordinary morning?

Picture a Tuesday in the middle of a project, with no crisis scheduled. The manager's first half hour is reading, not meeting. The risk log shows one item that has moved from "possible" to "likely": a supplier has hinted that a delivery may slip by a week. Yesterday's notes show that one of the testers is blocked by a missing access request. The calendar shows a sponsor check-in at 11:00 and a change request waiting for a decision.

By 9:00 the manager has done the part of the job that nobody sees. The access request is chased and given a name and a date. The supplier call is booked for before lunch. The slip is written into the schedule as a scenario, not yet as a fact, so the sponsor will hear about it from the manager rather than from a late delivery. Then comes the stand-up with the team, ten minutes in which the manager mostly listens and asks one question per person: what is in your way?

The rest of the day follows the same pattern. Between 9:30 and 11:00 the manager reworks the forecast: how far has the work really got, as opposed to how far people say it has, and what does that mean for the end date and the budget? At 11:00 the sponsor hears the honest version, including the supplier risk, and decides whether to spend money to protect the date. After lunch the manager writes the change request up so the people who will approve it can see the effect on cost, time and scope. The late afternoon belongs to people: a one-to-one with a team member who is overloaded, and a short note to stakeholders who are not in the room but depend on the outcome.

Read the morning again and you can pull out the working verbs of the role: plan, forecast, chase, decide what to escalate, negotiate, report and protect the team's time. None of them is a technical task. A project manager does not need to be the best engineer, designer or analyst in the room. The job is to make sure the best people can work and that the right decisions are taken by the right person at the right time.

How much of the day is management and how much is coordination?

Many job descriptions call the manager in the execution phase "more of a project coordinator". That is a fair description of the dullest part of the job and a misleading one of the whole. Coordination is passing information between people. Management adds the authority to commit the team, the duty to answer for the result and the judgement to say no. A coordinator can tell you that a task is late. A manager has already worked out what to do about it and who needs to agree.

Which responsibilities does the project manager own in each phase?

Most project frameworks, including the PMBOK Guide's process groups, divide the life of a project into five stages: initiating, planning, executing, monitoring and controlling, and closing. Real projects loop and overlap, so treat them as a map rather than a timetable. The manager's duties shift with each stage, and so does the amount of time spent on each.

Phase	What the project manager owns	What it produces
Initiating	Confirming that the work is a real project, understanding the business reason, identifying who is affected, getting authority in writing	A project charter, a stakeholder list, a named sponsor
Planning	Turning the goal into scope, a breakdown of work, a schedule, a budget, a risk plan and a communication plan	An approved plan and a baseline to measure against
Executing	Assembling and leading the team, running meetings, managing suppliers, keeping the work to the plan	Deliverables, status reports, a team that knows its priorities
Monitoring and controlling	Comparing progress with the baseline, handling change requests, managing risk and quality, forecasting	Variance reports, decisions on changes, updated forecasts
Closing	Getting acceptance, handing over, settling contracts, recording lessons, releasing people	An accepted result, a closure report, a lessons record

Initiating: earn the right to start

The first responsibility is a negative one: do not start until it is clear what you are starting. A manager who inherits a vague request such as "sort out the onboarding mess" has to turn it into a statement the sponsor will sign. That means a goal, a boundary, an owner and a rough sense of cost. The charter is the document that gives the manager authority to spend and to direct people, so a project that begins without one asks the manager to be accountable without being empowered.

Planning: where most of the responsibilities sit

Planning carries the heaviest load of duties and the least glamour. The manager breaks the work into pieces small enough to estimate, sequences them, estimates effort and cost with the people who will do the work, lists what could go wrong and decides what to do about it, and agrees how information will flow. A good plan is not a guess dressed up as certainty. It is a record of assumptions that can be tested, which is why the manager reads it again every time reality disagrees.

Executing and controlling: two jobs at the same time

Executing is about people; controlling is about numbers. A manager who only does the first drifts into friendly chaos, and one who only does the second becomes a spreadsheet that nobody wants to talk to. The two run side by side: the stand-up and the one-to-one on one hand, the variance report and the change log on the other. When work goes wrong, it usually does so in the gap between them, for instance when a team is cheerful and a forecast is quietly red.

Closing: the phase that gets skipped

Closing is the first responsibility to be dropped when the deadline passes, because the team is already wanted elsewhere. It should not be, for three reasons. Acceptance in writing ends the manager's accountability. Contracts left open produce invoices months later. And a lessons record is the only way the next project starts smarter than this one did.

Where does the project manager's job end and the sponsor's or the team's begin?

Most arguments about project roles are arguments about boundaries. A manager who is blamed for a missed benefit that was never in their hands, or a sponsor who assumes the manager will find the budget, is describing a boundary nobody drew. The table below draws one. It is a working default, not a law: your organisation may move a line, but every line should sit somewhere on purpose.

Question that comes up	Who normally answers	Why
Why are we doing this at all?	Sponsor	The business case belongs to whoever benefits from it and pays for it
How much money and time is available?	Sponsor sets the limit; manager plans inside it	The manager can say what the goal costs, not decide what it is worth
Which tasks come first, and who does them?	Project manager, with the team	Sequencing and assignment are planning duties
How long will a technical task take?	The person doing it	Estimates imposed from above are a common source of slipped dates
Should we accept a change that adds cost?	Steering group or sponsor, on the manager's analysis	The manager shows the effect; someone with budget authority decides
Is this deliverable good enough?	Team for quality in the work, stakeholders for acceptance	The manager sets the criteria and checks the process
Who talks to the people affected?	Project manager as the main voice, sponsor for the difficult conversations	One voice avoids mixed messages; senior weight is sometimes needed

Roles that sit between the manager and the team

Larger projects add layers, and IAPM's syllabus names them precisely. A steering committee holds the decisions that are too big for the manager and too operational for the sponsor. A core team works on the project most of the time, not in passing. A sub-project manager runs a defined part of a large project, and a work package owner answers for one slice of the scope. The manager does not do these jobs. The manager sets them up, makes sure each person knows what they own, and checks that information flows up and down.

What goes wrong when a boundary is blurred

• The absent sponsor. The manager is left to settle questions of value and priority, which they have no standing to decide, and every disagreement escalates to a meeting that nobody has time for.
• The overruling sponsor. Dates and scope are changed in a corridor conversation, the plan is never updated, and the manager is held to figures they did not agree to.
• The manager who does the work. A promoted specialist keeps coding, writing or designing because it is comfortable, and the planning, forecasting and stakeholder work quietly stops.

How do a project manager's responsibilities change from junior to senior?

The title "project manager" covers jobs of very different scale. What changes with seniority is less the list of activities than the size of what the person answers for and how far ahead they have to see.

Level	Typical scope	Main responsibility	What gets harder
Junior or assistant	Tasks inside someone else's project	Keeping the schedule, minutes, action lists and status data accurate	Learning to flag a problem early instead of fixing it quietly
Project manager	One project with a team and a budget	Delivering the agreed scope on time and on budget, and reporting honestly	Leading people who do not report to you
Senior project manager	Large, risky or cross-border projects with several teams	Managing sub-project managers, suppliers and executive expectations	Making decisions with incomplete information
Programme or portfolio lead	A group of related projects	Choosing which work to fund, stop or merge, and tracking the benefits	Letting go of detail and trusting others to run it

What a junior should not be expected to own

A junior takes on pieces of the manager's responsibilities, not all of them, and the line matters for both sides. They can maintain the schedule, but the commitment it represents belongs to the manager. They can draft a status report, but not decide what is escalated. Treating a junior as an accountable manager is a common way to burn out a promising person; treating a competent one as a note-taker for years is a common way to lose them.

What the move to senior really asks for

Seniority is mostly about uncertainty and influence. A senior manager is expected to see a risk two phases ahead, to negotiate with suppliers and executives who outrank them, and to coach the people running the pieces. Technical depth matters less at each step up, while judgement, credibility and the ability to give a clear answer to a vague question matter more.

Which skills decide whether a project manager is effective?

Lists of skills are cheap, so it helps to tie each skill to a responsibility it actually serves. These are the ones that separate people who deliver from people who only look busy.

• Estimating with other people. It serves planning. The manager gathers numbers from the team, challenges them gently and records the assumptions behind them.
• Telling the truth early. It serves controlling. A forecast that turns red in week three costs a conversation; the same forecast revealed in week twelve costs the project.
• Negotiating scope. It serves the sponsor relationship. Saying "yes, if we drop that" protects the team while keeping the sponsor's trust.
• Running a meeting that ends with owners and dates. It serves execution. A meeting with no named action is entertainment.
• Handling conflict without taking sides. It serves the team. The manager's job is to get the disagreement into the open and resolve it on the work.
• Enough technical and business knowledge to follow the discussion. The manager need not be an expert, but must know when an answer sounds wrong.

Credible sources agree that the role is a mix of the technical, the interpersonal and the commercial. PMI describes a "talent triangle" of technical project management, leadership, and strategic and business management skills, and the Wikipedia entry on the project manager lists the same spread. The practical lesson is that a manager who is strong in only one corner will eventually meet a project that needs the other two.

Where does the role break down in practice?

The textbook description of the job is clear. The practice is messier, and most trouble can be traced to a small number of patterns that are worth recognising early.

Accountability without authority

Many managers answer for results from people who report to someone else. The remedy is not a better title but a clearer charter: what the manager may spend, who may be asked to work on the project and how conflicts over priority are settled. If those three points are vague on day one, expect to renegotiate them in the middle of a crisis.

Status reports that describe activity, not progress

"Testing is 80% complete" tells the sponsor very little if nobody knows what is left in the last 20%. Better reporting names what has been finished and accepted, what is at risk and what decision is needed. A report with a request in it gets read; one without gets filed.

Scope that grows a little at a time

Few projects fail through one large change; most are worn down by dozens of small agreeable requests. The manager's defence is a change process light enough that people use it and firm enough that nothing enters the plan without its cost being visible.

A plan nobody revisits

A baseline is a reference point, not a promise carved in stone. The manager who re-plans openly when facts change protects credibility; the one who defends an outdated plan to the end loses it.

How does the IAPM Certified Project Manager test this division of duties?

If you want a recognised way to show that you know the role as it is taught, the IAPM Certified Project Manager (CPM) is built around the same material: the charter, the stakeholders, the steering committee and core team, work packages, the budget, risk, review and close-out, plus soft skills. The facts below come from the exam record; IAPM's own page for the certificate gives the registration details.

Item	IAPM CPM
Exam code	CPM
Full name	IAPM Certified Project Manager
Questions	120
Duration	80 minutes
Passing score	65%
Price	USD 599

Because the exam draws on the way IAPM defines each role, a candidate who has run projects informally is often surprised by how much of the question set is about who is responsible for what. The twenty areas are listed on the CPM syllabus page; only the role-related ones are mentioned here.

What the credential does and does not show an employer

The certificate cannot show that you have led a team through a difficult month; only a record of delivered projects can. What it does show is that you can use the vocabulary of the role correctly and answer questions on the sponsor, steering committee and work package owner the way an international body defines them. For a career changer or a team member stepping into a first project, that is a modest but real signal. Anyone preparing can rehearse the 80-minute format with a CPM practice exam before booking the sitting.

Other credentials cover other ground

IAPM runs a ladder of project management certificates, and its overview of certification levels shows where the CPM sits. PMI and other bodies offer their own credentials with their own fees and rules; check each vendor's page for current figures before comparing. The right choice depends on which framework your employer uses, not on which name is more familiar. Fees and registration for this one are on IAPM's CPM page.

How can you check that you are doing the project manager's job and not someone else's?

A short self-audit works better than a longer job description. Answer these five questions about your current project in plain words, and write the answers down.

1. Who is the sponsor, and when did they last make a decision on this project? If you cannot name them or the date, the sponsor's role is vacant.
2. What am I allowed to spend, and who can I ask to work on this? If either answer is "I am not sure", the charter is missing something.
3. Which three risks would hurt most, and who owns each? A risk without an owner is a worry, not a plan.
4. What did I decide this week that no one else should have decided for me? If nothing, you may be coordinating, not managing.
5. What did I do this week that a team member should have done? If a lot, planning and forecasting are probably slipping.

Running through those questions once a month takes ten minutes and will surface most role problems well before they show up in the schedule. If the answers keep pointing at a missing piece of authority, treat it as a project risk and take it to the sponsor, not as a personal failing.

Frequently Asked Questions

What are the main roles and responsibilities of a project manager?

A project manager owns the plan, schedule, budget, risk management and communication for one project. They lead the team, track progress against the baseline, handle change requests, report honestly to the sponsor and close the project with acceptance and lessons recorded. They do not set business value or do the specialist work.

What does a project management professional do day to day?

A typical day mixes reading the risk log and status notes, unblocking team members, updating the forecast, briefing the sponsor and deciding what to escalate. Most of the time goes on communication and planning rather than technical tasks. The aim is to keep the team productive and decisions timely.

What is the difference between a project manager and a project sponsor?

The sponsor owns the business case, funds the project and has the final say on value and major changes. The project manager owns delivery inside the limits the sponsor sets: planning, scheduling, managing risk and reporting. The sponsor decides why and how much; the manager decides how the work is run.

How do project manager responsibilities differ at junior and senior level?

Juniors support a project by keeping schedules, minutes and status data accurate. A project manager answers for one project's scope, time and budget. Senior managers run large or cross-border projects, manage sub-project managers and suppliers, and handle executive expectations. Scope, uncertainty and influence grow at each step.

Does the IAPM Certified Project Manager exam cover these roles?

Yes. IAPM's CPM syllabus includes the project charter, stakeholders, steering committee and core team, sub-project manager and work package owner, project organisations, risk, review, close-out and soft skills. The exam has 120 questions in 80 minutes, and the passing score is 65%.

Select ratingPoorOkayGoodGreatAwesome

Rating: 5 / 5 (90 votes)