Employee Experience

Employee Mobile Attendance Blueprint

This screen is the web version of the employee app flow so you can convert the same UX into mobile later. It follows the hybrid logic already supported by the backend: bootstrap, check-in/out, offline queue, sync, history, and leave.

Employee Daily app usage Ready to convert into app screens

Punch Check-in / Check-out Validated against branch, shift, and policy.

Offline Queue SQLite App stores unsynced punches locally until network returns.

Tracking Ping During Session Optional continuous location stream while attendance is open.

Employee Screen Set

These are the core mobile surfaces you can build directly from the backend that is already in place.

Dashboard Show assigned branch, shift, attendance policy, today status, and sync health.

Check In / Check Out Capture GPS, selfie, device info, network type, and remarks if the policy asks for them.

History & Leave Let the employee review attendance rows, sync queue outcomes, and leave requests without admin help.

Mobile Behavior Rules

The app should stay honest even when offline.

Never trust device time alone Send device punch time, but let the server compare sync delay and drift.

Queue items need stable local IDs Each offline punch should have a unique queue identifier to prevent duplicates.

Keep sync visible to employees People should know whether a punch is synced, pending, or flagged.

Workflow

This is the execution path the module supports.

Employee logs in and bootstraps The app loads policy, branch, shift, and employee context.

Employee punches online or offline If online, record is sent immediately. If offline, it is stored locally.

Sync and review continue When connectivity returns, queued items sync and the app can show updated results.

Key Data Touchpoints

These entities stay connected to this module across setup, attendance capture, and review.

mobile bootstrap attendance_logs attendance_sync_queue attendance_location_tracks leave_requests

Connected Backend APIs

These endpoints already exist in the backend and are the intended integration points for the frontend or mobile app.

Method	Endpoint	Purpose
GET	`/api/attendance/mobile/bootstrap`	Load employee app context before the workday starts.
POST	`/api/attendance/mobile/punch`	Submit live check-in or check-out.
POST	`/api/attendance/mobile/sync`	Upload queued offline attendance items.
POST	`/api/attendance/mobile/location-ping`	Track employee location during an active attendance session.
GET	`/api/attendance/mobile/history`	Show employee attendance history in the app.

Employee App Conversion Notes

These screens are shaped as mobile-friendly prototypes so you can convert the same flow into the app later.

Employee Dashboard

Start with the minimum daily information the employee needs before they act.

Today Check-in pending Shift General Shift Branch Kolkata Office Sync 0 pending

Attendance Capture

This screen should feel immediate and focused because it is used every day.

GPS Auto capture Selfie Required Network Wi-Fi / Offline Mode Office

Offline Queue

Employees should always know if a punch is still waiting to sync.

Queue ID Local unique ID Status Pending sync Delay Show elapsed time Retry Automatic

History & Leave

After attendance capture, employees need transparent access to their own records.

History Past punches Leave Apply / track Approval Show flagged items Remarks Visible