F02 configured supporting document
Volunteer Roster Template
A controlled, editable working derivative for M-T1-CP-02-SD-02. Complete local facts, approvals and operational evidence before use.
Release truth. This file is configured for substantive review. It is not approved for public distribution or operational use. Local law, insurance, safeguarding, accessibility, privacy, brand, rights and accountable-owner checks remain mandatory.
M-T1-CP-02-SD-02 — Volunteer Roster Template
Release control
| Controlled field | Controlled value |
|---|
| Status | REVIEW — configured derivative; not approved for operational release |
| Supporting-document code | M-T1-CP-02-SD-02 |
| Exact derivative title | Volunteer Roster Template |
| Source initiative | M-T1-CP-02 - Local Markets Engagement |
| Source initiative code | M-T1-CP-02 |
| Source initiative title | Local Markets Engagement |
| Initiative disposition | Absorbed as overlay |
| Canonical parent | M-T1-CP-14 - Pop-Up Rotary Activation System |
| Canonical parent code and title | M-T1-CP-14 - Pop-Up Rotary Activation System |
| Named overlay or migration label | Local Market Activation |
| Redirect or tombstone route | Permanent overlay alias from M-T1-CP-02 to M-T1-CP-14; retain M-T1-CP-02-SD-02 as the stable market-overlay asset code |
| Production family | F02 — People, Roster and Safety |
| Family master | Playbook_F02_People_Roster_Safety_Master.md |
| Family master version | 1.0, issued 1 August 2026 |
| Index authority | Playbook Supporting Documents Master Index v1.1, issued 2 August 2026 |
| Family / master version | F02 / 1.0 |
| Recorded master SHA-256 | e9c57df5391e7774a9c00b8ac8ca21906d0c5c2f1e87592601079309620a9b74 |
| Authoritative index | Playbook_Supporting_Documents_Master_Index.md v1.1 |
| Configured master variant | F02 Section 20 — M-T1-CP-02-SD-02 Local Market Activation roster overlay |
| Derivative version | 0.1 |
| Release status | REVIEW — initiative-configured working derivative; local approval required before operational release |
Adaptation note: This is the Local Market Activation roster overlay for the Pop-Up Rotary Activation System. It requires market/date/location/shift coding; setup and pack-down pairs; active conversation, data-custody and relief coverage; weather, wind, public-flow and organiser escalation briefings; task rotation; and shift-level conversation and follow-up handover.
This roster supports planning and governance. It does not determine legal duties, insurance cover, safeguarding requirements or market-organiser conditions. Confirm the current local position before use.
1. Instructions
- Create one controlled roster per market occurrence and use the same market, date, location and shift codes in F01 and F05 records.
- Enter only people who have accepted a defined role and completed the required competency, screening and briefing gate.
- Do not roster a person alone to manage public engagement, sensitive data, weather response and breaks.
- Keep private contact and adjustment details in the restricted roster; issue a separate public duty list.
- Record actual attendance, breaks, handovers, conversations and accepted follow-up at the end of every shift.
2. Controlled activation fields
| Field | Entry |
|---|
| Market / organiser | ______________________________ |
| Market code | ______________________________ |
| Date and location code | ______________________________ |
| Public operating time | ______________________________ |
| Approved footprint / stall position | ______________________________ |
| Access, setup and vehicle window | ______________________________ |
| Pack-down / site-clear deadline | ______________________________ |
| Event lead | ______________________________ |
| Roster lead | ______________________________ |
| Shift lead(s) | ______________________________ |
| Safety / first-aid contact | ______________________________ |
| Safeguarding contact | ______________________________ |
| Data custodian | ______________________________ |
| Organiser control contact | ______________________________ |
| Controlled roster/contact location | ______________________________ |
| Related F01 and F05 records | ______________________________ |
3. Market readiness gate
| Gate | Approved evidence or condition | Owner | Complete |
|---|
| Market terms, access, footprint, weights and permitted activity | ______________________________ | __________________ | [ ] |
| Weather/wind monitoring and shutdown triggers | ______________________________ | __________________ | [ ] |
| Emergency, lost-person, aggressive-conduct and organiser routes | ______________________________ | __________________ | [ ] |
| Insurance and local safety review | ______________________________ | __________________ | [ ] |
| Data capture, privacy notice, device/paper custody and follow-up | ______________________________ | __________________ | [ ] |
| Safeguarding and photography controls | ______________________________ | __________________ | [ ] |
| Accessible stall approach and conversation option | ______________________________ | __________________ | [ ] |
| Safe setup/pack-down travel, lifting and buddy arrangements | ______________________________ | __________________ | [ ] |
Gate decision / reviewer / date: ______________________________________________
4. Required roster pattern
- Setup pair with market access, footprint, weights and asset instructions.
- A named shift lead for every operating period.
- Approved public-facing coverage that never leaves one person to manage engagement, data, weather and breaks alone.
- Conversation hosts positioned forward of the table where the organiser permits.
- A data custodian controlling paper cards and devices.
- A relief host who can cover breaks without closing the stall or exposing data.
- A pack-down pair responsible for assets, waste, site sweep and organiser handback.
5. Controlled internal roster
| Shift code | Volunteer ID / preferred name | Role | Start | Finish | Briefing | Shift lead | Planned break | Relief | Contact confirmed | Adjustment flag only | Handover to | Sign-on | Sign-off |
|---|
| SETUP | __________________ | Setup / logistics | ______ | ______ | ______ | __________________ | ______ | __________________ | Yes / Pending | Restricted / None | __________________ | [ ] | [ ] |
| ______ | __________________ | Shift lead | ______ | ______ | ______ | __________________ | ______ | __________________ | Yes / Pending | Restricted / None | __________________ | [ ] | [ ] |
| ______ | __________________ | Conversation host | ______ | ______ | ______ | __________________ | ______ | __________________ | Yes / Pending | Restricted / None | __________________ | [ ] | [ ] |
| ______ | __________________ | Data custodian | ______ | ______ | ______ | __________________ | ______ | __________________ | Yes / Pending | Restricted / None | __________________ | [ ] | [ ] |
| ______ | __________________ | Relief / roaming host | ______ | ______ | ______ | __________________ | ______ | __________________ | Yes / Pending | Restricted / None | __________________ | [ ] | [ ] |
| PACK | __________________ | Pack-down / site sweep | ______ | ______ | ______ | __________________ | ______ | __________________ | Yes / Pending | Restricted / None | __________________ | [ ] | [ ] |
6. Critical coverage check
| Function | Setup | Opening | Peak | Break relief | Closing/pack-down | Backup accepted |
|---|
| Shift authority | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
| Weather/wind monitoring | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
| Conversation hosting | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
| Data and device custody | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
| Safety/first aid/safeguarding | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
| Asset and site control | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
7. Shift briefing
| Briefing item | Instruction or trigger | Owner | Confirmed |
|---|
| Purpose and approved visitor message | ______________________________ | __________________ | [ ] |
| Footprint, public flow and accessible approach | ______________________________ | __________________ | [ ] |
| Wind, weather, heat and shutdown route | ______________________________ | __________________ | [ ] |
| Emergency, lost person and first aid | ______________________________ | __________________ | [ ] |
| Aggression, harassment and organiser escalation | ______________________________ | __________________ | [ ] |
| Safeguarding and photography | ______________________________ | __________________ | [ ] |
| Data notice, forms, device and follow-up custody | ______________________________ | __________________ | [ ] |
| Breaks, rotation, hydration and fit-for-task reporting | ______________________________ | __________________ | [ ] |
| Handover, site sweep and asset return | ______________________________ | __________________ | [ ] |
8. Shift handover
| Shift code | Outgoing lead | Incoming lead | Time | People/break status | Weather/site status | Assets/stock | Data/forms/device | Follow-up actions | Accepted |
|---|
| __________________ | __________________ | __________________ | ______ | __________________ | __________________ | __________________ | __________________ | __________________ | [ ] |
9. Public duty list
Do not include telephone numbers, full legal names where unnecessary, adjustment details, screening status or emergency contacts.
| Time | Public role | Preferred name | Stall zone | Ask this person about |
|---|
| ______ | __________________ | __________________ | __________________ | __________________ |
| ______ | __________________ | __________________ | __________________ | __________________ |
10. Actual shift record and learning
| Shift code | Actual attendance | Breaks delivered | Conversations | Enquiries handed to F05 | Late change/no-show | Weather or safety exception | Improvement owner/date |
|---|
| __________________ | ____ | ____ | ____ | ____ | __________________ | __________________ | __________________ |
Counts are operational learning measures, not permission to pressure visitors or add people to a marketing list.
11. Close-out and REVIEW approval
- [ ] Every person is signed off and has a safe departure plan.
- [ ] Equipment, weights, signs, keys, data, forms and devices are reconciled.
- [ ] Site sweep and organiser handback are accepted.
- [ ] Safety, safeguarding, welfare or privacy matters are transferred by restricted reference.
- [ ] Shift-level follow-up is owned and due-dated.
- [ ] Public copies and surplus contact exports are removed under the approved records route.
| Approval role | Name | Decision | Date | Evidence |
|---|
| Roster/shift lead | __________________ | Reconciled / Return for action | __________ | __________________ |
| Safety/data reviewer | __________________ | Controls accepted / Conditions | __________ | __________________ |
| Event lead | __________________ | Approved / Not approved | __________ | __________________ |
Until approved, this derivative remains REVIEW.