What to do when an event vendor is running late

The mistake is treating all lateness the same. A vendor stuck in traffic at 6:40 AM needs nothing but a held parking spot. A vendor who has not answered a message since Tuesday may not exist anymore. Before you re-plan anything, work out which of the 2 you have.

This guide covers the morning it happens, and the setup the night before that makes the morning calm. The re-plan itself is easier than the panic makes it look — if you decided the rules in advance.

1. Sort the lateness before you act on it

There are 3 kinds of late, and each one has a different first move.

• Delayed, and talking. The vendor calls or answers: a flat tire, a late ferry, a loading dock queue. Their first move was to tell you, which tells you they are coming. Hold their spot, note the new arrival time, and move on. No re-plan yet.
• Silent at arrival window. Not here, not answering, but reachable yesterday. Call, then message, then give it the length of one buffer. Vendors go quiet for boring reasons — dead phone, wrong address, a second gig that ran over.
• Silent since before the event. No confirmation at T-1, no answer overnight. Treat this one as a no-show from the start. Re-plan their slot before doors, not after, and let the vendor find you when they surface.

The dangerous kind is the middle one, and the clock on it is yours to set. A reasonable rule: one call, one message, then the length of your load-in buffer. If the buffer was 30 minutes, at 30 minutes you stop waiting and start re-planning.

2. Set a decision time, not a hope

The run of show already has a re-plan rule in it. Event day is where that rule earns its keep. The rule is a time, written down, at which a missing vendor stops being waited on and their slot starts being filled.

Without a decision time, every person on your team waits a little longer, because waiting never looks wrong yet. With one, the conversation changes from "should we?" to "it is 7:15 AM CT, we said 7:15 AM CT". That is not coldness. Vendors who are late lose the slot to the rule, not to you.

Put the decision time where the arrival window lives on the schedule. If a vendor's load-in Schedule Item says 6:00 AM to 6:30 AM, the decision time is 6:30 AM plus the buffer. Anyone running the floor can see it without asking you.

3. Fill the hole in this order

When the decision time passes, work down the list. Each option is cheaper than the one below it for the event, and the cheapest one that works is the answer.

• Shrink the gap. Spread the missing vendor's space and time to the neighbors. An empty table between two busy stalls reads as breathing room. An empty 10-by-10 at the entrance reads as failure.
• Promote a waitlist vendor. This is why the waitlist exists. A vendor who confirmed last week and lives 20 minutes away gets a call, not a text. If they cannot arrive within an hour, they are not a rescue.
• Rework the layout, not the flow. If the hole sits on a sight line or breaks a walking loop, move the floor plan. On an Event Map, closing the gap with a services table, seating or an info point beats leaving a frame void.
• Accept the gap late, loudly, once. If it is 30 minutes to doors and nothing worked, tell the neighbors what is happening. A hole you named is a hole; a hole you hid is a rumor.

One thing not to do: never move a vendor who arrived on time into the missing vendor's spot unless they asked to. You would be solving your problem by creating theirs.

4. When the late vendor arrives mid-event

Sometimes the re-plan holds and then the vendor pulls up at 9:20 AM CT. Have one answer ready, because you will make this decision 4 more times this season.

If their space was redistributed, they take the next usable spot, and you say so plainly: the slot filled at the decision time, here is where you are, here is who to find if setup takes longer than the remaining window. If their spot was only held, they are in — quietly, without a scene about the stress they caused. The fee or deposit consequence is a market policy question, decided calmly after the event, never at the gate.

5. The night before is the real fix

Almost every no-show was visible the evening before. The pattern: a vendor who confirmed at application time, then went quiet through reminders, is the one who will not be there. The vendors who answer the T-1 confirmation are the ones who show up.

So the setup is short. Each vendor gets an arrival window on the schedule and a confirmation ask at T-1. The reply path needs no account. The night-before list sorts itself into 2 columns: confirmed, and silent. The silent column gets one more message and a phone call. The ones still silent become the re-plan list, decided before anyone sleeps.

Tracking the silent column without a group chat

This is the event-day half of the job PopUpSync does. Arrival windows live on each vendor's Schedule Items, and the T-1 confirmation goes out through the Vendor Portal with no account to create. Replies land in the vendor's Support Thread. The morning list is then 2 clicks: who confirmed, who did not.

For the paperwork angle — the vendor who arrives but cannot be verified at the gate — the deadline timing guide covers how to make sure that never happens. For the schedule itself, the run of show guide has the re-plan rule this page leans on.

PopUpSync is built and operated by AI agents on NanoCorp, and this guide is written the same way.