Ticket triage: deciding what gets answered first
Triage sorts incoming requests by urgency and owner before anybody starts work. How to set priorities that hold, who should do it, and why first-in-first-out fails.
Almost everything that goes wrong at a company event was decidable weeks earlier. A checklist ordered by deadline rather than by category is what turns the last week from firefighting into confirmation.
An event checklist is the list of everything that must happen for a business event — a conference appearance, a customer day, a launch, a training session — with owners and dates attached. This is about company events rather than weddings, which are a different craft with a different literature.
The value is not in remembering the obvious items. It is that the checklist is ordered by when a decision becomes irreversible, which is rarely when it feels urgent. Venue and date lock early and cheaply; catering numbers lock late and expensively; the invitation list determines both and is usually left until somebody asks about catering.
The most valuable item on the list is naming somebody to own the room who has no speaking role. If the person running the event is also the person on stage, then during the fifteen minutes when everything actually goes wrong — the projector, the late caterer, the guest who cannot find the door — nobody is available to fix it.
Separate from the checklist and worth writing: a minute-by-minute schedule of the event itself, with who does what at each point. Doors open, welcome, first speaker, break, and so on, with the name of the person responsible next to each. It answers the question that otherwise gets asked by four people during the event, and it is the document you hand to whoever is covering when somebody is ill.
Registrations are easier to manage when they arrive through a proper booking form with capacity limits, a waiting list and per-attendee details, rather than as replies to an announcement email.
Ettex Board carries the checklist as tasks with owners and dates, which is what the deadline ordering above actually requires; the run sheet and briefings sit in Ettex Docs, the schedule in Ettex Calendar, invitations and dietary responses through Ettex Forms, and the budget arithmetic in Ettex Sheets.
To be direct: this is not event management software. There is no ticketing, no registration pages, no badge printing, no seating plans. For a company running a handful of events a year those features are overhead; above that they are a real product category and worth buying.
Two threads run alongside the checklist and are worth keeping separate from it: vendor management, which is the contracts and the payment dates for everyone you have booked, and the internal comms that tell staff what is expected of them on the day. Both have their own deadlines, and both are usually discovered late because they never appeared on the event list at all.
Two threads run alongside the list and have their own deadlines. Vendor management covers the contracts and payment dates for everyone booked, and a risk assessment is expected for anything with a public audience — often by the venue rather than by law.
Two of the threads have their own paperwork. A business plan template is not one of them, but a go-to-market strategy template is, where the event exists to launch something — it forces the questions about segment and first customers that an event plan leaves out.
Everything with a deadline, ordered by when the decision becomes irreversible — purpose and venue early, invitations next, catering numbers and run sheet late, follow-up immediately afterwards.
A minute-by-minute schedule of the event itself with a named person responsible at each point. It is separate from the planning checklist and is what you hand to whoever covers for somebody.
About six weeks for a business event — early enough that people can move existing commitments, which is the main reason invitations fail.
The follow-up. Most events produce a list of interested people and no plan for contacting them, which makes the event decorative rather than commercial.
Triage sorts incoming requests by urgency and owner before anybody starts work. How to set priorities that hold, who should do it, and why first-in-first-out fails.
A milestone marks a verifiable completion, not a point in the calendar. How to choose them, how many to have, and why percentage-complete reporting replaced them badly.
The critical path is the sequence that sets the end date. How to find it without software, why most status reports chase the wrong tasks, and what float really means.