KMI HRM · PART 3 · NOVEMBER 2026
The web dashboard covered everything, but an HR manager on a factory floor is rarely at a desk. Leave waits for approval, a machine goes offline, and someone needs a payslip now. KMI Connect was already on the staff’s phones, so from October 2026 I built the HRM module into it.
How attendance, HR and payroll for a Pakistani company of several sites and plants came together, from fingerprint machines to the phone in an HR manager’s hand.
HR work does not stay at a desk, so I built the HRM module into the KMI Connect app in two halves: My HRM for employees and HR Admin for the people who run HR. One sign-in decides which one you see, and every action runs the same rules as the website.
Employees and HR managers need very different things, but nobody wants two logins. So there is one KMI HRM sign-in, and the role decides what opens. Super admins and HR staff get HR Admin. Employees get My HRM. Someone who is both gets a switch. HR Admin also opens behind fingerprint or face, because a phone left on a desk should not show salaries.
I started with the employee side on 11 October: attendance, leave, notifications and payslips. Later in the month came a My Work section, with issues, duties, team and appraisals. Starting here meant the live updates and the app’s connection to the HR system were already proven before admin screens depended on them.
The app has five tabs, and each answers one question an HR manager asks during the day:
The dangerous way to build this is to write the rules a second time in the app. Sooner or later, the app and the website would disagree about a leave balance or a salary. So when you approve leave on the phone, it runs the website’s own approval, with the same balance updates, payroll effects and notices to the employee. Edits go through the website’s own controllers too. The app is a new front door, not a second building.
Copying each website page by hand would have been slow and hard to maintain. All seven reports share one report screen, setup and Super Admin pages share one list screen, and the More menu is built from a list of modules, filtered by what each login may access. Adding a report is mostly a matter of describing it.
Real use found problems no plan would. The app runs edge to edge, so on Android the keyboard covered form fields near the bottom of the screen. I fixed that once at the root of the app rather than screen by screen. Long forms also needed a way forward, so the employee form now has “Skip for now”, and the first page asks for what HR actually knows on day one.
A mobile app for an existing system should be a new front door, not a second set of rules. If the phone and the website can disagree, eventually they will.