Suggest clarifications
Point out wording that feels confusing, too broad, too narrow, too technical, or difficult for small organizations to apply.
Contribute
Help improve the documentation standards.
Small Organization Records Framework is an early public project. Feedback, corrections, examples, and practical suggestions can help make the standards clearer and more useful for small organizations worldwide.
Please do not send passwords, API keys, recovery codes, private records, customer data, confidential contracts, sensitive incident evidence, or completed templates containing private information.
Ways to help
Useful contributions are practical and careful.
The project benefits most from feedback that identifies unclear wording, missing fields, unrealistic assumptions, confusing examples, and areas where the templates could be easier to use.
Share safe examples
Provide generalized, non-sensitive examples that show how an organization might use a standard or template.
Report issues
Let the project know about broken links, outdated references, formatting problems, missing warnings, or template issues.
Improve accessibility
Suggest changes that make the standards easier to read, navigate, translate, or use with assistive tools.
Help with localization
Future versions may include localized examples and translations. Feedback from different regions can help avoid overly local assumptions.
Review templates
Test whether the template fields are useful, safe, understandable, and realistic for small organizations.
Contribution principles
Keep contributions safe, general, and useful.
Contributions should help improve public documentation guidance without exposing sensitive information or creating professional-advice confusion.
Use non-sensitive examples
Redact or generalize examples. Do not submit real credentials, customer records, private incidents, contracts, regulated data, or confidential organizational information.
Respect the project boundaries
The project publishes documentation standards and templates. It does not provide legal, tax, financial, insurance, cybersecurity, compliance, or incident-response advice.
Prefer plain language
The standards should be understandable to people without formal operations, security, legal, or compliance backgrounds.
What not to send
Please keep private information out of submissions.
To protect contributors and organizations, do not send information that should remain private, confidential, regulated, or securely stored elsewhere.
Do not send passwords, API keys, MFA recovery codes, private keys, seed phrases, payment card data, bank details, customer records, employee records, confidential contracts, private business records, sensitive incident evidence, regulated data, or completed templates containing sensitive information.
Contact
Send feedback carefully.
For now, feedback can be sent through the contact address listed on the contact page. Future versions may add a public repository, contribution guide, issue tracker, or formal review process.
When sharing feedback, describe the page, standard, template, or section you are referring to, then explain what felt unclear, missing, unsafe, or difficult to use.
This project is still in early draft. Not every suggestion will be adopted, but careful feedback helps improve the standards over time.