Early public draft

Small Organizations Records Framework.

A practical public documentation framework for small organizations that need clearer records for responsibilities, vendors, access references, continuity notes, incident timelines, and review routines.

SORF is independently stewarded and currently in early public draft. Official files, releases, version history, and public review records are maintained through the official SORF GitHub repository.

Purpose

Helping small organizations document what matters.

Many small organizations rely on memory, informal habits, scattered accounts, and one or two key people who know how everything works. SORF provides plain-language records and templates that help make essential information easier to understand, review, and hand off.

Learn the framework

Understand the core record areas, why they matter, and how SORF helps small organizations document responsibilities, vendors, access references, continuity, and review routines.

Start learning

Download official templates

Official SORF templates and release packages are published through GitHub Releases so users can verify versions, release notes, and source history.

Get downloads

Contribute or review

SORF welcomes practical feedback from adopters, pilot users, professional reviewers, educators, technical implementers, and institutional reviewers.

How to contribute

Framework areas

Practical record areas for operational clarity.

SORF begins with records that many small organizations need, regardless of industry, country, or organizational structure.

Access References

Document where access is managed without recording passwords, API keys, recovery codes, private keys, seed phrases, or other secret values.

Learn more

Vendor Inventory

Maintain a clear list of vendors, services, subscriptions, tools, and outside relationships the organization depends on.

Learn more

Responsibility Records

Clarify who owns, maintains, reviews, and supports important records, services, vendors, and processes.

Learn more

Continuity Notes

Preserve essential context if a founder, owner, maintainer, director, or key person becomes unavailable.

Learn more

Incident Timeline

Record neutral timeline notes during outages, disruptions, vendor issues, access problems, or operational incidents.

Learn more

Review Routines

Keep documentation useful through simple, realistic review habits that match the organization’s size and capacity.

Learn more

Official releases

Downloads are handled through GitHub.

The SORF website explains the framework and helps users find the right materials. Official templates, release packages, changelogs, and public development history are maintained in the official GitHub repository.

Latest official release

Download the latest official SORF release package from GitHub Releases.

Download on GitHub

View the repository

Review source files, governance documents, changelog entries, issues, and public development history.

Open repository

Submit feedback

Use GitHub Issues to submit feedback, safety concerns, review comments, or proposed improvements.

Go to Issues

Public review

SORF improves through documented review.

SORF welcomes different kinds of contribution from different levels of experience. A small organization using the framework may notice practical confusion. A professional reviewer may identify risk or boundary issues. A technical implementer may identify structure or versioning needs.

Public feedback, review records, and official changes are handled through GitHub so SORF can preserve a transparent development record. Contribution does not imply endorsement, certification, approval, partnership, or formal representation of SORF.

Important disclaimer

SORF is not professional advice.

SORF is provided for educational and organizational planning purposes. It is not legal, tax, financial, accounting, insurance, cybersecurity, regulatory, compliance, or professional advice. SORF does not certify, audit, approve, or verify organizations.

Organizations remain responsible for determining what records are appropriate for their own circumstances and requirements. SORF should not be used to store passwords, private keys, seed phrases, API credentials, recovery codes, or other secret values.