Skip to content
The first pages of the Open Source Governance Document template

Open Source Governance Document

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Difficulty
Beginner
Updated
November 12, 2026

Every page (7)

Overview

Community projects stall when nobody knows who decides, how a vote passes or what happens after a dispute. This Google Docs template sets those rules out in seven pages, starting with roles and a RACI table, then decision-making, elections, stakeholders, a risk register and the amendment process, with a guide page at the end. Each section answers one question a contributor or a funder will ask before committing time or money to the project.

The sample describes a fictional foundation, Wrenfield Software, with a five-member steering group, a two-thirds rule for changes and a three-person panel for disputes. Its names, phone numbers, budget figures and vote thresholds are sample data. Replace the roles, the thresholds and the election calendar first, then have a lawyer check the licence and contributor terms before the document is adopted.

Useful for

  • A foundation adopting its first written rules before accepting outside funding
  • A maintainer group setting out how votes pass after a split decision
  • A steering group reviewing its election rules before the spring ballot

What's included

  • Cover page with the document version and the approval date
  • Roles page with contacts and a RACI table of key deliverables
  • Decision-making summary with the headline figures and routine vote rules
  • Stakeholder page listing who is consulted before each vote
  • Risk heatmap and register with owners and agreed responses
  • Amendment page with numbered clauses and a highlighted key rule

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the steering group, maintainers and contact details on the roles page with your own.

  3. 3

    Set the voting thresholds and election calendar to match your charter, then check them with counsel.

  4. 4

    Keep the risk register current by reviewing it at every steering group meeting.

  5. 5

    Delete the guide page, then share the document with the steering group for adoption.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Are the organisation, people and figures real?

No. Wrenfield Software, its steering group, the .example email addresses, phone numbers, budget figures and vote thresholds are fictional sample data. Replace them with your own before adopting the document.

Does this replace a constitution or charity documents?

No. It sets out internal rules for decisions and elections, and it should sit alongside any articles of association, trust deed or contributor licence the project needs. Ask a lawyer to check it.

How often should the document change?

Review it once a year and whenever a dispute exposes a gap. Each change needs a vote under the amendment rules, a new version number and a dated entry in the change log.

  • #open-source-governance
  • #project-governance
  • #decision-making
  • #steering-group
  • #google-docs
  • #governance-template

More contributing guide templates

See all 8

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…