Back to all articlesCampaign briefs

Match the campaign promise to fulfilment capacity

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A campaign promising a completed service creates an operational obligation, not just an attractive message. If the brief leaves accepted volume, delivery scope or the start of the delivery clock undefined, approval can authorise more work than the business can complete.

The practical task is to connect each accepted customer to the work required, reserve capacity for every included stage and check that those stages can happen in order. Aggregate hours alone cannot establish deadline feasibility.

The filled worksheet below shows how to make that decision. It budgets two possible repeat reviews per customer: one after internal findings are corrected, and another after customer factual corrections. That distinction changes the acceptance ceiling.

1. Translate the headline into obligations

Start with what a reasonable recipient will understand. An offer of priority setup might imply configuration, data cleanup, training and support even if the campaign team intended only a checklist.

Write the commitment in this form:

For each accepted customer, we will deliver [defined output] by [date or defined turnaround], provided [customer requirements], up to [acceptance limit].

Identify preparation, quality checks, handover, corrections and customer dependencies. For each activity, record what capacity it consumes and what must happen first. Include internal correction work even when customers never see it.

Define acceptance separately from interest. A submission need not create a delivery commitment, but wording that suggests submitting secures a place can create that expectation. The public message and internal acceptance process must describe the same event. Material conditions belong before the customer acts, not in a later clarification.

2. Count every review cycle before calculating the ceiling

Use an accepted commitment as the unit of demand. For each stage, subtract existing obligations and protected contingency from available capacity, then divide by the requirement per accepted customer. Round down.

The smallest stage ceiling governs. Preparation hours cannot compensate for missing review slots. Keep units separate and avoid counting the same person's time in overlapping allocations.

Review demand depends on the workflow. If corrected material must pass review before handover, and customers can subsequently request factual corrections, one repeat-review slot per customer is insufficient. Reserve both cycles unless the offer explicitly uses a different review model.

Correction production and correction review are also separate demands. An allowance for editing does not provide reviewer availability. Describe what each reserve covers, then test the sequence: preparation, initial review, internal fixes, pre-handover approval, handover, customer corrections and final approval.

Run a cautious case. A calculated ceiling remains provisional until capacity owners confirm both quantities and dates.

3. Filled worksheet: scope, capacity and acceptance limit

Fictional worked example: All business details, dates, quantities and durations in this worksheet are hypothetical planning assumptions, not Alactic customer results or benchmarks. Reuse the field labels, replacing the entries with confirmed information.

Offer and acceptance record

  • Original proposal: Accept 20 customers and promise a tailored onboarding pack within five business days.
  • Replacement commitment: Remove the five-business-day claim. Offer a fixed batch with final delivery by 17:00 on 16 October 2026, Europe/London time.
  • Included output: One onboarding checklist, one responsibility map and a 30-minute handover allocation covering the call and associated notes.
  • Quality model: Initial review, correction of internal findings and a repeat review before handover; then one customer factual-correction round with a further review if changes are made.
  • Scope boundary: New workflows, additional requirements and further customer revision rounds require a separate scope decision. Internal defects are not reclassified as paid additions.
  • Intake cutoff: Complete standard intake by 17:00 on 2 October 2026, Europe/London time.
  • Commitment event: Written acceptance issued by the fulfilment lead on 5 October, after intake, scope and capacity checks. Submission alone does not secure a place.

Capacity calculation

These allocations do not overlap. Preparation excludes handover and review. Review slots have sufficient duration for the defined pack; that assumption must be confirmed before release.

  • Initial preparation: 40 hours available, less 12 hours of existing obligations and 8 protected hours for corrections and uncertainty, leaves 20 hours. At 2 hours per customer, the normal ceiling is 10.
  • Quality review: 16 slots available, less 2 for existing obligations, leaves 14. Reserve 3 slots per customer: initial review, post-internal-correction review and post-customer-correction review. The ceiling is 4 customers, consuming 12 slots and leaving 2 spare.
  • Handover: 6 hours available, less 1 hour of existing obligations and 1 contingency hour, leaves 4 hours. At 30 minutes per customer, the ceiling is 8.
  • Correction production: Allow up to 1 hour per customer for internal-review fixes and customer factual corrections combined, not 1 hour for each source. Four customers require 4 hours from the protected 8-hour pool.
  • Remaining uncertainty allowance: The other 4 protected hours cover unexpected preparation work or correction overruns. They are not additional initial-production capacity.

Worked result: Preparation supports 10 customers, review supports 4 and handover supports 8. The normal-case ceiling is therefore 4. Reserving only one repeat review would understate the promise's possible review demand.

Cautious case

  • Preparation: Reduce usable initial-work capacity to 16 hours and increase effort to 2.5 hours per customer. The ceiling is 6; four customers require 10 hours.
  • Review: Assume the 2 spare slots disappear. Preserve 4 initial reviews and 8 repeat reviews: enough for 4 customers, with no spare review capacity.
  • Handover: Reduce usable capacity to 3 hours. The ceiling is 6.
  • Corrections: Preserve all 8 protected production hours: 4 for combined corrections and 4 for uncertainty.
  • Decision: Four remains the provisional ceiling. Do not transfer protected correction hours or repeat-review slots to expand intake.

The correction estimate needs its own credibility check. Before release, the fulfilment lead must inspect the proposed intake and pack scope and confirm that both sources of corrections can reasonably fit within the combined one-hour allowance. If not, increase the allowance, narrow scope or reduce acceptance and recalculate.

4. Test the dates, not just the totals

The following hypothetical sequence uses Europe/London time throughout. It gives every customer at least 24 hours between the latest handover and the correction cutoff.

  • 5 October: Confirm reservations, issue written acceptances and book all handovers.
  • 6–8 October: Complete initial preparation. Reserve at least the cautious case's 10 production hours within this period.
  • 9 and 12 October: Complete four initial quality reviews and record findings.
  • 13 October: Correct internal findings, then complete up to four repeat reviews. Only packs that pass this review may proceed to handover.
  • 14 October, by 12:00: Complete all four handovers and provide the reviewed materials. Reserve two hours for the handover allocations before this deadline.
  • 15 October, by 12:00: Receive each customer's consolidated factual corrections, allowing at least 24 hours after handover.
  • 15 October, after 12:00, and 16 October: Produce customer corrections and complete up to four final repeat reviews.
  • 16 October, by 17:00: Deliver final reviewed files.

As a hypothetical scheduling allowance, reserve two correction-production hours on 13 October and two after the customer cutoff, plus the four uncertainty hours accessible across those periods. Confirm that production can finish before the corresponding review slots begin. A reviewer available only before changes are ready does not satisfy the plan.

If internal fixes need more than their scheduled allocation, use the uncertainty reserve only after checking its timing and the remaining workload. If pre-handover approval slips, hold the affected handover and reassess the commitment; do not send unapproved materials to preserve the appearance of progress.

Filled release decision

Status: Hold approval. Reject the 20-customer proposal; release a maximum of four places only after the fulfilment lead confirms the dated production hours, all 12 review slots, handover bookings, credible combined correction estimate and accessible uncertainty reserve.

Overflow: Additional requests may join an interest list without a delivery commitment. Under this proposed process, no payment is requested for an unconfirmed place.

5. Put the operational boundary into the customer promise

A narrower promise is useful only if recipients can understand it. The following is proposed wording for the fictional example, not a statement about an available Alactic service.

Four tailored onboarding pack places, with final delivery by 17:00 on 16 October 2026. All times are Europe/London.

Submit your complete intake by 17:00 on 2 October to request a place. We will confirm accepted places in writing on 5 October. Submission alone does not reserve a place.

Each confirmed place includes an onboarding checklist, responsibility map, handover call and one consolidated customer factual-correction round. Your handover will finish by 12:00 on 14 October. Send factual corrections by 12:00 on 15 October, giving you at least 24 hours after handover. New workflows and additional customer revision rounds are excluded. Requests received after the correction cutoff need a separate timing decision.

Before acceptance, explain how customers submit corrections and whom to contact if the booked handover is unsuitable. If the response interval is unrealistic for the intended customers, move the handovers earlier, extend the schedule or change the offer before release. Do not solve that dependency by silently shortening their review time.

6. Make the acceptance limit enforceable

Maintain one authoritative record containing the customer reference, intake status, scope decision, acceptance status, promised date and authorising person. Separate requested, awaiting information, accepted, completed and withdrawn states.

Only authorised people should confirm places. Stop confirmations when the remaining capacity cannot be established reliably. Any increase requires a fresh calculation across production, review, handover and corrections, followed by another dated dependency check.

This is a recommended operating design, not a claim that Alactic supplies a particular enforcement control. Check the workspace and current plan before relying on any software feature or permission. If the required capability is unavailable, retain a controlled shared record and explicit authorisation process.

Choose the smallest change that resolves the actual constraint. Fewer places address review scarcity; simpler deliverables may reduce production effort. A vague availability condition does neither unless someone records capacity and stops acceptance.

7. Keep channel readiness separate from fulfilment approval

Publication-ready copy does not establish fulfilment readiness, and reserved capacity does not establish messaging readiness.

For WhatsApp campaigns, check the current WhatsApp Business Messaging Policy. Recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Automation needs a clear human escalation path.

Keep campaign preparation, template review and actual delivery as separate states. Template approval does not guarantee delivery or validate the offer's capacity assumptions. Expected non-delivery is not a safe way to limit commitments; the acceptance process must do that.

8. Respond to shortfalls and learn from the batch

Pause new acceptance when reserved availability falls, effort rises materially or a dependency no longer fits the sequence. Identify the failing stage before choosing a remedy: extra preparation hours will not replace an unavailable reviewer.

A named decision-maker should reconcile existing promises, assess feasible alternatives and oversee customer communication. If the commitment cannot be met, explain the issue and seek agreement on an alternative rather than silently moving the deadline or dropping quality checks.

After completion, compare estimated and actual effort separately for preparation, internal fixes, customer corrections, each review cycle and handover. Record when each stage finished, whether the 24-hour response interval was usable and how much uncertainty capacity was consumed.

Also record borrowed capacity, overtime and skipped work. Delivery achieved through unplanned effort does not validate the original assumptions. The next worksheet should reflect the work the promise actually created.

Campaign planningFulfilment capacityCampaign briefsOperational readiness

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications