Role and permission guide for academics, curriculum, and lesson planning

1. Define academic work before roles

List the actions each group performs: view a plan, create a lesson, edit a resource, review an outcome, approve a curriculum change, publish, export, correct, archive, or delete.

A job title is not a permission model. Define record, action, subject, class, campus, period, and purpose.

2. Separate academic actions

Specify view, create, edit, review, approve, publish, export, correct, archive, and delete independently. Add scope by subject, year group, class, campus, student, resource, and reporting period where appropriate.

Test whether a teacher can publish an unreviewed resource, a substitute can see unrelated records, or a family can access internal notes.

3. Cover the access lifecycle

Define joiner, mover, leaver, substitute, temporary assignment, support escalation, supplier, emergency, student, and family access. Require owner, expiry, approval, evidence, and review for elevated rights.

GOV.UK school guidance emphasises accountable and secure handling. The U.S. Department of Education data governance checklist covers access, security, lifecycle, sharing, disposal, and monitoring.

4. Protect publishing and exports

Record who reviewed, approved, published, changed, exported, corrected, or retired a plan or resource, with date, reason, previous version, new version, and audience.

Do not use shared accounts or unrestricted downloads to compensate for missing role design.

5. Test and teach

Use ordinary lesson, substitute, changed class, revised outcome, family view, accessibility, report, and staff-leaver cases. The U.S. Department of Education data-quality guidance links quality with definitions, validation, infrastructure, and professional learning.

6. Review permissions

Review publishing errors, access exceptions, exports, corrections, support demand, staff understanding, resource currency, and reporting confidence at 30, 60, and 90 days. Reduce access when evidence shows it is broader than the work.

Turn the guidance into an academic decision

Apply this guidance to one bounded part of role and permission guide for school academic management software. Define the academic decision, record, purpose, authoritative source, accountable owner, permitted users, correction route, and evidence needed to approve the next step.

Test an ordinary lesson or curriculum record and meaningful exceptions such as a changed class, missing lesson, substitute teacher, timetable change, transferred student, revised outcome, duplicate resource, or reporting-period change. Record who resolved it and how the correction reached dependent views.

Keep product capability, school responsibility, professional judgment, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review the result at 30, 60, and 90 days. Check completeness, timeliness, consistency, corrections, access exceptions, teacher effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Make the handoff readable to a teacher, academic leader, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how a correction is communicated without creating an uncontrolled copy.

Keep the approved definition beside its validation rules, training note, support route, and change history. A new year group, subject, campus, role, integration, or calendar can change the risk even when the lesson or field name remains the same.

Document what was tested and what was not. A successful demonstration with an ideal lesson plan does not establish readiness for substitutions, absences, mixed classes, resource changes, late work, or a new academic period.

Set the next review date and owner. A dependable academic system is maintained through clear definitions, controlled change, professional judgment, and visible accountability rather than a one-time setup.

Keep the evidence beside the decision record so a later reviewer can distinguish observed behavior from an assumption, estimate, or supplier statement. Name the next test where the current evidence is incomplete.

Revisit the boundary when the school adds a subject, campus, role, integration, reporting period, or policy. A small change can alter permissions, definitions, timing, or retention even when the workflow appears familiar.