Staff costs are usually the largest line in a school's budget, often more than half of it. Yet HR in many schools is spread across a personnel folder for each teacher, a leave register in the office, an attendance sheet, and a payroll spreadsheet that one person understands. Each works on its own. Together they produce a month end where leave taken is discovered after salaries were calculated, and an inspection where a missing document is found in the wrong folder.
This guide covers the HR cycle for a school or college, from recruitment to appraisal, and shows where connecting the pieces removes most of the manual work.
One personnel record
Everything else depends on a single, complete record for each member of staff:
- Personal and contact details, emergency contacts
- Role, department, campus, start date and contract type
- Qualifications and certificates, with expiry dates where relevant
- Salary structure, allowances and deductions
- Bank details for salary payments
- Leave entitlement and balances
- Training attended, appraisals and any disciplinary history
Sensitive fields such as identity numbers and bank details should be visible only to the people who need them. A good system lets you restrict those fields by role, so a head of department can see a teacher's timetable and training without seeing their bank account.
Compliance documents
Schools are often required to hold specific documents for every member of staff: identity, qualifications, background checks, contracts. Recording each document against the person, with an expiry date where one applies, turns an inspection from a search into a report: who is complete, who is missing what, and what expires this term.
Recruitment and onboarding
Hiring season puts pressure on a small team. Track each vacancy, the applicants, interview stages and outcomes in one place, so a shortlisting decision is recorded rather than remembered. When a candidate accepts, their application details should become the start of their personnel record, not be retyped.
A new teacher's first week goes better with their timetable, class lists, login details and a named mentor ready on day one.
Attendance and leave
Leave that is requested, approved and recorded
Leave should follow one path: requested by the staff member, approved by the right person, recorded against their balance. When staff can see their own balance and request leave themselves, the office stops answering the same question every week.
Staff attendance
Daily staff attendance, whether recorded by a register, a device or a login, matters for two reasons: arranging cover for the day, and calculating pay at the end of the month. When it is recorded in the same system as the timetable, the person arranging cover can see at once who is absent and who is free.
Payroll
Salary structures
Define salary structures once: basic pay, allowances, deductions, and how each is calculated. Staff on the same scale move together when an increase is approved. Individual exceptions are recorded on the person, with a reason.
A payroll run that reads what is already recorded
The most common payroll error in schools is leave or absence that was not reflected in salary because it lived in a different record. When payroll reads approved leave and attendance directly, unpaid leave is deducted automatically and nobody has to cross-check two lists at month end.
A practical monthly payroll looks like:
- Confirm attendance and leave for the month are complete.
- Run payroll, which calculates pay from structures, attendance, leave, loans and allowances.
- Review the exceptions: changes from last month, new joiners, leavers.
- Approve and lock the run.
- Publish payslips to staff and produce the bank transfer list.
Statutory requirements
Tax, pension and social security rules differ widely between countries, and often between regions within a country. Configure deductions to match the rules that apply to you, and check them with a local accountant or adviser when you set up, and again whenever the rules change. A school payroll system can calculate what it is told to calculate; it cannot replace local advice on what the law requires.
Payslips staff can see
Staff should be able to see and download their own payslips. It saves the office a steady stream of requests, and it gives staff confidence that their pay is calculated transparently.
Loans and advances
Many schools offer salary advances or loans to staff. These need to be visible: the amount, the agreed repayment, and the balance. When repayments are deducted automatically in payroll, nothing is forgotten and nobody has an awkward conversation about a balance that was not recovered.
Appraisals
Appraisals are often dreaded because they feel like paperwork rather than development. They work better when:
- The cycle and criteria are published at the start of the year
- Evidence (observations, results, training, attendance) is gathered through the year, not invented at the end
- The conversation focuses on one or two development goals
- Outcomes are recorded and revisited at the next cycle
An appraisal that leads to training, and training that is recorded and reviewed, is what professional development actually looks like.
Training records
Inspectors and boards frequently ask what professional development staff have received. Record every course, workshop and certification against the person, with dates and hours. The answer to "how many hours of training did your teaching staff complete this year" should be a report, not an estimate.
Cover and substitution
When a teacher is absent, cover needs to be arranged before the first lesson. With staff attendance and the timetable in one place, the person arranging cover sees the absent teacher's lessons and the staff who are free in each period, and can assign cover in minutes. Recording cover also shows over time whether the burden is being shared fairly.
Staff self-service
A staff portal that shows each person their timetable, classes, leave balance, payslips, training and notices removes much of the routine traffic to the office, and gives staff a sense that the system works for them, not only for administration.
An illustrative example: one month of payroll
Consider a school with 85 staff. In a typical month: two teachers take a combined six days of unpaid leave, one administrator joins mid-month, a teacher leaves at the end of the month, four staff are repaying salary advances, and the board has approved a cost-of-living increase on one salary scale from this month.
Where HR lives in separate files, the payroll officer starts by collecting the leave register from the office, the attendance sheets from each department and the advance repayment list from accounts. The unpaid leave for one teacher is in the register but the other's was approved by email and is missed. The new administrator's start date is taken from the contract rather than their first actual day. The salary increase is applied by editing each affected person's spreadsheet row. Two staff query their pay; one is owed money, the other has been overpaid and the correction carries into next month.
Where HR is connected, approved leave is already on each person's record, so both teachers' unpaid days are deducted automatically. The new administrator's start date comes from their personnel record and first recorded attendance. The leaver's final pay is calculated to their last day. Advance repayments deduct according to each agreed schedule. The scale increase is applied once to the salary structure, with an effective date, and every member of staff on that scale moves together.
The payroll officer's job becomes reviewing exceptions rather than gathering inputs: checking the joiner, the leaver and the increase, then approving the run. Payslips appear in the staff portal the same afternoon. When one teacher asks about a deduction, she can see her own leave record in the portal before she even calls.
Common mistakes to avoid
- Approving leave outside the system. Leave approved by message or in conversation never reaches payroll. Every approval should go through the same path.
- Editing individual salaries for a scale change. Change the structure once, with a date. Individual edits drift apart over time.
- Running payroll before attendance is complete. Close the month's attendance and leave first, then run payroll. Corrections after payment are more work and less pleasant for everyone.
- Keeping qualifications in a paper file only. Certificates and checks that expire need dates in the system, or they are discovered expired during an inspection.
- Exposing sensitive fields to everyone. Bank details and identity numbers should be visible only to the people who process pay.
- Treating appraisal as an annual form. Evidence collected through the year makes appraisals fairer and much quicker to complete.
Frequently asked questions
How do we handle staff who work at more than one campus?
Keep one personnel record per person, with their campus assignments and any split of hours recorded. Payroll then runs once for the person, with cost allocated to each campus if your reporting needs it.
Can payroll handle different contract types?
Most schools mix permanent, contract, part-time and visiting staff, often paid on different bases (monthly salary, hourly or per session). Configure each as its own structure rather than handling them as exceptions, so each group is calculated consistently.
How should salary advances be managed?
Record the advance with the amount, approval and repayment schedule, and let payroll deduct the instalments automatically. Make the outstanding balance visible to the staff member. Clear advances avoid both under-recovery and uncomfortable conversations.
What HR reports does leadership usually need?
Headcount by role and campus, staff attendance and leave trends, payroll cost against budget, upcoming contract and document expiries, and training completed. A short monthly set covers most governance needs.
A 30-day plan to connect HR and payroll
Week 1: complete the personnel records
Bring every member of staff into one record: role, campus, contract, salary structure, bank details, leave entitlement. List missing compliance documents and their owners.
Week 2: one path for leave
Move all leave requests to a single path: requested by the staff member, approved by the right person, deducted from their balance. Announce that leave approved any other way will not be recognised from next month.
Week 3: define structures
Set up salary structures, allowances and deductions, and record loans and advances with their repayment schedules. Check statutory deductions with your local adviser.
Week 4: run payroll in parallel
Run one month's payroll in the new way alongside your existing method, and compare the results line by line. Investigate every difference. When the two agree, switch over and publish payslips to the staff portal.
Bringing it together
HR becomes manageable when each part feeds the next: the personnel record drives payroll, attendance and leave feed salary, appraisals lead to training, and staff see their own information. That is how Scolvia Staff and HR, Payroll, Appraisals and Staff Training work together, with the staff portal giving each teacher their own view.
Checklist
- One complete personnel record per member of staff, with sensitive fields restricted.
- Compliance documents recorded with expiry dates.
- Leave requested, approved and deducted from balances in one flow.
- Staff attendance connected to cover and payroll.
- Salary structures defined once; exceptions recorded with reasons.
- Statutory deductions checked with local advice.
- Payroll that reads attendance, leave and loans directly.
- Payslips available to staff themselves.
- Appraisals based on evidence gathered through the year.
- Training recorded and reportable.