Turn a client brief into a lead-up plan, a supplier bump-in schedule, a minute-by-minute run sheet and a quote-versus-actual budget, all in one workspace.
The florist’s van turns up while the stage truck is still in the only loading bay, or the MC’s cue says 7:40 on the run sheet and 7:30 on the AV supplier’s copy. Both start weeks earlier, in two files nobody compared. Build each file from the one before it, starting with the brief, and check it against that file as you go.
Paste the client’s email, your discovery-call notes and anything they sent (a floor plan description, a guest count) and ask Lato to turn it into one brief with fixed headings.
A prompt might read:
“Turn these notes into an event brief. Headings: purpose, date and times, venue and access, guest numbers, format of the night, suppliers booked or needed, client decisions still open, budget ceiling. Put anything I didn’t give you under ‘To confirm’ instead of guessing.”
The event in this post is made up: a 120-guest awards dinner on a Friday night, with a function room, a caterer, an AV company, a florist and a photographer.
The brief opens in the Document editor. Select an open item and add a Comment to ask the client about it, so the answer stays pinned to its line. Track changes, on the Tools menu, shows who changed the guest number and when.
Keep the “To confirm” instruction in the prompt. Without it, a gap can come back filled with a 6:30 pm start nobody agreed to.
The weeks before the event are a small project. Ask for a project schedule from the brief: book the venue, send the brief to suppliers, receive quotes, client sign-off, final numbers to the caterer, run-sheet walk-through, event day. Give the confirm-by date for each supplier in the prompt. Those dates come from the suppliers, so the AI has no way to know them.
The schedule opens in the Project editor with tasks, durations and links. Right-click a row for Insert milestone (client sign-off and final numbers suit milestones), Link tasks, Assign to... and Set due date.... If one confirmation slips and you want to see what it pushes, the Gantt chart post covers linked schedules and late tasks, so it isn’t repeated here.
Add deadline to Calendar on the right-click menu creates a Calendar event for the selected task, on the day it’s due. In the Project editor’s Calendar view, Send deadlines to Calendar does the same for every upcoming deadline in one go and tells you how many were added. Each one lands as an all-day event with the project name in the title and the owner in the description, so “Final numbers to caterer” sits in your week view beside your other bookings. Nothing links the event back to the task afterwards, so if a due date moves in the project, send that task again and delete the old event in Calendar.
For bump-in and bump-out, the supplier schedule says who arrives when, where they unload and who lets them in. Many venues ask for one. Centennial Parklands’ event toolkit asks organisers for bump-in, event and bump-out hours, a vehicle delivery schedule for suppliers, and contacts for key staff, suppliers and contractors, including after-hours numbers. The City of Darwin’s events page asks for vehicle routes, access times and loading areas in the site plan, and says emergency access must stay clear through bump-in, the event and bump-out.
General information, not legal advice. Access hours, permits and site rules come from your venue or council, so read their conditions before you build the schedule.
Ask for it as a spreadsheet:
“Make a supplier schedule for the awards dinner. Columns: supplier, what they bring, arrive, unload where, finish set-up by, bump-out start, bump-out done by, on-site contact, phone, notes. Loading dock is free from 1 pm. Room must be guest-ready by 6 pm.”
It opens in the Sheet editor. Type times as 24-hour clock with a leading zero (07:30, 13:15) so they sort in order, then sort the Arrive column from earliest to latest with the sort on its column menu. Read down it looking for two suppliers in the same loading bay at the same time. Freeze top row keeps the headings in view on a long list.
| Supplier (example) | Arrive | Unload | Set-up done by | Bump-out |
|---|---|---|---|---|
| AV company | 13:00 | Loading dock | 16:30 | 23:30 to 00:30 |
| Caterer | 14:30 | Kitchen door | 17:30 | 22:30 to 23:30 |
| Florist | 15:00 | Loading dock | 16:45 | 23:30 to 23:45 |
| Photographer | 17:30 | Front entrance | 17:45 | 22:45 |
Made-up times for illustration. They are not a guide to how long any supplier needs.
Ask each supplier to check their row. The arrive time is the one they’ll argue about, so get it in writing before the day.
Camden Council’s event plan guidance describes the run sheet as the document that sets the timing and sequence of the event, with a production timeline that includes bump-in and bump-out. Ask for it as a document so it prints cleanly:
“Write a run sheet for the awards dinner from the supplier schedule and the brief. A table with columns time, what happens, who, where, cue or note. Start at venue access, 13:00, and finish when the last supplier leaves. Five-minute steps during the formalities.”
In the Document editor it arrives as a table, and the table tools add or delete rows, merge cells and toggle the Header row. For printing, choose Layout, then Orientation, then Landscape, so the cue column has room. The PDF export opens the print dialog, where you choose Save as PDF.
Read the run sheet against the supplier schedule line by line. Every arrival should appear at the same time in both, and every cue that needs AV (walk-in music, award slides, the MC’s microphone) should name the AV supplier in the Who column. The two files don’t update each other, so change a time in both at once.
Ask for a budget sheet with columns category, supplier, quote, deposit paid, invoiced, balance due, variance and notes. Type each quote as it arrives and each invoice when it lands.
Variance is invoiced minus quote. Ask the assistant to add that column for every row, or type each formula yourself. For totals by category, SUMIFS adds up the rows that match one category, such as AV or catering.
Conditional formatting has a rule type for cell value comparison. Apply it to the variance column with “greater than 0” and a red fill, and every supplier who invoiced over quote shows up at a glance. Do the same on balance due in the week of the event.
The figures are yours. Oppermind doesn’t know what an AV company or a florist charges, and asking it for typical rates gets you a guess.
If you also quote your own fee to the client and need variations when they add a second room, the tradies post covers the quote and variation documents.
The last document is the one you’ll reach for when something goes wrong. One page, grouped by role: client contact, venue duty manager, each supplier’s on-site person, your own crew, then emergency numbers. Camden Council’s guidance says the contact list can sit inside the run sheet and that emergency contacts, including 000, belong on it.
Ask Lato to pull the names and numbers from the supplier schedule into a contact table, then add the venue and emergency lines yourself. Keep it to what’s needed on the night (name, role, mobile, where they’ll be). Leave out home addresses and anything personal a supplier didn’t give you for this event. What you may keep about suppliers and crew is a matter for your own privacy obligations. How Oppermind handles what you type is set out in the privacy policy.
Print it, and open the same document on your phone in the Oppermind app or mobile browser. For the bump-in day itself, add a Calendar event with the venue in Location, the dock details in Description and a Reminder (up to one day before). Export visible events as .ics makes a file for anyone on a different calendar app.
| File | Editor | Built from | Check before the day |
|---|---|---|---|
| Client brief | Document | Client email and call notes | Every “To confirm” item answered |
| Lead-up plan | Project | The brief and supplier confirm-by dates | Deadlines sent to Calendar and still current |
| Supplier schedule | Sheet | Supplier quotes and venue access hours | Each supplier has checked their row |
| Run sheet | Document | Supplier schedule and brief | Every time matches the supplier schedule |
| Budget | Sheet | Quotes and invoices | Variance and balance due checked |
| Contact sheet | Document | Supplier schedule, venue, crew | Printed and on your phone |
No. It builds the documents around the bookings. Choosing and booking suppliers, and agreeing their prices, stays with you.
They are separate files, so a change in one stays there. Ask Lato to compare the two and list any times that don’t match, then fix each one yourself.
Yes. Ask for copies of the set with the new date, guest count and suppliers, then re-check every time. Last event’s dock hours may not apply at the next venue.
Planning is easier at a desk, and baselines are desktop only. The run sheet and contact sheet are documents, which open on a phone.
Oppermind is not affiliated with, endorsed by, or sponsored by Centennial Parklands (Centennial Park and Moore Park Trust), Camden Council or the City of Darwin.