OpsGrids HRMS keeps your people records, attendance and attendance corrections in one place, inside the same organisation and login as the rest of OpsGrids. It is built for teams spread across offices, shops, warehouses and sites, where attendance is marked away from a desk and a wrong mark needs a clear way to be put right. Personal data stays masked until someone with the right permission reveals it.
Who it is for
- An HR lead at a business with several sites who needs to know whether a check-in happened at the place it belongs to.
- A founder or operations head who wants attendance corrections approved by the right manager, not settled over chat messages.
- A business that keeps employee details in a spreadsheet and wants them encrypted, with a record of who looked at them.
- A team with more than one shift, where each location runs its own shift pattern.
What you can do with it
Employee records, lifecycle and reporting lines
Each employee has one record with their lifecycle transitions and the person they report to. The reporting line is what makes approvals work: when a correction is raised, OpsGrids knows whose desk it goes to.
Encrypted personal data with an audited unmask
Personal details are encrypted and shown masked by default. Someone who needs to see a value can unmask it only if they hold the permission, and every unmask is logged. HR can work without every manager seeing every phone number.
Check-in and check-out
Staff check in when they start and check out when they finish, so each day has a recorded start and end rather than a tick in a register.
Shifts
Define the shifts your team actually works, so each person's check-ins sit alongside the shift they were expected to work. That matters when a morning shift at one site and a night shift at another sit in the same organisation.
Geo-fences
Draw a geo-fence around each site so a check-in can be judged against the place it should come from. Our attendance geo-fencing guide covers choosing boundaries, field staff and the limits of location.
Attendance regularisation with an approval chain
When a mark is missing or wrong, the employee raises a regularisation request. It routes up their reporting line, escalates to the manager's manager if it goes unanswered, and applies to the attendance record on approval. This is the one approval chain running end to end in OpsGrids today. Notification rules can tell people on WhatsApp or email when a step escalates or a decision is made (see automations).
How it fits a working week
| When | What happens |
|---|---|
| Setup | HR adds employees with reporting lines, defines shifts and draws a geo-fence for each site. |
| Each day | Staff check in and check out against their shift and site. |
| When a mark is wrong | The employee raises a regularisation request; it goes to their manager. |
| If nobody answers | The request escalates to the manager's manager instead of waiting in an inbox. |
| On approval | The correction applies to the attendance record. |
| End of week | HR reviews the corrections, looks at repeated misses at a site and adjusts boundaries or shifts. |
Why approvals stall, and how to design a chain that keeps moving: stop chasing approvals.
Employee data and privacy
Employee records hold some of the most sensitive data a business keeps, and attendance adds location to it.
- Masked by default. Personal details show masked on screen.
- Reveal is a separate permission, logged every time. Seeing the full value needs its own permission, separate from viewing the record. Every reveal is logged, so you can answer "who looked at this, and when?"
- Scoped access. Permissions carry a scope: own, team, location or organisation. For example, you might let an employee see their own record, a manager their team, a site head their location and HR the whole organisation. See privacy and permissions on the platform page.
India's Digital Personal Data Protection Rules were notified in November 2025, and the main obligations are reported for around mid-May 2027. They are not in force today, and those dates come from secondary reports, so confirm timing and duties with your counsel. Location and attendance data are personal data, so giving notice and recording consent to that standard now avoids a rebuild later. OpsGrids gives you masking, scoped access and a reveal log; it does not make you compliant on its own, and what you must tell staff and record is a question for your counsel.
Where it stops today
OpsGrids HRMS has no leave ledger and no payroll yet. If you run payroll through a provider or your CA, keep doing so: OpsGrids holds attendance, not pay. Keep your existing leave process (a leave register, a spreadsheet or your current tool) alongside it for now.
Questions buyers ask
Does OpsGrids HRMS run payroll? No. There is no payroll today. Plan to keep a payroll provider or your current payroll process alongside it.
Can staff apply for leave in it? Not yet. There is no leave ledger, so keep your existing leave process running for now.
What happens when a manager does not respond to a correction? The request escalates to the manager's manager. Once approved, the correction applies to the attendance record.
Who can see an employee's phone number or other personal details? Only people whose permission covers that employee, by scope, and only after a reveal that is logged every time. Everyone else sees a masked value.
Can different sites have different attendance rules? Each site can have its own geo-fence, and people can be on different shifts. The geo-fencing guide covers choosing boundaries.