Plain language
Standards and templates should be written for people who may not have formal legal, security, compliance, or operations backgrounds.
Governance
Small Organization Records Framework is currently an early public draft. This page explains how the project approaches editorial review, versioning, contribution boundaries, and future governance.
Current status
Small Organization Records Framework is not yet a formal standards body, certification program, membership association, or accredited organization. The current project is a public documentation initiative publishing early standards, templates, and educational resources.
The materials are being developed carefully, but they should be treated as draft resources that may change over time.
Editorial principles
The project is guided by a few simple editorial principles. These principles help keep the standards useful for small organizations without turning them into heavy compliance documents.
Standards and templates should be written for people who may not have formal legal, security, compliance, or operations backgrounds.
The project should focus on records that people can realistically maintain, review, and use during normal operations or disruptions.
Templates should avoid encouraging people to store passwords, API keys, recovery codes, sensitive records, or private information in unsafe places.
The project should avoid presenting general documentation resources as legal, tax, financial, insurance, cybersecurity, compliance, or incident-response advice.
Changes should be made carefully, with version numbers and plain explanations where possible.
The project should avoid assuming that every organization uses the same laws, tools, terminology, business structures, or local practices.
Versioning
Version numbers help readers understand whether a standard or template is an early draft, stable release, or revised version.
Review boundaries
Small Organization Records Framework does not review, approve, audit, certify, or validate how any organization uses the standards or templates.
The project does not determine whether an organization is compliant, secure, protected, operationally resilient, legally prepared, financially prepared, or properly insured.
Future governance
If the project grows, future governance may include contributor guidelines, public issue tracking, editorial review notes, release histories, translation guidance, advisory contributors, or a more formal public-benefit structure.
For now, the priority is to publish clear draft standards, make the templates useful, and review the materials carefully before treating anything as stable.