Weekly shift rota with coverage warnings
Morning, evening and overnight shifts on a seven-day grid, with a minimum staff count per shift. The grid tells you which slot is under-staffed before the week begins.
HR & workforce
ZendrockHR is attendance and leave management software built for how Pakistani companies actually run shifts. Staff clock in from a phone, a kiosk tablet or a QR taped to the door; the roster, the hours, the overtime and the leave balance all land in one place, in Urdu or English, and payroll gets a CSV instead of a register.
The problem
Most companies in Pakistan already bought something for this — a biometric machine, an Excel sheet, a register at the gate. What they did not buy is anyone with the time to reconcile it against the roster, the leave applications and the overtime claims. So attendance and leave management stays a manual job that quietly falls on one person, and it falls on them on the 28th.
It captures a thumb at 9:04. It does not know that person was rostered on the evening shift, was on approved casual leave, or left at 1 pm. Someone exports the dump and matches it by eye against a roster in a different file.
The employee messages the supervisor, the supervisor replies 'ok', and three months later nobody can say how many of the annual days are left. Two people hold different numbers in their heads and both are certain.
Next week's shifts are written up on Friday, photographed, dropped in the group. Anyone who joined the group late, or lost the message, turns up on the wrong shift — and nobody notices the Sunday evening slot is one man short until Sunday evening.
There is no agreed record of who stayed late, so OT is settled by relationship and volume. The staff who argue get paid; the staff who do not, do not. That is a retention problem long before it is an accounting one.
Punches into a sheet, leave deductions by hand, OT added from a supervisor's notes, then the whole thing emailed to whoever does the salaries. Every one of those steps is a place to make a mistake that becomes a salary dispute.
The Karachi shop and the Lahore shop each keep their own register in their own format. Head office has no idea what the combined headcount on the floor was last Tuesday, and asks by phone when it needs to know.
How ZendrockHR works
The roster is the spine. Once the system knows who was supposed to work which shift, a punch stops being a raw timestamp and becomes late, on time, short, or overtime — without anyone deciding. That is the whole trick, and everything else hangs off it.
A seven-day grid of people against shifts. Set a minimum staffing level per shift and the grid warns you where you are short before the week starts, not during it. Copy last week forward in one click, or import the sheet you already keep.
An office team taps clock-in on their phone. A factory floor uses a PIN on a kiosk tablet at the gate. A shop uses the QR on the door. Geofencing can require the punch to happen on site, so nobody clocks in from the bus.
Each punch is checked against that person's rostered shift. Worked hours, late minutes, early exits and overtime are calculated as they happen. Breaks are separate punches, so paid and unpaid time do not blur into each other.
Staff submit their week, the reporting manager approves or sends it back, and admin exports a CSV for whoever runs the salaries — company-wide or per branch. Approved leave has already blocked those days on the roster, so nothing double-counts.
What you get
Morning, evening and overnight shifts on a seven-day grid, with a minimum staff count per shift. The grid tells you which slot is under-staffed before the week begins.
Android app, browser, PIN on a shared kiosk tablet, or a QR code at the door. Same punch record whichever one is used, so a mixed office-and-floor company runs on one system.
Tie a branch to its location and off-site punches are refused. The most common complaint about phone-based attendance, closed before anyone raises it.
Day, week and month views. Worked hours, late arrivals, early exits and OT are derived from the rostered shift, not typed in by a supervisor after the fact.
Annual, casual, sick, or whatever your appointment letters actually say. Yearly balances, carry-forward where you allow it, and an over-balance warning at the point of approval.
Approving leave blocks those dates on the roster automatically, so nobody gets scheduled onto a shift they are already off for. Unavailability requests work the same way.
Staff post an open shift or name someone to take it. The swap only happens once the reporting manager approves, and the roster and the timesheet both follow it.
A timesheet export for any date range, addressed to a payroll contact set company-wide or overridden per branch, with an audit entry recording who sent what and to whom.
Each user picks their own language and the whole interface follows, right-to-left included. The floor staff read Urdu while head office reads English, on the same screens.
Who it's for
One honest number for hours worked across every branch, and a month end that does not depend on one person's memory.
The reconciliation job disappears. Leave balances are a number the system holds, not a number two people disagree about.
Their own team, nobody else's. Roster it, approve the week, approve the leave, and get told where the coverage gap is.
Clock in with one tap, see the hours the company has for them, and apply for leave somewhere it cannot be forgotten.
Every location on one account, each manager seeing only their own, with head office looking across all of it.
Shift work with real rotations, a shared kiosk at the gate, and no assumption that every worker owns a smartphone.
Why it pays for itself
The hours are already computed against the roster and the leave is already deducted. The payroll export is a download, not a rebuild. The person who lost three days to this every month gets them back.
OT comes from punches measured against the rostered shift, the same way for everyone. Staff who never argued get paid what they are owed, and the ones who argued stop having to.
Most companies do not know which shifts are chronically over-staffed and which run one man short. The roster and attendance reports show both, usually within the first month.
Where it runs
The full system for admin and reporting managers. Roster, timesheets, leave, employees, org chart, holidays, reports and settings.
The employee companion. Clock in and out, breaks, this week's timesheet, submit for approval — and approvals for managers on the same build.
One shared tablet at the gate takes a PIN per employee; a printed QR on the door works where there is no tablet. Neither needs the worker to own a phone.
Subscription
Monthly subscription, no setup fee, and we build your data with you in the first session. Cancel whenever — we would rather keep you because it works.
Freefor 30 days
One branch, your real roster, your real staff. No card. If the supervisor does not stop keeping the register in parallel by week three, it is not working and we stop.
Rs 120/ employee / month
The whole system for every employee on the roster. Minimum Rs 12,000 a month. Setup and import are free.
Rs 120/ employee / month
The same thing billed centrally for a group with several branches, where head office wants one combined view and one invoice instead of each site buying its own.
Questions we actually get asked
More from Zendrock
Start with ZendrockHR
We will walk you through ZendrockHR with your routes, your roster, your numbers — not a canned demo. If it is not a fit, we will tell you.