Review the riders your approval created
Read the drafted contract and its auto-injected riders — and learn why you cannot edit them.
Owned by Venue Manager · 11 steps · about 12 minutes
Why this exists
Approving an application drafts a contract in the same transaction, and the riders in that draft are not chosen by a human — they are derived from the flags the promoter ticked on the application. Live music, alcohol, late night and ticket royalty each pull their clause from the rider library, and the headcount, average ticket price and event date are snapshotted into the contract's variables from what was submitted. The design goal is that the venue's standard terms cannot be forgotten by whoever happened to be reviewing that night.
Which is exactly why a venue manager can read this and not write it. The built permissions are clear and worth stating plainly, because the training plan assumed otherwise: every contract edit is admin-only. Editing a section, adding or removing one, changing the variables, re-syncing the riders, locking, unlocking, voiding, resending the signature link and countersigning are all refused for a manager. What you get is the contracts list, the contract page, the rendered preview, and the redlines view that shows how the draft differs from the template.
That is not a gap to work around. Your approval is the operational decision — this night is worth having — and the contract is the legal one. Reviewing the draft carefully and telling an admin exactly what is wrong is a faster path than an edit button would be, because the person who binds the venue is then the person who read the change.
One built behaviour to teach, because the requirements document says otherwise: sealing a contract flips the event from draft to announced. It does not move an application to some approved state — the application's own status stays approved until a deposit is recorded.
Before you start
- A venue manager or admin session.
- An approved application with a drafted contract. Approve the seeded Warehouse Frequencies to make one.
Practise with
| Persona | Password | Note | |
|---|---|---|---|
| venue_manager | manager@club.test | manager123 | shift lead: implies door_staff, plus intake, sales, guest list, marketing |
| admin | admin@club.test | admin123 | the only account that can touch money, identity and contracts |
| host_promoter | host@club.test | host123 | owns the two seeded applications, Warehouse Frequencies and Analog Sunrise |
Steps 1–6 — Venue Manager
their manual →-
1Start from the application you approved and re-read the Production flags block — live music, alcohol, late night, ticket royalty — plus the royalty percentage if it is set.Expected result The flags as the promoter submitted them.Watch out for These flags are the input to the riders. A promoter who ticked alcohol by accident has just acquired a clause, and this is the last screen where that is easy to see.
-
2Open the contracts list and find the draft your approval created.Expected result The contract against that application, in draft.Watch out for This list is open to managers and admins. The individual contract pages are broader still — a host can see their own — so do not assume a page being visible means it is yours to change.
-
3Open the draft and read it in the order that matters: the variables first — headcount, ticket price, event date — then the riders that the flags injected.Expected result The draft with its sections, its auto-injected riders and its variable values.Watch out for The variables are a snapshot taken at approval. If the promoter has since changed their numbers, the contract does not follow them — that divergence is the single most common thing to catch here.
-
4Open the redlines view to see where the draft departs from the standard template.Expected result The differences between this contract and the template it was built from.Watch out for This view is manager-and-admin only. It is the fastest way to spot a clause somebody edited by hand, which is exactly what you want to know before it is signed.
-
5Render the preview to read it as the promoter will see it, with the variables substituted.Expected result The contract as it will appear on the signing page.Watch out for Unfilled variables are glaringly obvious in the preview and easy to miss in the editor. Read the preview, not the source, when you are checking for blanks.
-
6Write up anything wrong and hand it to an admin — the clause, the variable, and what it should say. You cannot change it yourself: section edits, variable edits, rider re-sync, lock, unlock, void, resend and countersign are all admin-only.Expected result A specific request rather than 'the contract looks wrong'.Watch out for Do not ask for the permission instead. The split exists so that the person who binds the venue is the person who read the change.
Steps 7–10 — Admin
their manual →Is the only role that can change anything in the contract you are reviewing.
-
7As an admin, correct the variables the manager flagged.Expected result Updated values throughout the rendered contract.Watch out for Variables are substituted at render time, so fixing one repairs every place it appears — including clauses the manager did not think to check.
-
8Edit a clause where the standard wording genuinely does not fit this night.Expected result The section updates and shows up in the redlines view.Watch out for Every hand edit is a redline somebody has to justify later. Prefer fixing the rider library over hand-editing the same clause for the fifth time.
-
9If the promoter's flags changed after approval, re-sync the riders rather than adding clauses by hand.Expected result The rider set matches the current flags.Watch out for Re-syncing touches the auto-injected riders. Check the redlines afterwards to make sure a deliberate hand edit did not get reverted along with it.
-
10Lock the contract when it is right. From here it goes out for signature and, once sealed, flips the event from draft to announced.Expected result A locked contract ready for signing.Watch out for The seal moves the EVENT status, not the application's. The application stays approved until a deposit is recorded against it — the requirements document describes this differently from what was built.
Steps 11 — Host / Promoter
their manual →Set the flags that produced these riders, and signs whatever they end up saying.
-
11As the promoter, read your own contract before signing. Full signing and countersigning is covered in the Host / Promoter manual.Expected result Your contract, readable.Watch out for The riders came from the boxes you ticked on your application. If one surprises you, say so before signing, not after.