Book a Demo
Book a Demo

← Platform

Staff

From the punch to the payable day.

Staff attendance in a Pakistani school is rarely about who came to work. Everybody knows that. It is about the argument at the end of the month — who was late how many times, whether a half day counts, whether Saturday between two days of leave is leave, and what any of it should do to the salary.

GLOWSIMS settles those questions once, as your school's own rules, and then applies them the same way every month.

Four steps, and you can see which one you are on

Attendance moves through four stages. Each one is a deliberate action rather than something that happens quietly.

  • Record — Check-ins and check-outs arrive
  • Process the day — Each person's day becomes one record with their hours, lateness and status
  • Process the month — The days add up to the figures payroll needs
  • Finalise — The month is locked

A strip at the top of the screen shows all four with a count, green where that stage is done and red where it is not.

That matters more than it sounds. The single most common way school attendance fails is that somebody processes the days, assumes they are finished, and payroll never receives anything. The strip tells you what is left.

Finalising locks the month

Once a month is finalised, its figures cannot be changed — no editing a day inside it, no re-running the month over it. That is the point: payroll should not be built on numbers that can still move.

To correct a finalised month you unlock it, make the change, and lock it again. Which leaves a trail.

Getting the attendance in

Three ways, all into the same record

A biometric device at the gate. The Muallam app on a teacher's phone. Or typed in by the office.

Each record carries where it came from, and the device and app records are protected by their own permissions, so a staff member who can correct a hand-entered mistake cannot quietly edit what the machine recorded. If an automated record is edited by hand, the record says so.

Duplicate records are ignored, so a device re-sending what it already sent does not double anything up.

The spreadsheet that is already filled in

Most schools do not have a device yet, and typing two punches a day for sixty staff is nobody's job.

So download a spreadsheet for whatever date range you need. It arrives with every employee listed, every date in the range, and each person's own shift times already filled in — their start time as the check-in, their end time as the check-out.

You only change the exceptions. The six people who were late, the one who left early, the two who did not come. Everybody else is already correct.

Upload it back and every row is checked. Rows that fail come back in a list with the reason — wrong employee number, a time outside the shift, a date that does not belong — and you fix those rows rather than the whole file. The good rows are already in.

Or let it run overnight

Where a school has a device, the day's processing can run automatically each night once it is switched on, so the office arrives to a day already processed. We set that up with you rather than leaving it on by default.

Your shifts, including the short Friday

A shift can have different hours for each day of the week. Nine to three Monday to Thursday, nine to twelve on Friday, and whatever Saturday is at your school.

That is one shift definition, not seven. And the day's calculation uses the right hours for the right day, so Friday's early finish is not read as everyone leaving early.

Shifts are assigned to a person, a designation, a department, or the whole school — and the most specific one wins. Set the school's shift once, then set the three people whose hours are different.

Weekends, including alternate Saturdays

Name the days that are your weekend. Friday and Saturday, Saturday and Sunday, Sunday alone — whatever your school runs.

And alternate weeks are handled properly. Schools where the first and third Saturday are off, and the second and fourth are working, set the odd weeks and the even weeks separately. Nobody has to remember which kind of Saturday this is.

Weekends are assigned the same way as shifts, so the administrative staff and the teaching staff can have different weekends.

Holidays, and the people they do not apply to

Set a holiday with its dates, and who it applies to.

Then, separately, who it does not apply to. A holiday for the whole school, except the security staff. A holiday for the primary wing only. The exclusion is a field rather than a workaround.

Exam week, and the Saturday you have to open

Two kinds of exception, because schools need both.

A date range where the rules are different. Exam week has different hours; a sports week has a different policy. Set the dates, the shift and the policy that apply instead, and who they apply to. When the range ends, the normal rules return by themselves.

A single day flipped. Make this Saturday a working day for the event. Make that Wednesday a holiday. One date, one decision, applied to whoever it concerns.

The rules themselves

This is the part that decides every argument at the end of the month, and it is worth setting up properly once.

Late, and when late starts

Set the grace period for arriving and the grace period for leaving. A ten-minute grace means somebody at nine minutes past is on time and somebody at eleven minutes past is late by one minute, not eleven.

What counts as a half day

Set the hours below which a day is half, and the hours below which it is absent. Either as a number of hours, or as a percentage of that day's shift — which is the better choice for a school with a short Friday, because fifty per cent of Friday is not fifty per cent of Monday.

And decide whether breaks count as worked time or are deducted.

What lateness costs

Set your own ladder. Thirty minutes late in the month costs half a day. Sixty minutes costs a day. Ninety costs a day and a half.

Count it monthly across the whole month, or daily against each day. Count late minutes, or late days, or late minutes plus early departures. It is your policy; the system applies it.

Overtime

Where your school pays it, set the minimum overage that counts as overtime and the rate it is paid at — time and a half, double. Work past the shift that does not reach the minimum is not overtime, which stops ten minutes becoming a claim.

An absence that costs more than a day

Some schools charge an absence at more than one day's pay. Set the multiplier and it is applied consistently. It cannot be set below one, because a policy that pays people for not coming is not a policy.

The weekend between two absences

A teacher is absent on Friday and absent on Monday. Was Saturday a weekend, or a third day absent?

Set your rule: treat the weekend as absent if the day before was, if the day after was, if both were, or if either was. And whether the same applies to public holidays.

This is the single most argued-about rule in Pakistani school HR, and setting it once in writing is worth more than any report in this module.

Written so somebody can actually set it

The policy screen is in four sections with plain names and a help note on every setting, rather than one long page of terminology.

And it refuses to save a policy that does not make sense. An absent threshold above the half-day threshold. An overtime threshold longer than the working day. Two penalty tiers at the same number. You are told what is wrong before you save it rather than discovering it in a payroll run.

Processing the day, with the figures in front of you

Pick a date and see what the day would produce for every employee before anything is saved: their in and out times, hours worked, break time, overtime before and after the multiplier, late minutes, early minutes, whether it is a half day, their status, and any leave.

Review it. Then save it.

Where a day needs redoing — events arrived late, a correction came in — delete it and process it again. It rebuilds from the records rather than patching what was there.

Several days at once can be processed together, up to a month at a time, for a school catching up.

Breaks, recorded rather than assumed

Where somebody checks out and back in during the day, that gap is recorded as a break with its start, end and length. The day's hours are then honest about it, and you can see why somebody's hours look short.

Processing the month, which is what payroll uses

Name the period and give the dates, and see every employee's month before saving: present days, absences, lates, early departures, half days, total hours, break time, overtime, paid and unpaid leave, partial-paid leave, weekends, holidays, penalties — and the three figures that matter.

Gross payable days. What the month earned before penalties.

Penalties. The late ladder, plus the extra cost of absences where your multiplier is above one.

Net payable days. Gross, less the penalties, and never below zero.

That last figure is what payroll reads. One number per employee, arrived at by rules your school wrote, with every component visible above it.

Where HR needs to use judgement

A teacher was late three days. The policy charges a day. She has a doctor's note.

Rather than either overriding the policy or ignoring the note, HR can offset that penalty against her leave balance instead — take the day from her casual leave and credit the penalty back. The screen shows what the penalties were, how much is adjustable, what has already been adjusted and what is left.

Where the leave type is paid at a fraction, the offset is worked out proportionally.

And once the month is finalised, no further adjustment is possible. Discretion before the lock, not after.

Leave, applied for and approved

Applying

Pick the employee, the leave type, the dates and the reason. Only leave types they actually have balance in are offered.

Where the leave type requires a document — a medical certificate — the form asks for it and will not submit without it.

Their recent leave history is shown alongside, so whoever is approving has the context without opening another screen.

Approving, and what it does

Approval is a separate permission from editing, because they are different decisions.

On approval, the leave is checked against your rules — the shortest and longest run allowed, whether it overlaps something already approved, whether the balance exists — and then applied.

Partly paid, rather than overdrawn

This is the detail that stops most disputes.

A teacher asks for ten days and has three days of balance. The system does not refuse the leave and does not put her thirty-seven per cent into the negative. It works through the ten days in order: the first three are paid leave and come off her balance, the remaining seven are unpaid leave.

Her balance ends at zero, not at minus seven, and her payslip is correct without anybody calculating it.

Where your school does allow a negative balance, it does — because you set that per leave type.

The weekend inside the leave

Where your leave type says so, a weekend or holiday next to the leave is drawn into it and comes off the balance, by the same four rules as above. The record shows which days were asked for and which were added, so the employee can see exactly what was deducted and why.

Reversing an approval

An approval given in error is declined, and every day it consumed goes back onto the balance, recorded on the ledger as a reversal rather than quietly reduced.

The register, and the reports

The register shows every employee's month at a glance — presents, absences, leaves, half days, weekends, holidays, late days and minutes, early departures — and expands to show each day with its in and out times, hours, source and status.

Reports cover attendance events, the daily summary, the monthly summary, late arrivals, overtime and the weekend rule, filtered by campus, department, designation and employee. Networks can see late arrivals across every campus on one report.

Teachers can see their own shift

Where you switch it on, a teacher sees their shift times in the Muallam app. Schools running a morning and an afternoon shift find this removes a surprising number of questions in the first week of term.

Before you ask

Questions schools ask

Can we use a biometric device?

Yes, and the records arrive in the same place as records from the Muallam app and records typed in by the office. Each one shows where it came from, and device records are protected by their own permissions.

What if we do not have a device yet?

Download a spreadsheet for the dates you need. It arrives with every employee, every date and each person's own shift times already filled in, so you only change the exceptions. Upload it back and any row that fails comes back with the reason.

Can a shift have different hours on different days?

Yes. One shift can run nine to three Monday to Thursday and nine to twelve on Friday, and the day's calculation uses the right hours for the right day.

Can it handle alternate Saturdays?

Yes. Set the weekend days for odd weeks and for even weeks separately. Nobody has to remember which kind of Saturday it is.

Can a holiday apply to some staff and not others?

Yes. Set who it applies to, and separately who it does not — a holiday for the whole school except the security staff, or for the primary wing only.

How do we handle exam week, when the timings change?

Set a date range with the shift and policy that apply instead, and who they apply to. When the range ends, your normal rules come back by themselves. A single day can also be flipped — a working Saturday, or a sudden holiday.

Can we set our own late penalties?

Yes. Build your own ladder — thirty minutes in the month costs half a day, sixty costs a day — counted monthly or daily, on late minutes, late days, or late minutes plus early departures.

What happens to a weekend between two absences?

Whatever your school decides. Treat it as absent if the day before was, if the day after was, if both were, or if either was — and the same choice separately for public holidays. It is then applied the same way every month.

What if someone asks for more leave than they have?

The days are worked through in order. If a teacher asks for ten days and has three, the first three are paid leave off her balance and the remaining seven are unpaid. Her balance ends at zero rather than in the negative, and the payslip is right without anybody calculating it.

How does this reach payroll?

The month produces one figure per employee — net payable days — after your penalties are applied, and payroll reads that. Everything behind it is visible: gross payable days, each penalty, and every day that produced them.

Bring us your late policy

Book a demo with your actual rules — the grace period, the penalty ladder, the weekend rule — and we will set them up and run a month in front of you.