Marches

Marches

Summary

Marches assemble participants to move together along a public route as a visible, kinetic declaration of presence, grievance, or solidarity. When invoked, this planning-only skill produces a March Planning Package: purpose, audience and turnout model, legal / permitting posture, route and logistics plan, roles and staffing, marshalling / safety / accessibility plan, communications and documentation plan, contingency plan, debrief criteria, completion ledger, and readiness verdict. Like other atomic methods, march effectiveness is difficult to isolate at the tactic level; most documented cases pair marches with other tactics rather than treat them as standalone.

When to Consult This Skill

Consult when any of the following conditions apply:

• a planner seeks a visible, mid-to-high participation threshold assembly tactic
• the campaign needs a dateable, countable public moment to anchor subsequent narrative work
• a planner is preparing a specific march and needs a preparation pattern
• a user needs a planning package, readiness verdict, or unresolved-assumptions list before committing to a route
• a risk assessment is needed for processional action under counter-mobilization, kettling, or dispersal conditions
• a planner considers a speech, rally, or vigil at the start or endpoint of the route

Core Mechanism

The tactic operates through coordinated movement in public space. Pressure flows through four channels:

• Enumeration. A visible column produces a countable turnout, legible as an estimate of constituency size.
• Spatial claim. Moving through a specific route, such as around a capitol, past an embassy, or through a commercial district, asserts public standing on contested ground.
• Narrative anchor. The event provides a dateable reference point that coverage, memorials, and subsequent tactics refer back to.
• Shared risk. Participants visibly adopt some portion of the campaign's risk surface together, which tends to lower the perceived cost of entry for later recruits.

Target audiences include pillar-institution fence-sitters, sympathetic majorities, international observers, and the opponent. A march differs from a static speech act primarily in that its core signal is participation and spatial presence rather than authorship.

Typical Roles and Participants

Roles observed across documented cases:

• Marchers. Core participants whose count and composition produce the primary signal.
• Marshals / stewards. Visible role-bearers who manage pace, route, and de-escalation at flashpoints.
• Route lead and tail. Designated lead and closing contingents that shape pace and legibility.
• Documentarians. Photographers, videographers, and livestreamers who extend reach beyond the route.
• Medics and legal observers. Specialist roles whose presence is documented in many cases, particularly in adversarial environments.
• Speakers / convenors. Frequently present at start or endpoint.
• Bystanders and witnesses. Uninvolved observers whose accounts enter the documentary record.

Roles are descriptive; many marches compress these into fewer people, particularly smaller decentralized events.

Enabling Conditions

Marches tend to be legible rather than symbolic filler when several conditions correlate:

• a route that connects a start point, a claimed object of attention, and an endpoint with practical exit
• an organizing network able to mobilize and confirm turnout before the day
• legal posture: assessed permission or tolerated practice for the specific route, date, and composition
• marshalling capacity proportional to crowd size
• documentary infrastructure, including image and video capacity and real-time reporting channels
• timing that allows press pick-up and connects to a broader narrative arc
• an articulated reason participants are marching, usually linked to a shared slogan, symbol, or demand

Absence of several conditions reduces legibility but does not predict failure; documented cases include marches that mattered despite thin infrastructure when external events amplified them.

Risk Signals and Escalation Triggers

Outcomes tend to be worse when:

• route design creates kettling or chokepoint vulnerabilities that shift initiative to security forces
• counter-mobilization by hostile groups uses the route as a fixed target
• security response frames the march as disorder, shifting coverage to arrests, dispersal, or property damage
• a violent flank, whether participant, infiltrator, or opportunist, captures coverage and recontextualizes the event
• the route transits neighborhoods or communities whose consent was not secured, inviting legitimate counter-framing
• weather, timing, or logistics collapse turnout below visible threshold, producing a countable-but-weak signal
• opponents pre-seed the press with a frame that primes selective coverage
• legal overreach (mass arrest, charges under restricted-assembly statutes) shifts the contest into a legal arena the campaign may not have prepared for

These are descriptive historical tendencies, not mitigation instructions. Any specific march is low-risk only after a context-specific assessment: the profile is highly path-, date-, and regime-specific.

How to Prepare

Use this skill for planning only. The agent can produce a March Planning Package and readiness verdict, but it cannot perform the real-world assembly.

Load the reference files as needed:

• Planning protocol. Use references/planning-protocol.md to follow the phase map, track artifacts, record skipped or assumed items, and return a readiness verdict.
• Intake. Use references/intake-questionnaire.md to gather purpose, audience, turnout model, route idea, legal posture, accessibility needs, constraints, counter-mobilization concerns, and endpoint.
• Route and logistics. Use references/route-and-logistics.md to assess route fit, start / end points, exits, transit, weather, sound, signs, accessibility, toilets, water, and documentation vantage points.
• Legal posture. Use references/legal-permit-and-rights-check.md to identify jurisdiction-specific permit, public-forum, recording, and legal-observer questions. This is informational, not legal advice.
• Marshalling and safety. Use references/marshalling-safety-and-accessibility.md to plan role boundaries, steward communication, de-escalation posture, accessibility support, and medical / legal coordination.
• Communications and debrief. Use references/communications-documentation-and-debrief.md to define message frame, press packet, turnout estimate method, image / video plan, post-event materials, and learning loop.

Preserve source discipline throughout: do not invent permits, legal rules, turnout estimates, endorsements, safety capacity, or public facts. Do not advise deception, coercion, violence, property damage, evasion of lawful constraints, or unsafe confrontation.

Sources

Primary (descriptive, taxonomic):

• Beer NVI #4 / Sharp #038: the canonical entry for "Marches" in Sharp's Processions subcategory (methods 37-43).
• Albert Einstein Institution, 198 Methods of Nonviolent Action.
• Michael Beer / ICNC, Civil Resistance Tactics in the 21st Century.
• Full source index: ../../methods-registry/03-sources-and-references.md

Secondary (preparatory, training-derived, paraphrased):

• The Commons march organizing guide: logistics, symbolic activity, and event planning prompts.
• The Commons effective nonviolent actions guide: context, audiences, action choice, alignment, documentation, and evaluation.
• ACLU Protesters' Rights and ACLU NorCal protest guidance: public-forum, permit, recording, and time / place / manner considerations.
• Legal observer instructions: observer role boundaries, preparation, notes, and legal / medical coordination.
• Beautiful Trouble training and Amnesty right-to-protest materials: tactical safety, audience fit, debrief, and right-to-protest framing.
• CANVAS / ICNC training patterns, Swarthmore case observations, and standard movement marshalling practice.

Evidence caveat: ../../civil-resistance-evidence-and-critique.md: method-level effectiveness claims for marches in isolation outrun the evidence base; treat marches as one component of broader campaign arcs.

Definition of Done

User-value checks for this skill. Keep boxes unchecked; they are review criteria, not author attestation. Generic repository lint rules live in skills-catalog/README.md.

• Intake is complete, or missing facts are listed for the user to supply or verify.
• Legal / permitting posture is jurisdiction-specific or explicitly marked as unknown.
• Route and logistics plan covers start, endpoint, exits, transit, accessibility, weather, communications, and documentation vantage points.
• Roles and staffing plan covers marshals / stewards, documentarians, media, legal, medical, accessibility, and endpoint ownership.
• Risk and contingency review distinguishes route-design risks, counter-mobilization risks, legal risks, accessibility risks, and narrative risks.
• Final March Planning Package includes completion ledger and readiness verdict.

Version: 0.5.0 Last Updated: 2026-04-25