Skip to main content
GullySystem
Other industries

Business solutions for Event management companies

Explore software for work such as “Wedding planning and execution”. Review each business function below, including when it fits and what to check before implementation.

Event management companies

How the business operates.

Advances for the stage and the marquee leave your account first. The client’s cheque clears weeks later, and the profit is clear only when the last vendor bill arrives, which can be after the crew has gone home.

Event costing sheet

Build the quotation line by line, from venue hire and per-plate catering to artist fees and transfers, at the agreed head count. Vendor and crew cost are set against it at settlement.

Vendor bookings and advances

Record vendors from your panel against each event, with advance paid, balance due and confirmation status, so a verbal yes from a caterer is not read as a booking.

Quotation versions for client changes

Keep every quotation version as head count, theme or scope changes, with the accepted one marked. A client sign-off step is custom work, added at installation.

Run of show on every phone

Put the cue sheet from load-in to closing, with vendor contacts, on each team member’s phone, updated once for everyone.

Staff and crew deployment

Deploy your own staff and hired stagehands slot by slot, with attendance taken at the morning briefing.

Post-event settlement

Set final vendor bills against their advances. Then raise the client’s final invoice against the event.

Artist riders and travel

Hold each artist’s fee, rider items, flights, hotel and ground transfers on one sheet. The coordinator sees who still lacks a booking. Gaps show well before arrival day.

Guest lists and meal counts

Keep the guest list for each event with dietary needs and table seating. Final covers pass to the caterer from that list. A late addition updates the count.

The records that hold the operation together.

  • Enquiries and their sources. Hold every enquiry with its date, venue, guest count, budget and source, each with an owner and next follow-up date.
  • Site visits. Schedule visits against an enquiry with who went, what was measured and photographs of the hall, feeding the quotation.
  • Packages and rate cards. Price packages per plate, per item, per day or per person, with what each includes. Seasonal and weekend rates can differ.
  • Head-count quotations. Build quotations at a guest count so a change reworks plates, seating and totals together. Versions are kept, and the accepted one is marked.
  • Event calendar. Show weddings, receptions, corporate events, birthdays and exhibitions by date and venue, confirmed or tentative. Popular dates crowd into the same few weekends, so a warning comes before a date, a crew or a piece of equipment is double booked.
  • Vendors and bookings. Keep your panel of caterers, decorators, lights, sound, photographers and transport with rates and past work, and book a vendor against an event.
  • Vendor advances and bills. Record advances with mode and payer, and set every vendor bill against them so the closing figure is arithmetic.
  • Day schedule. Prepare the run sheet with time, activity, vendor, person in charge and place. A banquet desk knows this sheet as the banquet event order (BEO). It prints and opens in a phone browser at the venue.

Operational bottlenecks to check

Margin is known late

Extra LED panels go up and generator overtime is paid in cash at midnight, yet the cost sheet is never revised. Spend on the night goes unrecorded, so the margin looks better than it was.

Vendor advances do not reconcile

Several advances go to one sound and lighting vendor across events, and the balance on each is uncertain. Each coordinator remembers a different figure.

Client changes are not signed off

Forty more gala dinner covers are agreed on a call, and the client later declines to pay for them. Nothing was written down.

The run sheet sits on one phone

The event lead holds the only current cue sheet and vendor list. Nobody else can check the stage manager’s timings mid-event.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Enquiry

    Record name, date, venue, expected guests, budget range and source. Each enquiry carries a follow-up date until it is closed or lost.

  2. 2. Site visit and quotation

    Attach visit notes and photographs of the hall to the enquiry. Build the quotation from your package and rate card at the discussed head count, and keep every version sent.

  3. 3. Confirmation

    Create the event from the accepted quotation and block the date against your calendar and equipment. Booking the same date twice needs a deliberate override.

  4. 4. Vendor booking

    Book caterer, decorator, lights, sound, photographer and transport against the event at agreed amounts. Record advances as they are paid, and check final bills against them.

  5. 5. The day

    A printed run sheet carries timings, the vendor for each item and the person responsible. Staff are deployed by slot and marked present on arrival.

  6. 6. Settlement

    Adjust vendor bills against advances and close them. Collect the client’s balance against the final invoice and see what the event billed and cost.

Roles and responsibility boundaries.

For owners

Watch the calendar, confirmed events, advances out with vendors and what each event made. Approve quotations above a set figure.

For the enquiry and sales desk

Log enquiries, fix site visits, build quotations at different head counts and follow up until the date is confirmed or lost.

For event coordinators

Book vendors, build the day schedule, deploy staff and manage late changes, from a phone once the function starts.

For on-ground supervisors

Open the run sheet at the venue, mark staff present and note what left your stock and what returned.

For accounts

Record client payments, pay and adjust vendor advances, raise the final invoice and follow up on the balance.

Reports your managers need.

  • Events by date, with what is still tentative
  • Quotations sent, revised, won and lost, by enquiry source
  • Advances paid to each vendor and how much is still to be adjusted
  • Client payments received against each event, and the balance due
  • Staff deployed per event, by day and by slot, with what they are owed
  • What each event billed against what it cost
  • Equipment issued to an event and what came back damaged or short

Connections to scope

  • WhatsApp click-to-chat
  • Google Calendar for event dates
  • Wallet and bank transfer records
  • Excel imports of vendor and rate lists
  • Accounting software, through an export agreed at set-up

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your packages and per-plate rates

Rate cards, packages, what each includes and weekend or season pricing go in first. Quotation and invoice layouts carry your letterhead.

Your vendor panel

Caterers, decorators, lights and transport arrive with their rates and contacts. Advances already paid on running events are entered as opening balances.

WhatsApp for schedules and confirmations

Run sheets, vendor confirmations and payment reminders can leave on WhatsApp from your number, and a team member reviews before sending.

Training before a live weekend

Coordinators and the sales desk train on an event you have already run.

Hosting, backups and support

Servers, backups and updates are managed by us, with support available on event days.

Limitations to settle before implementation

  • A venue that only rents the hall and takes no part in the function. A booking calendar will do.
  • Anyone wanting a public ticketing site. Selling passes and registrations online is a different kind of software.
  • A single decorator doing three events a month. Your diary and a payment QR code cost you nothing.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Wedding planning and execution
  • Corporate and MICE events
  • Exhibitions and trade shows
  • Private and milestone celebrations
  • Venue and vendor partnership management
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements