Reference documents: hand crew the file before you ask for one back
Requests have always been about collecting things from crew: a certificate, an arrival time, a meal choice. This batch adds the other direction. You can now attach a document to a request, so the crew member reads what you’ve given them before they answer.
One document, right where the ask is
Open any request, per crew member or event-wide, and there’s an Attach a document button. Drop in a PDF, PNG, JPEG, or WebP up to 10 MB, or paste a link to something you already host on Drive, Dropbox, or your own site. Add a friendly label if the raw filename isn’t self-explanatory.
The crew member sees it on their live link as a button they tap to open, sitting directly above the box where they respond. The reading order falls into place on its own: here’s the request, here’s the thing to read, now answer. A “sign and return” finally reads as one motion instead of two disconnected steps.
It stays inside the request
A reference document is born inside the request and shows only there. It never lands in the event’s top-level Files list, so attaching a contract to one crew member’s request doesn’t scatter copies through your file area or leave you guessing which version is which. Delete the request, or the event, and the document goes with it.
One per request, on purpose. A request is a single ask, and a single supporting document keeps it that way. Need them to read three things? Combine them into one PDF, or split the asks across separate requests.
Where it fits
A few that come up constantly:
- A Terms and Conditions or safety brief above an “I have read this” tick.
- A contract or release form to read before they upload the signed copy.
- A floor plan or stage diagram before they confirm their position.
- A reference photo of the uniform or table styling before they pick an option.
For anything you’re sharing with the whole crew that isn’t tied to one question, the event Files area or a run of show attachment is still the right home. Reference documents are for when the file belongs to one specific ask and should be read right next to it.