Outbound resource
Cold email campaign brief template
A campaign can have a researched list and finished copy while nobody knows which version is approved or who will handle replies. Use this brief to connect those decisions before activation. It is a team handover document: the linked ICP, infrastructure and message resources contain the detailed checks.
Editorial update:
Copy the campaign brief and launch decision
Original planning conventions, not a proven performance formula or permission to send. Replace brackets, link the actual reviewed versions and assign real owners. A completed document does not certify legal compliance or inbox placement.
1. Campaign brief
Campaign / version / date: [reference] Business owner and operator: [people] Audience hypothesis: [account type, role, supported market] ICP and exclusions: [versioned record] List source and review: [source, date, reviewer, unresolved issues] Offer and supported capability: [approved facts] Reason this audience may find it relevant: [evidence or labeled hypothesis] Message and sequence version: [link to reviewed copy and steps] Requested next step: [one clear action] Sending configuration evidence: [infrastructure review reference] Recipient eligibility and provider-policy review: [owner, evidence, unresolved issues] Suppression and duplicate checks: [record and date] Reply owner and backup: [people, coverage] Booking / handoff destination: [tested path] Measurement definitions and review date: [record] Open blockers: [issue, owner, next check]
2. Launch decision record
Campaign version reviewed: [reference] Audience/list version: [reference] Copy/sequence version: [reference] Configuration reviewed at: [timestamp and evidence] Checks complete: [links to evidence] Decision: [approved for stated scope / hold / rejected] Approved scope: [audience, dates, sender configuration] Reason and unresolved blockers: [details] Decision owner and date: [person, timestamp] Activation operator: [person] Pause owner and conditions: [person, observed conditions] Next review: [date and owner] Change requiring another review: [audience / copy / sender / routing / other]
3. First review and change log
Campaign version / observation window: [reference, dates] Delivery or workflow problems observed: [facts, not guesses] Replies needing action: [internal references and owners] Booked / held / accepted outcomes: [separate counts and definitions] Pending outcomes: [count and observation date] Evidence limitation: [missing data, small sample, tracking gaps] Decision: [continue within scope / pause / revise] Change proposed and reason: [specific change, evidence] New version and reviewer: [reference, person] Next action and due date: [owner, date]
- Copyable worksheets
- 3
- Versioned decision
- 1
- Use immediately
- No gate
What belongs in the brief versus a supporting record
Scroll the table sideways to compare all columns.
| Decision | Keep in the brief | Link to supporting evidence |
|---|---|---|
| Who is included? | Audience, exclusions and list version | ICP criteria and account research |
| What will they receive? | Approved offer, message and sequence version | Exact copy and factual review |
| Is the sending path ready? | Review owner, outcome and open blockers | Infrastructure evidence and applicable provider requirements |
| Who handles responses? | Reply owner, backup and handoff destination | Routing rules and qualification checklist |
| Can this version launch? | Named decision, scope and activation owner | Completed checks and unresolved issues |
| When should it change? | Pause conditions and review date | Observed delivery, reply and meeting records |
Freeze the scope before reviewing
Give the audience list, message and configuration identifiable versions. An approval for one segment does not silently cover another market or an expanded list. Keep links readable by the people doing the review. If an important field is unknown, record the owner and next check rather than filling it with a plausible guess.
Check the actual campaign configuration
Compare the intended sequence with the configuration in the sending tool: sender identity, steps, schedule, personalization fields and destinations. Apollo's sequence documentation is one example of a vendor-specific setup workflow; verify the tool and account you actually use. An approved draft in a document is not evidence that the same version is configured for activation.
Review replies and handoff before activation
Name who reads responses, who covers absence and how a scheduling request reaches the receiving sales owner. Confirm the booking destination works and the team can find the relevant account context. Use the reply-handling resource for response categories and stop requests. This brief does not configure any sending, calendar or CRM automation.
Define observable pause conditions
Examples include a broken booking destination, messages reaching excluded contacts, unresolved sender errors or replies without an owner. Set operational thresholds from your own policy and provider requirements; this template does not invent a universally safe sending rate. When a condition occurs, identify the affected scope, pause as appropriate and assign a check before resuming.
Worked example: the message changed after approval
Fictional example: a team approves a campaign offering a sample dispatch-workflow worksheet to operations managers. Before activation, someone replaces that offer with a claim about a live integration. The operator finds that the claim has no supporting product evidence. The team marks the revised version on hold, restores the approved factual offer or obtains evidence for a new review, and records which version may proceed. The earlier sign-off is not treated as approval for the unsupported promise.
Evaluate outcomes without inventing a winner
Agree the observation window and definitions before launch. Keep reply activity separate from unique prospects and booked meetings separate from held or accepted meetings. If only a few outcomes exist, report the counts and uncertainty instead of declaring the campaign a winner. Use the reporting worksheet for cohort reconciliation; this brief records who will review it and what decision follows.
Who this helps
- Founders approving an outbound pilot
- Campaign operators handing work between teammates
- Agencies aligning a client and delivery owner
Work through the process
- 01
Assemble
Link the audience, copy and configuration evidence.
- 02
Resolve
Assign unknowns and blockers to named owners.
- 03
Decide
Record the approved version and scope before activation.
- 04
Review
Inspect observed outcomes and record the next version or pause.
Questions and answers
- How is this different from an infrastructure checklist?
- The infrastructure checklist examines the technical sending path. This brief links that result to the audience, message, operational ownership and launch decision. It does not replace the technical checks.
- Does approval mean the campaign is safe to send?
- Approval here is an internal operational decision for a stated scope. Recipient eligibility, applicable requirements and provider policies still need appropriate review. Authentication or a signed brief cannot guarantee delivery or results.
- Should a copy change require another review?
- Recheck any change that alters claims, audience expectations, destinations or approved scope. Record the new version and decision so the operator does not have to infer whether old approval applies.
- Does this template send emails?
- No. It is a copyable planning document. Your team remains responsible for configuration, authorization, activation and handling replies.
Sources and editorial notes
Original AI-assisted editorial templates and planning conventions prepared for LeadFlow. Examples are illustrative; they are not independently tested results, customer evidence or performance benchmarks. Check facts and adapt the material to your own workflow before use.
Keep reading
Cold Email Outreach
Managed cold email outreach with account research, email infrastructure, reviewed copy and reply handling. Compare scope, cost drivers and launch checks.
Cold Email Infrastructure Checklist
Audit sending ownership, authentication, recipient handling and monitoring with a five-stage checklist, evidence log and copyable handover template.
Ideal customer profile template
Copy three B2B ICP worksheets: segment criteria, account evidence and list acceptance. Includes a worked example, review rules and an AI checking prompt.
SaaS cold email templates
Adapt three SaaS cold email templates with a factual-review worksheet, a worked example and an AI prompt. Check product claims before sending.
Cold email reply templates
Use five cold email reply templates with stop-request checks, ambiguous-reply routing and clear ownership for interested, referral, pricing and not-now responses.
Outbound campaign report template
Copy separate weekly activity and cohort reporting worksheets, reconcile CRM exports and check outbound reply and meeting rates with a worked example.