PRFM1603 Chap.9 Protocols, Authority, and Gathering Ground
Protocols, Authority, and Gathering Ground
Protocol is not a universal checklist that grants automatic safety. It is a relationship-based practice for learning who holds authority, what responsibilities attach to an encounter and how decisions should be made. This chapter examines protocol through gathering ground, where cultural, institutional and public relations overlap.
A project may have administrative permission while lacking cultural authority, or may follow a formal rule while ignoring the reason behind it. The protocol pathway therefore begins with place and people, moves through consultation and consent, and remains open to revision or refusal. Documentation should record decisions without exposing restricted knowledge.
Accountability appears in who can stop the work, how disagreement is handled and what obligations continue after the event.
What this chapter covers
- 01
Protocol as relationship rather than checklist
- 02
Administrative and cultural authority
- 03
Consultation, consent and ongoing revision
- 04
Gathering ground as overlapping relation
- 05
Refusal and the power to stop
- 06
Documentation without extraction
Worked example · free
Build a protocol pathway for a gathering
- 1Identify Traditional Custodians, relevant community or cultural authorities, venue managers, everyday users and responsibilities attached to the place.
- 1Seek guidance through appropriate channels, explain the proposed action clearly and allow time for response or refusal.
- 1Record conditions, attribution, documentation limits and who can halt or change the project as it develops.
- 1Plan return, reporting and care after the event rather than treating consent as a single completed transaction.
Key terms
- Protocol
- Relationship-based guidance governing respectful conduct, authority, responsibility and decision-making in a particular context.
- Administrative permission
- Formal approval from an organisation controlling access, scheduling, safety or property.
- Cultural authority
- Recognised responsibility and right to guide the use, interpretation or restriction of cultural knowledge and practice.
- Ongoing consent
- Permission treated as revisable across changing actions, recordings, audiences and circulation.
- Refusal pathway
- A clear process through which an authorised person can pause, alter or stop the work without penalty.
Protocols, Authority, and Gathering Ground FAQ
Why is a protocol not just a checklist?
A checklist can prompt useful questions, but it cannot determine authority or replace relationship. Protocol changes with place, people, knowledge and purpose. Following generic steps without listening may reproduce the very extraction the process is meant to prevent. The maker must understand why a condition exists and remain responsive to guidance and refusal.
Can venue permission cover cultural use?
Not necessarily. A venue manager can authorise access and operational conditions but may not hold authority over cultural knowledge, representation or significance. Separate the forms of permission and identify who can speak to each. If the correct authority is uncertain, pause and seek guidance rather than treating administrative approval as complete consent.
How should consultation be documented?
Record who was approached, the scope of the proposal, decisions, conditions, changes and agreed forms of credit or return. Do not reproduce restricted knowledge merely to prove consultation occurred. Confirm what can be recorded and who can access it. Documentation should support accountability while respecting the limits set by the relationship.
Assessment move
Draft a protocol map with distinct lanes for cultural authority, site access, participant consent, public impact and documentation. Place a named question and decision point in each lane. Then rehearse a change scenario: a performer proposes a new object, the audience route expands, or recording is added. Trace which approvals must reopen. This exercise reveals whether consent has been treated as ongoing.
Write a refusal pathway that makes stopping possible without forcing an affected person to argue against group momentum. In the exegesis, analyse how protocol altered the work form and authority structure, not merely that the group was respectful. Run the change scenario again after the live event, when a photograph is requested for publicity or an archive is proposed.
Identify which earlier agreement applies, which new audience and risk appear, and who has power to decide. Record the response without turning private guidance into displayable proof. Compare administrative approval with cultural authority and participant consent in separate columns so that one cannot silently substitute for another.
Rehearse the refusal pathway with the group: who pauses activity, communicates the decision and removes material without demanding justification from the person affected. In analysis, name the design feature that changed because of protocol and the authority relation that produced the change. This is stronger than presenting good intentions as evidence of accountable collaboration.
The protocol map should remain available during rehearsal so a late creative idea reopens the relevant permission instead of inheriting consent from an earlier, narrower proposal. Review the map again before publication because circulation can create a new audience, purpose and decision point.
