Asking everyone for the same thing — Help

Some things you need from every crew member on an event: a meal preference, a confirmation that they've read the safety brief, a signed copy of the dress code. The Requests feature in 1pm is built for exactly this: one request, asked of every crew member on the event, with all the answers collected in one place.

This article covers how Requests work, what crew see, and the practical situations they fit. If you only need one person to answer something (just the photographer's insurance certificate, say), see the section on targeting a subset of crew further down.

One Requests system, asked of everyone by default

It's worth being clear up front, because the older 1pm had two flavors and you may remember them. There used to be "per-crew" requests that lived on a single crew member's row and "event" requests that lived on the event. That split is gone. There is now a single Requests system. Every request lives on the event, and by default every crew member sees it and answers it independently. You see all their answers grouped together in your planner view.

If you need to ask only some crew the same question, you don't make a different kind of request. You wrap the requests in a Section and limit it to a named set of crew. More on that below.

Where to add a request

Open the event in the planner. In the Crew area you'll find a Requests panel for the event. Expand it and you'll see the add form.

Pick a Type from the dropdown, give it a Label, and fill in the kind-specific options below. The form stays decluttered: only the type picker shows until you choose a kind, then the relevant fields appear.

The request types

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. An optional expiry date lets you track when a document needs renewing.
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-option Choice renders as an acknowledgement checkbox ("I've read the safety brief").
Contact field. Write the crew member's answer straight through to their contact record (their phone number, a social handle, or one of your own custom fields). Each crew member updates their own.
Section. Not a request, it collects nothing. A frame that groups the requests you put inside it, with an optional title shown to crew as a heading on their live link. A section can also be limited so only some crew see what's inside it (see "Asking only some crew the same thing" below). This one tool replaces the old "section heading" and "conditional section" markers: pick Section from the dropdown and it's added straight away, then set its title and any visibility limit on the section itself.

The Required toggle (for Text, Choice, and Contact field), the Multi-line toggle (for Text), the Multi toggle (for Choice), and the expiry toggle (for Upload) all do what they say.

What crew see

On the crew member's live link, the requests appear in a card titled "Requests all crew" (it reads "Requests all Guests & Crew" when RSVP is turned on for the event). The label makes it clear these are shared asks: every other crew member is being asked the same thing.

Each crew member sees the request, fills it in (file, text, choice, or contact detail), and submits. Their submission only shows their own answer. There's no peer visibility: crew don't see what other crew have answered.

A completion bar at the foot of the requests tells each crew member how many required items they still have outstanding, so they know when they're done.

What you see back

In the event Requests panel on the planner, each request shows a "View responses" or "View files" button with a count. Open it and you see the 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 upload request, each file shows the crew member it came from, so you can tell which photo, certificate, or document belongs to whom. Uploads can be approved or rejected in place, and a rejected file frees the slot so the crew member can re-submit.

The view is designed to let you scan who has and hasn't answered. Anyone missing either hasn't submitted yet or doesn't need to (if you've marked the request optional, or it sits in a limited section that doesn't apply to them).

When Requests are the right tool

A few situations where one shared request beats chasing crew 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 single-option Choice "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.

Asking only some crew the same thing

Not everything applies to every crew member. The DJ doesn't need public liability insurance for their role; the photographer does. You handle this with a Section that limits who sees what's inside it, rather than a separate kind of request.

Add a Section from the type dropdown (it appears the moment you pick it), then put the requests that only apply to a subset inside it. Open Limit who sees this on the section to gate it two ways, which you can combine:

By named crew. Pick exactly which crew members the section applies to. Only they see the requests inside it; everyone else sees nothing, with no hint that the section exists. Good for one-off compliance asks you don't want broadcast.
By answer. Reveal the section only when crew answer an earlier Choice question a particular way. For example, ask "Are you driving on site?" and reveal a vehicle-registration request only to those who pick "Yes".

You don't close a section by hand. It encloses the requests you put inside it, and the frame ends where the next section begins or the list ends.

So the rule of thumb is simple. Same question for everyone: a plain request. Same question for some: the same request inside a limited section. There's no longer a one-person-only request type; even a single-recipient ask is a named-crew section with one crew member in it.

Limits

Up to 50 requests per event (conditional-section markers and headings don't count toward that cap). Each crew member responds independently, so the actual number of submissions can be much larger.

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 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 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.

Tracking documents over time

Uploads with an expiry date feed the Requests page in the main navigation, where you can see certificates and licences expiring soon across all your events. From there you can prompt a crew member by email to upload a fresh copy, approve or reject incoming files, and review anything you've rejected. It's the home for keeping crew documents current without opening each event one by one.