> For the complete documentation index, see [llms.txt](https://docs.contributionism.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contributionism.io/implementation-and-organisational-lifecycle/tools-templates-and-operating-processes.md).

# Tools, templates and operating processes

Contributionism can be implemented using ordinary organisational tools. The priority is reliable rules and records, not technological complexity.

## **A practical documentation set**

An organisation may use the following templates.

**Configuration statement**

Summarises:

* Purpose.
* Beneficiaries.
* Legal structure.
* Primary governance group.
* Compensation approach.
* Treatment of historical rights.

**Contributor agreement**

Records:

* Accepted contribution.
* Compensation.
* Risks.
* Rights.
* Duration.
* Departure and dispute terms.

**Contribution and rights registers**

Track contributions, active entitlements, payments and expiry.

**Distribution worksheet**

Calculates:

* Available distribution pool.
* Eligible rights.
* Allocation weights.
* Caps.
* Payments.
* Remaining entitlements.

**Leadership mandate**

Defines authority, duration, review and removal.

**Decision log**

Records proposals, approvals, conflicts of interest and implementation responsibilities.

**Departure statement**

Summarises the rights and obligations remaining when someone leaves.

## **A recurring operating cycle**

A typical cycle might include:

1. Agreeing roles and budgets.
2. Recording accepted contributions.
3. Paying current compensation.
4. Reviewing selected outcomes.
5. Updating rights.
6. Assessing cash and distribution capacity.
7. Approving payments.
8. Processing expiry.
9. Reviewing governance and risks.

The timing can be monthly, quarterly, annually or linked to milestones. Not every process must occur at the same frequency.

## **Spreadsheets**

Spreadsheets can be sufficient for a small organisation. Useful safeguards include:

* Protected formulas.
* Separate input and output areas.
* Version history.
* Clear units and dates.
* Independent review.
* Reconciliation with payment records.
* Tests for missing or duplicated entries.

A spreadsheet should not silently change historical rights when a parameter is edited.

## **Dedicated software**

As complexity grows, software may provide:

* Role-based access.
* Automated expiry.
* Approval workflows.
* Audit trails.
* Contributor statements.
* Voting records.
* Financial integration.

Software should support the agreed rules rather than introduce hidden assumptions.

## **Automation and AI**

Automation can reduce repetitive work. AI may assist with summarising contribution evidence or identifying inconsistencies, but its output should not be treated as an authoritative valuation. Potential problems include bias, missing context, inaccurate attribution, overweighting measurable outputs, inability to explain a decision and exposure of confidential information. People should be able to challenge consequential automated assessments.

## **Blockchain and smart contracts**

A blockchain may help record transactions or execute defined payment rules. However, it does not establish:

* Whether work was valuable.
* Whether a valuation was fair.
* Whether input data was accurate.
* Whether a contract complies with law.
* Whether a disputed decision should be reversed.

Automated execution can make errors harder to correct. Upgrade, pause and dispute mechanisms require careful design.

## **Administrative proportionality**

Tools should be evaluated against their cost. Useful questions include:

* How much time does the process take?
* Which disputes does it prevent?
* Which decisions does it improve?
* Could a simpler process achieve the same result?
* Are contributors actually using the information?

An organisation should not devote excessive resources to measuring contribution at the expense of making useful contributions.