Forge Academy: Campaign Review

A campaign review should explain what the team intended, what actually went live, how the audience responded and what happened after that response. Those are related questions, but they need different evidence. Bringing them together gives the team a reasoned basis for its next commitment of time and budget.

This lesson is a practical retrospective for a group of Forge publications that your team treats as a campaign. It uses documented information from Content Plan, Content History and Performance alongside your own brief and verified business records. “Campaign review” describes the team activity; it does not imply a named Campaign Review tab or native CRM reporting.

Bring the original commitment into the room

Start with the brief that existed before publication. It should identify the offer, intended audience, buying problem, evidence, next action, campaign period and success criteria. If a campaign began without those decisions, acknowledge the gap. Write down what can still be assessed rather than inventing an objective that makes the results look successful.

A useful review group includes someone who understands the offer, someone who operated the publishing work and someone who can verify the commercial follow-up. In a small team, one person may cover several roles. The point is to make sure each type of evidence has an accountable owner.

Ask each participant to bring facts rather than a prepared verdict. The operator brings publication references and exceptions. The offer owner brings changes to scope or proof. The commercial owner brings verified enquiries and their status. Personal opinions about the writing can be discussed, but should not replace the evidence.

Prepare one review pack

Use a short document or spreadsheet maintained by the team. Include the original brief, the selected post references, a delivery summary, comparable metrics where available and a separate record of qualified next actions. This is a proposed review pack, not an additional Forge feature.

Check scheduled activity in Content Plan and publication outcomes in Content History. Use Performance only for the metrics supported by the connected account and format. The Forge User Guide explains these areas and their limitations. If a result was checked on the destination platform or in another system, label the source.

Include relevant operational conditions: an offer change, a delayed approval, an unavailable image, a connection problem or a revised destination page. These conditions help explain why planned and actual work differed. Avoid reconstructing the campaign solely from the posts that performed well.

Run a focused 45-minute discussion

The following agenda is a suggested facilitation pattern. It assigns time to the questions that often become mixed together.

Time	Question	Required output
5 minutes	What did we intend?	A shared statement of the original audience, offer and next action
10 minutes	What did we deliver?	A reconciled account of planned, published and withheld work
10 minutes	What response is supported by evidence?	Observations with sources, time windows and missing data marked
10 minutes	What happened commercially?	Verified next actions, qualification outcomes and follow-up gaps
10 minutes	What do we commit to next?	Decisions, owners, conditions and a review date

Keep the distinction between observation and explanation visible. “The finance message received fewer impressions” is an observation if the data supports it. “Finance buyers are not interested” is an interpretation that needs more evidence. When participants disagree, write the competing explanations and identify what would help distinguish them.

Reconcile delivery before judging effectiveness

Count the work in meaningful units. A planned Auto run, a generated draft, an approved message and a published post are different events. A campaign can generate its intended drafts and still fail to publish enough suitable content. Conversely, withholding an inaccurate draft can be the correct editorial decision.

For each missing publication, identify the reason and its operational owner. If the reviewer had no capacity, changing the buyer description will not solve the delivery problem. If the Node repeatedly produced unsupported claims, adding schedule slots will not solve the input problem. If the destination was wrong, the next action concerns the linked surface or credential.

Use the content governance guide when responsibility is unclear. The review should produce a correction the team can perform, not a general instruction to “improve execution”.

Read a hypothetical campaign without overstating the result

Imagine a fictional stock-count readiness assessment aimed at warehouse operations managers and finance managers. The campaign ran for 4 weeks and planned 8 publications. Its next action was a suitability discussion about the assessment. The following figures are illustrative teaching data, not Forge customer results.

• 7 posts were published: 4 addressed operations questions and 3 addressed finance questions.
• 1 planned finance post was withheld because its offer wording needed correction.
• The available supported-post records showed 84 link clicks.
• A separate enquiry log contained 6 enquiries during the period.
• The commercial owner verified that 3 enquiries met the agreed suitability criteria; 2 discussions were booked and 1 was awaiting a reply.

The review can establish that the team published 7 of the 8 planned posts and that 3 of the 6 logged enquiries met its criteria. It cannot assume that all 6 enquiries came from Forge content, or divide 6 by 84 and call the result a valid conversion rate without matching the underlying events and tracking method.

It also cannot compare the operations and finance audiences as if delivery were equal. The finance sequence contained one fewer publication, and the withheld message may have addressed a different buying question. A sensible next step might be to repair the finance offer wording, complete the missing explanation and improve enquiry-source recording before deciding to reduce that audience's coverage.

Separate message weakness from follow-up weakness

For the verified enquiries, review the next step promised by the content and the action actually provided. Was the linked page relevant? Could a buyer request the advertised discussion? Did the responsible person reply? Was the offer suitable for the people who responded?

If readers repeatedly ask for a service you do not provide, the message or audience may be wrong. If suitable enquiries wait without a response, there is a follow-up problem even if the content worked as intended. If the form provides too little information to assess suitability, the qualification process needs attention.

Record those findings in the systems where your business manages them. Do not assume a native Forge CRM connection, automatic lead scoring or sales attribution. The analytics and reporting guide helps maintain the boundary between publication metrics and other business evidence.

Make decisions that survive the meeting

End with a short decision record. For each decision, state the evidence, the action, the owner, the due date and what will be checked next. “Refresh the evidence for the assessment deliverable before the next finance post” is actionable. “Do more thought leadership” leaves the work undefined.

Useful decisions include retaining a well-supported angle, revising an unclear offer, investigating a missing measurement, reducing a schedule to match review capacity or retiring a proof item that is no longer valid. Some decisions belong in the Node; others belong in the publishing plan or commercial process.

Update source information through the Knowledge Base Setup workflow and adjust cadence using the content calendar guide. Use the weekly Performance Loop to monitor the narrower changes between campaign reviews.

A review is complete when the team knows what it will do next and why. It need not end with a claim that the campaign caused growth. Open Forge to assemble the publication evidence, and request a demo focused on your campaign review workflow if you need help defining the handoffs. The platform overview explains where Forge fits in that operating model.