Crew requests, file uploads, event-wide forms, and bulk CSV import
Two new ways to collect what you need from crew before the event: per-crew requests (different ask for each person) and event-wide requests (one ask, everyone answers). Plus event-level file uploads, more request field types, and a CSV importer for getting a whole crew list in at once.
Ask each crew member for documents and info
Every crew member’s row in the planner now has a Requests panel. Add a request, pick what kind of answer you want, and the next time that crew member opens their live link, they see a clear “your planner needs this” card at the top of their run sheet.
Use it for everything that varies per crew member: a signed Public Liability certificate from the audio supplier, a Working With Children card from the kids’ entertainer, a photo of the licensed truck from the rigging team, or a free-text question like “what gauge cable will you bring”.
Requests support five field types now:
- A single line of text (for short answers like a name on the door)
- Multiline text (for paragraph answers and briefing notes)
- A single choice from a list of options you define
- A file upload (PDF, JPG, PNG, signed docs of any kind)
- A simple Yes / No
You can mark a request as required (so the planner sees who hasn’t responded at a glance) and give it an expiry date (so the crew member sees a deadline on their card, and the request stops accepting answers after it passes).
Templates so you don’t write the same request twice
If you ask every audio supplier for the same three things, define a request template once and apply it to any crew member in two clicks. Templates live at the workspace level, not per event, so the next show you run reuses the same library without rebuilding it.
We seeded the workspace with a handful of common templates (PLI certificate, Working With Children, performer rider, etc.) which you can edit or delete.
Event-wide requests: one ask, everyone answers
Some questions are the same for every crew member. “Will you need a meal on the night?” “Confirm your call time.” “Send me a portrait photo for the run-of-show briefing.”
Event-wide requests put one prompt at the top of every crew member’s live run sheet for that event. Each crew member’s answer is theirs alone (planner sees who said what, and who hasn’t replied). The planner side groups all the submissions under the event-wide request so you can review them in a single panel rather than clicking through each crew member.
Event file uploads
Run sheets often need supporting documents. The full venue floor plan, the photographer’s shot list, a stage plot, a contract. Each event now has its own Uploads area where you can drop those files. They live with the event and stay private to your team (crew don’t see this panel; if you want a crew member to see a doc, attach it to their personal brief instead).
Personal briefs for each crew member
Alongside the request panel, every crew member’s row on an event also gets a Notes field. Type whatever you want them to know in advance: call time, what door to use, what to wear, who to meet on arrival. The note shows on their live run sheet, above the timeline, so it’s the first thing they see when they open their link.
This replaces the old workflow of sending a separate email to each crew member with their brief. The brief travels with the link, updates if you edit it, and is always one tap away.
Bulk crew import from CSV
Onboarding a new client’s crew list is now a one-page upload. Map the columns, preview the rows, and the importer creates everyone in one transaction. The mapping accepts the column names most spreadsheets ship with (First name, Last name, Email, Mobile, Company, Role) and lets you point custom column names at the right field if your source file is shaped differently.
Mid-event tweaks still work the way they did: edit one crew member at a time from the Crew page. The importer is for the “I have a list of forty people, I need them all in here today” case.