Vendors
Check vendor readiness before the truck reaches the gate
Editorial team · Reviewed
Arrival problems are often information problems discovered too late. A concise readiness check brings together the route, access window, unloading requirements and person who can solve an exception.
A practical sequence
- Confirm a precise entrance and arrival window with the venue.
- Ask about vehicle size, loading time, equipment and access needs.
- Give the supplier a named on-site contact and a fallback number.
- Record en-route, on-site, delayed and needs-help states separately on the day.
Work through an example
The rental truck is on time but arrives at the guest entrance, where it cannot turn safely. A pin to the correct loading gate, a description of the route and a named contact would have been more useful than another copy of the full timeline.
Where judgement matters
A status update should trigger an appropriate action. A supplier marked delayed needs an owner reviewing the dependency, not merely a red badge. Avoid collecting live location data when a simple voluntary arrival update is enough.
Make it usable
Open the working tool and replace its sample assumptions with your own. Adapt the structured template to record the resulting decisions and handoffs. Review the finished version with the person responsible before it becomes an instruction to someone else.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
The DJ vehicle reaches the venue at 14:30, but equipment is still waiting for lift access. The ceremony sound system is not usable until the microphones are checked at 15:10. Reporting only arrived hides the risk to a 15:00 rehearsal. Arrival and readiness need different definitions.
| Decision | Why it matters |
|---|---|
| Record arrival as a location fact. | Being on site does not mean setup, sound check or service preparation is complete. |
| Give readiness an observable condition. | For sound, this might be tested microphones in the actual ceremony position with the cue owner present. |
| Escalate a blocked resource rather than blaming a late task. | The lift booking may be the root cause and need a coordinator’s decision. |
Make one usable artifact
Create a vendor handoff with arrival, access granted, setup complete, ready-for-service and named confirmer. Include the blocker and its current owner.
Then test the difficult case
The DJ is ready but the officiant has not rehearsed the microphone. State which readiness check remains open and whether the rehearsal can safely begin.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.