How to build a digital PR skills forecast

What to take away

A digital PR skills forecast covers the capabilities your team will need over a set period, tied to named sources rather than opinion.
Start with the skills your current client work already demands, then map each one to a source you can cite.
Treat AI literacy as a content and standards question, using BSI guidance and Pew Research data on public attitudes.
Write down what would change your mind, so the forecast can be revised rather than abandoned.

A digital PR skills forecast is a documented estimate of the capabilities a team will need to deliver outreach, coverage and reporting over a defined period. Each line should point to a source, a date and an owner.

Start with the work you already sell. Look at the last two quarters of briefs and note the recurring tasks: data sourcing, journalist outreach, disclosure checks, reporting. Those are your baseline.

Map each skill to a named source

Every forecast line needs evidence behind it. For strategy claims about how the discipline is changing, practitioner commentary from the Chartered Institute of Marketing articles and reports is a reasonable starting point. Note the date and write the claim in your own words.

Skill to source mapping

Strategy claims

Source: CIM articles
What it covers: Discipline change
Date needed: Yes

AI standards

Source: BSI guidance
What it covers: Good practice
Date needed: Yes

Public attitudes

Source: Pew Research
What it covers: Audience acceptance
Date needed: Wave date

For AI-related skills, split the question in two. The first is standards: what good practice looks like when AI tools touch content and marketing work. BSI guidance on artificial intelligence is the right reference, and it is written for organisations rather than vendors.

The second is public attitudes. If your forecast assumes audiences accept AI-assisted content, test that against evidence. Pew Research Centre data on artificial intelligence publishes ongoing survey work, and figures move between waves, so cite the wave you read with its date.

If you are still deciding which capabilities matter most, use recurring tasks in recent client briefs to set the demand picture this forecast should sit inside.

Separate durable skills from tool skills

Tool skills age quickly. Platform interfaces change, and a forecast built around one dashboard needs rewriting within months. Durable skills hold up better: source verification, disclosure judgement, plain-English reporting, and explaining a method to a sceptical client. They also transfer between clients and sectors without retraining.

Durable vs short-life skills

Durable skills

Examples: Source verification
Review window: Longer
Budget: Training budget
Transferability: Across clients

Short-life tool skills

Examples: Dashboard operation
Review window: Shorter
Budget: Tool budget
Transferability: Limited

For each line, ask whether the skill survives a change of tool. If it does not, mark it as short-life and give it a shorter review window. The marker also shows which budget should pay, and it keeps the plan honest about what is transferable. Two or three short-life lines are manageable. A page of them is not.

If you are weighing where to spend on capability, use the durable-versus-short-life distinction to show which training needs a longer-term commitment.

Set owners, dates and triggers

A forecast without an owner is a document nobody reads. Give each line a named person, a review date and a trigger for early revision, such as a new client brief requiring a skill you lack.

Keep the document to one page per quarter, because long forecasts get ignored and the value comes from the review cycle. Date each line, since a claim without a date cannot be checked later.

Checklist

A one-sentence definition of what the forecast covers and the period it runs to.
A baseline list of skills drawn from the last two quarters of actual briefs.
A named source and date for every external claim.
A split between durable skills and short-life tool skills.
One owner and one review date per line.
Two written triggers that would force an early revision.
A note on how AI-assisted content is checked before it reaches a journalist.

Common questions

How often should a digital PR skills forecast be reviewed?

Quarterly is a workable default for most teams. Review sooner if a client brief demands a capability you do not hold, or if the standards guidance underpinning a line changes.

Do I need AI skills in every digital PR role?

No. The realistic split is broad literacy for everyone who touches content, and deeper review responsibility for one or two people. BSI guidance is a sensible shared reference.

Can I build a forecast without paid data?

Yes, for a first version. Government statistics, regulator publications and standards bodies publish free material. What you cannot skip is naming the source and its date.

What makes a forecast line weak?

A line with no owner, no date and no source. If nobody can check the claim later, it is an opinion dressed as a plan.