How this library is written.
Useful guidance starts with clear scope, traceable sources and honest limits.
Purpose and approach
Our aim is to explain school technology and resources in plain English and help readers make informed decisions. Articles focus on practical school tasks, questions to ask, responsibilities to clarify and processes that can be maintained after implementation.
This launch edition was prepared with AI assistance and research against named primary sources. It has not been independently certified by a solicitor, accessibility auditor, safeguarding adviser or product testing laboratory. The editorial byline identifies the publication; it does not imply an individual professional qualification or first-hand experience with every system discussed.
Sources you can identify
Where a guide relies on official or technical guidance, its source notes name the organisation, document title and date checked. Sources include government departments, relevant regulators, standards organisations, national cyber-security guidance and a product's own documentation where its operation is discussed.
Source titles appear as plain text. Public pages contain internal navigation rather than external links. Readers can locate the named original document and check its current version. Source notes establish where information came from; they do not imply that the source organisation approves this publication.
Original classroom activities, worked calculations and resource-planning suggestions are identified as Schools Direct editorial material. A named official source supports the relevant factual point; it does not imply that the source prescribed every activity or example. Historical category and product names identify a subject, not a current offer, specification or endorsement.
Guidance, requirements and judgement
We distinguish practical recommendations from a duty or requirement. A process that works well in one school may need adaptation elsewhere. England-specific publication or attendance requirements are identified as such, and general advice should not be read as a complete account of the law in every UK nation.
Check current official guidance and obtain appropriate specialist advice before making a decision with legal, safeguarding, contractual or regulatory consequences. Article checklists are planning aids, not certificates of compliance.
Examples and product mentions
Any sample price or calculation is illustrative unless explicitly described otherwise. Budget tools use the figures a reader supplies. Product names may appear when needed to explain a system people encounter, but this is not a supplier directory or a ranking service.
We do not publish invented user reviews, customer testimonials, test results, market-share figures or claims that our team used a product when it did not. We do not sell placement in the guide library or include affiliate links.
Review and correction
Each guide shows when it was last updated. Its source notes have their own check dates, which may differ from the page update date. These dates are not automatically refreshed when a visitor opens a page.
An update may be needed when official guidance changes, a product's process changes, a factual error is identified or an explanation becomes unclear. A recent date alone is not evidence that every claim has had a new external review. Compare consequential statements with the latest original source.
Accessibility and useful structure
We use descriptive headings, readable text, practical examples, internal related-guide links and checklists. Our accessibility page describes the website's design choices and current limits. The glossary explains technical terms without assuming an IT background.