Advertising agency project manager: what the role owns day to day

An advertising agency project manager owns the movement of work from request to delivery: intake, schedule, resourcing, internal review, client approval, and the handoff to whoever publishes or ships the asset. The title hides a specific job. It is making the next decision possible for other people, on a predictable cadence, so the account team is not chasing status and the creative team is not guessing what is approved.

The role exists because agency work has two properties that resist ordinary planning: the time a creative task takes is not knowable in advance, and the definition of done is subjective until a named client says otherwise. A PM who ignores either one ends up running a very organised process toward a date nobody can hit.

What the role owns, and what it deliberately does not

An agency PM owns the schedule, the resource plan, the review calendar, the record of what was approved, and the escalation when a date is going to slip. Those five things are the job. Everything else is either shared or belongs to someone else.

The PM does not own the creative idea, the strategic recommendation, the media plan, or the final quality call. In most agencies that last one belongs to the creative director or the discipline lead, and a PM who starts editing the work creates two problems: the creative team stops trusting the review gate, and the PM loses the standing to push back on scope because they are now arguing about taste rather than time.

The title also varies by agency. In smaller shops the same person may be called traffic manager, studio manager, or project coordinator. Where an agency has a producer, the producer typically owns the production budget and the crew, and the PM owns the campaign schedule and the client-facing record. When one person holds both jobs, the honest tradeoff is that budget discipline tends to win on shoot weeks and schedule discipline tends to win the rest of the time.

A worked example: ten days for one campaign

Say an agency of eight receives a request for a product launch: a 30-second film, three cutdowns, two static sets, and one email. The launch date is fixed by the client's event. Here is where the PM adds value, and where they mostly stay out of the way.

Day 0, intake. The PM checks the request against the intake gate: objective, audience, channel specs, mandatories, budget code, launch date, and the name of the person who will approve. If the approver is unnamed, the job does not get a date. This single rule prevents more rework than any scheduling tool.

Day 1, scoping and the workback. A 45-minute session with the creative director, designer, and editor produces the schedule. The arithmetic runs backwards: launch date, minus publishing lead time, minus two client review rounds at three working days each, minus two internal review days, minus five production days. That gives a brief-freeze date. If the brief-freeze date is already in the past, the PM raises scope now — not in week two when the client asks why the film is late.

Days 2 to 4, protected production. The PM does not schedule status meetings inside this block. One check at the end of day two on the brief, one before internal review. Protecting the block is the actual deliverable here; a PM who fills the week with check-ins has moved the cost onto the people doing the work.

Day 5, internal review gate. Work does not reach the client while the creative director still has outstanding notes. The PM records the decisions, names the version, and sets the next gate. This is the cheapest place to catch a problem, because it costs internal hours instead of a client review round.

Days 6 to 10, client rounds and lock. Round one goes out with a consolidated change request, not a thread of forwarded emails. Freeform notes get converted into a numbered list. When the named approver signs off, the PM records approval in writing with the version name and date, then hands the file to publishing with the channel spec attached.

Across those ten days the PM also maintains six records: the brief, the workback schedule, the resource plan, the review log, the approval record, and the delivery manifest. If those live in five tools, the PM becomes the integration layer, which is exactly the failure mode the role is supposed to prevent. Many teams keep them together on a board — one card per deliverable, stages that mean something, and review comments attached to the file version rather than pasted into chat. Board automations can move a card when a stage changes and nudge assignees when a card passes its due date, but they cannot decide that a brief is thin.

Agency PM vs general PM vs producer

The three roles get conflated in job ads, and the confusion is expensive when you hire. The differences that matter are in the work itself, not the tooling.

The practical consequence: advice written for software project management — story points, velocity, deterministic sprints — transfers badly. An agency PM who promises a creative team will "burn down" a campaign is making a commitment the work cannot support.

Four failure modes and the counter-move for each

These recur across agencies of every size. Each one is cheaper to design out than to manage.

Thin brief, then rework. The brief arrives as a Slack message with a reference link. Counter-move: the intake gate, enforced without exceptions. A job with no named approver or no mandatories sits in intake until it has them, and the PM says so in writing to the account lead.

Silent double-booking. Two jobs are promised the same editor in the same week, and nobody notices until both slip. Counter-move: a weekly committed-hours view per person, checked before a date is promised rather than after it is missed. The mechanics of that check are covered in creative agency resource management.

Unbounded feedback. The client sends notes in three channels, on two versions, with no round limit in the contract. The team then revises against notes written about a cut that no longer exists. Counter-move: a round cap written into the scope, one consolidated response per round, and comments tied to a specific version. See how to reduce revision rounds on video projects for the versioning side of this.

Verbal approval. Someone says "looks good" on a call, the file ships, and a week later the client says that is not what was agreed. Counter-move: one written approval per deliverable, naming the version and the date. A thumbs-up in a meeting is not an approval, and the PM should be comfortable being the person who says so.

A fifth problem sits next to these: the handoff to publishing or media is nobody's job, so a finished film arrives without the right aspect ratio or caption file. Counter-move: a spec line on the card and a named recipient for each channel, decided at scoping.

Advertising agency PM role charter checklist

Produce a one-page charter that states who decides what, so the PM role is defined before you hire or hand over a job.

An illustrative capacity calculation for the role

Whether you need one PM or three is a numerical question, and the numbers should be yours. The example below is illustrative, not a benchmark — rerun it with your own hours.

Assume a 40-hour week. Recurring status and account syncs take 6 hours. Internal admin — billing triggers, timesheets, file wrangling — takes 4. That leaves 30 hours for job work. Suppose a campaign in steady production costs about 1.5 hours a week of PM attention, and a campaign in review or launch week costs about 5 hours.

Six production campaigns cost 9 hours. Three campaigns in launch week cost 15. Total 24, leaving a 6-hour buffer. Add a fourth launch campaign and you are at 29 of 30 — which means the first sick day, the first client escalation, or the first reshoot breaks a date. The buffer is the point. It is a decision about how much unpredictability the agency is willing to absorb, not a leftover after the calendar fills.

Two signs the role needs splitting rather than more hours: the PM is spending launch weeks purely on status reporting, and intake is being skipped because there is no time to hold the gate. At that point the usual split is one person on intake and resourcing and one on client-facing schedule and approval. Splitting the role without splitting the record — one board, one source of truth for stages and approvals — tends to make things worse, which is why configuring the board, routing, and handoffs comes before the hiring conversation.

Defining the role in your agency this week

If you are hiring for the role, writing the job description, or trying to explain to an account lead why the PM keeps asking for the same seven fields, the fastest route is a one-page charter. It does not need to be elegant. It needs to say who decides what, and where the record lives.

Then compare it with how you actually run jobs. The gaps are usually in two places: approvals that happen verbally, and handoffs that nobody owns. Both are fixable without new software, and both are what a competent agency PM is really being paid to hold. If you are also weighing tooling for the role, the criteria differ from the role itself — choosing an ad agency project management tool is a separate decision, and the general shape of campaign work is covered in creative agency workflow.

Start with one change rather than a system: pick your most recent job that went wrong and identify which of the four failure modes did the damage. Write the counter-move into the charter. One enforced rule — usually the intake gate — reduces more rework than a full process redesign.