
Campaign management connects these parts. Before making more assets, agree the outcome, message, destinations and responsibilities that will make the launch work as one plan.
Choose the outcome before the channel list
Describe what the launch is meant to support. Is the priority to introduce a new offer, bring people to an event or generate suitable enquiries? Choose a main outcome and define the action that would provide useful evidence of progress.
Reach, clicks, enquiries and sales describe different things. Decide which matters to the brief and how it will be recorded. Do not use an easily available number as a substitute for the actual goal.
Write down the audience, the offer and the reason to act. If those are unclear, opening more channels usually creates more versions of the same unanswered question.
Create one brief that every channel can use
A shared brief should contain the main message, supporting facts, intended action, key dates and constraints. Include the people who supply information and the person who can approve it.
Asana's creative-brief guidance brings objectives, audience, messaging, deliverables, stakeholders and distribution into the same planning document. The useful principle is simple: the work needs a common reference before different people start producing it.
Adapt the expression to the placement. An email can explain more than a short social post. A landing page can answer questions that an ad only introduces. Keep the offer and facts consistent without forcing identical copy into every format.
Give each channel a job
List the channels you can realistically prepare and maintain. For each, record the audience, message, format, destination and owner. Leave out a channel if there is no clear reason to use it.
A social announcement might introduce the launch. An email might explain it to an existing audience. A landing page might carry the detail and enquiry route. These are possible roles, not a requirement for every campaign.
Map the connections. If a post leads to a page, that page needs to be ready before the post goes out. If a response needs a call back, the person handling it needs the offer details and an agreed process.
Build the schedule around dependencies
Work back from the launch date. Identify content deadlines, asset production, approvals, destination checks and any outside requirements. Give each task an owner and allow time for corrections.
Mark what blocks something else. Product facts may be needed before copy; approved copy before final artwork; a working destination before distribution. A date on a calendar does not remove those dependencies.
Keep the approved version easy to identify. When a price, date or offer changes, update every affected asset and tell the people using it. Record the change rather than assuming a new message in a group chat will reach everyone.
Check the whole journey before release
Review the actual exported assets and live destinations at the sizes people will use. Check names, dates, links, legibility, form behaviour and confirmation messages. Make sure different channels describe the same offer.
Where measurement is part of the scope, agree how visits and useful actions will be identified. Test the setup before relying on its reports. A tag being present is not, by itself, proof that the intended action is being measured correctly.
Separate creative approval from spending approval. Record any media budget, production costs and paid tools, with clear limits and a person authorised to approve changes. Campaign access should not be treated as permission to increase spend.

Plan the response and the review
Decide who monitors questions and enquiries after release. Keep a route for correcting an error, pausing an asset or escalating a problem. The launch plan should continue beyond the moment something is posted.
Choose when to review the evidence and what decision that review will support. Early activity can reveal a broken link or a confusing question; it is not automatically enough to judge the full commercial result.
House813's work includes campaign management alongside creative, marketing and digital design. Bring the outcome, audience, offer, launch window and available assets to the first discussion. Explore House813 and share what needs to come together for your launch.
Next: Technical solutions: defining an integration or automation project →