Project Manager Responsibilities: A Clear List

Every project manager has a job description written by three people who never met. One wrote "coordinates tasks". One wrote "must be comfortable with ambiguity". One wrote "other duties as required", which is the phrase that means "buys the cake, fixes the printer and tells the CEO the date is not going to happen."

If you have ever wondered what a project manager is actually responsible for, you are in good company, and the confusion is not your fault. The role looks different in a construction company, a clinic, a software team and a family restaurant. But underneath the different words, the responsibilities are surprisingly stable. This guide lays them out as a clear list, shows where the role stops and is honest about the hardest part: being responsible for results when you do not control the people who produce them.

I write this as a project and operations manager, for two readers: people who want to become project managers, and owners who are about to hire one and want to know what to ask for.

The short answer

A project manager is responsible for getting a defined piece of work done, on an agreed schedule, within an agreed budget, to an agreed quality, with the people involved still speaking to one another. That last part is not a joke. It is on the list of real project outcomes.

Notice what the sentence does not say: it does not say the project manager does the work. A project manager who does every task is a very expensive team member and a project with no manager.

Swipe sideways to see the whole figure

The seven responsibilities

1. Define: what are we doing and why?

Before anything starts, someone must write down the goal, the scope, what success looks like and what is out of scope. If this is skipped, every person on the team imagines a slightly different project, and the differences surface at the worst possible moment.

The tool for this is a short project charter: a page that names the sponsor, the goal, the boundaries, the budget range and the people involved. It is also the first step of the PMBOK step-by-step series, where a business case turns an idea into a project worth doing.

A good sign: any team member can say what the project is for in one sentence.

2. Plan: how will we get there?

Planning is turning the goal into work packages, dates, people and money. In practice that means a work breakdown structure, a schedule, a budget, a list of who does what and a plan for how you will check progress. It does not mean a 90-page document that nobody reads.

• Break the work into pieces someone can own: see scope and the work breakdown structure.
• Turn the pieces into a schedule with dependencies and a critical path, the chain of tasks that sets the end date. A Gantt chart is one way to show it.
• Estimate cost in ranges and agree on a baseline. The cost management guide explains the difference between contingency and reserve.
• Put the pieces together in a lean project management plan.

A good sign: the plan fits on a few pages and people refer to it during the week.

3. Lead: who does what, and are they able to do it?

Projects are done by people, and the project manager's job is to make sure the right people are on the right tasks, with what they need and clear on what is expected. This is where the soft skills matter: motivating without a title, resolving conflict, saying thank you and noticing when someone is overloaded. A RACI chart is a plain tool for this. It says who is responsible, who approves, who is consulted and who is informed.

Capacity is part of leading. If three people are each assigned 150 percent of their time, the schedule is fiction. The article on capacity planning and bottlenecks shows how to see it early.

A good sign: nobody says "I thought that was someone else's job" in the weekly meeting.

4. Communicate: who needs to know what, and when?

Most project problems are communication problems wearing a project costume. A project manager is responsible for making sure that the right information reaches the right person at the right time, in a form they will read. That includes the sponsor, the team, the client and anyone affected by the change.

• Make a stakeholder map and a stakeholder register so you know who matters and what they expect.
• Write a short communication plan: what, to whom, how often.
• Send a one-page status report that tells the reader what changed, what is at risk and what you need from them.
• Keep the sponsor engaged; the guide on keeping your executive sponsor engaged is the cheapest insurance a project can buy.

A good sign: nobody is surprised by news that was available a week earlier.

5. Manage risks and issues: what could go wrong, and what has?

A risk is something that might happen. An issue is something that already has. A project manager keeps a list of both, with an owner and a next action for each, and looks at it every week. The method is not complicated; see project risk management in plain English and the lighter version for small teams, the risk register.

A good sign: at least one risk was avoided because someone saw it two weeks early.

6. Control: are we still on track, and who approved the changes?

Control is the habit of comparing the plan with what is happening and acting on the difference. That covers schedule, cost, quality and scope.

• Scope: changes are asked for, evaluated and approved before the work starts. Without that, you get scope creep, and in construction, a change order dispute.
• Schedule and cost: track them against the baseline. Earned value turns two numbers into a clear answer to "are we ahead or behind, and by how much?"
• Quality and results: check that what is built does what the project promised, and that the benefits are really captured later; see benefits realization.

A good sign: the number "we think we will finish on this date" changes slowly and for stated reasons.

7. Close and learn: did we finish, and what did we learn?

Closing is not a party, though a party is allowed. It is formally handing over the result, confirming that the client accepts it, releasing the team, settling the accounts and capturing what you learned so the next project is better. The project closeout guide and the lessons learned template guide show how to do it in an hour, not a week.

A good sign: a new project manager can read your notes and avoid your three biggest mistakes.

The hardest part: responsibility without authority

Here is the uncomfortable truth about the role: in many organizations, the project manager is accountable for the result but does not manage the people who do the work. Team members report to someone else. The money belongs to a sponsor. The decisions belong to a committee. You are responsible for all of it and in charge of none of it.

Swipe sideways to see the whole figure

This is not a flaw in you. It is a feature of the role. The way to handle it is to close the gap deliberately:

1. A written charter that names the sponsor and gives the project manager the right to plan, ask for resources and escalate.
2. A clear decision list: which decisions the project manager makes alone, which need the sponsor and which need a committee. Put it on one page.
3. An escalation path: if a blocker is not solved in two days, to whom does it go? Agree on this before you need it.
4. Influence, built on small promises kept. You will not be able to order people around. You can be the person whose meetings are short, whose messages are clear and whose requests are always reasonable. People help that person.

For the owner who is hiring: if you want a project manager to succeed, give them the authority in writing. If you do not want to, you are hiring a note-taker. The guide on how to hire a project manager has the interview questions and the red flags.

What a project manager is not

Part of the confusion about the role comes from tasks that wander in by accident. A project manager is usually not:

• The technical expert on everything. You need enough knowledge to ask good questions, not to out-engineer the engineers.
• The sponsor. The sponsor owns the "why" and the money. The project manager owns the "how and when".
• Everyone's line manager. Performance reviews and pay are usually someone else's job.
• The only person who communicates. You set up the channels. You do not have to write every message.
• A program manager. One project is one project; coordinating several related projects is a different role, explained in project manager vs. program manager.
• A construction manager by default. In construction, the roles overlap and differ by contract; see construction management vs. project management.

Saying these things at the start saves months of awkwardness.

A week in the life, in boring detail

What does a project manager actually do on a Tuesday? Something like this (illustrative):

• 8:30 Look at the page: three numbers, the risk list, today's decisions.
• 9:00 Ten-minute check with the team lead about a task that turned yellow.
• 10:00 Call a supplier about a delivery date that slipped. Update the schedule and the risk list.
• 11:00 Review a change request: what does it cost in time and money? Prepare a recommendation for the sponsor.
• 13:30 Write the weekly status report. One page: done, next, at risk, need.
• 14:30 Meet a stakeholder who is worried and listen. Write down their concerns in their words.
• 16:00 Close the loop: send the three commitments made today to the people who made them.

Notice how much of this is communication, estimation and follow-up, and how little is "managing a Gantt chart". The weekly rhythm in Project Focus Part 4 shows the meeting that holds this together.

It depends on the kind of project

The seven responsibilities stay the same, but the emphasis shifts:

• Construction: schedule, cost, contracts and change orders weigh heavily. See project management in construction.
• Software and fast-changing work: communication, priorities and short cycles matter more than a long plan. The guide to agile, waterfall or hybrid helps you pick a method.
• Small business: the project manager is often also the owner or the operations lead, wearing three hats. The lightweight governance article explains how to keep it simple.
• Process and operations work: measuring before and after is the main job, as in map, measure, fix.

Skills, in the order they matter

If you are building the role in yourself or another person, this is the order I would train:

1. Clear writing. A short email that says what you need and by when is worth more than a month of meetings.
2. Asking good questions. "What would have to be true for this to finish on time?" reveals more than "Are we on track?".
3. Basic estimation. Ranges, not single numbers.
4. Conflict and conversation. Disagreement is normal. Being able to say "let us write down the options" is a superpower.
5. A tool or two. A spreadsheet and a task board are enough for most projects.

If you are coming from a different field, the article on becoming a project manager without experience shows how to translate what you already do.

A one-page job description you can steal

Owners and new project managers can use this as a starting point. It is a template, not a contract; adapt it to your business, and have your attorney or HR advisor review any real job posting.

Purpose: Deliver the project's agreed result on schedule, within budget and to the agreed quality.

Responsible for: 1. Writing and maintaining the charter and the one-page plan. 2. Breaking the work into owned packages, with dates. 3. Running the weekly meeting and keeping the commitments list. 4. Keeping risks, issues and decisions on a visible list with owners. 5. Reporting status to the sponsor once a week, in one page. 6. Controlling changes: nothing is added without an estimate and an approval. 7. Closing the project: handover, acceptance and a short lessons-learned session.

Has the authority to: request resources from the sponsor, approve minor schedule adjustments within agreed limits and escalate blockers.

Needs from the sponsor: a named decision-maker, a budget range and a response within two working days.

Measured by: schedule and cost against the baseline, the quality of the handover and how the team and sponsor rate the working relationship.

Mistakes to avoid (the hall of fame)

• Doing the work yourself and calling it management.
• Starting without a written goal. The project will have as many goals as it has people.
• Reporting only good news. A green report that turns red overnight ends careers.
• Having no authority and not saying so. Ask for it in writing.
• Treating the plan as finished. A plan is a living document. Update it when reality changes.
• Skipping the closeout. Without it, you will repeat every mistake, with new people and the same enthusiasm.

An illustrative example: the owner who became a project manager

This is a made-up example. The owner of a 12-person landscaping company is asked by a hotel to redo its grounds in six weeks. She has never managed a project, only a business. On Monday she writes a one-page charter: goal, deadline, budget range, who decides. On Tuesday she breaks the work into nine packages and gives each to a crew lead. On Wednesday she writes down the three biggest risks: a late delivery of plants, a rainy week and a change of mind by the hotel's manager. For the last one, she agrees with the hotel in writing how changes are requested and priced.

Every Friday she sends a half-page update with three lines: done, next, at risk. In week four the plants are delayed. Because the risk was on the list, she already has a second supplier. The job finishes four days late, which the hotel accepts because the changes they asked for were priced in advance. She does not call herself a project manager. But she did all seven things on the list, and that is the job.

Try it: is your role clear?

Tick the statements that are true for a project you manage or sponsor. The tool tells you where the role may be fuzzy.

Interactive tool

Is the project manager role clear in your project?

Loading the tool…

What to do this week

1. Write the seven responsibilities on a page and mark which are clear in your current role and which are not.
2. For one real project, write the one-sentence goal and ask three team members to repeat it. Compare the answers.
3. Write the decision list: what the project manager decides, what the sponsor decides and what needs a committee.
4. Create or update the risk list, with an owner and a next action for each risk.
5. Send one page of status this Friday: done, next, at risk, need.
6. Book an hour after the project to capture lessons. Put it in the calendar now.

If you are an owner who needs a project manager's habits in your business, see my services or take the diagnostic. And if you want the whole method on a single page, start with Project Focus on one page.

Frequently asked questions

What are the main responsibilities of a project manager?

Defining the goal and scope, planning the schedule, budget and resources, leading the team, communicating with stakeholders, managing risks and issues, controlling changes and results, and closing the project with a handover and lessons learned. The project manager is responsible for the result, but the team does most of the work.

Is a project manager responsible if the project fails?

A project manager is accountable for managing the project well: planning, communicating, flagging risks early and escalating blockers. Whether a project succeeds also depends on factors the manager may not control, such as funding or sponsor decisions. That is why a written charter, clear authority and honest reporting matter so much.

What is the difference between a project manager and a team leader?

A team leader manages people who report to them, usually on an ongoing basis. A project manager manages a temporary effort with a start, an end and a defined result, often across people who report to others. In small businesses one person may do both, but the two roles ask for different habits.

Do I need a certification to be a project manager?

Not always. Many project managers started by running projects in another role. A certification such as the PMP can help in some industries and hiring processes, and it has a cost and requirements, which the PMP cost guide on this site breaks down. Real experience delivering projects usually matters more than a credential.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

Name (optional) Which of the seven responsibilities has been missing in a project you worked on, and what did it cost? Post comment

No email and no sign-up. Every comment is reviewed before it appears. Please keep it respectful and leave links out.