Choose a teacher information system by separating the staff identity, the evidence behind recorded qualifications and the teaching allocation for a defined period. Decide who maintains each part and which audiences may see it. Demonstrate a change of allocation and a profile correction so the system’s records remain useful after the initial staff import.
Begin with the questions the school needs to answer: who teaches the course, what evidence supports the relevant staff information and where a colleague finds the current timetable. These questions involve related records, but they should not be collapsed into a single public staff directory.
Which teacher record is authoritative?
Gibbon’s staff documentation describes one approach. Gibbon’s staff directory lists teachers and support staff. Gibbon staff membership requires an existing user record. Ask the implementer to show the relationship between the person’s account and the staff record before importing a sample teacher.
Gibbon staff profiles can include qualifications and a biography. Keep the act of recording a qualification separate from the school’s process for verifying it. Agree who checks the source evidence, how its status is represented in the operating process and which information is suitable for the intended profile audience.
Avoid collecting a field simply because the form provides it. Identify its purpose and maintainer, and discuss which staff role needs access. A directory used to find a teacher’s contact route has a different audience from the records used by an authorised staffing administrator.
Give corrections a clear route. A teacher should know where to raise a mistaken title, qualification entry or other profile detail. The person maintaining the record needs a way to identify the requested change and its supporting information, using the school’s approved process.
How should teaching allocations be represented?
Frappe Education’s instructor guide offers a separate product example. A Frappe instructor record selects an employee identity. Frappe Education instructor records can maintain a history of courses taught. Retain the product and record context when comparing it with another system’s staff profile.
The instructor log records the academic year and term. The instructor log can identify a programme, course and student group. Ask the academic owner to explain which combination represents a current allocation and how an earlier assignment remains identifiable when responsibilities change.
Creating an assessment plan from an instructor allows supervisor or examiner selection. Treat those responsibilities as explicit academic decisions. The person teaching a group and the person supervising an assessment may need different records or approvals in the school’s operating model.
Gibbon’s staff guide describes these separate staff-management features. Gibbon’s staff-management area can link facilities and contract records. A Gibbon staff profile includes a timetable view. Inspect the intended relationship between the allocation, facility and timetable rather than assuming that saving a teacher’s name automatically resolves every scheduling requirement.
| Teacher-information question | Owner to identify | Evidence for the demonstration |
|---|---|---|
| Which person is this? | Staff-record administrator | Intended account and staff identity are linked |
| What supports the qualification entry? | Authorised verifier | School-approved evidence and recorded meaning agree |
| Which group is being taught? | Academic allocation owner | Course, group and period identify the intended assignment |
| Where is the current schedule? | Timetable owner | Teacher can find the agreed timetable route |
| What changes after reassignment? | Responsible academic and record owners | New and earlier allocations remain understandable |
This original worksheet gives each record a purpose and an accountable maintainer. It can be used with a shortlist, provided each claimed product feature is checked against that product’s actual documentation and proposed configuration.
How should profile and allocation access differ?
List the audiences separately: the teacher, teaching colleagues, academic administration, staffing administration and any approved public directory reader. Write the information each audience needs and the actions it may perform. Use that map to request a role demonstration in the selected system.
Review qualifications and supporting documents with particular care in that design. A short verified profile statement and the underlying document may serve different purposes. Decide their handling through the school’s approved responsibilities instead of assuming that both belong in the same visible field.
Also review people who hold several responsibilities. A teacher may coordinate a department or supervise an assessment while retaining their own staff profile. Ask the implementer to explain the intended role combination and inspect what the sample account can actually read and change.
Keep access changes connected to staffing changes. Identify who reviews permissions when a role ends or a teacher moves to another responsibility. The handover should make that review part of the operating process rather than leaving it to someone who happens to remember the old assignment.
What should historical information retain?
Decide which questions an earlier allocation needs to answer. The school may need to identify the teacher responsible for a course during a particular term or understand which instructor was assigned to an assessment. Retain the relevant period and identity in the proposed model.
Discuss corrections and historical changes separately. Fixing a mistaken teacher reference in a record is different from recording a genuine change of allocation. Ask the academic owner how those situations should be explained, then verify that the proposed workflow can preserve the intended meaning.
Use actual requirements to guide reports. A list of current teachers and a history of course allocations are different outputs. Request both where they are needed, and inspect the sample record behind each result rather than accepting a general staff dashboard as evidence of the complete workflow.
Original teacher-allocation handover exercise
Prepare a fictional teacher, an approved sample qualification entry and a course group in a separate test environment. Give the allocation a defined academic period. The exercise follows a profile correction and a later teaching handover, using invented personal information.
First, have the responsible administrator locate the account and staff identity. Enter the approved sample profile information and ask the designated reviewer to explain what the qualification entry means. Inspect each intended audience’s view using the agreed access map.
Next, create the sample allocation and ask the teacher to find the course, group and timetable information. Compare the displayed period and responsibility with the academic owner’s written expectation. Record any dependency on another record or manual maintenance step.
Then introduce a sample reassignment and inspect the new allocation alongside the earlier history. Ask another colleague to identify who was responsible in each period. Retain any ambiguity as a modelling or handover issue until the responsible owner resolves it.
Finally, review the profile correction, allocation change and affected access together. Assign ongoing record and timetable maintenance responsibilities, retaining the version and configuration used in the exercise for later review.
For related planning, see business systems and software development. Get started with the staff information, teaching allocations and access decisions your school needs to manage.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.