Run vendor applications, approvals, documents, deposits, pitch allocations, setup requirements, and on-site coordination from one checklist — built for multi-zone festivals and busy production offices.
“If vendor truth lives in inboxes and tabs, your site team will improvise at the worst possible moment.”
A short preview of the operational rows included in the full checklist pack.
Use this checklist to manage vendor applications, approvals, documents, deposits, pitch allocations, setup requirements, and event-day coordination from one place. It is written for festival production, site ops, and agency producers who cannot afford conflicting vendor truth across email, drives, and gate radios.
How to use this page: Skim the preview rows below, then unlock the PDF for the full grid. Pair it with your run-of-show and schedule template so servicing and changeovers stay aligned.
Festivals compress months of commercial and technical decisions into weeks. Vendors touch power, water, waste, noise limits, crowd flows, and cashless spend. When those facts live only in threads, gates slow down, finance chases proofs, and safety risk rises. A single checklist is the minimum viable operating layer before you wire software.
Collect once, reuse everywhere: legal identity, category, offer description, insurance and sector documents, technical declarations (power, structure, cooking), pitch dimensions, arrival plan, vehicle needs, and named show-day contacts. If any field is blank, downstream teams should refuse to print passes or allocate slots.
Define who can approve what: commercial for category fit, technical for power and structures, safety for fire and food, finance for deposits. Timebox decisions so late approvals do not collapse load-in sequencing. Evidence should attach to the vendor row, not float in attachments with opaque filenames.
Non-negotiables: Do not issue vehicle or crew passes without insurance dates that cover strike, not just show day.
Track deposit received, balance due, refund rules, and VAT or fee treatment before you allocate prime pitch. Tie payment status to servicing and power handovers so crews are not funding risk on your behalf. For on-site spend and cashless models, align vendor expectations with your bars and top-up strategy early.
Pitch rows should capture dimensions, orientation, shared services, waste handling, and blackout windows where vehicles cannot move. Cross-check against your master schedule so vendor load-in does not fight headline artist truck packs.
On show day, the checklist becomes the escalation index: who answers radio calls, who can approve late arrivals, where spare power lives, and how servicing windows overlap with public movement. Sync with event operations so vendor issues roll up the same path as production holds.
Close with damage notes, deposit releases, incident flags, and rebook intent. Procurement and finance should inherit the same row for PO closure — avoid “export and pray” spreadsheets after the last truck leaves.
EventSuite is built so vendor records, schedules, access, and commercial signals can converge: fewer duplicate profiles, clearer approvals, and less manual reconciliation between gate, finance, and field teams. Start with this checklist, then map each column to the workflow you want in software.
Connect checklist rows to the product modules teams use for live delivery.
Procurement, documents, and on-site vendor coordination.
Explore module →Coordinate planning, production, and delivery around one event record.
Explore module →Sell tickets, manage admissions, and connect sales to event operations.
Explore module →Menus, devices, settlement batches, and on-site revenue controls.
Explore module →Track stock, replenishment, and POS-linked inventory controls.
Explore module →More practical resources from the EventSuite library.
Cashless payments and POS are not just payment tools. For festivals and venues they reduce queues, improve reconciliation, support vendors, unlock offers and vouchers, lift revenue per attendee, and sharpen post-event reporting — when ticketing, commerce, and finance share one commercial spine.
View resource →Spreadsheets are useful for early planning, but event teams outgrow them when they need shared workflows, live status, approvals, ticketing and RSVP, vendors, venue availability, payments and POS, offers, attendee comms, reporting, and a defensible audit trail. This comparison maps where sheets still help — and where connected software pays for itself.
View resource →Use this event budget template to plan income, costs, deposits, supplier spend, staffing, ticketing revenue, vendor revenue, POS income, sponsorship, contingency, and post-event reconciliation — so commercial, ops, and finance share one workbook before doors open.
View resource →It is the end-to-end control of who trades on site: commercial vetting, technical fit, compliance evidence, money movement, access credentials, servicing, and strike — so production, finance, and procurement share one vendor record.
At minimum: identity and category, what they sell, proof of insurance and sector compliance, power and pitch needs, vehicle and crew access, payment status, contract state, day-of contact, and post-event close-out. The downloadable pack expands each row into fields your office can run in a grid.
Spreadsheets work early on; they break at scale when attachments, approvals, and live gate data diverge. Use a sheet for discovery if you must — then graduate to a system where changes propagate to access, servicing, and finance without re-keying.
EventSuite ties vendor records to tasks, schedules, access, and commercial data so accreditation, servicing windows, and settlements reference the same truth — fewer “which tab is canonical?” moments when the site is live.
Connect resource owners to ticketing, vendors, payments, and reporting modules so operational work stays tied to live delivery.
