Set Up a Marketing Team Capacity Forecast Before Accepting Work

Overview

A lightweight forecasting method for estimating available hours, protecting critical work, and making realistic campaign commitments.

Why a task list is not a capacity plan

A team can have a clear list of tasks and still miss deadlines because the list does not show whether the work fits the people and time available. Ten tasks labelled 'small' can consume a week when each requires stakeholder review, asset collection, revisions, and publishing checks. Capacity planning makes the trade-off visible before a deadline becomes a crisis.

A useful forecast does not need sophisticated resource-management software. A spreadsheet with weekly availability, committed work, estimated effort, dependencies, and a confidence level is enough for many small businesses. Its purpose is to support a decision: accept, defer, reduce scope, reassign, or decline.

Calculate realistic available capacity

Start with working hours, then subtract time that is already committed to meetings, customer support, administration, leave, and recurring maintenance. Do not treat every paid hour as a production hour. A marketer scheduled for 40 hours may have substantially less time for new campaign work after reviews, reporting, and coordination.

Use historical evidence when possible. Compare estimated and actual effort for common tasks such as a landing page, newsletter, product photo set, or local promotion. If estimates are consistently low, adjust the standard range rather than expecting people to work faster every week. Separate hands-on production time from waiting time for approvals or materials.

Include role constraints. A designer may have spare hours while the only person authorised to approve claims is fully booked. Total team capacity can look healthy even when one specialist is a bottleneck. Forecast by skill or required decision-maker for work that cannot be freely reassigned.

Estimate work with ranges and assumptions

Use a range for uncertain tasks rather than a false-precision estimate. For example, a simple email update might take two to four hours when copy and assets are ready, but substantially longer if pricing, audience rules, or approvals are unresolved. Record the assumptions behind the estimate so the team can see what would cause it to grow.

Break large deliverables into stages: brief, research, draft, production, review, revision, launch, and measurement. Each stage has different dependencies and owners. This helps reveal that a campaign may require only a few production hours but several days of calendar time because legal, sales, or client approval is pending.

Add a contingency for work with high uncertainty, external dependencies, or a history of rework. Do not hide the contingency inside every task estimate without explanation; label it so managers can see why the forecast contains a buffer. The right amount depends on the work and historical variance, not a universal percentage.

Create a decision rule for incoming requests

Every new request should state the outcome, audience, deadline, required deliverables, approver, and consequence of missing the date. A request that says 'need a post urgently' does not provide enough information to compare it with a scheduled launch or customer-support obligation.

Compare the request with the remaining capacity in the relevant role and week. If it does not fit, make the trade-off explicit: which existing item moves, which deliverable is reduced, or what extra support is authorised? Do not accept the new work and silently push the cost onto evenings or quality checks.

Use priority tiers sparingly. A genuine customer-impacting incident or fixed contractual deadline may outrank a routine content update. If everything is marked urgent, the labels no longer help. Require the requester to explain the impact and decision deadline for emergency work.

Review forecast accuracy and rebalance

At the weekly planning meeting, compare planned effort with actual effort and note why major differences occurred. Typical causes include missing inputs, late feedback, unclear briefs, unexpected technical problems, and tasks that were underestimated. The objective is not to judge individuals; it is to improve the next forecast.

Track a few practical indicators: committed hours versus available hours, work carried over, overdue dependencies, urgent work added after planning, and estimate accuracy for repeated task types. Avoid using a single utilisation percentage as a performance target. A fully booked team has no room for unexpected customer needs, training, or quality improvement.

Keep a short reserve for unplanned but legitimate work. When the reserve is repeatedly consumed by the same category, either create a recurring capacity allocation or fix the upstream cause. For example, repeated product-page corrections may indicate poor product data readiness rather than a need for more emergency hours.

A 30-minute weekly routine

First, confirm leave and recurring obligations. Second, list work already in progress and its remaining effort. Third, identify dependencies and approval bottlenecks. Fourth, compare new requests against skill-specific capacity. Finally, publish the agreed commitments and explicitly name what is not being done this week.

Keep the forecast easy to maintain. If updates take longer than the decisions they support, simplify the fields. A forecast that is slightly approximate and reviewed consistently is more useful than a complex model that becomes stale after two days.

Worked example: a one-week launch request

A three-person team has already committed to a product page, a monthly email, and a customer support campaign. A manager requests a new launch announcement with two days' notice. The forecast shows that the designer has no capacity and the only approver is reviewing a pricing change. The team offers three options: move the product page, publish a simpler approved announcement, or assign an additional qualified designer and reviewer. The requester chooses the simpler version. The team records the scope reduction and protects the existing deadlines. After launch, actual hours are compared with the estimate so the next forecast reflects the real review effort. The point is not to reject urgent work automatically, but to make its cost visible.

Implementation note

Use the forecast as a conversation tool, not a hidden scoring system for employees. Estimates are affected by unclear briefs, dependency delays, and rework outside an individual's control. Share the assumptions with requesters and revisit them when scope changes. If the same kind of work repeatedly takes longer than planned, update the estimate range and investigate why. A mature forecast becomes more accurate because the organisation learns, not because staff are pressured to make every estimate smaller.

Key Takeaways

• Capacity means realistic available time by skill, not total hours on the payroll.
• New urgent work must displace something or receive additional capacity.
• Use estimate-versus-actual data to improve forecasts without turning them into individual surveillance.

Conclusion and Next Steps

Use the forecast to make commitments visible, not to pretend every task can be predicted perfectly. Update estimates from real delivery evidence and make every new urgent request carry an explicit trade-off. Protecting capacity is part of protecting quality.

References and Further Reading

• Atlassian — Capacity planning- Google re:Work — Understand team effectiveness- Project Management Institute — Resources and standards