Module 15, Attendance & Rostering

Attendance
& Rostering

The Attendance module tracks staff presence in the hospital. It integrates with biometric devices (fingerprint, face recognition, RFID) to record check-in and check-out times, manages shift schedules, and feeds data into payroll.

What is Attendance Management?

Attendance Management handles biometric check-in/check-out, shift scheduling (assigning staff to shifts), leave management (requests, approvals, entitlements), overtime calculation, and attendance reporting. It ensures staff are where they need to be, when they need to be there.

The system handles multiple shift patterns (day, night, rotational), late arrivals, early departures, absent markings, and public holiday policies.

Why Does It Exist?

  • → Shift coverage — A hospital needs 24/7 coverage; missed shifts can be dangerous
  • → Payroll accuracy — Pay depends on hours worked; manual tracking leads to errors
  • → Leave abuse — Without tracking, staff might take unauthorized leave
  • → Compliance — Labor laws require accurate attendance records
Step by Step

How Attendance Works

1

Shift Scheduling

Managers create shift schedules (who works which shift on which day). Shifts can be fixed (e.g., 9 AM - 5 PM) or rotational (day/night rotation). Staff can view their schedules on their dashboard.

Behind the scenes: Schedules are created in advance (weekly or monthly). Conflicts (double-booking a person) are prevented. Unfilled shifts are highlighted.
2

Biometric Check-In

Staff check in using fingerprint, face recognition, RFID card, or PIN at the start of their shift. The system records the exact time. Late arrivals are flagged. Staff check out at the end of their shift.

Behind the scenes: The system de-duplicates entries (if someone checks in twice). Only the first check-in and last check-out are counted. Break times can be auto-deducted.
3

Exception Handling

Late arrivals, early departures, missing check-in/out, and absences are flagged for manager review. Staff can request corrections (e.g., "I forgot to check in but I was here") which managers can approve or reject.

Behind the scenes: Exceptions are logged with timestamps. Corrected records show both the original and corrected values for audit purposes.
4

Payroll Feed

At the end of the pay period, attendance totals (regular hours, overtime, late minutes, unpaid leave) are calculated and sent to the Payroll module. Managers review and approve before payroll processing.

Behind the scenes: Overtime is calculated based on institutional rules (e.g., 1.5x for weekdays, 2x for holidays). Approved corrections are included in the calculations.
Deep Dive

Every Feature Explained

Biometric Integration

What it is

Connect to fingerprint, face recognition, or RFID devices.

Why it exists

Prevents buddy punching (one person checking in for another). Accurate records.

How it works

API integration with biometric hardware. Check-in/out events are sent to the system and matched against the shift schedule.

Shift Management

What it is

Create and assign shifts to staff.

Why it exists

Ensures proper coverage for 24/7 operations.

How it works

Shift types (Morning, Evening, Night, General) are configured with start/end times. Staff are assigned to shifts. Rotational patterns are supported.

Leave Request vs Approve vs Types

What it is

Three surfaces: self-request, HR approval queue, and leave-type/policy config.

Why it exists

Segregation of duties and correct nav (Attendance vs HR hub).

How it works

Request: /dashboard/attendance/leave-requests (leave:request + create geo). Approve: /dashboard/hr/leave-requests (leave:approve-manager then leave:approve-hr + edit geo). Types/entitlements: /dashboard/hr/policies (leave:manage-types). Flow: Requested → manager_status → hr_status → approved only after both. Balances are ledger-backed (not live prior-year recompute).

Geo Punch Fence

What it is

Optional campus GPS fence for self clock-in/out.

Why it exists

Stops remote buddy punches when the hospital enables geo enforcement.

How it works

BranchSetting attendance.geo.* (default off; radius 200 m). Self punches require browser GPS inside fence; attendance:manage desk punches may omit. UI gates via GET /attendance/geo-fence-status. Clock-in ANDs create geography; clock-out ANDs edit geography.

Overtime Calculation

What it is

Auto-calculate overtime based on actual hours worked.

Why it exists

Ensures staff are compensated fairly for extra work.

How it works

Overtime rules are configurable (e.g., >8 hours = OT, >12 hours = double OT). Weekend and holiday multipliers apply. Overtime requests have their own approval workflow.

Overtime Request Workflow

What it is

Formal overtime request and approval chain.

Why it exists

Prevents unauthorized overtime and ensures proper compensation for extra hours worked.

How it works

Staff submit OT requests with date, start/end time, total hours, and reason. Workflow: Draft → Submitted → HOD Approval → HR Approval → Approved. Both HOD and HR can reject with reasons. Comments are tracked in a timeline. Once processed, OT hours flow to payroll.

Manual Attendance Corrections

What it is

Staff can request corrections for missed or incorrect check-ins.

Why it exists

Biometric devices can fail or staff may forget to check in. Corrections ensure accurate attendance records.

How it works

Submit manual attendance request with employee, date, check-in/out times, reason, and optional attachment. Status: Pending → Approved/Rejected. Approval auto-creates an attendance record. IP address and user agent are logged for audit.

Late Coming Policy

What it is

Configure institutional late-coming penalty rules under HR Policies.

Why it exists

Standardizes how late arrivals are penalized across the institution.

How it works

Create an active late_coming HR policy (HR → Policies; /api/v1/hr/policies) with lates-per-deduction thresholds and effective dates, not a standalone late-coming page. Late counts feed into payroll deductions.

Late Exemption

What it is

Exempt specific employees from late-coming penalties.

Why it exists

Certain roles (consultants, on-call staff, executives) may have flexible attendance requirements.

How it works

Employees can be flagged as late-exempt with optional date ranges (from/until) and a free late allowance per month. Exempted employees are not penalized within their allowance.

Technical Architecture

FieldTypeInstitutional Role
idUUIDUnique identifier for the attendance log.
staffIdUUIDInstitutional ID of the workforce member.
checkInDateTimeVerified biometric entry timestamp.
integration_idVarchar(64)Identifier of the biometric integration source.

Note: Sensitive fields use AES-256 field-level encryption where applicable.

Governance & Power

attendance:view
payroll:view

The system supports Fingerprint, RFID, and Face-ID integration. Logs are de-duplicated at the edge before being committed to the central Workforce Ledger.

1
Verification

Entry is matched against the assigned shift schedule.

2
Exception

Late arrivals or overstays are flagged for HR review.

3
Finalization

Attendance totals (overtime, late minutes) are made available for payroll.