For each school task, name an operational owner, the access needed and a reviewer. Teachers, office staff and accounts colleagues should work within their responsibilities. Important corrections need an agreed approval process; giving everyone unrestricted editing access does not make ownership clearer.
If a task belongs to everyone, it can become unclear who must finish it. Small institutions can still distinguish preparation from review, even when one person holds more than one role.
Start with tasks rather than job titles
List daily, weekly and month-end work before assigning people. When someone performs several roles, specify which responsibility applies to each task.
| Task | Operator | Reviewer | Access question |
|---|---|---|---|
| Subject attendance | Assigned teacher | Responsible coordinator | Which class and subject? |
| Admission entry | Office colleague | Admission lead | Which fields may be changed? |
| Marks submission | Subject teacher | Examination coordinator | Is the correction reason retained? |
| Fee receipt | Authorized accounts colleague | Designated reviewer | Who may cancel or correct it? |
| Monthly summary | Department owner | Institution lead | What information can each role view? |
Adapt this discussion template to your institution’s responsibilities. It is not a prescribed staffing structure.
Test access in the demonstration
Use a teacher account to complete a permitted task. Then attempt one action outside that account’s authority using fictional records. A hidden menu alone is not sufficient evidence: the action itself should be refused.
Confirm whether the teacher may access other classes or branches. If responsibilities are temporarily reassigned, document their scope and review point. Do not share another colleague’s password as a substitute for an authorized assignment.
Plan handovers
Before a colleague leaves a responsibility, list unfinished work, records and outstanding questions. Removing account access is separate from updating a contact number. Record who transferred each responsibility and who accepted it.
Review unfinished work each week
Instead of asking only whether everything is complete, inspect missing attendance, outstanding marks, pending approvals and unresolved questions. A small list containing the task, owner, review date and next action is often useful. Login frequency is not a complete measure of work quality.
Review staff management, attendance and reporting when preparing your responsibility map. Discuss access questions alongside the security information.
Frequently asked questions
Does a small school need distinct roles?
One person may perform several jobs. It is still useful to define access boundaries, important correction rules and review responsibilities.
Should we use a colleague’s password during a handover?
Use your own authorized account and assigned responsibilities. Shared accounts make it harder to establish who performed an action.
Does an invisible menu prove permissions are correct?
No. Check actual permitted and refused actions. Verify viewing and editing access separately.
Bring your responsibility list to an iilmaa demo to test the relevant roles.