HRMS Suite

What was broken

HR data lived in several disconnected places. Leave requests went through chat, attendance came from a separate device export, and payroll inputs were compiled by hand. Sensitive employee information was also more widely visible than it should have been.

How we built it

1. Permissions as a design inputRoles for employees, managers, HR and admins were defined before features. Every endpoint checks access against that model, so sensitive fields are protected by default.
2. Self-service for the common casesEmployees apply for leave, check balances and view attendance themselves. Managers approve from a single queue.
3. Attendance that reconcilesDevice imports, manual corrections and approved leave are reconciled into one daily record, with an audit trail for every change.
4. Clean payroll inputsAt the end of each cycle the system produces a checked summary of days, leave and adjustments, ready for payroll.

Inside the product

The real product is confidential, so these screens are illustrative mock-ups. I can walk you through the real product on a short call.

Confidential · internal product

Illustrative mock-up.

Request a live demo →

Confidential · internal product

Illustrative mock-up.

Request a live demo →

What changed

Leave, attendance and records now live in one system with clear ownership. Managers approve in one place, employees answer their own questions, and access to personal data follows explicit rules instead of habit.

“Security, permissions and observability are design inputs, not a hardening sprint at the end.”