Read itonce.Run it on your date.
A playbook here is a list of dated steps. Pick your festival date and every step gets a due date, an owner role and the Lanark document it comes from.
How a run works
Opens Festival OS, where the playbook becomes tasks for your edition.
- 01Pick the editionThe edition start date is day zero.
- 02Steps become recordsTasks and document requirements, each with a due date.
- 03Run onceRunning the same version again for the same edition adds nothing.
Starter playbooks
Written from the working notes of UAFest Lanark County.Loaded from the UAFest.com catalogue.
- Comms
A core team of two to four: roles and weekly rhythm
How the Lanark County 2026 season plan split the work between a coordinator, a publisher and a content person, and what it scheduled for the first 48 hours.
- Volunteers
Volunteers and the festival day
One row per volunteer, staffing counted only from real assignments, paper sheets at the gate and an entrance count that survives a dead phone signal.
BeforeAfterDAYT-60T-30T-21T-14T-2T-1DAY×4T+111 stepsSpan: T-60 → T+1v1
- Sponsors
Sponsor package: a tier ladder, zones and in-kind
The structure UAFest Lanark County uses: five cumulative tiers, zone sponsorships as à la carte, an in-kind path and proof a partner can check.
BeforeAfterDAYT-120T-118T-115T-110T-105T-100T-90T-14T+149 stepsSpan: T-120 → T+14v1
- Grants
Evidence for grants: measure the day you will report on
A before / during / after protocol for attendance, program, volunteer hours and an anonymous visitor survey, so the next application quotes figures you can defend.
BeforeAfterDAYT-30T-21T-14T-10T-7DAY×3T+1T+3T+7T+14T+2113 stepsSpan: T-30 → T+21v1
- Comms
Consent to publish: one wording, a dated answer
A single optional checkbox on every application form, stored with the submission, so the answer is known before anyone asks to be taken down.