Community Organization

Why This Matters

A group of 30 people with good leadership and clear roles will outperform a group of 300 in chaos. Organization is not bureaucracy — it is the difference between a community that thrives and one that collapses into infighting within months. Every failed post-disaster group in history fell apart not from lack of food or shelter, but from lack of structure: unclear leadership, unfair work distribution, festering disputes, and no mechanism for making decisions. Getting this right early is the single most important thing you can do for long-term survival.

---

What You Need to Know

Core Concepts

• Leadership is a function, not a personality trait. You need someone (or a group) making decisions and being accountable. Charisma helps but is not required — reliability, fairness, and competence matter more.
• Division of labor multiplies output. Ten people each spending all day doing everything poorly will produce less than ten specialists who each master one domain.
• Decisions need a process. “Whoever shouts loudest wins” is not a process. It is a recipe for resentment and eventual violence.
• Conflict is inevitable. The question is not whether people will disagree, but whether your community has a way to handle disagreements before they become feuds.
• Record-keeping is governance. If decisions, work assignments, and resource inventories are not written down, they will be forgotten, disputed, and repeated.

Population Thresholds — What Changes as You Grow

Understanding these thresholds will help you anticipate problems before they happen.

5-15 People: The Band

At this size, formal governance is unnecessary. Everyone knows everyone. Decisions happen through conversation. A natural leader usually emerges — often the most competent or experienced person.

What works: Informal consensus. Talk things out around the fire.

What to watch for: Even at this size, freeloaders and personality conflicts can poison the group. Address problems directly and immediately. Do not let resentments build.

20-50 People: The Work Group

This is where things start requiring structure. Not everyone knows what everyone else is doing. Work needs to be divided and tracked. Disputes between people who barely know each other start occurring.

What you need:

• A recognized leader or small council (3-5 people)
• A skills inventory — who can do what
• A work rotation system
• A regular group meeting (weekly minimum)
• A simple dispute resolution process

50-150 People: The Village

You are approaching Dunbar’s number — the cognitive limit where humans can no longer maintain personal relationships with everyone. Gossip, reputation, and personal trust start failing as governance mechanisms.

What you need:

• Formal leadership structure with defined roles
• Written rules (even if basic)
• Specialized work teams with team leaders
• A dispute resolution system beyond “talk it out”
• Record-keeping for resources, decisions, and work assignments
• Defense planning and watch rotations

150-500 People: The Town

Beyond Dunbar’s number, you are governing strangers. Personal relationships cannot hold the community together. You need institutions.

What you need:

• Elected or appointed officials with defined terms
• Written legal code (see Law & Justice)
• Currency or formal trade system (see Trade & Currency)
• Education system (see Education)
• Specialized roles: judges, teachers, record-keepers, defense coordinators
• Tax or contribution system for communal resources
• Infrastructure planning

---

Method 1: Establishing a Council

The council is the simplest effective governance structure. It works well from about 20 people up to several hundred.

Step 1: Define the Council’s Purpose

Before choosing members, the whole community must agree on what the council does and does not do. Hold a full community meeting and establish these ground rules:

1. The council makes decisions on communal matters — resource allocation, work assignments, dispute resolution, defense, infrastructure projects
2. The council does NOT control personal matters — who you marry, what you eat from your own stores, how you spend your free time, your personal beliefs
3. The council is accountable — any community member can challenge a decision at the next open meeting
4. Decisions are recorded — every council meeting produces a written summary of decisions made, posted publicly or read aloud

Write these principles down. Post them where everyone can see them. This is your proto-constitution.

Step 2: Choose Council Members

There are three proven selection methods. Each has tradeoffs.

Option A — Election:

• Community votes for 3-7 members (odd number avoids ties)
• Term length: 3-6 months initially (short terms prevent entrenchment)
• Votes can be by show of hands (transparent but allows intimidation) or by secret ballot using marked stones in a container (fairer)
• Advantage: Perceived legitimacy — the people chose their leaders
• Disadvantage: Popularity contests; charismatic but incompetent people may win

Option B — Skills-Based Appointment:

• The community identifies 4-6 critical domains: food/agriculture, construction/shelter, medicine/health, defense/security, resource management, education/training
• The most competent person in each domain sits on the council
• Competence is determined by community recognition — who do people actually go to when they need help in that area?
• Advantage: Ensures expertise on the council
• Disadvantage: May exclude good generalists; conflicts if people disagree on who is “most competent”

Option C — Rotation:

• Every adult serves on the council for a fixed term (1-3 months)
• Rotation follows a set order (alphabetical, by household, by drawing lots)
• Advantage: Everyone understands governance; no power concentration; perceived as most fair
• Disadvantage: Some people are terrible at governance; continuity suffers

Recommended approach for most groups: Start with Option B (skills-based) for the first 6 months while the community stabilizes. Transition to Option A (election) once people know each other well enough to vote wisely. Use Option C elements for specific duties like night watch coordination.

Step 3: Establish Meeting Rhythms

Structure your governance around regular, predictable meetings.

Weekly Council Meeting (1-2 hours):

• Review work assignments and progress
• Address any disputes raised during the week
• Allocate resources for the coming week
• Hear proposals from community members
• Record all decisions

Monthly Community Assembly (2-3 hours):

• Council reports to the full community on what was decided and why
• Open floor for any community member to raise concerns
• Major decisions (new construction, trade agreements, rule changes) require community vote
• This is the accountability mechanism — the council answers to the assembly

Emergency Meeting:

• Called by any council member for urgent matters (attack, fire, disease outbreak, critical resource shortage)
• All adults expected to attend
• Decisions made by majority vote of those present

Step 4: Decision-Making Process

For each decision, follow this sequence:

1. Present the issue. One person describes the problem clearly. No solutions yet — just the problem.
2. Gather information. What do we know? What don’t we know? Who is affected?
3. Propose options. Any council member (or community member at assemblies) can propose a solution. List all options.
4. Discuss tradeoffs. For each option: who benefits, who loses, what are the risks, what resources are needed?
5. Decide. Use one of these methods:
   • Consensus — everyone agrees (ideal but slow; use for small groups or critical decisions)
   • Supermajority — 2/3 or 3/4 agree (good for important decisions)
   • Simple majority — more than half agree (fast; use for routine decisions)
6. Record the decision. Write down what was decided, who voted which way, and the reasoning.
7. Assign responsibility. Every decision must have a named person responsible for carrying it out and a deadline.

---

Method 2: Creating a Skills Inventory

A skills inventory is the foundation of efficient labor division. It answers the question: “What can each person do, and what does the community need?”

Step 1: Survey Every Person

Interview each community member (including children over about 10 — they often have useful skills). Record:

1. Name and household
2. Pre-collapse skills: Former occupation, hobbies, training, education. A retired nurse is invaluable. So is a former plumber, electrician, farmer, mechanic, teacher, or carpenter.
3. Current demonstrated skills: What has this person actually done successfully since the collapse? Theory matters less than practice.
4. Physical capabilities: Age, strength, mobility, health conditions. An older person with bad knees cannot do construction but might be an excellent teacher or record-keeper.
5. Learning interests: What does this person want to learn? Motivation matters — a motivated beginner often outperforms a reluctant expert.

Step 2: Categorize Community Needs

Map your needs into domains. A typical community needs:

Domain	Key Tasks	Critical?
Water	Purification, distribution, well maintenance	Yes
Food — Farming	Planting, tending, harvesting, seed saving	Yes
Food — Hunting/Gathering	Hunting, trapping, foraging, fishing	Yes
Food — Preservation	Smoking, drying, salting, fermting, root cellaring	Yes
Construction	Building, repair, carpentry, masonry	Yes
Medicine	First aid, herbalism, surgery, midwifery	Yes
Defense	Watch duty, perimeter security, weapons training	Yes
Energy	Generator maintenance, fuel, electrical systems	Moderate
Metalworking	Tool making, repair, forging	Moderate
Textiles	Clothing, rope, fabric, sewing, repair	Moderate
Education	Teaching children, preserving knowledge	Moderate
Governance	Record-keeping, dispute mediation, planning	Moderate
Sanitation	Latrine maintenance, waste management, hygiene	Yes

Step 3: Match People to Roles

Create a matrix: people on one axis, domains on the other. Mark each person’s skill level:

• E = Expert (can teach others)
• C = Competent (can work independently)
• B = Beginner (needs supervision)
• blank = No skill/experience

Look for critical gaps. If nobody has medical experience, that is an emergency training priority. If only one person can forge metal, they need to start teaching immediately — what happens if they get injured?

Rules for assignment:

1. Every critical domain must have at least two competent people (redundancy)
2. No person should hold more than two primary roles (burnout prevention)
3. Pair experts with beginners for on-the-job training
4. Rotate unpleasant tasks (latrine duty, night watch) among all able-bodied adults

---

Method 3: Setting Up Work Rotations

Fair work distribution prevents the most common source of community resentment: the perception that some people work harder than others while freeloaders coast.

Step 1: Classify Work Types

Daily essential work — must happen every day regardless:

• Cooking (communal meals)
• Water purification and distribution
• Fire maintenance
• Childcare
• Watch duty (day and night shifts)
• Animal care (if livestock)
• Sanitation (latrine, waste)

Scheduled project work — regular but not daily:

• Farming (seasonal cycles)
• Construction and repair
• Hunting and foraging expeditions
• Firewood collection
• Tool making and repair

Specialist work — requires specific skills:

• Medical care
• Teaching
• Metalworking
• Governance and record-keeping

Step 2: Create a Rotation Board

Build a physical board (a large flat piece of wood, a wall section, or a stretched hide) that everyone can see. Create a grid:

• Columns: Days of the week
• Rows: Tasks
• Cells: Names of people assigned to each task on each day

Rules for filling the board:

1. Every able-bodied adult works. No exceptions except for illness or injury.
2. Daily essential tasks rotate — nobody gets stuck on latrine duty every day.
3. Specialist tasks go to the skilled person but they are exempt from an equivalent amount of rotation duty.
4. Post the board publicly at the start of each week.
5. Track completion. A council member or designated person checks tasks off each evening. Patterns of non-completion are addressed at the weekly council meeting.

Step 3: Handle Freeloaders

Every community has them. Someone who consistently avoids work, does tasks poorly, or disappears during their shifts. Handle this with a clear escalation process:

1. First instance: Private conversation. “We noticed you missed your shift. Everything okay?” Assume good faith initially.
2. Second instance: Public mention at the weekly meeting. “We need everyone pulling their weight. Here is the record.”
3. Third instance: Reduced resource share. If someone is not contributing, their share of communal resources (food, shelter quality, preferred tasks) decreases proportionally.
4. Persistent refusal: Community assembly decides the consequence — which may include expulsion in extreme cases.

Document every step. Fairness requires a paper trail.

---

Conflict Resolution Basics

Before you have a formal legal system (see Law & Justice), you need a basic way to handle disputes.

The Three-Step Process

Step 1 — Direct Conversation: The two people in conflict talk to each other privately. Most disputes resolve here. The rule: each person speaks without interruption for 3 minutes, then the other responds. No yelling. No threats.

Step 2 — Mediation: If direct conversation fails, a neutral third party (council member, respected elder, or anyone both parties trust) mediates. The mediator does NOT decide the outcome — they help the parties find a solution both can accept.

Mediation process:

1. Each party states their version of events without interruption
2. The mediator restates each position to confirm understanding
3. The mediator asks: “What would make this right for you?” to each party
4. The parties negotiate, guided by the mediator
5. If agreement is reached, it is written down and both parties sign or make their mark

Step 3 — Council Decision: If mediation fails, the dispute goes to the council. The council hears both sides, asks questions, and makes a binding decision by majority vote. Both parties must accept the outcome. If someone refuses to accept a council decision, that is a threat to community order and is treated as a separate, more serious matter.

---

Defense Planning

Even the most peaceful community needs defense planning. Other groups may not be friendly. Wildlife is a threat. Natural disasters require organized response.

Basic Defense Structure

1. Watch rotation: 24-hour coverage, minimum 2 people per shift, 4-hour shifts. Watchers must have a way to alert the community (bell, horn, whistle).
2. Perimeter: Define your community’s boundary. It does not need to be a wall — cleared sight lines, noise-making tripwires (cans on string), and designated entry points are sufficient initially.
3. Response plan: Everyone must know what to do when the alarm sounds. Designate a rally point. Assign roles: fighters, evacuators (for children and injured), fire response.
4. Weapons policy: Decide early whether weapons are communally stored or individually kept. Both approaches have tradeoffs. Communal storage is safer but slower to deploy. Individual storage is faster but risks internal violence.
5. Diplomacy first: When encountering other groups, establish trade relationships before they become adversarial. A neighbor who trades with you has incentive to keep you alive.

---

Record-Keeping for Governance

Even before you have a formal writing system, governance requires records. Use whatever medium is available: paper, bark, clay tablets, charcoal on flat wood.

What to record:

• Council decisions (date, decision, vote, reasoning)
• Work assignments and completion
• Resource inventory (food stores, tools, materials, weapons)
• Skills inventory (updated as people learn or join)
• Disputes and resolutions
• Population (births, deaths, arrivals, departures)
• Trade agreements with other communities

Who keeps records: Designate a record-keeper — someone literate, detail-oriented, and trustworthy. This is one of the most important roles in the community. Backup the records: keep copies in two locations.

---

Common Mistakes

Mistake	Why It’s Dangerous	What to Do Instead
No defined leadership	Decisions stall or get made by whoever is loudest; resentment builds among quieter members	Establish a council within the first week, even if informal
One person holds all power	Single point of failure; power corrupts; community has no recourse if leader is wrong	Always use a council (3+ members); rotate leadership roles
No regular meetings	Problems fester; people feel unheard; rumors replace information	Weekly council + monthly assembly minimum
Ignoring freeloaders	Hard workers resent carrying the lazy; morale collapses; more people stop contributing	Address non-contribution early and publicly with a clear escalation process
Making rules for problems that do not exist yet	Creates resentment and bureaucracy; rules feel oppressive without justification	Only create rules in response to actual problems
Not writing decisions down	”I never agreed to that” — disputes over what was decided multiply	Record every council decision; post or announce publicly
Assigning all hard work to newcomers	Newcomers feel exploited and leave or rebel; community gains reputation as hostile	Rotate unpleasant tasks among all members equally
No conflict resolution process	Small disputes escalate to violence; factions form; community splits	Establish the three-step process (conversation, mediation, council) on day one
Ignoring children and elderly in planning	Children grow up without skills; elderly knowledge is lost; both groups feel useless and become depressed	Include everyone in the skills inventory; assign age-appropriate roles
Purely democratic votes on every decision	Decision fatigue; trivial matters consume hours; urgent decisions are delayed	Delegate routine decisions to the council; reserve community votes for major issues

---

What’s Next

With a functioning organizational structure, your community is ready to build more sophisticated systems:

• Next step: Law & Justice — formalize your rules, establish proportional consequences, and create a dispute resolution system that can handle serious conflicts
• Next step: Trade & Currency — once your community is organized, you can begin trading with other groups and establishing economic systems
• Related: Cartography & Surveying — mapping your territory supports defense planning and resource management
• Foundation for: Education — organized communities can sustain education programs that isolated individuals cannot

---

Quick Reference Card

Community Organization — At a Glance

Population thresholds:

• 5-15: Informal consensus
• 20-50: Need council, skills inventory, work rotations
• 50-150: Need formal rules, record-keeping, specialized teams
• 150-500: Need written laws, currency, institutions

Council setup:

1. Define council scope (communal decisions only)
2. Select 3-7 members (skills-based initially, then elections)
3. Weekly council meetings + monthly community assemblies
4. Record all decisions in writing

Decision process: Present issue ⇒ Gather info ⇒ Propose options ⇒ Discuss tradeoffs ⇒ Vote ⇒ Record ⇒ Assign responsibility

Conflict resolution:

1. Direct conversation between parties
2. Mediation by neutral third party
3. Council binding decision

Work rotation rules:

• Every able adult works
• Unpleasant tasks rotate equally
• Track completion publicly
• Escalate freeloading: private talk ⇒ public mention ⇒ reduced share ⇒ expulsion

Critical records to keep: Decisions, work logs, resource inventory, skills inventory, disputes, population, trade agreements