An event ends with boxes still in storage, and another team wants to use them next month. That sounds like a saving until the old logo permission has expired, another campaign has reserved the same units, or moving the stock costs more than buying locally. This workbook helps event operations, inventory, brand and finance teams make that decision together. It separates permission to reuse, quantities available for three future events, and the incremental cost comparison. None of those calculations is permission to dispatch.
Start with the right decision, not a disposal target
The question is not whether the warehouse can become empty. It is whether a particular physical lot can meet a named future requirement without creating a larger rights, quality, inventory or cost problem. A successful review can therefore end with a transfer, a smaller transfer, continued quarantine, a new purchase or an approved disposition. A negative decision is useful when it prevents an unsuitable item from reaching a recipient.
The US Environmental Protection Agency's materials-management hierarchy places source reduction and reuse ahead of recycling, while recognizing that no single approach suits every material and circumstance. That is context for considering existing stock first, not evidence that every transfer reduces emissions or complies with product requirements. This workbook does not calculate carbon savings or certify reuse.
Its scope is deliberately narrower than a warehouse management system. Use one file for one physically reconciled lot and up to three destinations in date order. The model proposes quantities from the same diminishing pool. A shared inventory register must still reserve those quantities after approval. If multiple people can promise the same stock simultaneously, fix that coordination problem before treating any spreadsheet as executable.
For broader choices about aging stock, use the inventory aging and slow-mover guide. If the previous event's returns are not reconciled, complete the event gift-kit returns workbook first. This tool begins with a trusted remaining balance and evaluates its next use; it does not reconstruct the preceding event's loss or credit claim.
Download the workbook and understand its boundaries
Download the English surplus redeployment workbook. The file contains Inputs, Rules, Decisions and Audit Trail sheets. Version 2027-10-26 identifies this 2027 planning edition, not a claim that research occurred in the future. Source verification is dated October 28, 2026. The example dates, quantities, permissions and costs are fictional; replace them with evidence before operational use.
Start by saving a working copy associated with a real lot identifier and review date. Do not make a separate live copy for each destination with the entire opening quantity. That would erase the principal control: three competing events share one stock pool. Keep the original example available for regression testing, and store the working file in the team's controlled location with a named editor.
Blue input cells accept the lot facts and event proposals. Decisions are calculated; Audit Trail records a later human decision and actual movement. A blank audit entry means there is no recorded approval, even if the decision sheet says the transfer is worth considering. The file has no connection to purchasing, stock reservation, warehouse dispatch or a carrier, and it does not send data to a service.
Use one currency throughout a working file. The English example uses US dollars, but the label itself does not convert values. If a quotation is in another currency, finance must supply a documented comparable amount and rate date before entry. Different local editions use illustrative local currencies, not market quotations or exchange-rate conversions. Compare delivered, usable alternatives rather than a supplier's base price against a fully loaded transfer cost.
Build an evidence packet before entering an approval
The inventory owner supplies the physical count, lot identifier, location and the quantity already reserved or quarantined. These excluded units must not overlap: a unit that is both reserved and quarantined should be excluded once, not twice. Record the reconciliation outside the calculation, then enter the distinct excluded total. If that total exceeds the count, the model holds the proposal for correction instead of turning a negative balance into useful inventory.
The brand or rights owner confirms that the intended design, audience, destination and period are permitted. Possession of a box does not establish permission to reuse its artwork. The workbook's shared rights approval must cover all three proposed uses. If conditions differ by destination, do not tick a broad approval; obtain a common valid scope or evaluate an appropriately separated, nonoverlapping lot allocation with the shared stock register controlling the total.
Quality staff establish condition and a safe-use boundary using the product's applicable documentation. The date field is not a substitute for an expiry label, inspection or a product-specific rule. For a durable item without a printed expiry, enter a documented review horizon rather than an arbitrary distant date. The model treats the chosen final date as inclusive. If the actual instruction excludes that day, the owner must enter an earlier permitted boundary.
The event owner confirms demand and the receiving location. A forecast of visitors is not automatically demand for this particular item. Record the intended distribution rule, confirmed quantity and destination evidence. Finance then checks storage, transfer, rework and other incremental costs. Keep the underlying quotation, approval and inspection references in the evidence register so a second reviewer can trace each input without guessing what a Yes means.
Read quantity eligibility separately from financial attractiveness
The model first checks whether required values are present and internally usable. Counts and demands must be nonnegative whole units; reserved stock cannot exceed the physical count; costs cannot be negative; use dates must not precede the cost reference date. Events must appear in nondecreasing date order. Missing evidence references or an unrecognized approval answer produce a hold. An explicit failed permission, condition or date check produces a blocked result.
For an eligible event, proposed quantity is the smaller of its confirmed demand and stock remaining after earlier proposals. An event that fails a gate receives zero proposed units. The next event can still use stock that was not allocated, provided its own gates pass. A held earlier row is different: later results remain on hold because the available pool has not been safely established.
The financial calculation then compares the purchase that the proposed units could avoid with the incremental transfer scenario. Avoided purchase equals proposed units multiplied by the entered landed new-buy cost. The scenario includes those units' storage days and daily unit cost, event-specific freight, per-unit rework and other fixed costs. Historical purchase cost is not deducted again; it is already committed and does not disappear because a transfer occurs.
Decision sequence for this workbook; all monetary results are scenarios, not realized outcomes.
| Stage | Question | Evidence required |
|---|---|---|
| Permission and condition | May this lot serve the named use? | Current rights scope, inspection and safe-use boundary |
| Quantity | How much remains after earlier proposals? | Physical count, exclusions and confirmed event demand |
| Economics | Is the incremental transfer scenario preferable? | Comparable purchase quotation and transfer inputs |
| Execution | Has an accountable owner approved and reserved it? | Human signoff, reservation reference and dispatch instruction |
Hypothetical case one: expired artwork permission defeats apparent savings
Imagine a US event team finding 100 untouched notebooks bearing a dated partner design. A new event needs 50, the replacement landed price is 12 dollars each, and the preliminary freight quote is 30 dollars. It is tempting to call the boxes a 600-dollar opportunity. The brand reviewer instead finds that permission ended the day before the intended use. The physical condition is acceptable, but the rights gate fails.
In a copy of the sample workbook, change the rights-valid-through date to August 6, 2027 while the first event remains August 7. With later events on August 17 and August 27, all three proposals become blocked and receive zero units. This is a hypothetical boundary test, not a legal interpretation of any actual contract. Its purpose is to demonstrate that an attractive purchase comparison cannot override a failed condition.
The event manager owns the unmet demand; the brand owner owns the permission question; the inventory owner keeps the lot unavailable for dispatch. The team should compare an authorized redesign, an item already cleared for the audience, a smaller order, or a different recognition format. Rework is not presumed to solve the defect. Covering a mark might leave contractual or quality issues, so the reviewer must approve the revised use before a new scenario is calculated.
If written permission is later extended, attach that decision to the evidence register, enter its actual permitted dates and repeat the quantity and cost review. Keep the earlier rejected result rather than replacing its history. Acceptance requires both a current authorized scope and the receiving team's confirmation that the revised item is suitable. Without them, quarantine or separately approved disposition remains the honest result; a spreadsheet status change alone completes nothing.
Hypothetical case two: one hundred units, three competing events
Now consider a different, explicitly fictional lot of 100 sealed generic items, with no excluded quantity. The responsible owners have approved the condition and all proposed uses. Rights remain valid through August 28, 2027, safe use through September 28, and the cost reference date is July 28. Three events on August 7, 17 and 27 have confirmed demands of 50, 40 and 30 units. The total demand is 120; the stock is still only 100.
The model proposes 50 for the first event, 40 for the second and 10 for the third. Remaining quantities become 50, 10 and 0. It does not propose 50, 40 and 30 independently, and it does not claim the third event is fully supplied. The event owner must address the remaining 20-unit demand through an approved purchase, another genuinely distinct lot or a reduced distribution commitment. Mixing another lot into this file without reconciling its conditions would conceal that decision.
At a hypothetical 12-dollar new-buy unit cost, 0.02-dollar daily storage cost and 30-dollar freight for each event, avoided purchases are 600, 480 and 120 dollars. Storage periods are 10, 20 and 30 days. Transfer scenario costs are 40, 46 and 36 dollars, producing net differences of 560, 434 and 84 dollars. These calculations assume no additional rework or other fixed costs, and they are not evidence of actual savings, tax treatment or environmental benefit.
If the final route quotation rises from 30 to 130 dollars, the third proposal's cost becomes 136 and its net difference becomes negative 16. Earlier feasible transfers do not make that last transfer worthwhile. The owner could buy locally, decline the final allocation or combine a legitimate shipment after obtaining a new quote. When an earlier proposal is declined, update its demand or plan deliberately and recalculate; the file does not infer acceptance from a positive difference or optimize route combinations.
Test the working copy before anyone relies on it
An example that looks reasonable is not enough. Use a retained test copy to challenge the gates. Set the first demand to zero: proposed quantities should become 0, 40 and 30, leaving 30 units. No freight should be charged to the zero-unit first proposal. Set excluded stock to 60: available stock becomes 40, so the first event receives 40 and later events receive zero. Restore each input before the next test so results remain attributable.
Next test dates. Set the rights final date equal to the first event's use date: the first proposal remains eligible under the model's explicit inclusive convention, while later proposals fail. Move it one day earlier and all three fail. Test the safe-use boundary separately because a valid artwork permission cannot extend a product's usable life. A negative cost, fractional demand or blank required quantity must not become a favorable scenario.
Test financial sensitivity without changing the physical facts. A zero new-buy price is mathematically valid: avoided purchase becomes zero, so a positive transfer cost is unfavorable. No division is needed, and there is no misleading infinite percentage saving. Increase freight and rework until the preferred alternative changes. Then ask whether any omitted incremental charge would also change the decision. Document the answer rather than adding a generic contingency that nobody can explain.
Finally, have someone other than the preparer reopen the saved workbook and inspect its inputs and results. Check that dates remain dates, the currency is clear, formulas have not been overwritten and the lot identifier matches the evidence. Compare at least one line by hand. Keep the tested version with its review record; later input or formula changes require a new check, not reliance on an old approval email.
Check the cost reference date especially carefully. Storage days run from that common date to each event's use date, so the model charges a longer period to stock intended for a later event. It does not separately model several warehouse stops, seasonal tariffs or shared-truck pricing. If the real route has those features, obtain a comparable incremental quote and document which input includes it. Never count the same storage charge in both the daily rate and other fixed cost.
A reservation for a different campaign should also have a current owner and expiry rule in the authoritative register. This workbook intentionally subtracts the excluded total supplied by that owner; it does not decide whether an old reservation can be released. If someone disputes the exclusion, keep it until the existing controller resolves the reservation. The resulting smaller allocation is more defensible than using an unsupported larger balance to make the transfer look economical.
Record what the review did not establish. The file cannot validate a licensing contract, identify a recalled product, determine customs treatment or prove that an item meets a recipient's accessibility needs. Those are separate checks with their own owners and evidence. A short explicit list of unresolved questions is better than a completed-looking sheet whose approval cells conceal assumptions.
Move from a proposal to controlled dispatch
The model stops before operational commitment. The inventory owner must turn approved quantities into reservations in the existing authoritative register and verify that no competing request has consumed them. If the available balance changed since the spreadsheet snapshot, stop and reconcile rather than subtracting the difference privately. A fresh count or stock-system confirmation should identify the specific lot and location, not just a product family total.
The receiving event owner confirms where and when delivery is acceptable, who will receive the goods, and what happens if the venue changes. Dispatch instructions should reference the approved lot, quantity, packaging condition, destination and reservation. Do not put unnecessary attendee personal information into this workbook. It is a stock-decision record, not a recipient mailing list or a substitute for an authorized fulfillment workflow.
- Inventory owner has reconciled count, exclusions and the formal reservation.
- Brand and quality owners have approved the exact destination, use and dates.
- Finance has accepted the comparable incremental cost assumptions.
- Event owner has confirmed the receiving contact and acceptance conditions.
- A separate reviewer has checked the saved file and signed the decision record.
After dispatch, record actual quantity sent and received in Audit Trail. Investigate differences with the carrier or warehouse evidence; do not amend the approved count merely to make the row balance. A partial receipt may require a claim or replacement, but neither should recreate the original 100-unit pool. Closure means the physical movement, remaining stock and exception record agree. The calculated proposal remains visible as the decision that preceded execution.
Know when a spreadsheet is the wrong control
A workbook is useful for a bounded review with a clear owner and a small number of competing uses. It becomes a poor source of truth when many teams edit copies, lots have different rights and shelf-life conditions, or reservations change continuously. At that point, the valuable output is the decision method and evidence structure, not the continued multiplication of files. Move reservations and operational balances into the existing inventory workflow.
Compare options against the same questions. A manual controlled register can be sufficient for infrequent transfers if responsibility and reconciliation are explicit. A stock-management system can support ongoing movement and location records, but its actual configuration still needs testing. A company merchandise program may help coordinate approved collections and fulfillment, yet it does not automatically decide whether an old lot's permissions or condition remain valid. Do not purchase a platform to avoid resolving ownership.
For an illustrative application, a team could use Giftpack's enterprise storefront offering to discuss an approved collection and future ordering program after completing this review. The current offering describes coordination of merchandise, inventory planning, packing and delivery, with reporting and export options dependent on setup. It is not evidence that this workbook is integrated, that a particular old item is supported, or that Giftpack supplies legal or quality approval.
What if the destination changes after approval?
Keep the original decision and reservation reference. Recheck the new audience, rights scope, condition, route cost and use date. Suspend dispatch until the responsible owners approve the changed proposal. Record whether the original reservation remains held or is safely released; never create a second promise against the same units while the first is unresolved.
Finish with evidence of the next use
The strongest surplus decision is not the one with the largest positive number. It is the one another person can reconstruct: this lot existed, these units were available, this use was permitted, this destination needed them, and this option compared favorably with a real alternative. A well-documented refusal can be more valuable than a transfer whose recipient, rights or physical count was never checked.
Use the workbook to expose those decisions, then preserve the approved version, current evidence and actual receipt. Refresh the review when the event, design, condition, quantity or cost changes. Treat future sample dates as examples, source guidance as context and financial outputs as conditional scenarios. Keep product-specific, contractual, tax and disposal decisions with the responsible professionals rather than attributing them to a formula.
If repeated surplus reviews reveal a need for a more coherent merchandise collection, Giftpack can be part of a discussion about company-store planning and fulfillment. Bring the approved stock and destination requirements to that conversation. Your organization still owns the permission, product-safety, financial and release decisions that make the next use defensible.