How to build a programmatic advertising skills forecast for your team

Start with observable work, not employee labels

A reliable comparison starts with campaign tasks, not employee labels. Weak version: Set job titles and headcount first, then assume the people cover the work. The document may look complete while hiding task ownership, competence gaps and places where the team needs more capacity.

Better version: Begin with the campaign sequence: brief interpretation, audience design, deal setup, pacing checks and billing reconciliation. Assign a named owner and a written competence level to each task. A wider market outlook can inform the planning horizon, but the forecast still needs to describe the team's own work.

Weak version: Treat a team of five as if everyone covers every task equally. Without recorded competence levels, a missing capability can look like a personality issue, and the team cannot see whether a task has a capable owner or merely someone assigned to it.

Better version: Record what level of competence each task requires and who can perform it. The Back to Basics Guide to Programmatic from IAB UK describes foundational tasks a junior should manage unaided. That gives the team a concrete point of comparison when it decides where support or development is needed.

Keep capability and demand on separate scales

Two separate scores make a forecast useful: current team strength and demand twelve months ahead. Weak version: Combine them into one rating or let current client pressure decide the rank.

Either method can hide a strong capability with little demand, or an urgent future gap that has not yet caused a complaint.

Better version: Score each skill from 1 to 5 for current strength and expected demand in 12 months. Rank the gap using the difference between those scores, rather than smoothing both judgements into a single average.

Weak version: Give a skill a moderate combined score and assume it can wait. Averaging obscures whether the team is strong in a capability that is unlikely to be needed, or weak in one clients are likely to require.

Better version: A skill rated 4 for strength and 2 for demand can wait. A skill rated 2 for strength and 5 for demand belongs near the top of the action list, even if a live client complaint seems more pressing today.

Name a response for each exposed gap

A gap becomes manageable when the forecast names one response, rather than recording a general concern. Weak version: Write that the team needs to improve, without deciding whether the capability will be built, bought, borrowed or removed from the offer.

The issue stays open, with no priced or owned next step.

Better version: Choose whether to hire, train, contract or drop the service, and record the reason for that choice. Hiring can be slow and expensive, while training takes calendar time and contracting can cover a peak without a permanent cost. Each option answers a different kind of gap.

Weak version: Keep selling a capability that the team cannot staff, hoping to solve the shortfall after a client commits. That leaves the client relationship exposed and makes the forecast less useful as a decision record.

Better version: Treat dropping a service as a legitimate outcome. If the team cannot provide a capability, deciding not to sell it can protect the client relationship. For work involving data handling, consent or data protection principles, the ICO guidance on business-to-business marketing sets out rules staff need before working unsupervised.

Put a cost beside every proposed action

Affordability belongs beside each proposed action, because an unpriced plan cannot be tested against the annual skills budget. Weak version: Collect attractive ambitions, approve the page, then discover that nobody assigned costs before budget sign-off. The gap between intent and spend remains invisible.

Better version: Estimate the cost of each response. A contract specialist covering reporting at £400 a month would cost £4,800 a year. Keep that labelled as an illustrative figure, not a market rate, so nobody mistakes the example for a general price.

Weak version: Spread the available money thinly across every action, even when the combined estimate is above the agreed amount. This can leave every gap partly addressed without making clear which capabilities the team will actually secure.

Better version: Set a total annual skills budget, rank the responses and compare their combined cost with that limit. If the estimate is too high, remove actions from the bottom of the ranking instead of reducing the funding for each one indiscriminately.

Make ethics and sustainability practical

Ethics and sustainability need a defined place in the skills decision, rather than vague pitch language. Weak version: Mention them as broad values without asking whether staff can handle the related wording or consent questions. That leaves the capability unspecified and difficult to plan for.

Better version: Where ethics and sustainability language appears in pitches, identify the knowledge staff need to support it. The Sustainable Marketing Hub from CIM is a reasonable starting point for client-facing wording, and the government Green Claims Code is another reference when considering sustainability wording.

Use events to reopen the forecast

A review date alone is not enough; event triggers keep the forecast connected to changes in the agency. Weak version: Save the document for a yearly check, even when client mix, platform rules or staffing shifts earlier. The recorded picture may already be stale by the time anyone reopens it.

Better version: Name the events that require a review, such as two client wins in a new sector, a platform rule change, a senior departure or a decision to close a service line. The risk scenarios for English agencies offer a way to consider demand shocks before they arrive.

Weak version: Add review triggers to a note but leave the timing vague. Without an owner or calendar entry, a useful warning can pass without prompting anyone to reconsider the team plan.

Better version: Review the forecast twice a year as a workable rhythm for most agencies, with an additional review when a named trigger fires. The event matters more than the date alone, because it signals a change that may affect what the team needs.

Leave a record the team can operate

A working record should expose task coverage, scoring, selected action, ownership and cost in one place. Weak version: Keep those decisions across notes and conversations, so leadership cannot tell what is funded or who must follow up. The record cannot reliably guide action.

Weak version: Let a shared document belong to everyone, or ask finance to own the operational decisions. The work can then lose a clear maintainer, while proposed actions may lack the cost input needed for approval.

Better version: Give ownership to the operations or delivery lead, with finance input on costs. One named owner prevents the document becoming a shared file nobody maintains. Even a small agency should score its gaps: for a team of five, the exercise takes under an hour.

Weak version: Treat the forecast as the training plan, or assume that listing a gap is enough to close it. The need is recorded, but no sequence for addressing it is established.

Better version: Use the forecast to feed a training plan, which sequences how the gaps will be closed over the year. Keep the estimate focused on capabilities, actions, named owners, costs and review points so the team can return to it and decide what to do next.