Start with the moment the gifts are needed
Distinguish the event date from the date the organising team needs the packed sets in hand. The team may need time to count, inspect, sort by location and resolve questions. Agree where receipt takes place and who can accept the shipment. A delivery to an unattended office does not complete the operational handover.
List the known constraints, including venue access windows, staff availability and recipient information that is still missing. Mark assumptions clearly. If a date depends on a third party, identify who will confirm it rather than quietly converting it into a fixed milestone. This gives the organiser a realistic view of the remaining decisions.
Build the approval sequence
Product selection should identify the exact model and relevant variation before final artwork is approved. The printing area, colour and packaging configuration may affect the design. Personalised names need their own checked list. Keep a single approval owner for each decision so conflicting messages do not leave the supplier guessing which version to use.
Ask the supplier to confirm what starts production and what information must be final at that point. Record any confirmed timings in the project file. If artwork changes after approval, ask for the schedule impact before accepting the change. A small visual adjustment can still require another proof or a different production step.
A hypothetical dependency map
Imagine a company preparing welcome sets for an internal gathering. This is a planning example, not a delivery promise or an actual production schedule. The organiser first confirms the set contents, then approves the artwork, then releases the checked names, and finally confirms packing labels for two offices. Each stage has a named owner.
The name list arrives late. Instead of pretending the original plan is unaffected, the team asks whether names can move from the product to an approved card, whether a general set remains suitable, and what each option changes. The final choice is documented along with a newly confirmed schedule. No substitute is treated as approved merely because it is faster.
Use milestones that produce evidence
Each milestone should leave something reviewable: a confirmed product list, an approved proof, a packing list or a receipt record. Track open questions alongside dates, because a green calendar entry is misleading when a required file is still missing. Hold a brief review whenever a key dependency changes.
The Brandkom catalogue can help create an initial shortlist while the event team develops its brief. Keep planning estimates separate from confirmed supplier commitments. At the end, record what caused delays or rework so the next timeline starts from actual experience rather than an assumed universal lead time.
Before you move forward
- Define the date packed sets are needed in hand.
- Name an owner for every approval and missing input.
- Confirm which approval releases production.
- Record the effect of changes before accepting them.
- Keep evidence for each completed milestone.
Common questions
Can we plan backwards from the event date?
Yes, but include inspection and internal distribution before the event. Confirm each supplier-dependent stage instead of inventing a standard lead time.
What should happen when the design changes late?
Document the requested change and ask the responsible supplier or team to confirm its effect on production, cost and timing before approving it.
Ready to turn the brief into a shortlist? Explore the catalogue or start a project in Brandkom’s free Gift Design Studio.