Choose a student discipline system by separating the recorded event, the information used to review it and the decision made by an authorised person. Restrict each view to its intended role and test corrections and follow-up explicitly. The school’s accountable process should determine the workflow; a category or score should never silently become its decision.
Begin with the school’s agreed pastoral and disciplinary process. Identify who may record an observation, who reviews a disputed account and who communicates an outcome. Write down what each person needs to know. This creates a useful basis for software selection without turning a demonstration into a substitute for school policy.
What should an incident record say?
Gibbon’s behaviour documentation provides a concrete example. Gibbon behaviour records represent individual events or behaviours. Gibbon behaviour events can be positive or negative. Keep the description of what was observed distinguishable from later interpretation, supporting information and the authorised outcome.
Use clear, factual wording appropriate to the record’s purpose. Ask the person entering it to identify the pupil, relevant context and source of the information. Where accounts differ, retain the distinction between an observation and an allegation so a reviewer can understand what still needs checking.
A teacher can add a record for a student or a group. Include a group incident in the selection exercise and ask how the intended record distinguishes the pupils involved. A shared event should not lead the team to assume that every pupil has the same account, responsibility or follow-up need.
Gibbon allows initial comments and later follow-up information. Ask the reviewer to explain where a clarification belongs and how another authorised colleague recognises it. The useful question is whether the record remains understandable as new information arrives, rather than whether the form contains a large notes box.
How should categories support review rather than replace it?
Behaviour descriptors can be customised or turned off. Behaviour levels can be customised or turned off. Treat those choices as part of the school’s design decision. Ask what a descriptor means, who approves its wording and how a level is used in the actual review process.
Avoid importing a category list merely because it is available. Staff need to interpret the same label consistently and understand when a situation needs more context. Use sample cases to discuss ambiguity before configuring the vocabulary, then keep the agreed meanings with the handover.
The documented negative-event workflow notifies the form tutor. Verify the applicable recipient and notification content in the selected installation. Ask what the recipient should do next, and give that action a named owner. A delivered notification is one observation; an accountable review needs its own evidence.
| Process question | Requirement to agree | Demonstration to request |
|---|---|---|
| What happened? | Clear event account and source | Reviewer distinguishes observation from interpretation |
| Who is involved? | Correct pupil and event relationships | Group example preserves individual context |
| Who may read it? | Explicit role and action map | Intended and unrelated accounts have the specified views |
| What changed? | Clarification and correction route | Reviewer can understand the updated account |
| Who decided? | Authorised decision and follow-up owner | Outcome is traceable to the agreed process |
This original worksheet makes the school’s responsibilities visible beside the proposed system. Keep any unresolved policy interpretation with the appropriate school owner rather than encoding it as an unexplained automation rule.
How should restricted access be assessed?
Gibbon’s roles and permissions guide describes its access model. Gibbon roles group users by what they can do. Gibbon permissions enable or disable module actions for selected roles. Build the proposed access map around actual responsibilities, including the difference between recording an event and reviewing its outcome.
Gibbon’s guidance recommends thoroughly auditing permissions. Demonstrate the intended role combinations, not only the administrator’s view. Include a colleague who should have no access to the sample record and record the observed result alongside the expected restriction.
Discuss which information should appear in a family-facing view or message, where that is part of the school’s approved process. The public explanation and internal working record may serve different purposes. Review the exact content and recipient relationship before making a disclosure route part of acceptance.
Give changes to access an owner. A staff reassignment or pupil move can affect who needs a record. Ask how the responsible team reviews that change and who checks the resulting view. Keep the operating process and its test evidence together so access does not depend on informal memory.
Original disputed-event and follow-up exercise
Prepare a fictional playground event involving two pupils in a separate test environment. Use invented names and approved sample information. Include an initial account, a later clarification and a proposed follow-up decision. The exercise examines the quality of the record and the people who can act on it.
First, ask the designated staff member to create the event through the proposed route. Have a reviewer identify the observation, source and pupil relationships from the resulting record. Record any field or wording that obscures those distinctions and revise the requirement where necessary.
Next, add the sample clarification using the agreed process. Ask another authorised reviewer to explain what changed and which issue remains unresolved. Keep the initial account and the correction context understandable in the retained evidence, following the actual capabilities and school process being tested.
Then record the authorised sample outcome and follow-up owner. Inspect any configured notification and ask the recipient to identify their next action. Compare that interpretation with the school’s intended process and leave disagreements visible until they are resolved.
Finally, test the relevant staff and family views using the approved accounts. Inspect an unrelated account separately and retain the result. Review the exercise with the school’s pastoral owner and implementer before deciding whether the proposed arrangement fits the work.
Include a vocabulary review in that meeting. Ask staff to apply the proposed descriptors to the fictional account and explain their reasoning. If they interpret a label differently, resolve its meaning before relying on reports built from it. Retain the agreed definition and the person responsible for future changes with the configuration notes.
Ask the follow-up owner how the school will know that the agreed action has been reviewed. Record the evidence they expect and where an authorised colleague can find it. This keeps the exercise connected to pastoral support and accountable decisions, rather than ending when the last form field has been saved.
For broader requirements, see business systems and software development. Get started with the review process, role map and record questions your school needs to assess.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.