Answering planner questions
As well as asking for files, planners can ask crew for text answers or for a selection from a list of options. These show up in the same Requests card as file uploads on your link. This article covers the two ‘non-upload’ request types and how to answer them.
Text questions
A text question is the planner asking you for a written answer. Common examples:
Your arrival ETA at the venue.
A backup phone number for someone covering for you.
Your dietary requirements.
A song request for the playlist.
A URL to your portfolio or social media links.
A free-form note like "anything we should know about your setup?"
The request row shows a pencil icon, the question as a label, and an input box. Type your answer and tap Submit. The answer appears below the question once submitted.
Two variants of the text question:
Single-line. A short input box, for a short answer (phone number, time, one-line note).
Multi-line. A bigger text area, for paragraph-length answers (a paragraph about your setup, a list of requirements, a longer note).
The planner picks which variant they want when they set up the question. You don't have to think about it: the input that appears is the one they want.
If you submit and then want to change your answer, tap into the input again, type the new answer, and submit again. The new answer replaces the old.
Choice questions
A choice question is the planner asking you to pick from a list of options. Common examples:
Meal preference (beef, fish, vegetarian, vegan).
T-shirt size (S, M, L, XL).
Time slot preference for a load-in window.
Yes / no confirmations on a clause or instruction.
Role preference if you've offered multiple services.
The request row shows a list icon, the question as a label, and the options as either radio buttons (pick one) or checkboxes (pick any number). The planner sets which.
Tick the option(s) you want and tap Submit. Your selection appears below the question.
If the planner has made it a single-pick (radio buttons) and you change your mind, pick the other option and submit again. The previous pick is replaced.
If it's multi-pick (checkboxes), you can submit any combination including all of them or none. Re-pick and resubmit to update.
Required vs optional
Each text and choice question has a Required or Optional badge.
Required means the planner is expecting an answer. You'll see a Required badge on the row.
Optional means it's nice to have but not required.
There's nothing that hard-stops you from leaving a required question unanswered, but the badge is a clear signal of what the planner actually needs from you.
When to answer
Try to annswer requests asap before the event. The day is for the run sheet, the venue, and the work. Requests are about getting paperwork and details squared away in advance.
A typical sequence:
The planner sends you the link a week or two before the event.
You open the link, scroll through, and answer any requests sitting on it.
The planner sees your answers and can plan accordingly (caterer gets meal counts, transport gets ETAs).
By event day, the requests are done and the run sheet is the only thing on your screen.
You can answer (and re-answer) at any time, including during the event. But anything time-sensitive (meal counts, transport pickups, who's where) is best resolved well before the day starts.
What the planner sees
As soon as you submit, your answer appears against your name on the event. The planner doesn't have to refresh; the live update channel pushes the answer to their view within a few seconds.
They can see whether you've answered, what you answered, and when. They don't see drafts; an in-progress answer you haven't submitted is invisible to them. Only what you actually submit.
Changing your answer later
Both text and choice answers can be updated as often as you like. Type a new answer or pick different options and tap Submit. The new value replaces the old.
If the planner has already used your answer (printed the meal-count sheet, locked in the transport pickup), changing your answer late might not propagate to whatever downstream document they've prepared. Worth dropping them a message as well if you change something significant close to the day.
When a request is missing
If you've been told a request is on your link but you can't see it, a few possibilities:
You're looking at an old cached version of the page. Pull down to refresh on a phone, or hit the browser refresh on a laptop.
The planner has deleted or changed the request since they told you about it. Ask them what they need.
You're looking at the public shareable runsheet (the URL has /r/ in it) rather than your personal crew link (the URL has /v/ in it). Requests only appear on the personal link. Open the email or message that originally pointed you at 1pm and check the URL.
If none of those apply, the planner can check the request state on their side and resend.
Privacy of your answers
Answers you submit are visible to the planner. Other crew on the same event do not see your answers. If you've submitted a meal preference, the other suppliers on the wedding aren't seeing your choice.
The exception is anything the planner has chosen to share publicly through the event briefing or a timeline item description. Those are visible to whichever crew can see the relevant row. Your direct answers to requests stay between you and the planner.
