Attain OS for event teams

One workspace per event, from the first venue visit to the thank-you email.

Registration, the run of show, vendor contracts and insurance, sponsor records, the production board and the budget stop being twelve files and a wall of printouts. They live in one workspace the producer opens on a laptop and the floor lead opens in a phone browser during load-in. Attain OS does not sell tickets, take payments or schedule volunteer shifts.

14 days free · No card needed · Cancel anytime

Event Management Software for Conferences, Galas and Gatherings

Who this is for

What this looks like today

Conference and summit organizers, community and membership groups running recurring gatherings, nonprofit teams producing fundraising galas and benefit events, training and workshop providers, and festival and venue operations teams.

Load-in is Thursday. The run of show is a document on version nine, the vendor certificates are attachments in three different email threads, the volunteer shift sheet is taped to a wall with names crossed out in pen, and the caterer wants a final headcount by noon while registration is still open. Somebody asks who is meeting the AV crew at six in the morning, and the room goes quiet. Nothing has failed yet. It is just that the whole event exists in six people's heads, and only one of them will be standing at the loading dock.

  • The run of show is on version nine and two people are working from version seven
  • Vendor contracts and insurance certificates are attachments buried in old email threads
  • Registration lives in one tool, the attendee list in a spreadsheet, and neither matches
  • Nobody can say who owns the AV check, the signage or the dock window without asking the producer
  • The real cost of last year's event is a guess, so this year's budget is also a guess

What changes

Each event is a project, and the Event project type switches on the apps an event usually needs. It carries its registration form, attendee and sponsor records, the run of show on the calendar, a production board, vendor documents and the budget. Last year's event stays in its own project for reference. Nothing copies it into the new one, but tasks and Work Board tickets can move across by CSV export and import.

On site, the phone browser is the whole tool. A floor lead opens the board, sees the cards for their area, moves them as load-in progresses and posts a photo of the wrong room set to the feed. Where your organization has WhatsApp enabled, staff can send Atty a voice note while carrying a case, and Atty drafts the task or ticket for their approval. Atty does not message volunteers or vendors who are not members.

The follow-through gets a head start. Registrations sit in the form's table, costs sit in the budget, and the day's issues sit on the board and the feed. Ask Atty what is still open and it drafts the wrap-up note and the follow-up tasks for your approval. The thank-you email to attendees goes out from the Emails app, written and sent by a person.

One version of the plan, on every screen

The run of show, the production board and the vendor documents are shared records, not a document that got emailed. When the schedule shifts, you change it once and everyone sees it the next time they open the calendar, so the day stops running on printed copies that went stale on Tuesday.

Forms, records and documents already in the box

Registration forms, attendee records, contracts, a task board, email updates and team chat come in one workspace, so you stop renting a separate stack for each event. Budget items show the estimate against what was actually paid, so next year's number starts from what this year really cost.

Every task and vendor item has an owner and a date

Load-in steps, room sets and speaker handoffs are cards with a name and a due date, and moving them is visible to the team. When a sponsor asks whether their signage went up, the floor lead's photo on the feed or on the ticket answers it.

Run more events with the same core team

Events repeat, but most teams rebuild them from memory. When each event keeps its structure in a project, last year's tasks can be exported and imported, and Atty drafts the new tasks and notes for your approval, the same small team can take on more dates.

The apps that carry the work

Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.

Forms

Registration, RSVPs and applications

Share a public registration or RSVP form by link or QR code, with no login for the attendee. Answers land in a table you can filter. To email registrants later, turn on case creation so each submission with an email adds the person to your records and opens a case, shortly after, since processing runs on a schedule. Forms take no payments and have no file-upload or signature field.

  • Attendee registration for a conference, workshop or community meeting
  • Speaker, session and vendor applications collected in one table
  • Dietary and accessibility needs asked at sign-up
Forms
Customer Management

Attendees, sponsors, speakers and donors

Keep one record per person or organization with contact details, labels such as sponsor, speaker or donor, and custom fields for what they committed. Tasks and documents can link to the record, and a one-off email sent from it is logged. There is no sponsor pipeline, giving history or ticket record.

  • Sponsors and speakers told apart by labels
  • A speaker's rider and bio linked to their record as documents
  • Follow-up tasks linked to the sponsor they are about
Customer Management
Calendar

Run of show, sessions and load-in windows

Put the schedule on the event calendar as timed or all-day events, from the six a.m. dock window to the last breakdown crew, with attendees from your team, RSVPs and reminders. Share the calendar by public link for people who are not members. Changes show the next time someone opens it; there is no live push to a screen.

  • A multi-track session schedule for a conference
  • Load-in, rehearsal, doors, program and load-out as timed events
  • Recurring workshop and training dates across the year
Calendar
Work Board

The production board

Permits, room sets, AV needs, signage, print deadlines and the day-of checklist are tickets with an owner, a priority, a due date and photos, moving through statuses you define. Moving a card is the status update, which keeps the Wednesday production call short.

  • A pre-event production plan from booking through final walkthrough
  • A day-of checklist by area, worked from a phone on site
  • A punch list of what broke, exported to CSV for next year
Work Board
Team

Staff, floor leads and roles

The Team app is the directory and org chart for your event staff and core volunteers, with admin and standard roles. Members can be limited to the projects they work in. There is no shift scheduling or volunteer check-in, so shifts go on the calendar or the board.

  • A directory of staff and floor leads for the event
  • An org chart of who reports to the producer
  • Crew added only to the events they work
Team
Documents

Contracts, permits and certificates on the event

Venue contracts, catering orders, insurance certificates, permits and rider requirements live on the event project, with labels, an owner, a due date and an optional link to the sponsor or speaker record. Search and filters find the one someone asks for at the gate. There are no folders.

  • Venue and vendor contracts stored on the event they belong to
  • Permits and insurance certificates gathered before load-in, with due dates
  • Speaker and performer requirements linked to their record
Documents
Budgets

Event budget against actual spend

Track each cost as a budget item with an estimate, the amount actually paid, partial payments, the vendor and a receipt. An item turns red when paid passes the estimate, while there is still time to cut something. Budgets track costs only: no ticket or sponsorship income.

  • Budget by line: venue, catering, AV, print, staffing
  • Deposits recorded as partial payments against each line
  • Last year's budget open next to this year's for comparison
Budgets
WhatsApp + Atty

Day-of help from Atty for your staff

Atty works over WhatsApp for the linked members of your organization, so a floor lead can ask what is next on the calendar or send a voice note or photo from the ballroom. The photo is saved to the project's documents, and Atty offers to attach it to the right ticket once you approve. WhatsApp is enabled per organization on request.

  • A voice note from the floor drafted into a ticket for approval
  • A photo of a wrong room set attached to its ticket after approval
  • Staff ask what is next without finding the producer
WhatsApp + Atty
Appointments

Walkthroughs and vendor calls from a link

Give venues, vendors and speakers a booking page for walkthroughs and prep calls. They pick a free slot without an account, get a confirmation email and reminders, and can cancel or reschedule from the email. The call blocks the team's calendar.

  • A venue walkthrough before the contract
  • A speaker prep call a week out
  • A vendor load-in check call
Appointments
Working guide

Event management software is a shared workspace for the work of one event: registration, the schedule, vendors and contracts, the production tasks and the budget. Use it to keep one current version of the run of show, to give every vendor and crew task an owner and a date, and to see what each cost against its estimate. Ticket sales and payments belong in a separate tool.

In practice

Load-in week, with one current run of show

  1. Monday · the production call

    The producer walks the production board with the leads. Permits, room sets, AV needs, signage and print deadlines are tickets with an owner and a due date. Moving a card is the update, which keeps the production call short.

    Work Board
  2. Tuesday · registrations check

    Registration answers sit in the form's table. The producer filters for dietary and access needs and gives the caterer the headcount the venue contract asks for. Responses show what each guest wrote, so the final list still needs confirming with the caterer.

    Forms
  3. Wednesday · vendor paperwork

    Venue contracts, insurance certificates and permits are documents on the event, each labelled with an owner and a due date. The person at the dock can search the event's documents for the certificate they need, rather than scrolling through forwarded emails.

    Documents
  4. Thursday · the schedule on the calendar

    The run of show sits on the event calendar as timed events, from the dock window to the last breakdown crew, with the crew invited. A schedule change shows when someone next opens the calendar. Nothing is pushed to a screen on site.

    Calendar
  5. Friday · on site, from a phone

    A floor lead opens the board on a phone, moves the cards for their area as load-in goes on, and posts a photo of a wrong room set to the project feed. The producer sees the photo there without a phone call.

    The Feed
  6. Saturday · after the show

    The budget shows each line's estimate against what was paid, so an overrun is visible while there is still time to cut something. The open tasks and issues from the day become the follow-up list. The thank-you email goes out from the Emails app, written and sent by a person.

    Budgets
Workflow map

Where each part of the event is handled

JobAppWhat it does here
Registration and RSVPsFormsA public form you share by link, which attendees fill in without an account. Answers collect in a table you can filter. The form takes no payments, sells no tickets and sets no capacity limit, so a paid event takes payment in another tool.
Attendees, sponsors and speakersCustomer ManagementOne record per person or organization, with labels such as sponsor or speaker and custom fields for what each one committed. Documents and tasks can link to the record. There is no sponsor pipeline and no giving history.
Run of show and sessionsCalendarTimed and all-day events for sessions, rehearsals, doors and load-out, with attendees from your team. The calendar shows RSVPs from workspace members only. Share it by public link for guests who are not members.
Production tasksWork BoardPermits, room sets, AV, signage, print deadlines and the day-of checklist are tickets with an owner, a priority, a due date and photos. Your team sets the statuses. Sequencing stays on the calendar, because the board holds no dependency links or sprints.
Contracts, permits and certificatesDocumentsVenue contracts, catering orders, insurance certificates and permits sit on the event, each with a label, a named person and a deadline. Preview PDFs and images in the app. There are no folders, so the labels and search do the sorting.
Budget linesBudgetsEach cost is an item with an estimate, the amount paid, any partial payments, a vendor and a receipt. An item turns red when the amount paid passes its estimate. Budgets track costs only, in US dollars.
Start here

Forms and pages to start an event from

Event RSVP form

Keep the required part to a name and a yes, no or not-sure answer, so guests can reply before the caterer's deadline.

Vendor application form

Collect what each vendor provides, the space and power they need and their insurance before deciding where they set up.

Speaker proposal form

Ask for the talk, its audience and outcomes, and the format the program can fit, so the committee scores comparable proposals.

Dietary requirements form

Ask in plain words for each guest's diet, any allergy that must be kept separate and the meal sessions they attend.

Post-event survey

Send the survey within a day or two of the event, rating the parts the organizer can change, such as the venue and the sessions.

Mistakes to avoid

Three habits that break an event week

Running the show from a printout

A printed run of show goes stale the moment the schedule moves, and the crew then works from two versions. Keep one current run of show on the calendar. If paper is needed at the dock, print it once from that calendar at a fixed time, and mark which copy is final.

Counting a registration as a paid seat

A form response shows that someone asked to attend, not that they paid. The workspace takes no payments, so match payments in the tool that takes them before you finalize the headcount. Set a cut-off date for changes so the caterer's count stays fixed.

Expecting last year's event to copy itself

A project's structure cannot be copied into a new one. Last year's project stays readable, and its tasks and tickets can be exported to CSV and imported into the new event. Rebuild the apps, the board statuses and the calendar on purpose, then keep the lessons as notes.

Working checklist

Before load-in, and after the last breakdown

Before load-in

  • Put the run of show on the calendar and print from it only once.
  • Give every production ticket an owner and a due date.
  • Put the dock window and the AV contact on one card that the floor lead can open.

After the last breakdown

  • Export open tasks and tickets to CSV before archiving the event project.
  • Compare each budget line's estimate with the amount actually paid.
  • Send the thank-you email from the Emails app once the recipient list is final.
What this agreement means

What the event workspace covers, and what it leaves out

  • Registration forms, attendee and sponsor records, the run of show, production tickets, vendor documents and the budget sit in one project per event.
  • Every task and vendor item carries an owner and a date, and each budget line shows its estimate against what was paid.
  • There is no ticket sale, payment processing, ticket income, shift scheduling or check-in.
  • Each event starts from the apps it switches on; last year's project stays readable but is not copied.

Contracts, insurance minimums and permit conditions differ by venue and city. Have the people responsible for them confirm the requirements before load-in.

Frequently asked questions

Does event management software sell tickets?

No. Attendees register on a public form with no login, and their answers land in a table. There are no payments, tickets or capacity limits, so a paid event takes payment in a separate tool.

Can we reuse last year's event instead of starting over?

Not as a template. Last year's project stays readable, but its structure cannot be copied into the new one. Export last year's open tasks and tickets to CSV, import them into the new event, and set up the apps again on purpose.

Is it too much for a small monthly community meeting?

No. Each event is a project that carries only the apps you switch on. A monthly meeting might use one form, a recurring calendar entry and a short board, while a conference uses sessions, speaker records, a production board, documents and a budget.

Can we track event costs against the budget?

Yes, for costs. Each line has an estimate, the amount paid, any partial payments, a vendor and a receipt, and it turns red when the amount paid passes the estimate. Budgets track costs only, not ticket or sponsorship income, and they use US dollars.

What do we ask attendees after the event?

Send a post-event survey within a day or two of the event ending, and report each score with the number of people who answered it. A small group can swing a result, so say how many people replied next to every number.

Who Attain OS Is For — One Operating System for the Team You Actually Run

Attain OS BETA