Agency Delivery Roles

A short canonical list of project delivery roles in a marketing, creative, digital, social, brand or integrated agency.

The aim is not to capture every market title. We need a clear set of standard roles, with enough definition underneath each title to make agency delivery easier to understand, hire for and organise.

Observed titles such as Digital Project Manager, Creative Project Manager, Delivery Lead, Senior Delivery Manager, Delivery Director or Head of PM should be treated as variants or modifiers unless the responsibilities clearly justify a different canonical role.

Variant and modifier rules

Domain words usually modify the role rather than create a new canonical role.

Digital Project Manager = Project Manager, digital modifier
Creative Project Manager = Project Manager, creative modifier
Integrated Project Manager = Project Manager, integrated modifier
CRM Project Manager = Project Manager, CRM modifier
Social Project Manager = Project Manager, social modifier
Healthcare Project Manager = Project Manager, healthcare modifier

Seniority words should be tested against responsibility.

Junior Project Manager may be Project Coordinator or Project Manager.
Lead Project Manager may be Senior Project Manager or Project Director.
Delivery Lead may be Senior Project Manager, Project Director or Head of Project Management depending on responsibility.
Delivery Manager may be Senior Project Manager or Project Manager.
Delivery Director may be Project Director, Programme Director or Head of Delivery.
Director of Project Management is usually Head of Project Management.
Director of Delivery is usually Head of Delivery if the role owns the delivery function.

Important distinction

The canonical title should be chosen by responsibility, not by observed market title.

The test is:

What does the role own?
At what level does it own it?
Is the role about projects, connected programmes, the PM discipline or the delivery system?

1. Project Coordinator

Role purpose

A Project Coordinator supports the delivery of agency projects by keeping project information accurate, organised and visible. The role exists to make sure the practical details around the work are captured, maintained and followed up.

Owns

A Project Coordinator usually owns project documentation and coordination support. This may include trackers, meeting notes, action logs, project files, status documents, version control, schedules, asset lists and project tool updates. They help the team understand what has happened, what needs to happen next, who owns each action and where the latest information lives.

Supports / works with

They support Project Managers, Senior Project Managers and sometimes Project Directors. They work with account teams, creative teams, strategy, production, design, development, QA, media, social, CRM or other specialist teams depending on the agency.

Does not normally own

A Project Coordinator does not usually own scope, budget, senior client expectations, major delivery risk, commercial escalation, team leadership or the delivery process. They can support those areas. They are not normally accountable for them.

Difference from neighbouring roles

The difference between a Project Coordinator and a Project Manager is ownership. A Coordinator supports delivery. A Project Manager owns delivery for defined projects.

Common observed title variants

Project Assistant
Project Administrator
Delivery Coordinator
Programme Coordinator
Assistant Project Manager
Junior Project Manager, where the role is mainly support-based

How to build the next-stage skills

To move from Project Coordinator to Project Manager, the change is from supporting delivery to owning delivery. That doesn’t happen through training alone. It happens by taking responsibility for small pieces of real work, gradually.

A Project Coordinator should look for contained chances to own something small: a project, a workstream, a review cycle, a status process, a timeline update, a recurring action list. The aim is to move from keeping information accurate to using it to drive the work forward.

A practical route is to ask the Project Manager for one defined area of ownership: “Can I own the review tracker on this project?” or “Can I run the weekly action follow-up?” or “Can I maintain the timeline and flag movements to you?” These are small asks, but they create evidence of ownership.

They should also learn the commercial basics: what the fee is, what the timeline assumes, what is in scope, what is out of scope, who is approving the work, what happens if the team spends more time than planned. They don’t need to own these areas yet, but they need to understand them.

If the agency has a learning budget, they should ask directly about using it for project management, Agile, delivery, commercial or communication training. Many agencies have training budgets and don’t publicise them well. The request should be practical and linked to the role: “I’d like to use some training budget to build the skills needed to move from coordination into project ownership.”

The next-stage evidence is being trusted to own a small piece of delivery and keep it under control.

2. Project Manager

Role purpose

A Project Manager is responsible for the day-to-day delivery of defined agency projects. The role exists to turn agreed work into a controlled delivery path, then keep that work moving through the agency.

Owns

A Project Manager usually owns project plans, timelines, actions, scope control, delivery coordination, internal team orchestration, review cycles, approval routes, project documentation, basic budget tracking, issue-spotting and regular stakeholder updates. They make sure the right people know what needs to happen, when it needs to happen and what decisions are required.

Supports / works with

They work closely with account management, strategy, creative, design, copy, production, development, QA, media, data, CRM, social, client service and external partners. The exact mix depends on the agency and the type of work.

Does not normally own

A Project Manager does not usually own the wider delivery process, manage other project managers, carry senior commercial accountability or set the delivery operating model. They can flag risks and budget movement. More senior roles own escalation and commercial protection.

Difference from neighbouring roles

The difference between a Project Coordinator and a Project Manager is that the Project Manager owns the delivery of assigned projects. The difference between a Project Manager and a Senior Project Manager is complexity, autonomy and judgement under pressure.

Common observed title variants

Digital Project Manager
Creative Project Manager
Integrated Project Manager
CRM Project Manager
Social Project Manager
Campaign Project Manager
Healthcare Project Manager
Marketing Project Manager
Junior Project Manager, where the role owns delivery rather than only supporting it

How to build the next-stage skills

To move from Project Manager to Senior Project Manager, the change is from controlled delivery to delivery judgement. A Project Manager needs to learn how to manage work that isn’t perfectly set up: unclear scope, shifting priorities, budget pressure, difficult stakeholders, late feedback, weak briefs, overloaded teams.

The best way to learn this is to keep a private delivery judgement log. On each project, note where the plan changed, where scope moved, where budget pressure appeared, where approval slowed, where the team became overloaded, where escalation should have happened earlier. This turns day-to-day delivery into learning, not just pressure.

They should also ask for exposure to the harder parts of the work. That might mean sitting in on scope conversations, budget reviews, risk calls, client status meetings, senior internal escalations. They don’t need to lead those conversations immediately. First, they need to hear how experienced people frame the problem.

A Project Manager can also practise senior judgement in small ways: flag risks earlier, write clearer status notes, explain the consequence of a delay, document a scope change, ask “what decision do we need?” rather than only “what is the update?”

If formal development isn’t offered, they should ask for specific support, not vague mentorship. For example: “Can we review one difficult project together each month and talk through where my judgement was strong or weak?” That’s easier for a busy manager to agree to than a broad personal development promise.

The next-stage evidence is the ability to see when a project is becoming unsafe and to act before the damage is obvious.

3. Senior Project Manager

Role purpose

A Senior Project Manager owns the delivery of more complex, higher-risk or higher-value agency projects. The role exists where delivery requires stronger judgement, greater autonomy and more active management of ambiguity, pressure and risk.

Owns

A Senior Project Manager owns project delivery across more complex work. This usually includes planning, live delivery control, scope management, budget tracking, resource coordination, internal orchestration, stakeholder expectation management, risk and issue control, review and approval management, governance, documentation and delivery recovery where needed.

Supports / works with

They work across the same agency disciplines as a Project Manager, but with more senior involvement. They may work directly with account directors, strategy leads, creative leads, production leads, technical leads, finance, resource managers and senior clients.

Does not normally own

A Senior Project Manager does not automatically own the project management discipline, line-manage the PM team or design the agency delivery model. They can mentor others. People leadership isn’t always part of the role.

Difference from neighbouring roles

The difference between a Project Manager and a Senior Project Manager is the level of difficulty the role can carry without constant senior intervention, not years of experience. A Senior Project Manager should be trusted with unclear scope, difficult stakeholders, budget pressure, cross-discipline complexity and emerging delivery risk.

Common observed title variants

Senior Digital Project Manager
Senior Creative Project Manager
Senior Integrated Project Manager
Senior CRM Project Manager
Delivery Manager
Senior Delivery Manager
Delivery Lead, where the role mainly owns complex project delivery rather than director-level accountability
Lead Project Manager, where the role is senior project control rather than functional leadership

How to build the next-stage skills

To move from Senior Project Manager to Project Director, the shift is from running difficult work to carrying senior delivery accountability. A Senior Project Manager needs to see beyond the project plan and understand the wider commercial, stakeholder and operational consequences of delivery decisions.

This can be built inside the current job by asking better questions around every significant project: What was sold? What fee is attached to it? What assumptions were made? Where is the margin risk? Who owns the client relationship? What happens if the team over-services? What will leadership need to know if this goes wrong?

A Senior Project Manager should start building the habit of writing short senior delivery summaries. Not long reports. Just clear notes that explain: what is happening, why it matters, what decision is needed, what the commercial implication is and what risk exists if nothing changes. This is one of the practical bridges into Project Director work.

They should also seek opportunities to support other PMs. That could mean reviewing a plan, helping a junior PM prepare for a client status, sharing a risk template, joining a difficult internal meeting or helping stabilise a messy project. The point is to move from “I can run my own work” to “I can improve the delivery health of work around me.”

If the agency has a training budget, useful areas are commercial management, negotiation, stakeholder management, finance for non-finance managers, facilitation, conflict handling and leadership communication. The request should be framed around agency value: “This would help me manage risk and commercial pressure earlier, instead of escalating problems once they are already expensive.”

The next-stage evidence is calm, senior control, not heroic delivery: clearer escalation, better commercial judgement, the ability to protect major work before it becomes a leadership problem.

4. Project Director

Role purpose

A Project Director is responsible for senior delivery ownership across major projects, accounts or workstreams. The role exists to protect the delivery shape, commercial position, stakeholder confidence and risk profile of important agency work.

Owns

A Project Director usually owns senior scope control, commercial delivery control, risk and escalation, senior stakeholder expectation management, governance, resource pressure, delivery recovery and the overall delivery health of major work. They are expected to see where delivery is becoming structurally unsafe and intervene before damage occurs.

Supports / works with

They work with account leadership, client services, strategy, creative, production, technology, finance, resource, operations and senior clients. They may guide Project Managers and Senior Project Managers, support difficult client conversations and help reset troubled work.

Does not normally own

A Project Director does not necessarily own the project management discipline or the whole agency delivery system. They can influence process and mentor delivery people. Unless they own PM standards, PM people or the delivery operating model, they should not be treated as Head of Project Management or Head of Delivery.

Difference from neighbouring roles

The difference between a Senior Project Manager and a Project Director is accountability. A Senior Project Manager runs difficult work. A Project Director carries senior responsibility for the delivery health of major work.

A Project Director is also different from a Programme Manager. A Project Director is usually defined by senior delivery authority across important work. A Programme Manager is defined by control of connected projects or workstreams.

Common observed title variants

Senior Project Director
Group Project Director
Integrated Project Director
Client Project Director
Delivery Director, where the role owns major work but not the delivery function
Senior Delivery Lead, where the role carries director-level delivery accountability

How to build the next-stage skills

The next step from Project Director is not always one fixed role. A Project Director may move towards Programme Director, Head of Project Management or Head of Delivery depending on the shape of their work.

To move towards Programme Director, they need to practise managing connected work, not just major projects. That means paying attention to dependencies, decision routes, cross-workstream risks, governance, reporting and the overall health of a programme. A practical step is to ask to own the programme view across related projects, even if individual PMs still own the project plans.

To move towards Head of Project Management, they need to build evidence of discipline leadership. That means improving how PMs work, not just how projects are delivered. They might create better templates, mentor PMs, run delivery reviews, improve escalation habits, define clearer role expectations or help raise the standard of project management across the team.

To move towards Head of Delivery, they need to think beyond PM. That means understanding how project management connects with resource, production, traffic, studio, finance, commercial control, account leadership and agency operations. A practical step is to map how work actually moves through the agency and identify where the system creates avoidable friction or margin loss.

A Project Director who wants to progress should not wait to be given a transformation project. They can start by making one part of the delivery system clearer: a better escalation route, a cleaner delivery report, a more useful margin review, a clearer scope-change process or a stronger project close-out habit.

If training budget exists, this is the point to ask for leadership, commercial, finance, operations or coaching development. The argument is straightforward: the agency benefits when senior delivery people protect margin, develop teams and improve the delivery system, instead of just rescuing troubled work.

The next-stage evidence is the move from owning major work to improving the system around major work.

5. Programme Manager

Role purpose

A Programme Manager is responsible for managing a connected body of work rather than a single project. The role exists where multiple projects, workstreams or delivery tracks need to be coordinated as one larger programme.

Owns

A Programme Manager usually owns programme plans, dependency tracking, cross-workstream coordination, programme reporting, governance rhythms, risk and issue visibility, decision logs, stakeholder alignment and the overall control structure for connected work. They make sure the separate parts of a programme are visible, sequenced and understood.

Supports / works with

They work with Project Managers, Senior Project Managers, Project Directors, account leads, discipline leads, senior clients and sometimes PMO or operations teams. They may coordinate multiple delivery owners without directly managing all of them.

Does not normally own

A Programme Manager does not necessarily own every individual project plan in detail. They also do not automatically carry senior commercial accountability or function-level delivery leadership. Those responsibilities depend on the role and agency.

Difference from neighbouring roles

The difference between a Project Manager and a Programme Manager is the unit of control. A Project Manager owns defined projects. A Programme Manager owns the coordination of connected projects or workstreams.

A large project is not automatically a programme. There should be genuine multi-workstream, dependency or programme-governance responsibility.

Common observed title variants

Programme Lead
Senior Programme Manager
Delivery Programme Manager
Integrated Programme Manager
PMO-style Programme Manager, where the role is governance-heavy
Programme Coordinator, only where the role owns programme coordination rather than project support

How to build the next-stage skills

To move from Programme Manager to Programme Director, the change is from programme coordination to senior programme accountability. A Programme Manager needs to move beyond tracking the programme and start shaping the decisions that keep it safe.

They can build this by making programme information more useful to senior people. A good programme view shows more than status. It shows dependencies, blocked decisions, risk concentration, resource pressure, scope movement, commercial exposure and the choices that need to be made.

A practical habit is to turn programme reporting into decision support. Instead of reporting “Workstream 3 is delayed”, the Programme Manager should learn to say: “Workstream 3 is delayed because approval is blocked. This affects launch timing and increases resource pressure in two other workstreams. We need a decision by Friday on whether to reduce scope or move the date.”

They should also ask to attend or support senior governance forums, even at first as an observer. Programme Director skill is built by seeing how senior people make trade-offs across cost, timing, scope, risk and stakeholder pressure.

If development is not offered, the Programme Manager should ask for a specific growth opportunity: ownership of a governance forum, responsibility for the risk view, responsibility for dependency reporting, or the chance to lead a programme review. These are practical steps into programme authority.

The next-stage evidence is the ability to turn programme complexity into clear choices for senior stakeholders.

6. Programme Director

Role purpose

A Programme Director is responsible for senior delivery ownership across a major programme, portfolio or connected set of workstreams. The role exists where a programme needs senior authority over governance, risk, stakeholder alignment, scope, commercial control and escalation.

Owns

A Programme Director usually owns programme-level delivery shape, senior governance, stakeholder alignment, commercial delivery risk, escalation, dependency control, scope protection, resource pressure and programme recovery. They are expected to understand whether the programme is structurally able to deliver, not just whether the individual projects are moving.

Supports / works with

They work with senior clients, account leadership, delivery leads, Project Directors, Programme Managers, discipline leads, finance, operations and agency leadership. They may guide the delivery team and provide senior cover for difficult decisions.

Does not normally own

A Programme Director does not automatically own the delivery function. They can influence ways of working and governance. Unless they own the delivery operating model, PM discipline or function-wide delivery capability, they should not be treated as Head of Delivery.

Difference from neighbouring roles

The difference between a Programme Manager and a Programme Director is authority. A Programme Manager controls and coordinates the programme. A Programme Director carries senior accountability for programme delivery, stakeholder alignment, escalation and commercial risk.

A Programme Director should not be used as a grand title for a single large project. There should be genuine programme-level responsibility.

Common observed title variants

Senior Programme Director
Global Programme Director
Programme Management Director, where the role is programme-led rather than function-led
Delivery Director, where the role owns programme-level delivery but not the whole delivery function

How to build the next-stage skills

The next step from Programme Director is usually towards Head of Delivery, Head of Operations, Delivery Director or another senior leadership role. The shift is from owning a major programme to improving the system that allows many programmes and projects to succeed.

A Programme Director can build this by looking for patterns beyond their own programme. Where do projects repeatedly lose margin? Where do approvals fail? Where does resourcing break down? Where do teams lack authority? Where does reporting create noise rather than decisions? Where do roles blur? Where does commercial risk arrive too late?

They should start turning those patterns into practical improvements. That might mean a better governance model, a clearer escalation path, a more useful delivery dashboard, a stronger scope-change process, a better handoff between sales and delivery, or a clearer split between PM, production and resource responsibilities.

They should also build stronger commercial and operational literacy. This includes margin, utilisation, revenue recognition, forecasting, write-offs, retained revenue, external spend, capacity planning and team structure. A Programme Director moving towards wider leadership must understand whether the delivery model is healthy, not just whether a programme can deliver.

If the agency has training budget, useful development includes business finance, operations, leadership, coaching, negotiation, organisational design and commercial management. The request should be tied to business performance: “I want to build the skills to improve delivery reliability and commercial control across more than one programme.”

The next-stage evidence is the ability to make delivery more reliable across the agency, not only across one programme.

7. Head of Project Management

Role purpose

The Head of Project Management owns the project management discipline inside an agency, department or business unit. The role exists to make sure project management is clear, consistent, capable and commercially aware.

Owns

The Head of Project Management usually owns PM standards, PM ways of working, templates, tools, delivery documentation standards, mentoring, line management, capability development, hiring input, role clarity and the quality of project management across the team. They may also support resourcing, escalation, risk management and delivery improvement.

Supports / works with

They work with Project Managers, Senior Project Managers, Project Directors, account leads, resource managers, finance, operations, production, creative, technology and senior agency leadership.

Does not normally own

The Head of Project Management does not always own the whole delivery operating model. They may own the PM discipline without owning production, resource, traffic, studio, technical delivery, delivery operations or agency workflow as a whole.

Difference from neighbouring roles

The Head of Project Management is not simply the most senior Project Manager. The role owns the discipline, not just difficult projects.

The difference between Head of Project Management and Head of Delivery is scope. Head of Project Management owns the PM discipline. Head of Delivery owns the wider delivery system.

Common observed title variants

Head of PM
Director of Project Management
PMO Lead, where the role owns PM standards and governance
Delivery Lead, only where the role clearly owns the PM discipline rather than a project or account

How to build the next-stage skills

To move from Head of Project Management to Head of Delivery, the change is from owning the PM discipline to owning the broader delivery system. A Head of Project Management should already be strong on PM people, standards, tools, templates, mentoring and ways of working. The next step is to understand how the whole agency delivery machine works.

They can build this by mapping the connections between project management, production, resource, traffic, studio, technical delivery, finance, account leadership, governance and commercial control. The question is no longer only “Are PMs doing their jobs well?” It becomes “Is the agency set up to deliver work reliably and profitably?”

A practical route is to take one recurring delivery problem and trace it across the system. For example: why are projects over-serviced, why are approvals late, why is resource always squeezed, why are budgets unclear, why do PMs escalate too late, why are retainers unhealthy, or why do project handovers fail? The Head of Project Management can then propose a system-level improvement rather than another PM-only fix.

They should also seek more exposure to finance, resource planning, operations and senior leadership decisions. If those meetings are closed, they can ask to attend one monthly review as development, or ask for a short debrief afterwards. The point is to learn how delivery choices connect to agency performance.

If there is a learning budget, this role should use it for operations, commercial management, organisational design, leadership coaching, finance or change management. The case is easy to make: stronger delivery leadership reduces waste, improves margin and makes the agency easier to run.

The next-stage evidence is broader ownership: improving how work flows through the agency, not only how project managers manage it.

8. Head of Delivery

Role purpose

The Head of Delivery owns the wider delivery system inside an agency, department or business unit. The role exists to make sure work can move through the agency in a clear, reliable, commercially controlled and scalable way.

Owns

The Head of Delivery usually owns the delivery operating model. This may include project management, programme management, production, resource, traffic, studio operations, technical delivery, delivery operations, governance, tools, standards, escalation routes, role boundaries, capacity management, commercial delivery control and delivery capability.

Supports / works with

They work with agency leadership, client services, operations, finance, creative, strategy, production, technology, resource, project management and senior clients. They may also become involved in major pitches, troubled accounts, operating-model redesign or senior escalation.

Does not normally own

The Head of Delivery does not normally run individual projects as their primary role. They can step into difficult work. Their responsibility is the health of the delivery system.

They should not be confused with a Project Director who owns major work, or a Programme Director who owns a major programme. Head of Delivery should involve function-level responsibility for how delivery works.

Difference from neighbouring roles

The difference between Project Director and Head of Delivery is the object of ownership. A Project Director owns major work. A Head of Delivery owns the delivery system.

The difference between Head of Project Management and Head of Delivery is breadth. Head of Project Management owns PM people and standards. Head of Delivery owns the broader operating system that may include PM, production, resource, traffic, governance, commercial delivery and delivery operations.

Common observed title variants

Director of Delivery
Delivery Director, where the role owns the delivery function
Chief Delivery Officer
Head of Operations & Delivery, where delivery operating model is central
Programme Management Director, where the role owns delivery function, not only programme delivery

How to progress beyond this role

Head of Delivery is already the top role in this canonical delivery ladder. Progression beyond it usually means moving into wider agency leadership rather than a more senior delivery title.

Possible next steps include Operations Director, Chief Operating Officer, Managing Director, General Manager, Chief Delivery Officer or agency founder / partner, depending on the organisation. The shift is from owning delivery as a function to owning wider business performance.

A Head of Delivery can build towards this by increasing their grip on the business beyond delivery. That means understanding agency P&L, revenue, margin, utilisation, forecasting, client portfolio health, talent strategy, pricing, business development, operations, organisational design and leadership decision-making.

The practical route is to ask for exposure to the senior commercial rhythm of the business: monthly numbers, forecast reviews, resource planning, client profitability, leadership meetings, board packs or operating reviews. If access is limited, they can ask for one regular commercial review with the MD, COO, Finance Director or founder.

They should also build a record of business-level contribution. That might include reducing delivery leakage, improving forecasting accuracy, making resourcing more transparent, improving escalation, reducing write-offs, strengthening delivery governance or helping the agency make better decisions about client work.

If training budget exists, the right areas are finance, commercial leadership, organisational leadership, negotiation, business strategy, coaching and executive communication. At this level, development should be framed as business value, not personal interest.

The next-stage evidence is the ability to connect delivery performance to the overall health, direction and commercial strength of the agency.

Across every role on this ladder, the same rule applies. Build the evidence. Take the ownership in front of you. The next-stage evidence is being undeniable when the opportunity comes.