Open the repository
View official files, governance documents, changelog entries, review activity, issues, and release history.
Open GitHubContribute
Help improve SORF through public review.
SORF welcomes practical feedback from people and organizations with different levels of experience. Public feedback, review records, issues, and proposed changes are handled through the official SORF GitHub repository.
Where to contribute
Use the official SORF GitHub repository.
GitHub is used as SORF’s public development record. This helps keep feedback, review decisions, version history, and official changes traceable over time.
Submit feedback
Use GitHub Issues to submit corrections, clarity concerns, safety concerns, review comments, or proposed improvements.
Go to IssuesRead contribution guidelines
Understand contributor pathways, public review records, acknowledgement rules, and how suggestions are reviewed.
Read guidelinesContributor pathways
Different kinds of feedback are welcome.
You do not need to be a technical expert to contribute. SORF values practical feedback from people using the framework as well as specialist review from professionals, educators, implementers, and institutions.
Basic user or adopting organization
Share what was easy to understand, what was confusing, what felt missing, or whether a template was practical for a real small organization.
Pilot contributor
Test SORF more deliberately across documents, workflows, teams, or organizational situations, then share practical adoption feedback.
Professional reviewer
Review SORF for clarity, boundaries, risk concerns, unsafe assumptions, missing disclaimers, or practical improvements based on field experience.
Educational reviewer
Evaluate whether SORF is understandable for learners, useful in workshops or classes, and clear enough for teaching practical recordkeeping habits.
Technical implementer
Suggest improvements related to field structure, terminology, versioning, accessibility, exports, forms, or machine-readable records.
Standards or institutional reviewer
Help evaluate scope, terminology, governance, public review records, development process, or possible future standards pathways.
What to submit
Useful feedback is specific, safe, and practical.
The most useful submissions explain what document or section is being reviewed, what concern or improvement was noticed, and why the change may help small organizations.
Clarification suggestions
Point out wording that feels confusing, too broad, too narrow, too technical, or difficult for small organizations to apply.
Template improvements
Suggest safer, clearer, or more useful fields, prompts, labels, examples, or instructions.
Safety concerns
Report guidance that could encourage unsafe recordkeeping, expose confidential information, or be misunderstood as professional advice.
Accessibility improvements
Suggest changes that make SORF easier to read, navigate, translate, teach, or use with assistive tools.
Implementation concerns
Identify issues that affect forms, exports, structured data, software tools, versioning, or practical implementation.
Misleading use reports
Report altered documents presented as official SORF releases, false endorsement claims, removed attribution, or unofficial copies that may confuse users.
How review works
Suggestions are reviewed before becoming official.
Not every suggestion can or should become part of the official framework. Suggestions are reviewed for usefulness, safety, clarity, evidence, scope fit, consistency, and benefit to small organizations.
Change review method
Read how SORF evaluates suggestions before they become part of the official framework.
Read methodReview record policy
Learn how SORF records feedback, decisions, contributor permissions, and public review history.
Read policyGovernance
Understand how SORF is stewarded, how decisions are documented, and how official releases are protected.
Read governanceWhat not to send
Keep private information out of public submissions.
GitHub Issues may be public. To protect contributors and organizations, do not submit information that should remain private, confidential, regulated, or securely stored elsewhere.
Endorsement boundary
Contribution does not imply endorsement.
Submitting feedback to SORF does not mean the contributor endorses SORF. Being acknowledged by SORF does not mean the contributor, their employer, their institution, or their organization certifies, approves, sponsors, or formally supports SORF.
Any formal endorsement, certification, approval, partnership, or recognition must be separately agreed in writing.