Events and the event workspace
When to use this
Use this page when you want the mental model behind event records before diving into a workflow.
The event workspace
An event is the main BloomBoard workspace for a customer job. It holds:
- client and venue details
- event dates and working status
- arrangements and standalone items
- the proposal and its version history
- invoices and payments
- notes, files, and planning context
The five views
The workspace is organized into five views, each matching a phase of the job:
| View | What it is for |
|---|---|
| Proposal | Create the vision and pricing: arrangements, moodboard, markups, and terms. |
| Production | Plan recipes and orders: what to buy, what to make, and which suppliers get what. |
| Week-of | Run the event: the schedule, tasks, team, and weather for delivery week. |
| Finances | Payments and margin: invoices, what has been paid, and how the event is performing. |
| Client conversations: every email with this client about the event. On the Studio plan with automations on, this view is called Client and also shows the event’s automations. |
You move between views as the job progresses, but everything stays attached to the same event, so nothing has to be re-entered.
One package per event
Each event has one set of arrangements, hire items, services and costs, and its proposal shows all of them as one package with one total. A proposal has no optional extras, and there is no second package for the client to choose between.
To give a client two prices, for example with and without the bud vases:
- Send one version, then make a revision with the other version when the client asks. See Revise a sent proposal.
- Or duplicate the event: open the menu on its card on the Events board and choose Duplicate event, then change the copy. Each event gets its own proposal.
Some older events can hold more than one option from before this changed. The event page and the proposal show only the selected one.
One proposal, with history
Each event carries one live proposal. When a client asks for changes after sending, you create a new version rather than editing the sent one. Earlier versions stay in the history, marked as superseded, so the commercial trail is always intact.
Dates and lifecycle
Event dates matter beyond the calendar: rental pricing and week-of planning both depend on them. Keep them accurate while the job is active.
The event status tells your team whether the job is a lead, in proposal review, booked, completed, or canceled. See Understand event statuses for how the pipeline board presents these.
Treat the event as the system of record. If event dates or status are stale, downstream pricing and supplier work become harder to trust.