Event Attributes

Event attributes are the structured, typed fields that describe an event itself: its load-in date, its dress code, the venue, the production company, the client. This is data about the whole event, distinct from the per-collaborator information you collect through advancing and distinct from the work you track as tasks.

Every event carries a body of data like this, and until now it had nowhere good to live. The load-in date ended up buried in a settings field. The dress code got stored in an advance that was never meant to hold it. Teams with a real intake process ran it in a Google Form and then re-keyed the answers into BackOps by hand. Event attributes give that data a real home.

Why Event Attributes Matter

The data that defines an event is the first thing you need and the last thing that had a proper place. When the details that describe an event are scattered across buried settings, misused advances, and external forms, the event's own profile is fragmented, and nothing downstream can rely on it.

Event attributes fix this by making the event's defining data a first-class part of the event. Your organization decides what gets captured for each kind of event and which fields are required. Producers fill that data in once, in one place, front and center on the event. Intake stops being a separate document you transcribe and becomes the event's data directly.

This also draws a clean line between two things that were getting confused:

If you ever found yourself "making an advance just for the venue," event attributes are where that data belongs instead.

How Event Attributes Work

Event attributes are built from a small set of concepts that fit together the same way collaborator types and attributes do in the Collaborator Database.

An attribute is a single typed field, such as "Dress Code" (text), "Load-In Date" (date), or "Production Company" (a select list). Attributes are defined once at the organization level and live in a shared attribute library, so the same attribute can be reused across many kinds of events.

An event type is a kind of event your organization runs, such as Concert, Corporate, or Festival. A type organizes its attributes into named sections, like "General Info," "Trucking," or "Labor," so the event's data is grouped instead of being one long flat list. Assigning an attribute into a section is called an assignment, and each assignment can be marked required, task-tracked, or review-required.

Every event is given exactly one type. That type's sections determine which attributes the event captures and in what order. The values your team fills in are stored on the event itself, where they make up the event's profile.

Once an event has a type, its profile appears on the event dashboard, ready to be filled in. Attributes marked as task-tracked turn unanswered fields into tasks, the same way advancing turns gaps into work.