Openevent

Stop writing down ideas where nobody sees them.

The little details that matter, dietary requirements, supplier quirks, run-of-show changes, "always order extra ice for this client", live where the event lives. Internal-only, never exposed to the client.

Müller wedding · notes
3 entries · last edited 12 min ago
Team
RiverToday, 11:04

Bride wants a quiet apéro, keep music low until 17:00. Pass to FOH.

ElizYesterday

Catering note: table 4 gluten-free. Florist drops at 14:00, leave loading dock open.

Thomas2 days ago

@River check setup ladder is at the venue by Friday.

Open any event. The notes are already there.

Open any event, see the notes for that event. Add a note, write a briefing, leave a comment for a colleague.

Always there alongside everything else about that event.

Rich formatting for proper run-of-show notes. mentions to ping a teammate. Searchable across years.

Müller wedding · notes
3 entries · last edited 12 min ago
Team
RiverToday, 11:04

Bride wants a quiet apéro, keep music low until 17:00. Pass to FOH.

ElizYesterday

Catering note: table 4 gluten-free. Florist drops at 14:00, leave loading dock open.

Thomas2 days ago

@River check setup ladder is at the venue by Friday.

One place everyone checks.

Notes shared with the whole team instantly. No version confusion, no files over email.

Before a large event, the full briefing is inside the event detail. One place everyone checks.

Müller wedding · briefing
Read by 6 of 7 team members
RSEMTBDKLMNS?
  • Allergies: gluten-free for table 4, dairy-free for the bride.
  • Photographer arrives 15:30, apéro lasts until 17:00.
  • Father of the bride speech 21:00, keep music low until 21:15.

Real notes, from real events.

These are the briefings event managers wish they had next time, written down once, attached to the event, surfaced to whoever needs them.

Kitchen brief

Allergies, dietary requirements, table-by-table preferences, service timing.

Supplier quirks

"The florist needs the loading dock open at 14:00", "the DJ pool prefers cash float".

Client preferences

Always order extra ice. Switch off the strobe at the apéro. Keep the music low until 21:15.

Security plan

Door policy, capacity caps, VIP entrance flow, after-incident notes.

AV & DJ rider

Sound check times, line check, set-up requirements, the night's playlist notes.

Post-event lessons

What worked, what didn't, what we'd change for the next one. Searchable across years.

Notes, tasks, documents, what goes where.

Three places on every event. They look similar at first glance; they each do one thing well.

Notes, context

Briefings, preferences, lessons learned. Things to remember about the event itself.

Tasks, actions

Things to do before, during or after the event. Assignable, due-dated, ticked off.

Documents, files

Invoices, offers, contracts, certificates. Filed automatically when paid or signed.

See Tasks and Documents for the matching pages.

Stay on top of your events

The event detail view is the operational core of Openevent, the single place where everything about an event lives. Fully modular: no clutter, no fixed structure, just what matters.

Common questions

  • No. Notes are internal-only and never appear on offers, invoices or public ticket pages.
  • Only if you explicitly grant them access to the relevant event. By default, notes stay inside your team.
  • Notes live right on the event, client or task they belong to, so the next person who opens it sees the context, no more ideas lost in chat threads or someone's notebook.
  • Yes. Notes are shared across your team by default, so everyone works from the same context. You can still keep them out of any client-facing document.

Keep the team in the know.

Free to register · free to use · 1%* only on processed payments.