Writing a vendor scope that survives the event day
Decor, catering, sound and photography disputes almost always trace back to four unwritten assumptions. Here is how to close them before you accept a job.
Vendors rarely lose money on the price they quoted. They lose it on what the price was assumed to include. Every recurring dispute in event services comes from one of four gaps, and each one can be closed with a single line in writing before you accept the job.
Gap 1: Quantity without a ceiling
"Decorate the entrance and stage" has no upper bound. "Stage backdrop 20ft x 10ft, two entrance arches, twelve pathway stands" does. Quote against countable units, and state the rate for each additional unit so an on-the-day addition has a known price instead of a negotiation.
Gap 2: Time without a boundary
Agree three separate timestamps: when you can access the venue, when your setup must be complete, and when you may begin dismantling. A caterer who gets kitchen access two hours late and a photographer asked to stay three hours extra are the same problem — an unpriced hour.
- Venue access time and who unlocks it
- Setup completion deadline
- Service window: start and end
- Dismantle and clearance time
- Overtime rate per hour beyond the window
Gap 3: Dependencies you do not control
Your delivery usually depends on someone else's. Power supply and backup, water, kitchen access, ladder or scaffolding permission, a cleared floor before setup, parking for your loading vehicle. Name each dependency and who is responsible for it. If the venue does not provide power backup, that sentence protects you when the lights fail.
Gap 4: Payment terms without triggers
"Balance after the event" is not a term. Tie each payment to an event: advance on confirmation, a portion on setup completion, the balance within a stated number of days after the function. Record the amount and the status against the job, not in a personal diary.
Staffing your own crew
If a job needs eight people, arranging them the night before is a risk you are carrying for free. Confirm the crew when you accept the job, with the reporting time and payout agreed per person. A crew that knows the address, the time and its pay does not need six calls on the morning of the event.
Rejecting work well
Turning down a job you cannot deliver is cheaper than delivering it badly. Give a reason and give it fast — a client who gets an honest no on Monday can still find someone, and will call you again. A yes that collapses on Friday ends the relationship.
How EventOrbit handles this
A job assigned to you arrives with the venue, address, date, start and end time, priority and description already attached, and accepting or rejecting is recorded against it with a reason. The payment amount and status stay on the same record, and workers you hire for the job are tracked through the same accept, start and complete flow.
Put this into practice
Create a free account and keep your enquiries, jobs and payments in one record.
Get started