Your team roster and week-of planning
When to use this
Use this page when you want to understand how BloomBoard organizes your people and the internal execution work around an event.
The team roster
The Team page in the Directory holds your roster: the florists, drivers, and helpers your studio works with. Each person’s record keeps their contact details and shows the history of events they have been part of.
Editing a person is meant to be safe to do between jobs:
- A failed save does not lose your typing. If the save cannot go through, the panel stays open with every change still in it and tells you what happened. Fix the problem and save again.
- Only what you changed is sent. Fields you did not touch are left exactly as they are, so two people editing different details do not overwrite each other.
- A saved rate that cannot be shown exactly is protected. The field reads Saved value unverified and the rate stays on the record. It is only replaced when you type a new rate, or removed when you deliberately clear it.
The roster is separate from account access. Someone can be on your roster without having a BloomBoard login, and inviting a teammate to sign in is done from Business → Members instead. See Multi-account and team access for the difference.
Week-of planning
Execution planning for a specific event lives in that event’s Week-of view. In the week of delivery it brings together:
- the run sheet and schedule for the days around the event
- task checklists so nothing is missed
- the team and venue context for the days on site
- the weather outlook for the venue
You can also share a week-of link with the team working the event, so everyone sees the same plan without needing accounts.
Week-of tasks and checklists are separate from the tasks on an event. Event tasks have due dates and show in Today and on the event’s Tasks chip; Week-of tasks never do. See Task lists.
Keep the roster practical. The goal is execution clarity during delivery week, not a second project management system inside every event.