Take the register06 / 11
The register is the easy part. What happens to it afterwards is not.
Marking a class present takes a minute. Turning a month of registers into a payroll input, a leave balance and an answer to “how often has this child been absent” is what takes the week.
The problem today
The mark is quick. Everything downstream of it is not.
- Attendance is taken on paper and typed in later, or not typed in at all.
- Staff attendance and student attendance live in different places.
- Leave is a form, a signature and a file, and the balance is calculated only when someone asks.
- Carry-forward and encashment are calculated by hand in April.
- A biometric device stops reporting and nobody finds out until payroll is wrong.
What EduBold changes
From the device to the payroll calculation, without a retype.
Take the register/Every mark carries its source
- Biometric device
- Teacher
- Import
Students and staff, one engine
The same attendance layer serves both, with types, statuses and view modes you configure. Half day, late, on duty, whatever your school actually uses.
Attendance carries its source, so you can tell whether a mark came from a device, a teacher or an import. When something looks wrong, you can see where it came from.
Devices push in, and failures are visible
Biometric devices send punches to the system rather than being polled. Register a device from the interface, map staff to it, and every incoming call is logged with its status.
A device that stops reporting shows as a failed sync the same day, rather than as a payroll discrepancy at the end of the month.
To be clear about what this is: EduBold receives what the device sends. It does not perform recognition. Whatever your device does, it keeps doing.
Leave is an engine, not a form
Policies are evaluated, not just stored. Entitlement is kept separate from allocation, because what someone is owed and what they have been given are different questions. Accrual runs on a schedule, so balances build through the year without anybody processing them.
Carry-forward processes at year end, and expires on the policy date. Encashment converts a balance into money through payroll.
Applications go apply, submit, approve or reject, cancel or withdraw, with HR review as a distinct second stage after the manager. Bulk actions clear a backlog. Students apply for leave too, which turns a parent’s phone call into a record.
Working days are configuration
Working day patterns define which days count and what a working day is. From the pattern the system calculates working hours for a date, calculates overtime, and determines attendance status automatically.
Holidays are data. Shifts are assigned to staff and can be terminated.
It feeds payroll without anyone carrying it
Monthly summaries are generated for all staff, recalculated when something changes, finalised when correct, and linked to the payroll run.
Loss-of-pay days prorate the salary. Nobody retypes a number between HR and payroll.
The detail that decides it
Leave is approved by the department, then checked by the office.
A leave application is approved by the person who manages the work, and then reviewed by HR. Two stages, not one.
Every school has had the conversation where a head of department granted leave that HR would not have granted, or HR refused leave a department had already planned around. It is not a software problem. It becomes one when the software collapses two decisions into a single Approve button.
Here they are two steps, in order, with a record of each.
For the management committee
Leave liability is a real number, and most schools cannot state it.
Accrual, carry-forward, expiry and encashment are computed here rather than estimated, which means the provision is defensible.
There is also an audit angle on attendance. Source tracking and device sync logs mean the attendance underlying the payroll can be evidenced, rather than asserted.
Biometric devices post straight into the register, so the roll is already taken before the first bell. Bring your device model to the demonstration.
Next
Bring your hardest question.
Half an hour, on the problems your school actually has. Bring the thing your current system cannot do, and you will watch EduBold run it against your own rules before you decide anything.