Project management for marketers: one intake, one queue, and the five statuses that stop work sitting in somebody's head

Marketing work rarely stalls because somebody is slow. It stalls because a request arrived in a corridor conversation, nobody wrote down what decision it supports, three things started at once, and the draft then sat for nine days waiting on an approver who did not know they were the approver. Project management for a marketing team is mostly four fixes to those four facts: one way in, one list of what is active, a status set that makes waiting visible, and one named approver per item with a window. The tool you use matters far less than whether those four exist.

Why marketing work is harder to run than it looks

• The requests come from everywhere. Sales wants a one pager, the founder saw a competitor's post, an event has a deadline, and the content calendar is already full. None of those arrive through the same door.
• Half the work is recurring and half is a project. A weekly publishing rhythm and a product launch need different handling, and running them in one list is why the rhythm slips first.
• The dependency is usually a person, not a task. Legal, a founder, a client, a designer with three other jobs. Waiting is the dominant state of most marketing work and most trackers do not show it.
• Done is ambiguous. Published is not the same as promoted, and a landing page without the tracking on it is not finished even though it is live.

The intake form, which is six fields

Everything comes in one way: a form, a single channel, or one shared board with a request template. Six fields, and a request that will not fill them is not ready to start.

Field	Why it is there
What you want, in one sentence	If the requester cannot write it, the brief does not exist yet
Who it is for	A named audience, not a market. This is the field that kills most vague requests
The decision it supports	What changes because this exists. Requests with no answer here go to the bottom honestly rather than quietly
The date, and why that date	A date with a reason is a constraint. A date without one is a preference
Who approves it	One name. Two approvers means the item waits for both and blames neither
What already exists	The old deck, the previous version, the brand file. This field saves hours per request

One queue, with a limit on what is active

Keep a single ordered list of work that is accepted, and a hard limit on how much is in progress at one time. Two or three items per person is the usual working number for a small team. The limit is the mechanism: when everything is in progress nothing can be prioritised, because starting something new costs nothing and finishing something is the only thing that frees capacity.

Order the queue on two questions rather than on a scoring spreadsheet. Which item has a date fixed by something outside this team, such as an event or a product release, and which item unblocks the most other work. Everything else is sequence rather than priority.

The five statuses, and one flag

• Requested. In the form, not yet accepted. The requester can see it and nobody has promised anything.
• Accepted, with a date. The team has taken it and said when. This is the only place a commitment is made, and it is made once.
• In progress. Somebody is working on it now and it counts against the limit.
• In review. With one named approver, and a date by which comments are due. If that date passes, the item moves on with the comments received so far, which is a rule agreed in advance rather than an argument on the day.
• Done, against a written definition for that kind of work.
• Blocked, which is a flag on top of a status and never a status of its own, with the name of the person or thing it waits on. Keeping it as a flag is what makes waiting countable at the end of the month.

Definition of done, written once per artefact

Artefact	Done means
Blog or landing page	Published, internally linked from at least one relevant page, tracking confirmed, and the target query recorded
Email campaign	Sent, with the segment, the subject line and the result stored against the campaign name
Printed item	Delivered, with the response code and the quantity recorded
Paid campaign	Live, with conversion tracking verified and the budget cap set
Event	Run, with the follow up sequence scheduled and the list imported with its consent source

Each line removes a specific argument. The first one exists because a page that nothing links to is published and invisible, which is the most common half finished item in marketing.

Separate the rhythm from the projects

A marketing team runs two kinds of work and they belong in two places.

• The rhythm. Weekly posts, the monthly newsletter, the monthly report, the quarterly review. These are commitments with no end date, they are planned on a calendar, and the discipline they need is a smaller promise kept for longer. A twelve week shape for this is in the marketing implementation schedule, and the editorial side lives in a content calendar.
• The projects. A launch, a rebrand, a site migration, an event. These have an end, a dependency chain and a date, and they belong in the queue with a sequence and an owner.

The reason to separate them is capacity. A project eats the rhythm first, because the rhythm has no external deadline, and six weeks later the publishing has stopped and nobody decided that. Reserve the rhythm's time before the project takes the rest.

The weekly meeting that replaces chasing

Twenty five minutes, the queue on the screen, and three questions in order. What finished since last week. What is blocked and on whom, by name. What is next out of the queue, and does anything in progress have to stop for it. Nobody reports status individually, because the board already says it, and an update spoken aloud is an update nobody can find on Thursday.

Four numbers worth keeping

• Cycle time: accepted to done, in days, per kind of work. This is the number you quote when somebody asks how long a landing page takes.
• Started against finished, counted monthly. A team that starts nine and finishes four has a limit problem rather than a capacity problem.
• Days spent in review, as a share of cycle time. In most teams this is the largest single component and the cheapest to fix.
• Requests declined or parked, with the reason. A queue with nothing declined is a queue that is quietly dropping things instead.

Choosing the tool, which is the last decision

Kind	Fits	Where it breaks
A shared spreadsheet	One or two people, under about twenty live items	No request form and no history, so the audit trail is somebody's memory
A kanban board tool	A small team wanting the queue visible	Thin reporting, so cycle time has to be counted by hand
A work management platform	Several people, intake forms, approvals and reporting in one place	Configuration becomes a project of its own if nobody owns it
The module inside your marketing suite	Teams already living in that suite all day	Weak for work the suite does not run, such as print and events

One rule whichever you pick: the tool holds the request, the brief, the status and the dates. Files live where files live. A tool that becomes the file store stops being searchable within a quarter.

When the capacity is outside the team

Freelancers and agencies sit in the same queue with the same statuses, and two things change. The brief has to be complete at acceptance, because a contractor cannot absorb a vague request the way a colleague does, and the review window has to be agreed in the contract rather than assumed. Whether a given job belongs in house, with a contractor or with an agency is a capacity question before it is a cost question, and the trade offs are set out in hire, outsource or use a contractor. Where the work is a scoped specialist project, the shape of the brief and the acceptance test matter most, as in outsourcing an SEO project.

Questions marketing teams ask about running the work

Do we need a project manager?

Below about six people, the role is a set of habits rather than a hire: somebody owns the intake, the queue order and the weekly meeting, usually the marketing lead. A dedicated coordinator earns their place when several streams run at once with external dependencies.

How do we handle urgent requests from the founder or from sales?

They go through the same form and jump the queue openly. The rule is that something in progress stops to make room, and the person whose work stopped is told. Urgency handled visibly costs one item. Urgency handled quietly costs the schedule.

What is the single biggest time sink?

Review and approval. One named approver, a stated window and an agreed default when the window passes removes more days from cycle time than any tool change.

Should we use sprints?

Two week cycles suit project work with dependencies. Continuous flow with a work in progress limit suits teams whose work arrives unpredictably, which is most marketing teams. The limit matters more than the ceremony.

How much planning is too much?

When the plan takes longer to maintain than the work it describes. One queue, six intake fields and a weekly meeting is the floor that holds; anything beyond it should be earning its keep in a number you look at.

How do we stop the calendar slipping during a launch?

Book the recurring work as committed capacity before the launch takes the remainder, and publish a reduced rhythm during that period on purpose. A smaller promise kept is worth more than a full calendar abandoned in week three.

One queue item most teams have never written down

Somewhere on your board is an item for checking what search results say about the business. Almost nowhere is there an item for checking what an assistant says, and buyers now ask ChatGPT, Gemini, Perplexity or Claude who to use and take the two or three names it returns. That answer is assembled from what has been published about you, it changes without warning, and nobody owns it. It makes a good recurring item: one owner, one date each month, the same five buying questions, and the wording recorded so a change is visible. AI Knows Us asks those questions across the main assistants and records which companies get named and what the answers were built from.