Review whether a proposed phone policy has addressed communication, exceptions, storage, enforcement, accessibility, emergencies, privacy, and evaluation. This tool runs entirely in your browser.
Readiness summary
A practical guide to reviewing your school phone policy
A phone policy needs more than a rule about keeping devices out of sight. It needs workable arrangements for families, students and staff, including people whose circumstances do not fit the standard approach. Use this checklist to identify gaps in a draft or review an existing policy. It is a discussion aid, not approval to introduce restrictions.
How to complete the checklist
- Gather the current policy, family communications, staff instructions and any supporting procedures. Review what is documented and happening, rather than what the school intends to do.
- Answer all ten statements. Choose Yes when the statement is fully supported, Partly when some elements remain incomplete, and Not yet when the arrangements are missing or have not been established. A planned family briefing is not the same as one already delivered.
- Select Calculate readiness. The tool requires an answer to every question before displaying a score and suggested actions.
- Discuss the suggested actions, assign responsibility and record what evidence would demonstrate completion. If you change an answer, calculate again to update the result.
Print summary opens a browser print view of the result; it does not include the individual answers. Keep a separate dated record of your reasoning. Reset clears the selections and summary.
What the main decision areas mean
Look for procedures that people can follow on an ordinary school day and when something goes wrong. This table summarises the decisions behind the checklist.
| Decision area | What to check | Example to resolve |
|---|---|---|
| Scope | Define who is covered, which devices are included, and the times and places where restrictions apply. | Does the same rule apply during lessons, lunch, school transport and trips? |
| Communication and emergencies | Explain the policy before implementation. Document and test urgent contact routes, including a backup if the usual route fails. | How can a family report an urgent change to collection arrangements? |
| Exceptions and equitable access | Provide a clear, confidential route for individual requests. Check whether alternative arrangements are genuinely available to each student. | Can a student access a required school service without a personal phone? |
| Storage and privacy | Specify handover, storage, return and incident reporting. Review the boundaries around searches, confiscation and device content. | Who records a missing device, and what happens if collection is delayed? |
| Enforcement and staff preparation | Explain proportionate responses and train staff to apply them consistently while recognising agreed exceptions. | Would a substitute teacher know how to handle an apparent breach without exposing private information? |
| Evaluation | Set goals, a review date and accessible feedback routes. Consider implementation workload as well as student experience. | Who reviews repeated disputes, and how can students suggest changes? |
Handling exceptions without creating new barriers
Exceptions need individual consideration, not assumptions based on a diagnosis, age group or family situation. Relevant examples may include a student using phone-linked health support, assistive communication or translation, or someone with particular safety, travel or caring needs. These examples do not establish an automatic entitlement or prescribe the right arrangement.
- Make the request route easy to find. Consider how a family can use it if they face language, literacy or digital-access barriers.
- Seek appropriate medical, accessibility, safeguarding or legal input where needed. Avoid asking students to explain sensitive circumstances publicly.
- Agree how relevant staff will recognise an arrangement, what information they need and when it should be reviewed. Keep sensitive details out of general classroom instructions.
For example, a student with an agreed health-related arrangement may need device access at particular times. The practical question is how to support that arrangement discreetly, not simply whether the general rule has been broken.
How to interpret the score
Each Yes contributes 10 points, Partly contributes 5, and Not yet contributes 0. All ten questions carry equal weight. The result therefore summarises your answers; it is not a percentage likelihood of success or a measure of legal compliance.
- 85–100: The tool describes a strong planning foundation, with local review still needed.
- 65–84: A promising draft, with implementation details needing attention.
- 40–64: An early-stage policy with important unresolved issues.
- Below 40: Major gaps requiring substantial review.
Do not let the total hide a critical omission. Nine Yes answers and one Not yet produce 90 points, even if the missing area is emergency communication. Review every suggested action and prioritise issues affecting safety, access or rights before routine refinements. A score of 100 still does not demonstrate that the arrangements work in practice.
What the tool cannot determine
The checklist cannot inspect your documents, verify answers, assess an individual student’s needs or establish compliance with applicable requirements. It cannot determine whether restrictions will improve learning or wellbeing, whether enforcement will be fair, or whether a particular storage or search practice is appropriate. Those questions require evidence, consultation and relevant local expertise.
Use the result to prepare a short action plan: identify the gap, name an owner, set a review date and specify how progress will be checked. Invite feedback from students, families and staff, including those likely to need exceptions. After implementation, revisit both the written policy and everyday practice rather than treating the initial score as a permanent judgement.