Event requests for uploads, text or choices
Some questions you only need to ask one crew member: their certificate of insurance, their backup phone number. Other questions you need to ask everyone: a meal preference, a confirmation that they've read the safety brief, a signed copy of the dress code. The Event requests feature in 1pm is the second of those: one request, asked of every crew member on the event, with all the answers collected in one place.
This article covers how event requests work, how they differ from per-crew requests, and the practical situations they fit.
Per-crew requests vs event requests
It's worth being clear about the two flavors up front, because the form looks almost identical.
A per-crew request lives on a single crew member's row. You ask the photographer for their insurance certificate; the request only appears on the photographer's live link, and only the photographer can answer it.
An event request lives on the event itself. You ask every crew member for the same thing; every crew member sees the same request on their live link, and every crew member can submit independently. You see all their answers grouped together in your planner view.
Picking the right one is usually obvious. If the answer is specific to one person, use a per-crew request. If the answer is the same question for everyone, use an event request.
Where to add an event request
Open the event in the planner. Above the Crew accordion you'll see a Requests accordion at the event level (separate from each crew member's own Requests section).
Expand it and you'll see the same form you already know from per-crew requests: a Type dropdown, a Label field, and the kind-specific options below.
Upload. Ask everyone for a file. PDF, PNG, JPEG, or WebP, up to 10 MB per file. Useful for signed contracts, headshots, copies of certificates everyone needs to provide.
Text. Ask everyone for a written answer. Single-line or multi-line. Useful for "what's your arrival ETA?", "give us a one-line bio for the program", "any allergies we need to know about?".
Choice. Ask everyone to pick from a list, one pick or multi-pick. Useful for meal selection, t-shirt size, role preferences, yes/no confirmations. A single choice will default to a checkbox so ideal for ‘I agree’ or ‘I have read and understand the safety briefing’.
The Required toggle (for Text and Choice), the Multi-line toggle (for Text), the Multi toggle (for Choice), and the Expiry toggle (for Upload) all behave the same way they do on per-crew requests.
What crew see
On the crew member's live link, event requests appear in a card titled "Requests all crew", visually above the per-crew "Requests" card. The label makes it clear these are not personal asks: every other crew member is being asked the same thing.
Each crew member sees the request, fills it in (file, text, or choice), and submits. Their submission only shows their own answer, not anyone else's. There's no peer visibility: crew don't see what other crew have answered.
The flow is exactly the same one they already use for per-crew requests, so if they've already submitted documents for a previous event they don't need to learn anything new.
What you see back
This is where event requests differ visibly from per-crew ones. In the event Requests panel on the planner, each request shows a list of submissions grouped by crew member. A typical view for a meal-preference Choice request might read:
Bright Events: Vegetarian
Tony's AV: No restrictions
Acme Catering: Vegan, Gluten free
For an Files upload request, each file shows the crew member name prefix as well, so you can tell which photo, certificate, or document came from which crew.
The view is designed to let you scan who has and hasn't answered. Anyone missing from the list either hasn't submitted yet or doesn't need to (if you've marked the request optional).
When event requests are the right tool
A few situations where event-wide requests usually beat asking every crew member individually:
Meal selection for a sit-down crew dinner. One Choice request with the menu options; everyone picks; the caterer gets a clean list.
T-shirt or uniform sizing. One Choice request with sizes XS through XXL; everyone picks; you order in one go.
Safety briefing acknowledgement. One Choice request with a single option "I've read and understood the safety brief"; everyone confirms.
Arrival ETA for a long-load-in day. One Text request asking "What time are you arriving on site?"; everyone responds; you build the unload schedule from the answers.
Headshots for the program. One Upload request asking for a square headshot at least 800px on the long side; everyone uploads; you build the program from the files.
Signed forms (NDAs, photography releases, contractor agreements). One Upload request; everyone uploads the signed version; you collect them all in one place.
When a per-crew request is still the right tool
Things that are specific to one person belong on a per-crew request, not an event request. For example:
The photographer's PLI certificate (the DJ doesn't need one for their role).
A specific contact's mobile number that you want as a backup.
A note to one crew member with a question you don't want broadcast.
Limits
Up to 50 event requests per event. Each crew member responds independently, so the actual number of submissions can be much larger (50 requests times the number of crew members times the Max counts on upload requests).
Each file upload is capped at 10 MB. For larger files, attach a link instead through the Attachments feature.
Editing while the event is live
You can add, edit, or delete event requests at any time. The crew side updates within a few seconds via the live update channel; no one needs to refresh. If you delete a request after some crew have already submitted, those submissions go too (with a confirm prompt before it happens).
Adding a new event request mid-event is sometimes useful: a late-running question, a last-minute consent form, a quick pulse-check of the crew. Everyone sees it the next time they look at their live link.
Combining event and per-crew requests
The two are designed to be used together. A typical setup for a corporate dinner might look like:
Event requests: meal selection (Choice), signed safety briefing (Upload), arrival ETA (Text).
Per-crew requests: PLI certificate for the AV lead (Upload), backup contact for the producer (Text), uniform size for the bar staff (Choice).
Crew see both sections on their live link. The "Requests all crew" card sits above their personal "Requests" card so the shared questions read first, then the personal ones.
