An academic calendar that ignores the payroll month
Terms, vacations and examination periods do not align with anybody's attendance policy. Teaching and non-teaching staff work to different rules, and the same institution runs both.
What education actually needs
Academic calendars
Term dates, vacations and examination periods held as calendars, so attendance rules change with the calendar rather than by exception.
Two workforces, one institution
Teaching staff on academic terms and non-teaching staff on ordinary ones, in the same system, under different policies.
Qualifications on file
Degrees, teaching certifications and registrations held in the vault, with renewal dates surfaced before they lapse.
Periods, not just presence
Attendance that reflects teaching load rather than only clock time, where the institution works that way.
Payroll across categories
Permanent, contract and visiting faculty in one run, each under their own structure.
Registers for inspection
Attendance and wage registers maintained contemporaneously, whatever the term calendar is doing.
Vacation is not absence
The first thing an ordinary HR system gets wrong in a school is that it reads a vacation as a run of absent days. Teaching staff on vacation are neither working nor on leave, and treating the period as either produces wrong pay or a wrongly depleted balance.
Holding the academic calendar as a first-class object — terms, vacations, examination periods — lets the attendance rules change with it, instead of somebody applying exceptions for six weeks.
Two workforces under one roof
Administrative staff, support staff and drivers work ordinary calendars. Teaching staff do not. Visiting faculty may be paid per session.
These are three genuinely different arrangements, and an institution needs all of them running simultaneously without maintaining three systems. Policy layered by grade handles this without duplicating anything.
Credentials lapse quietly
Teaching qualifications, registrations and, for some institutions, statutory approvals all have dates. A lapse discovered during an inspection or an accreditation visit is a considerably worse experience than one flagged three months ahead.
How the calendar drives everything else
The academic calendar
Terms, vacations and examination periods defined once, per institution.
Rules follow it
Attendance treatment changes with the calendar rather than by manual exception.
Categories stay separate
Teaching, non-teaching and visiting staff under their own policies, in one system.
One payroll run
Every category computed together, with the registers produced from the same run.
Schools, colleges and training institutions FAQs
How is vacation handled for teaching staff?
As a defined period in the academic calendar rather than as leave or absence. Pay continues, the leave balance is untouched, and the register reflects what the period actually was.
Can we pay visiting faculty per session?
Yes — a per-session or per-hour structure sits alongside the monthly structures used for permanent staff, in the same payroll run.
Do we need a biometric device in every building?
No. Phone-based punching bounded by location works, and any existing device you have can push punches in rather than being replaced.
Does it track teaching load as well as attendance?
It records attendance against the shift or period structure you configure. Where load matters more than clock time, that is how it should be modelled.
Academic and administrative staff have different terms.
Grades carry their own leave, attendance and pay rules, so teaching and admin staff do not have to share a policy that suits neither.
Long vacations affect leave accrual.
Accrual, carry-forward caps and encashment are configured per grade, which is where institutions usually need something other than a standard corporate policy.
Can we start with one site and expand?
Yes, and most do. Start where the pain is, prove a month, then roll out. A big-bang rollout across every location is how a project acquires a reputation before it has results.
What does it take from our team each month?
After setup, the monthly job becomes reviewing what the system drafted rather than assembling it. The teams who see the biggest change are the ones who were retyping attendance into a spreadsheet.
See it on your own data
Fourteen days, no card, no consultant. Import your spreadsheet and watch it compute.