Social recruitment campaign brief template: from role facts to approved creative

A social recruitment campaign brief connects one approved hiring need to the message, supporting evidence, creative assets and application destination. It gives the creative and delivery teams the same source of truth, so automation does not turn an incomplete job brief into a misleading campaign.

Use the template below before someone writes the first headline or selects an image. It is a copyable working brief for one campaign, with a place for the facts, the proof and the person who can approve each part. Its purpose is to make the handoff clear enough that the receiving team can explain what it is producing and why.

Key facts

• Begin with an approved role, its job ID and a valid application destination.
• Connect each proposed message to a role fact, approved asset or attributable statement.
• Give the creative team named owners, requested placements and a version to work from.
• Hold unsupported claims until their owner supplies evidence; do not fill gaps with plausible promises.
• Approve the message and the candidate journey together, then record later changes.

What information should the brief begin with?

Name the vacancy or role family and record the job ID that connects it to the recruiting system. Add the location, work pattern and genuine requirements from the approved role information. If the brief covers a role family, make clear which facts apply across it and which need confirmation for an individual vacancy.

Write down the candidate question the campaign needs to answer. Keep the audience situation grounded in relevant role context: what someone needs to understand about the work, its requirements and the next step. This is not an instruction to use sensitive or prohibited targeting. A message brief does not establish which targeting options a delivery team may use.

State the intended action and include the application destination. The team should be able to follow the link back to the same role and job ID. A destination is part of the brief, not a detail to resolve after the creative has been signed off. If the route is undecided, show that as an unresolved item with a named owner.

How should the message and proof be connected?

Use this social recruitment campaign brief template to connect the proposed message to its evidence and approval responsibility. Copy it into your working document and fill the cells with actual information. The headings organise the decision; they do not supply facts about your employer.

Brief field	Supplied information	Approval responsibility
Role and destination	Job ID, location and valid application route	Recruitment owner
Candidate question	What someone needs to understand about this role	Recruitment and marketing
Message	One truthful reason to consider the vacancy	Employer or client approver
Proof	Approved role fact, asset or attributable statement	Evidence owner
Creative handoff	Assets, requested placements and version	Creative owner
Launch readiness	Approved copy and tested mobile-to-ATS route	Delivery and recruitment operations

For each proposed reason to consider the vacancy, identify the approved source that supports it. A role description can establish a job fact. An approved asset can show the work or setting it actually depicts. An employee statement needs an attributable source and permission for the proposed use. Do not treat those different kinds of support as interchangeable.

Check the wording against the evidence, including any conditions or limits. If the proposed message promises more than the source establishes, narrow the message or remove it. A benefit that sounds credible is still unverified when nobody can point to its support. Never invent a testimonial, career promise or performance claim to complete a blank cell.

Keep the source reference alongside the proposed wording so the approver can assess both together. The creative team should not have to guess whether a statement was checked, copied from an old campaign or written as an aspiration. An empty proof field is a visible decision to resolve before production.

What belongs in the production handoff?

List the approved assets and requested placements, then name the formats the team needs to produce. Ask the delivery team to verify the current requirements for those placements before production. Do not copy an assumed character limit or image dimension into the brief and present it as a verified platform requirement.

Identify the asset version, where the current file can be found and the documented permission for its intended use. Keep proposed assets separate from assets that are ready to publish. A picture being available in a shared folder does not, by itself, answer whether the employer has approved it for this campaign.

Name the creative owner and the person who can approve the resulting copy and visual. Include the application destination in the same handoff. That gives the receiving team one version of the message, evidence and route to check, rather than a set of disconnected files whose status is unclear.

Record open questions explicitly. If the requested placement needs an adaptation, the production team can bring that change back against the approved message. Adaptation should preserve what the source supports. It should not introduce a stronger benefit or remove a condition simply to make the creative shorter.

How should a brief be approved?

Review the brief with the people responsible for the role facts, evidence, creative and application route. Each owner should confirm their part against the version being approved. A general comment that the campaign looks good does not resolve a missing job detail or an unsupported statement.

Use a clear approval sequence:

1. Confirm that the role information and job ID are current and refer to the intended vacancy.
2. Check that the message stays within the supporting evidence and any usage permission.
3. Review the creative against that message, including the relationship between the image and copy.
4. Test the application destination and confirm the handoff with recruitment operations.
5. Record the approved version, owners and any unresolved conditions before launch.

Freeze the version that passes those checks. If a fact, asset or destination changes later, log what changed and return the affected part to its owner. Keeping an approval record does not mean a later version is automatically approved. The record should make the difference between the launch version and the proposed revision clear.

Missing proof is a hold. It is not an invitation for the executor to write something that sounds likely. The same discipline applies when the deadline is close: the brief should show the unresolved decision instead of concealing it in polished copy.

What does a filled brief look like?

Fictional brief exercise: a role description confirms an employer-provided training programme but does not establish rapid promotion. Approve a message about the actual training and link to its approved explanation; exclude a guaranteed-career-growth claim. The receiving team uses the supplied job ID and checks the application destination. This is an example of claim control, not a statement about an Adway customer or a current vacancy.

The confirmed fact is the training programme. The unsupported promise is guaranteed career growth. The editorial choice is to describe the training that the source establishes and leave the promotion promise out. An approver cannot turn the second statement into evidence merely by liking the wording.

In the filled brief, the proof entry points to the approved training explanation, while the message entry stays within that explanation. The creative owner receives the approved wording and assets with their version. The recruitment owner remains responsible for the role information rather than passing that responsibility to the designer.

Close the exercise by following the supplied application route. Check that it leads to the intended role and that the receiving team can connect the application to the supplied job ID. If that check fails, record the issue before launch. Correct copy alone does not complete the handoff when its destination points somewhere else.

How does the brief connect to campaign automation?

The brief defines the inputs that the campaign workflow will use. The existing recruitment marketing automation guide explains the wider launch workflow. Keep that implementation discussion connected to the brief without asking the brief to become a second technical setup guide.

Adway describes Always-On Job Ads as turning vacancy information into social recruitment campaigns. That is a supplier description of the workflow, not evidence that an incomplete input will become accurate or that an unapproved claim will be detected. Responsibility for the supplied role facts and message remains explicit.

Bring the approved brief to a product demonstration and follow its role, message and destination through the proposed implementation. Use the version and owner fields to make the discussion concrete. The demonstration should establish how your supplied inputs will be handled; it does not replace the approvals recorded in the brief.

Book a demo to walk through one approved role, its application journey and the handoff to your recruiting system.

Sources

• Always-On Job Ads: Adway’s first-party description of the vacancy-to-campaign workflow, checked on 13 November 2026.
• Recruitment marketing automation guide: the existing guide to the wider launch workflow.

The template and fictional training example are Adway editorial proposals. They are not customer results, industry benchmarks or a current vacancy advertisement.

Start with one role. Verify the whole journey.