Community guidelines

• Be respectful and practical. Write to help a colleague, not to impress one.
• Be honest about testing and limitations. If you tried something and it only partly worked, say so — that is often the most useful part.
• If you have a commercial interest in a tool or resource you mention (you sell it, you are paid to promote it, or you built it to sell), disclose that plainly.

To protect learners, colleagues and schools, do not include:

• Learners’ personal information of any kind.
• Identifiable images of learners.
• Confidential school information.
• Passwords, API keys or other credentials.
• Private records — anyone’s, including colleagues’.

Any screenshots must use demonstration data, or be redacted so that no real personal or confidential information is visible.

• Sales pitches dressed up as stories or resources.
• Harassment, personal attacks or disrespect.
• Unsubstantiated claims — especially about what a tool can do, its safety, or its results. Share what you actually observed.

When a contribution is published, it means an editor judged it appropriate and useful to share. It is not a certification that the ideas, tools or resources described are accurate, secure or suitable for your particular classroom. Always use your own professional judgement and check anything before relying on it.

If you see something that breaks these guidelines, please tell us. Every teacher story, classroom resource and staffroom response carries a Report a concern option so you can flag it directly from the page. You can also email [email protected]. We review concerns and can amend or remove content where needed.

See the contribution terms for the permissions involved in contributing, and the privacy notice for how information is handled.