One Diwali order, three Bangalore offices: how to split the delivery

If one Diwali gifting order has to land at more than one Bangalore office, keep the order single and split the delivery: one brief, one approved hamper, one consolidated invoice, but a separate count, a separate named receiver, a separate gate pass and a separate proof of delivery for every site. The choice to make before anything is ordered is whether the whole lot arrives at one office and you move it yourself, or whether each site takes its own drop. For most offices split across the city — a Whitefield headquarters and an Electronic City engineering floor, say — the direct drop per site is the better answer, because an internal transfer across Bangalore costs a working day and the cartons take the damage. OfficeSmart delivers across Koramangala, Indiranagar, HSR, Whitefield, Electronic City, Manyata Tech Park, Bellandur and Hebbal, with same-day delivery available on orders placed before 11 AM, so multiple drops in one city are a normal dispatch rather than a special request. The hard part is not the delivery. It is the count table you hand over with the order.

Should the order ship once, or once per site?

The instinct is to consolidate: one address is less to coordinate and one receiver to brief. The cost arrives later. Hampers consolidated at the main office have to move again, in your own vehicles or a local courier, between buildings that sit an hour or more apart in traffic. Every extra handling is a chance for crushed boxes and a drifting count, and the second leg is unpaperworked — there is no challan and no proof of delivery for the leg you ran yourself, so a shortage found at the satellite office cannot be pinned anywhere.

A direct drop per site costs you one more slot to book and one more person to brief, and it removes the internal leg completely. Consolidating is still the right call in a few cases:

• The sites are in the same tech park or campus, where the move is a trolley rather than a vehicle.
• A satellite office of a dozen people, where the whole count fits in a car boot with no stacking.
• Only one site has a room that can hold the pallets securely until handout day — the staging space, not the delivery, is then the binding constraint.

What has to be counted per site?

Headcount by site is not gift count by site. Base-location fields in an HR system go stale fastest for exactly the people a festive handout is most visible to: hybrid staff attached to one office who work out of another, people seconded to a client site, and shared-services teams that sit under no site at all. The count you need is not where someone is recorded, it is where the gift will physically sit in handout week.

• Whose desk each gift lands on during the handout week, resolved against the real seating or the team lead's answer rather than the HR record.
• People who will be at a client site, in another city or on leave that week, and whether their gift waits at their base office or goes to a home address.
• The housekeeping, security and cafeteria teams on each premises, who are counted per building and are usually on a separate list from payroll.
• Anyone joining between the day the list is frozen and the day of the handout.
• The spare boxes, and which site holds them.

Which site gets the spare gifts?

Spares belong where a replacement can be walked to a desk the same morning, which is normally the largest site — but a satellite office with no spare at all is the one that calls you on handout day, because a damaged box there has no local answer. The split that works is most of the spares at the main site and a small, explicit number at each satellite, written into the dispatch sheet rather than left to whoever loads the van.

Decide the spare count before the order goes in, not in handout week. Off-the-shelf curated hampers carry a minimum of 25 boxes and logo-printed custom kits a minimum of 100 units, so adding a handful of boxes late is not a top-up — it is a fresh order against a fresh minimum, and in festive season it competes with everyone else's rush. Rush orders are possible in 7 days with a small surcharge, but that is a recovery, not a plan.

Who signs for each drop, and what do they count?

Each site needs a named receiver with a phone number on the dispatch paperwork, and the explicit authority to refuse or annotate a short delivery. Count cartons against the dispatch sheet at the gate before anything is wheeled inside, and write the carton count onto the challan before signing it. Client gifting on a Bangalore address list already runs with proof of delivery per address; a multi-site office drop is the same discipline — one POD per site, filed against that site's count.

Brief each receiver on five things, in writing, the day before:

• The carton count for that site and the gift count inside those cartons.
• The delivery slot and the gate or dock the vehicle will arrive at.
• Who to call at the supplier and who to call internally.
• That a short or damaged count is noted on the challan before signing, not reconciled afterwards.
• Where the cartons go once counted, and who holds that room's key.

How do three gate passes get raised?

Each Bangalore tech park runs its own entry process, its own notice period and its own idea of a goods slot, and the facility team that raises a pass for Manyata Tech Park is not the team that raises one for Electronic City. A pass raised for the wrong date is the commonest reason a pallet of hampers waits at a gate while a receiver waits at a dock. As soon as the dispatch dates are fixed, raise a pass per site for that date, and share vehicle and driver details per site rather than assuming one pass covers a multi-drop route.

Should every site hand out on the same day?

Yes, as far as the logistics allow. A festive gift is a message, and people compare across sites within the hour on a group chat; a floor that receives its hamper three days after another floor reads the delay as a ranking. Stagger the delivery if you must, never the handout: have every site stocked by the evening before and hand out everywhere on the same morning. Booking by 15 days before Diwali for standard delivery across Bengaluru gives enough room to sequence three drops inside one week without touching the handout date.

What goes wrong with a split order?

• Cartons labelled with the order number but not the site, so the right total arrives in the wrong proportions.
• A dispatch sheet whose total matches the order and whose per-site lines were never checked against it.
• Every spare box sitting at head office while the satellite has a damaged hamper and no replacement.
• A satellite receiver on leave in handout week with no backup named.
• One site's gate pass raised for the day the hampers were ordered rather than the day they ship.
• Surplus left at three sites with nobody owning the leftovers, which is how next year's order starts with an unknown.

The minimum plan for a two- or three-site order

• One frozen gift list with a site column, agreed with each site's lead.
• A per-site count in writing, spares included, sent with the brief and not after it.
• One named receiver and phone number per site, with a backup for each.
• A gate pass per site, raised for the dispatch date, with vehicle details.
• Cartons labelled by site at the point of packing.
• One proof of delivery per site, filed against that site's count.
• One handout morning across all sites.

None of this changes what you order, and all of it changes whether the order lands. A brief that carries the per-site split from the start also gets quoted faster: options come back within 24 hours of a brief with headcount and budget, and what usually delays a multi-site festive order is not the hamper design but the address and count table arriving a week late. Write that table first, and the rest of the gifting run is the easy part. The invoice stays consolidated whether the gifts went to one office or three.