Write a One-Page Wedding Brief Suppliers Can Use on the Day

A group chat is good at announcing a change and poor at proving which version is current. The arrival entrance can disappear between a photograph and a menu question. A short operational brief gives suppliers a stable reference while leaving their contracts and specialist instructions intact.

The Health and Safety Executive’s event guidance highlights relevant site information and coordination between work activities. That supports the purpose of this brief: communicate the facts people need to perform their agreed roles. It is not a substitute for venue inductions, technical plans or local safety requirements.

📋 Put actions above atmosphere

Your supplier may appreciate the creative mood board, but the operational page should begin with the date, site address, access instructions and contact person. Include a plain-text address alongside any map link so a broken link does not remove the destination.

1. Collect confirmed logistics from the venue and each supplier.
2. Choose one editor and a clear version label.
3. Write a master brief, then remove information irrelevant to each recipient.
4. Ask recipients to acknowledge details that affect their work.
5. Issue changes with a summary and mark earlier versions superseded.

Use absolute dates and a clearly stated local time zone if people are travelling internationally. Avoid relative messages such as “arrive tomorrow” that become confusing when forwarded. For multiple sites, name each location rather than repeating “the venue.”

A worked two-location brief

Assume an illustrative ceremony at Garden Room and a reception at Harbour Hall. A florist has a confirmed arrival slot at the first site, then moves two agreed arrangements to the second. Your brief should make that movement visible without assuming the florist has accepted extra labour.

Include a simple site sketch only if the venue has approved its accuracy. Mark the relevant unloading point and handover location, not a speculative route through restricted areas. Ask the supplier what vehicle and unloading requirements the venue needs to know.

Control the change loop

Suppose reception access moves from 14:00 to 14:30. Update the brief and send a short change message identifying that exact field. Ask affected suppliers whether their delivery and setup still work. Acknowledging receipt is different from confirming that the new arrangement is feasible.

Keep a small record of outstanding acknowledgements. Telephone the relevant contact if a time-sensitive change has not been confirmed; do not assume that a message being delivered means it was read. Record the resulting agreement in writing afterwards.

Avoid turning the one-page brief into a compressed novel. Attach approved schedules and layouts separately, with matching version labels. The front page should tell someone under time pressure which document to open and whom to call.

Ask one recipient to find their arrival time using only the draft brief. This is a document check you can perform, not evidence that the whole event plan has been tested. If the answer requires searching several attachments, move that essential field onto the front page before circulation.

Share only what is needed

Do not distribute the full guest database to every supplier. A caterer may need dietary information through an agreed process; a lighting team generally does not. Obtain consent before circulating personal contact numbers and use role-based contacts where available.

This approach depends on accurate inputs and a responsive editor. It cannot solve an unconfirmed access arrangement by formatting it beautifully. The useful takeaway is a closed communication loop: one current instruction, the right recipient, explicit confirmation and a visible route for changes.