Employee checks in
Check-in or check-out happens from the Android app at the workplace.
Mobile attendance verified against workplace context and turned into a clear operational state for management.
Employee app, workplace location and Wi-Fi verification, management web, automation, and notifications in one operating loop — without continuous employee tracking.
Check-in, check-out, and attendance-related requests
Location + workplace Wi‑Fi according to organization settings
Turns verified actions into a reviewable operational state
Enabled operating rules react to relevant attendance states
WhatsApp is the currently supported operational notification channel
Review states, exceptions, requests, reports, and setup
The employee performs the action, RAKZ verifies workplace context, and the result becomes an operational state management can review and act on.
Check-in or check-out happens from the Android app at the workplace.
Location and workplace Wi-Fi are checked against enabled organization controls.
The result is reflected in the employee state and attendance record on the web.
When an enabled rule is met, WhatsApp can notify the responsible team for review.
A direct Android experience for check-in, check-out, and attendance-related requests under the independent RAKZ product identity.
A web experience for employees, attendance states, requests, reports, workplace policies, locations, and notifications.
Purchase and subscription management happen through WESSAAL. Once RAKZ is enabled for an organization, employees use the RAKZ app for attendance actions tied to workplace context.
Google PlayAndroid is the current public employee-app scope for RAKZ.
App StoreiOS is not part of the currently published public scope.
RAKZ is designed for Saudi workplace context and treats Arabic, RTL behavior, time, status, and organization policy as first-class product concerns. The heritage reference is inspired by the rhythm of Najdi architecture and stays secondary to the product itself.
RTL, numbers, time, control order, and spacing are reviewed as an original experience rather than a late translation.
Locations, networks, and attendance policies stay tied to how each organization operates.
WESSAAL is the operating, commercial, and legal provenance for the product.
RAKZ uses location and Wi‑Fi information during attendance actions to verify approved workplace context. The product is not a continuous tracking system and does not present a persistent GPS history of employee movement outside the attendance action.
Every plan includes the Android employee app, attendance management on the web, location and Wi-Fi verification, adjustments, leave management, and reports. Plans differ by resource capacity and operational history access.
No. Public location use is tied to the attendance action context and is not continuous background tracking.
RAKZ is designed around employee mobile attendance with workplace verification instead of relying on a separate biometric device for this operating loop.
In the RAKZ web experience, with employees, requests, reports, policies, locations, and operational settings.
Attendance states covered by enabled automation rules can generate operational notifications. WhatsApp is the currently supported notification channel.
The current public employee-app scope is Android. RAKZ does not advertise iOS as a released public capability today.
RAKZ is purchased and its subscription is managed through WESSAAL while the product keeps its independent RAKZ identity.
Buy RAKZ through WESSAAL and configure workplace verification and automation around how your organization operates.