A corporate gift campaign can look affordable at the invitation stage and become difficult to fund or fulfill once recipients respond. A useful forecast follows each decision and operational handoff: invitations sent, invitations delivered, claims, completed recipient records, approved recipients, inventory accepted, and deliveries that actually succeed. This 2027 planning model lets your team enter its own assumptions, compare three scenarios, and expose the decisions hidden by a single “redemption rate.” Its numbers are illustrative inputs, not industry benchmarks or outcomes from Giftpack.
Download the calculator and define the forecast
Download the editable English forecasting workbook and, if you need the sample scenario rows in another analysis tool, download the English CSV export. The workbook is version 1.2, finalized October 9, 2026. The unchanged CSV remains version 1.1, exported October 9; its baseline scenario rows still match the version 1.2 workbook for 2027 planning. The workbook has eight sheets: Read Me, Inputs, Funnel Model, Scenarios, Capacity & Budget, Sensitivity, QA, and Methodology. Start with Inputs; the three scenario columns are editable. The CSV is a snapshot of the illustrated scenarios and will not change when you edit the workbook.
Model scope and limits
The model answers a planning question: given a defined population and a set of conditional rates, how many gifts might require approval, stock, labor, shipping, service, and funding? It is not a prediction of an individual recipient's behavior. Your team should replace every example rate with a documented assumption drawn from a comparable internal program, a small pilot, a contracted channel capacity, or a clearly labeled planning judgment. Record the source population, time window, campaign design, and owner next to the rate. A past claim rate from a different invitation channel or recipient relationship is a starting question, not a transferable fact.
Use the same denominator for every stage. A claim rate applies to delivered invitations, not sent invitations. An address completion rate applies to claims, not all invitees. An eligibility pass rate applies only after the fields needed for that check are complete. If recipients can decline, select a no-ship item, or choose a digital option, define how those outcomes enter the funnel before estimating stock. The model's inventory acceptance rate is a planning control for approved gifts that can actually be supplied, not permission to accept more claims than stock can support.
Funnel calculations: each rate uses the immediately preceding stage as its denominator.
| Planning output | Calculation | Owner and evidence |
|---|---|---|
| Delivered invitations | Invitations sent × deliverability rate | Campaign operations; channel test and suppression count |
| Claims | Delivered invitations × claim rate | Program owner; comparable cohort or pilot |
| Complete records | Claims × address or required-data completion rate | Recipient operations; completion policy and time window |
| Approved recipients | Complete records × eligibility pass rate | Policy owner; documented exclusions and review path |
| Fulfillments | Approved recipients × inventory acceptance rate | Supply chain; reserved sellable stock |
| Successful deliveries | Fulfillments × delivery success rate | Fulfillment owner; service-level and exception definition |
The outputs are expected values and can contain fractions. An operational purchase order, pick wave, support roster, or shipping batch needs an explicit rounding rule. Round only at the decision point: rounding every intermediate stage can compound error. If a gift is selected before address collection, the stock decision may precede a complete address; change the process map and validation evidence rather than pretending that the model's sequence describes your exact workflow.
Choose assumptions that a team can defend
Define the population first. “Ten thousand employees” can mean everyone in a directory, only eligible active employees, or the subset who will receive an invitation in the specified period. Export a deduplicated eligible count with a cut-off date and exclusions approved by the business owner. Keep the source record outside the public workbook. The workbook needs counts and rates, not names, addresses, or any recipient-level personal data. If a source roster changes during a long campaign, version the count and explain whether a new invitation wave is additive or a replacement.
Next choose the clock. A claim rate measured at seven days will usually be different from the rate at thirty days because a reminder or deadline changes opportunity to respond. The scenario's claim period should match the date on which procurement or logistics must commit. Label the invitation launch, response deadline, address deadline, procurement lock, and final delivery target. When stock has a lead time longer than the recipient response window, reserve a bounded amount early and schedule a second decision on actual claims. Do not quietly use a final campaign outcome to justify an earlier purchase.
Separate rates that describe behavior from rates that describe capacity. Recipients may or may not claim; that uncertainty belongs in the claim assumption. Eligibility, inventory acceptance, and delivery success depend on policy, stock, addresses, lanes, and exception handling. A global program should segment markets if one shared rate hides materially different deliverability, product availability, import processes, or recipient choices. Calculate segments with the same method, then sum comparable outputs. Do not average percentages from unequal groups and multiply by the whole population.
For each input, write an owner, source, observed period if any, rationale for low/base/high, and date for the next refresh. The low scenario should not simply be “everything goes badly” if a lower claim rate reduces budget but leaves a fixed production minimum. It is a coherent operating state. The high scenario should test volume and cost exposure together, including whether a response spike makes inventory or service capacity the binding constraint. If evidence for a rate is weak, widen the range and name the decision that would reduce uncertainty, such as a pilot, a supplier stock hold, or an invitation-domain test.
The versioned model provides a low/base/high comparison, not a statistical confidence interval. Without a representative dataset and a justified sampling design, labels such as “95% likely” would imply precision the inputs do not support. Finance can use the high case to set a commitment ceiling and the low case to examine stranded minimums. Procurement can ask for split orders; operations can set a response threshold that triggers more stock or staff.
Worked decision one: an addressless client campaign
Hypothetical case. A customer team wants to invite 10,000 client contacts without collecting shipping addresses until someone claims a gift. The sender has verified permission to contact the selected audience and defined a policy for which client roles are eligible. The campaign owner models the base case as 10,000 sent, 96% delivered, 50% of delivered invitations claimed, 90% of claims completing the required data, 98% passing eligibility, 96% supported by inventory, and 97% delivered successfully. These are deliberately illustrative inputs. They do not describe a Giftpack program or a market norm.
The base calculation produces 9,600 delivered invitations, 4,800 claims, 4,320 complete records, 4,233.6 expected approved recipients, 4,064.26 expected fulfillments, and 3,942.33 expected successful deliveries at two-decimal display precision. It would be a mistake to buy exactly 4,800 physical units because some claimants never complete an address and others do not qualify. It would also be a mistake to promise 4,064 deliveries without checking item choice, stock allocation, lane availability, and the time left before the deadline.
Here is the operational decision. Marketing owns the invitation population and channel test. The policy owner signs off on eligibility and gift value. Procurement asks suppliers for a staged allocation around the base case, with a written option to add stock if claims pass a measured threshold. Recipient operations monitors incomplete records and sends a clearly timed reminder that follows the approved communication policy. Finance reserves a ceiling that covers the high case and distinguishes cash committed now from spend conditional on a claim. The fulfillment team checks actual inventory before the offer is displayed, not after a recipient has selected an item.
Two alternatives deserve an explicit comparison. Pre-buying the full high-case volume can protect a hard delivery date but increases stranded inventory exposure if claims fall short. Waiting until every address is complete reduces pre-buy commitment but can fail a production lead time. A supplier stock hold or split production order may reduce both risks if its fee, release deadline, and cancellation terms are acceptable. Record the decision in a log: assumption version, supplier quote, release trigger, maximum liability, decision owner, and the date actual claims will replace the forecast.
An exception changes the forecast rather than disappearing from it. If a recipient opens the invitation but never submits an address, it remains a claim without a complete record under this model. If the person later opts for a digital reward, treat that as an approved branch with a different cost and fulfillment path, not as a failed delivery of a physical gift. If an address is rejected, decide whether one correction attempt belongs within the current delivery-success rate or creates a separate recovery budget. Acceptance evidence is a reconciled invitation count, a documented completion window, inventory hold confirmation, a cost ceiling, and a daily dashboard whose stage definitions match the workbook.
Worked decision two: a global employee choice program
Hypothetical case. A People team plans a choice-based recognition campaign for employees in several markets. The total eligible workforce is not a single homogeneous shipping population. Some markets support local merchandise, some have only selected digital options, and a few require extra employer review. The team can use a common funnel definition, but it should create a scenario per material market or product lane and aggregate expected volume only after classifying the lane. These are planning examples, not legal, payroll, tax, customs, or privacy advice.
Imagine that the global roster contains 10,000 eligible people, but the initial invitation wave reaches only a subset while employee records are reconciled. One region has a 98% delivery assumption and slower address completion because employees choose between home and office receipt. Another has a lower physical inventory acceptance rate because a preferred item cannot be replenished before the holiday. A third offers a digital reward that does not require a shipping address, so its “complete record” means the minimum information required to issue that reward. Applying one worldwide address-completion percentage would mix different journeys and distort both stock and support plans.
The People owner first approves eligibility, communications, value bands, and the recipient choices shown in each market. The local operations owner validates product availability, language, address format, and the last realistic delivery date. Finance maps unit costs and taxes to the appropriate internal budget accounts after its own review. Privacy and security owners decide what data a workflow may collect and retain; the forecasting workbook receives only aggregate assumptions. Procurement checks minimum order quantities and whether items can be substituted without changing what the invitation promised.
Consider a decision at the procurement lock. If claims in a market exceed the base path but one item is constrained, the team may narrow that choice for new recipients, seek approved equivalent stock, or extend only the affected lane's delivery promise. It should not silently count every claim as a successful fulfillment. If an eligibility review removes a group after invitations have been sent, keep those delivered invitations in the delivery count while lowering the approved share; record who owns a respectful recipient message. If a country lane becomes unavailable, pause that lane, preserve the other segments, and recalculate the total from the revised branches.
The high case is especially useful for support staffing. A large early claim wave may increase questions before it increases shipments. Model expected support cases from the applicable stage and local contact behavior, then compare that volume with staffed service capacity during the response window. A delayed physical delivery can require more service even if the number of successful deliveries eventually remains similar. The acceptance package should include market-specific assumption sheets or a controlled segment roll-up, confirmed local offer and fulfillment capacity, decision owners, a dated exception register, and a consolidated total with no double-counted employee.
Read the three scenarios without turning them into promises
The workbook's example rows produce 9,200, 9,600, and 9,800 delivered invitations for low, base, and high, respectively. Example claims are 3,220, 4,800, and 6,370; expected fulfillments are 2,202.48, 4,064.26, and 5,931.08 when shown to two decimals. The accompanying CSV exports these displayed values for a reader who wants to inspect them without opening a workbook. Replace the illustrative rates before making a commercial decision. A high claim rate does not improve delivery success automatically, and a low claim rate does not remove fixed fees.
Read each column as a chain of conditional assumptions. If the high scenario calls for more fulfillments than reserved stock, the team must decide whether to add inventory, constrain availability, substitute, or revise the promise. If the low scenario is below a supplier minimum, the cost of unused units belongs in the exposure analysis. A scenario that is attractive on average but breaches a hard launch date or budget ceiling is not acceptable. Mark the first stage where a constraint becomes binding so the response is operational rather than a vague request for “more buffer.”
Use sensitivity tests to find a decision threshold. Hold other assumptions constant and vary claim rate or address completion within a plausible range. Ask how many additional accepted orders, staffed support cases, and dollars of exposure a five-point change causes. The chart on the Sensitivity sheet is a visual aid to those input-driven changes; verify the axes and labels after you alter the model. For a global program, repeat the test on the segment whose capacity is genuinely constrained. A smooth total curve can hide a local warehouse or customs cutoff.
Convert volume into inventory, cost, and service commitments
Inventory reserve is not the same number as expected successful deliveries. Reserve policy may account for damaged goods, selection mix, exchange requirements, or a contractual safety quantity, while the fulfillment forecast traces eligible accepted orders. Enter reserve assumptions explicitly and check that a safety amount is not accidentally included twice in both a unit price and a quantity buffer. A reservation may be a cancellable hold, a paid commitment, or stock already owned; those have different cash implications even when the item count is identical.
Cost exposure needs a named unit and a decision window. The sample workbook calculates its displayed exposure from entered assumptions, including fulfillment volume and applicable cost components. Inspect Inputs and Capacity & Budget before treating that result as a purchase authorization. Does the price include decoration, packaging, duties, outbound shipping, return handling, support, replacement, and payment fees where relevant? Which charges are fixed regardless of uptake? A local shipping rate cannot stand in for a cross-border lane. If a component is unknown, mark the budget estimate incomplete and request a quote rather than inserting a convenient zero.
Create a commitment ladder. At launch, approve the amount needed for fixed setup and a reversible inventory hold. At the first claim checkpoint, release only the stock justified by claims and the remaining response window. At the address deadline, convert complete eligible records into purchase orders or pick waves according to the supplier's lead time. At delivery close, reconcile actual shipped, successful, returned, replaced, and unclaimed quantities. Each checkpoint should include a person who can stop or increase spend and a maximum approved exposure. The workbook is a decision aid; it does not grant approval.
Capacity follows the same logic. Expected support cases should be matched to staffed hours, language coverage, response commitments, and likely peaks. Fulfillment capacity should be matched to daily pick, pack, personalization, and carrier handoff limits, not just total stock. A campaign with enough inventory can still miss a date if the queue exceeds daily throughput. If the sensitivity result shows a likely breach, the options are to stagger invitations, narrow the assortment, reserve extra labor, or adjust the deadline before the public offer. Document the chosen tradeoff and what evidence would trigger a revised plan.
Run the model as an owned operating process
Before launch, assign input owners and a forecast owner.
-
Marketing or People provides the invited population and communication schedule.
-
Data operations verifies deduplication and suppression.
-
The policy owner signs off on eligibility.
-
Supply chain validates available products, production minimums, and stock hold terms.
-
Fulfillment validates lane and service capacity.
-
Finance validates cost components and the commitment ceiling.
-
Customer support validates contact volume and escalation coverage.
Use the recipient experience guide to investigate claim and address friction; use the global gifting operations hub to assign cross-team handoffs.
Use a simple execution sequence. First, freeze the eligible cohort version and the planned invitation wave. Second, test the delivery channel and record an evidence-backed deliverability assumption. Third, enter low, base, and high conditional rates on Inputs with dated sources. Fourth, read Funnel Model and Scenarios for monotonicity and out-of-range outputs. Fifth, compare Capacity & Budget with supplier quotes and staffing plans. Sixth, vary the most uncertain rates on Sensitivity. Seventh, record the approval threshold and the first live-data checkpoint. Finally, save a versioned copy and a short decision log with the input owner, time window, and reason for changes.
On launch day, collect aggregate facts against the same definitions used in the workbook. Report sent and confirmed delivered separately. Do not count an opened message as a claim, an abandoned form as a completed record, an approved gift as shipped, or shipped as successfully delivered. If the channel cannot report reliable delivery, label that input as estimated and seek a more suitable source; avoid presenting a precise rate derived from a partial denominator. For privacy, use aggregate stage counts and controlled access to any underlying recipient record.
Set refresh triggers rather than changing assumptions continuously. A fixed daily review may be appropriate during an intense launch, while a weekly review may suffice for a long program. Reforecast when actual claims materially diverge from the base case, stock availability changes, a market closes, or the deadline moves. Preserve the old version and note what changed. Otherwise, a model can appear accurate merely because its inputs were silently rewritten after outcomes became known. Compare the forecast available at each commitment date with what happened afterward.
Test boundaries, failures, and acceptance evidence
The QA sheet is a starting point for checking the workbook, but it does not replace a human review of business definitions. Enter a zero claim rate in a disposable copy and confirm that downstream claims, complete records, and fulfillments become zero without negative values or hidden error cells. Enter a full claim rate and confirm claims do not exceed delivered invitations. Repeat for address completion, eligibility, inventory acceptance, and delivery success at zero and one. Restore the intended inputs afterward. A rate outside zero to one should be rejected or visibly flagged before anyone relies on the outputs.
Change one input at a time to test a dependency. Raising claim rate should increase or leave unchanged all downstream expected volumes when every other rate is held fixed. Raising a unit cost should affect cost exposure without changing the recipient funnel. Raising delivery success should change successful deliveries without manufacturing more fulfillments. The same scenario row in the CSV should equal the workbook's displayed row to the stated two-decimal precision; the CSV is a versioned export, not a live calculation. Verify that a chart still points to the intended scenario cells after editing.
Operational failures need their own route. A mail or message delivery defect calls for a corrected invitation denominator and possibly a controlled resend. An address form failure calls for a service incident and a new completion window. An item stockout requires an approved alternative or a changed offer before a recipient commits. A shipping exception requires a case owner, promised update, and a closure state. A budget ceiling breach requires a named approver before additional liability is incurred. Each failure should be visible in actual-versus-forecast reporting; hiding it inside a lower “success rate” can obscure the action required.
Acceptance evidence is concrete: a deduplicated eligible count, dated input sources, signed-off eligibility definitions, a reconciled three-scenario workbook, a supplier capacity or hold confirmation, a budget authorization ceiling, support coverage, and a launch dashboard with matching stage names. At close, compare claims, completed records, approved gifts, fulfillments, delivered outcomes, service cases, and actual cost with the prior forecast. Explain material misses by the stage where they occurred. That history improves the next campaign's assumptions without pretending one result is a universal benchmark.
Make the forecast useful at the next decision
A useful forecast gives a team a decision it can act on before the outcome is known: how much stock to reserve, how much spend to authorize, when to release a second production wave, and what evidence would change the plan. Keep each scenario coherent, separate buyer behavior from operational constraints, preserve the version used at each commitment, and replace assumptions with actuals only at a recorded checkpoint. The model is most valuable when it exposes an uncertain stage early enough for a supplier, policy owner, or program manager to respond.
For teams that want to execute the approved plan across invitations, recipient choice, address collection, global fulfillment, and exceptions, Giftpack can provide an operational layer around those decisions. The company still owns its eligibility, privacy, tax, legal, payroll, budget, and recipient-policy judgments; the forecast and execution records help its owners see when reality diverges from the plan.