UAFEST.com
All playbooks
UAFest playbooks · Commsv1 · 9 steps

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.

Outcome
Three named owners, one applications table, one access table and a weekly ceiling everyone can keep.
Source
Adapted from the UAFest Lanark County 2026 season plan, sections 2–4. Hours per role are the Lanark plan; adjust them to your team.
Run for my edition

Opens Festival OS, where the playbook becomes tasks for your edition.

Ask a mentor about this playbook
Dates below update in your browser. Nothing is saved.

Before8

  1. T-46

    TaskOwner role: Coordinator

    Name the coordinator, the publisher and the content person

    Coordinator (about 2 h a week): access, applications, letters to press and partners, disputed decisions. Publisher (about 4 h): three posts a week and the tracker. Content (1–2 h plus the whole festival day): vertical phone video into the shared media folder. With only two people, posts drop to two a week.

    Source: Lanark working notes · §4

  2. T-46

    TaskOwner role: Publisher

    Make the call for volunteers the first post of the season

    Name the need for people on content, filming and marketing as well as on the festival day. The call to action is the volunteer form on your site.

    Source: Lanark working notes · §2, action 1

  3. T-45

    Festival OSOwner role: Coordinator

    Keep every application in one place, one stream per tab

    Volunteers, vendors, sponsors and business networking each get their own stream. Site forms write there directly, so nothing lives only in a mailbox.

    Source: Lanark working notes · §2, action 2

  4. T-45

    TaskOwner role: Coordinator

    Build an access table before the first post

    Rows: each social account, the website, the shared inbox, the media folder, the applications table. Columns: system, who holds the login, handed to the volunteer. A task stays blocked while its cell is empty.

    Source: Lanark working notes · §2, action 4

  5. T-44

    TaskOwner role: Content

    Put all media in one shared folder with plain file names

    Latin letters, numbers and underscores only, so a volunteer can save a file to a phone gallery in one tap. Cut a set of short vertical clips while you are there.

    Source: Lanark working notes · §2, action 3

  6. T-44

    TaskOwner role: Anyone

    Open the site and every form in a private window and write down what loads

    Check the contact address you publish actually receives mail. Where a post and the site disagree, fix whichever is wrong so they match.

    Source: Lanark working notes · §2, actions 5–6

  7. T-42

    TaskOwner role: Publisher

    Fix the weekly ceiling: 4 hours a person, 3 posts, at least 2 of them video

    Ask everyone who appears in a video to repost it. One short comment check on publishing day is enough.

    Source: Lanark working notes · §3

  8. T-7

    TaskOwner role: Coordinator

    Staff the festival day: publisher, filming, two counters in shifts

    The Lanark plan needed at least four people for this on the day, with a separate person filming on site the whole time.

    Source: Lanark working notes · §3–4

After1

  1. T+1

    TaskOwner role: Publisher

    Send every participant a ready thank-you text and ask for a repost

    The harvest week: participants' own feeds reach people who do not follow the festival yet.

    Source: Lanark working notes · §3, last row