Finish the service scope before choosing contract wording

A carefully written agreement cannot compensate for a service nobody has defined. Start with the operational promise: what will be delivered, where, when, by whom and under which assumptions.

A practical sequence

1. List concrete deliverables and quantities.
2. Identify exclusions and dependencies on the client or another supplier.
3. Name the approval process and the point at which changes need a new quote.
4. Take the completed scope to the appropriate legal adviser for agreement review.

Work through an example

Coordination may begin six weeks before the event and include one rehearsal plus a stated crew on the day. Those specifics distinguish it from full planning. A client should not have to infer them from a broad sentence saying wedding support.

Where judgement matters

This is a scope-planning method, not legal advice or a ready-to-sign contract. Legal terms about cancellation, liability, payment and jurisdiction need appropriate review. Keep operational clarity and legal review as complementary tasks.

Make it usable

Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.

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.

A vendor is asked for full-service support, but the phrase could mean design, sourcing, installation, guest communication or all of them. Before turning the conversation into an agreement, write the deliverables and boundaries in plain language. The purpose is to expose different expectations while they can still be resolved.

Three decisions and why each matters

Decision	Why it matters
Name deliverables and quantities.	A list of concrete outputs is easier to review than a broad service label.
Identify decisions and dependencies owned by the client.	A delayed approval can affect delivery without changing the vendor’s willingness to help.
State exclusions and change handling.	Both parties need to know how new requests will be reviewed and priced.

Make one usable artifact

Draft a service brief with included work, excluded work, delivery dates, client inputs, revision limits and acceptance conditions. Have the responsible parties review it before formalizing terms.

Then test the difficult case

The client assumes setup includes next-day collection. Add that difference to the scope discussion and resolve ownership before treating the agreement as settled.

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.