UAFEST.com
UAFest playbooksDated from your festival

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.

  1. 01Pick the editionThe edition start date is day zero.
  2. 02Steps become recordsTasks and document requirements, each with a due date.
  3. 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.

  1. 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.

    9 stepsSpan: T-46T+1v1

  2. 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.

    11 stepsSpan: T-60T+1v1

  3. 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.

    9 stepsSpan: T-120T+14v1

  4. 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.

    13 stepsSpan: T-30T+21v1

  5. 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.

    8 stepsSpan: T-90T+1v1