Request Management + Geofenced Attendance

This internal HR platform combines two problems organizations in Kuwait often solve with disconnected tools: employee requests that need multi-level approval, and attendance that should prove someone was actually at the branch or site.

On the web, managers handle leave, procurement, and IT tickets through configurable approval chains with delegation and escalation windows. Request types are not hard-coded theater — each can define who must sign, in what order, and what happens when a step stalls.

The companion React Native (Expo) app captures attendance only inside pre-defined geofences. That constraint alone removes a class of "checked in from home" abuse. Tamper-aware signals further reduce fake check-ins when users try to spoof location.

Field connectivity is unreliable, so the mobile client queues events and reconciles with the MERN backend when devices reconnect. Workers are not blocked from doing their job because a basement has weak signal; managers still get a coherent timeline once sync completes.

Automated overtime and absence calculations feed payroll without a second manual pass in spreadsheets. That handoff is where many attendance apps fail — the product stops at a CSV dump. Here the workflow was designed to continue into compensation logic.

Architecturally, one source of truth serves desktop managers and phone-first workers. MongoDB, Express, React, and Node.js power the web side; geolocation APIs and offline queues power the mobile edge. Shared domain rules keep request status and attendance events consistent across clients.

If you need geofenced attendance, multi-level approvals, or a full-stack developer who has shipped web + React Native operations software, this case study shows the practical requirements: offline sync, role clarity, and payroll-minded outputs — not only a map pin on a demo screen.