Staff Attendance and Leave Management System

Yes you can. You need not pick the other modules of Vawsum.

Attendance comes from ESSL biometric and face recognition devices, RFID or proximity cards, or a desktop punch at the office. Where a device is not practical, an administrator marks attendance directly in the system.

No. Attendance is captured from a device or marked by an administrator rather than through staff self check-in, so a punch always corresponds to someone physically present at the institution. Staff use the app for leave, balances, payslips and documents.

The staff member raises a regularisation request for the missed punch, which goes for approval like any other request. The correction is recorded rather than edited quietly into the attendance register.

Yes. You configure the grace window your institution allows, so a staff member arriving a few minutes behind schedule is not marked late while genuine lateness still is.

Yes. Late arrival rules are configurable, so a policy such as three late marks becoming one half day is applied by the system every month rather than tracked by hand.

An auto-absent cutoff marks the day absent when no punch has arrived by the time you set, so an unrecorded absence does not survive unnoticed until month end.

Yes. Minimum working hours are tracked against every employee and overtime hours are captured, so the institution sees time actually worked rather than only days present.

Yes. Staff see their leave balance in the Vawsum app before applying, which removes most of the balance queries that otherwise reach the HR desk.

Yes. Leave accrues on the monthly or annual cycle you configure, so balances stay correct without a parallel spreadsheet being maintained.

Yes. Unused leave carries forward into the next year or is encashed through the salary run, following the rules your institution applies to each leave type.

The absence is treated as leave without pay and carried into the salary run, so the loss of pay reaches payroll rather than being missed at month end.

Yes. Maternity, paternity and medical leave are held as distinct leave types with their own entitlements, so statutory leave is not absorbed into the general leave pool.

Yes. Requests can route through multiple levels, so an application needing both the head of department and the principal follows that path in the system.

Yes. Each department routes to its own approver, so requests reach the person who manages that team rather than queueing at a single central desk.

Yes. Before approving, the approver can see which other staff are already off on the same dates, so two teachers from the same subject are not released on the same morning.

Yes. A reason and supporting documents are attached to the leave request, so the approver decides with the evidence already in front of them.

Yes. Backdated applications are supported, which is how sudden illness actually works, so the record is completed properly rather than left as an unexplained absent day.

The request escalates automatically after the period you configure, so an application does not sit unanswered while the staff member waits to know whether they can travel.

Yes. Approved leave triggers the substitution flow, the timetable arranges cover for the periods that teacher would have taught, the covering teacher is notified automatically, and the substitution is recorded for workload tracking.

Staff are notified when a request is approved or rejected, approvers are notified when a request is pending, and the principal receives the same-day absence position each morning.

Yes. Contract, part-time and visiting faculty are handled alongside permanent teaching and non-teaching staff, each on the entitlements that apply to them.

Staff apply for leave, check balances, raise regularisation requests, view payslips and access their own employment documents, so routine requests stop arriving at the office in person.

Yes. Attendance, approved leave and loss of pay flow directly into the Vawsum Payroll System, so the salary run works from the same record rather than a re-keyed summary.

Reporting across branches is available from a single login. Day to day transactions such as leave approvals are handled through separate logins at each branch.

Yes. You set a quota for how many staff can be on leave on any one day. Once that limit is reached for a date, further applications for that date are stopped, so the institution is not left short because separate approvers each said yes without seeing the others.

Yes. Restricted and blackout dates are configured in advance – examination and invigilation days, the day the institution reopens after a vacation, results day – and requests for those dates are stopped at source rather than being declined individually.

Yes. Probation can be set as a restriction, so staff serving probation are prevented from applying and the condition already written into your appointment letters is enforced by the system.

It is recorded as on duty rather than leave. Invigilation at another school, marksheet evaluation duty, training or any official work away from campus marks the staff member present, so nobody loses leave for working elsewhere on the institution’s behalf.

We can configure the system in a few hours if we have all the data.