How to Set a Weekly Marketing Capacity Limit for a Small Team

Executive summary

A weekly marketing plan often fails because it counts tasks but ignores the hours needed to finish them. A “quick post” may involve writing, translation, design, approval, link testing and replies. When every request is labelled urgent, the team starts many tasks and finishes too few.

A capacity limit makes the trade-off visible. Allow 45 minutes to set up the first planning sheet and 15 minutes for a weekly review. This is a planning method, not a claim that every task can be estimated precisely.

Start with available hours, not wish-list tasks

List the real hours each person can give to marketing after customer service, operations, meetings, leave and other obligations. If an owner has six nominal hours but can reliably protect only three, plan around three. Use recent experience rather than the most optimistic week.

Then reserve capacity for recurring duties that cannot simply be skipped: responding to enquiries, checking active offers, maintaining public information and handling urgent corrections. The remaining hours are the discretionary capacity for new content, experiments and improvements.

Example: a two-person shop team has eight hours per week available for marketing after daily operations. Reserve two hours for monitoring and customer responses, one hour for QA and reporting, and one hour for unexpected work. That leaves four hours for planned production. The figures are illustrative; calculate your own.

Estimate the complete task, not the visible output

Break a task into steps. For a short local campaign, the estimate might include 20 minutes for the brief, 30 for copy, 45 for design, 15 for translation review, 15 for approval follow-up, 10 for link QA and 10 for publishing. The “post” is not a 20-minute task just because writing the caption takes 20 minutes.

Track actual time for a few weeks, without turning the exercise into employee surveillance. Compare estimates with reality and adjust future planning. If approvals regularly add two days of waiting, record elapsed time separately from hands-on work. A task can require little labour and still block the schedule.

Use a simple priority score with an override rule

Score each candidate task from 1 to 3 on three dimensions:

• Customer or business impact: will it remove a real obstacle or support an important offer?
• Time sensitivity: does a date, event or customer promise make delay costly?
• Confidence: do we have enough evidence and inputs to complete it well?

Add the scores for a rough ranking, but do not let the number replace judgement. A broken booking link should be fixed even if it is not a high-impact content idea. Compliance, safety and customer-impacting errors get an explicit override category.

Avoid scoring dozens of tasks in detail. The purpose is to resolve conflicts between a handful of candidates, not to create a second job maintaining the prioritisation system.

Limit work in progress

Choose no more than two or three active production tasks per person, depending on task size. New work enters a queue rather than displacing everything already underway. When an urgent request arrives, the owner names what will be delayed or cancelled. This makes the cost of “just one more task” visible.

A weekly board can use four columns: queued, ready, in progress, and done. “Ready” means the brief, source facts, destination and approver are available. Do not move a task into progress when a key input is missing; that creates activity without progress.

The weekly planning meeting

Keep the meeting to 15 minutes:

1. Review last week’s unfinished work and identify why it stalled.
2. Protect the time needed for recurring operational duties.
3. Choose the highest-value tasks that fit remaining capacity.
4. Check dependencies: who must approve, translate, supply photos or update the landing page?
5. Name the owner and define what “done” means.
6. State what will not be done this week.

The final step matters. A plan that contains only commitments but no exclusions is usually a wish list.

Build a buffer for small-business reality

Leave some capacity unassigned. Customer issues, staff absences, stock changes and urgent corrections are normal operational events. If the buffer remains unused, pull one item from the queue; do not automatically fill every spare minute in advance.

For campaigns with fixed dates, work backwards from the final release and include approval and QA time. Scheduling tools can help with publication, but scheduling does not replace checking that the offer remains valid or that someone can respond to customer enquiries.

Review the system after four weeks

Measure planned versus completed tasks, recurring duties missed, urgent interruptions and estimate accuracy. Do not judge the plan only by number of posts produced. A week with fewer posts but correct prices, prompt replies and a working booking path may be operationally stronger than a high-volume week with errors.

If the team repeatedly exceeds capacity, choose among three honest options: reduce scope, extend deadlines, or add resources. Do not solve a structural capacity problem by permanently expecting unpaid overtime or silently dropping customer service.

Copyable planning fields

task | business outcome | owner | estimated hands-on hours | dependencies | deadline | priority | definition of done | status | reason delayed

Conclusion and next steps

Set the first capacity limit using actual availability and protect the recurring work before adding new campaigns. Use estimates to improve planning, not to punish people. A small team gains reliability by finishing a realistic amount of work well, and by making the cost of new requests explicit.