Onboarding Protocol

Download this template

Generated 2026-04-29 · Download all templates

  • Layer: 1 — Membership System
  • Status: Template — adapt for your community
  • RCOS reference: §3.2, §3.3, §3.8

Admission Criteria

RCOS clauses: 3.2.3, 3.2.4

Why write down who gets in?

Admission is the moment a stranger becomes bound by — and protected by — the community’s rules. If the criteria are informal, the decision collapses into whoever happens to like the applicant. Written criteria make admission a governance act, not a social favor, and make rejection defensible on grounds the community can point to.

How to fill this in

State the explicit conditions under which an applicant may be admitted. Each criterion should be testable from the application itself or from an external check.

Onboarding Steps

RCOS clauses: 3.2.1, 3.2.2

Why make the process a fixed sequence?

Consent to governance only means something if the member has actually seen the governance. A fixed sequence — review, consent, technical setup — ensures every Full Member crossed the same threshold in the same order, so nobody slips into full rights without having encountered the constraints that come with them.

How to fill this in

List the ordered steps every new member must complete to move from applicant to Full Member. Include explicit consent steps and any tooling/access provisioning required.

Initial Membership State

RCOS clauses: 3.1.2, 3.1.4

Why assign a state at the end of onboarding?

Between “applicant approved” and “fully integrated” there is a real gap — permissions, access, and expectations all change. Declaring the exact state a new member holds at each step removes ambiguity about what they can do right now, and prevents unintentional grants of rights before onboarding is complete.

How to fill this in

State the membership states a member transitions through during onboarding, and what triggers each transition. Reference the Membership State Registry.

  • On approval:
  • On onboarding completion:

Trial and Evaluation

RCOS clauses: 3.3.1, 3.3.2, 3.3.3, 3.3.4

Why bound the trial period?

An unbounded trial is a second-class membership that never ends — all obligations, fewer rights. Fixing the duration, the criteria, and the failure path forces a decision point: either the new member transitions into full standing or a defined exit runs. It prevents the trial state from becoming a permanent holding pen.

How to fill this in

Define the duration, evaluation criteria, transition decision, grace period, failure path, and any extension rules. Trial rights are defined in the Membership State Registry.

  • Duration:
  • Evaluation criteria:
  • Transition decision:
  • Grace period:
  • Failure to complete:
  • Extension:
  • Rights during trial:
  • Re-application block:

Completion Record

RCOS clauses: 3.8.2

Why keep the record permanent?

The completion record is the evidence that a member consented to a specific version of the rules on a specific date. Losing or editing it would make it impossible to answer, months or years later, “what exactly did they agree to?” — which is the only question that matters when a dispute arrives.

How to fill this in

State where the completion record is kept, what it captures (timestamp, artifact versions consented to), and the retention rule.


Ratification Record

  • Adopted:
  • Decision type: Strategic
  • Version:
  • Decision record:

RCOS Blueprint by EcoHubs

A modular operating system that defines how intentional communities organize — from governance and roles to resource sharing and conflict resolution — in support of resilience, fairness, and regeneration.

Connect

© 2026 EcoHubs Platform. All rights reserved.