Requests are one thing now

Requests are how you ask crew and suppliers for the things an event needs: a certificate, a headcount, a song list, a signed form, a dietary count. Until now there were two ways to do that, a per-crew version and an event-wide version, and you had to decide which one to reach for before you’d even written the request. They are one system now.

One list, not two

You used to choose up front whether a request went to a single crew member or to everyone on the event. Now there is one Requests panel per event. Add what you need once, and decide who sees it afterwards rather than before.

Show a section only when it matters

Group requests under a conditional section and gate it. There are two ways to gate, and they combine:

• By answer: show the requests below only when a question is answered a certain way (“show when Need catering? is Yes”). Match all of your conditions, or any of them.
• By crew: tick the specific crew the section is for, and only they see it.

Set both and both have to match. There’s also a per-request “Show only when” for one-off gating when a whole section is overkill.

Hide from crew without deleting

Hide a request and it drops off the live crew view, stops accepting submissions, and leaves the completion count alone, while staying in your panel with every response intact. One click puts it back.

Headers and info blocks

A new Section header kind collects nothing from crew. Use it to title a group of requests, or to drop a note and an attached file (a floor plan, a menu PDF) into the requests card for crew to read.

Save an option set once

Building the same Choice request again and again? Tick “save these options as a reusable custom field” and it’s in the picker next time. Custom-field requests carry a small badge so you can tell at a glance why their options live on the field rather than the request itself.