Respond to a request for more information
Answer the venue's question through your tokenised edit link and put the ball back in their court.
Owned by Host / Promoter · 6 steps · about 10 minutes
Why this exists
When the venue needs something from you, they do not send a personal email and hope. Asking for more information is a status: the application moves to info_requested, the question is stored as a note against the application, and you are emailed a tokenised link that lets you edit your own submission with no account and no password.
Two design ideas sit behind that. The first is that the queue must never lie — as long as your application is in info_requested, the board says out loud that the venue is waiting on you, and nothing is quietly stuck in somebody's inbox. The second is that the token is the credential. It is a 14-day, multi-use link scoped to exactly one application, stored only as a hash. Treat it like a password: whoever holds it can edit your pitch.
When you resubmit, the application returns to under_review with your change recorded in its history, and the venue's Telegram channel gets a fresh "UPDATED APPLICATION" card with new action buttons. The moment a decision is made — approved or rejected — every unused token on the application is invalidated, so bookmarking the edit link buys you nothing afterwards.
Before you start
- An application of yours sitting in info_requested.
- The edit link the venue emailed you (or, in a demo, the recorded outbound email).
Practise with
| Persona | Password | Note | |
|---|---|---|---|
| host_promoter | host@club.test | host123 | the applicant on all three seeded demo applications |
| venue_manager | manager@club.test | manager123 | asks the question and re-reviews the answer |
Steps 1 — Venue Manager
their manual →Asks the question — and requesting info is a first-class status, not an email thread.
-
1From the application's action bar, request more information and say exactly what is missing, in 1 to 2000 characters.Expected result Status moves to info_requested, the question is stored as a note flagged as an info request, a 14-day host_edit token is minted, and the promoter is emailed a link to it.Watch out for Only legal from under_review — anything else is 422 invalid_transition. Claim the application first (opening it from the Telegram review deep link does that for you).
Steps 2–4 — Host / Promoter
their manual →-
2Open the link from your email. There is nothing to log into — the token in the URL is your credential.Expected result Your application, editable, with the venue's question printed at the top.Watch out for Four ways this page turns you away, and it tells you which: an invalid link, an application that no longer exists, one that is no longer editable because a decision was made, and an expired link. All of them render a friendly page with a 410 status rather than a stack trace. If it is dead, ask the venue to send a fresh one — do not go hunting for another way in.
-
3Understand what the page loaded: the same editable payload the API returns for your application, resolved from your token.Expected result Your current answers, tiers and attachment list.Watch out for The guard order is deliberate and worth recognising in an error: a bad token is 401, a wrong status is 409 not_editable, and an expired token is 410. A 409 means your token is fine but a decision already happened.
-
4Answer the question, fix whatever they asked about, add or remove attachments, and resubmit.Expected result The application returns to under_review, your change is recorded in its status history, and the venue's channel gets an UPDATED APPLICATION card with fresh action tokens.Watch out for Removing an attachment is explicit — you send the ids to remove, you do not just leave the file out. The same validation rules apply as on first submission, so a date that has drifted inside the minimum lead time will now fail.
Steps 5–6 — Venue Manager
their manual →Asks the question — and requesting info is a first-class status, not an email thread.
-
5Re-open the application and read the update against the timeline.Expected result The new values, the recomputed viability score, and the whole exchange in the status history.Watch out for You can loop: request info again. Each round trip is another status event, which is exactly the record you want three months later.
-
6Approve once you are satisfied.Expected result Status approved, every unused token on the application invalidated, an acceptance email to the promoter, and — in the same transaction — a draft contract created with the riders your flags implied.Watch out for Approving is the moment the paperwork exists. You can approve, but you cannot lock or counter-sign what you just drafted: that split between running the calendar and binding the venue is intentional.