Operational Core — The Records Behind the Work
Manage the people, work, events, communication, knowledge, and relationships that support HEPO's three offerings alongside existing business systems.
Manage attendance records and their review lifecycle across working styles, with clear links to people, time definitions, and operational context.
Presence is HEPO's module for attendance and working-style records. It supports recording and reviewing how people participate in the working period, using the organisation's configured types and lifecycle. Administrators and participants can examine submissions, decisions, corrections, and relevant event information.
These records help coordinate work and supply context where an authorised analysis needs it. Presence is one source of information about activity; being recorded as present does not establish engagement, performance, or wellbeing.
A person may work on site, remotely, in the field, or in training during different parts of a week. Absence and leave have their own relevant definitions and processes. The organisation decides how these situations are represented and how records are submitted and reviewed.
The module's lifecycle includes submission, approval, rejection, and contesting a record, with self-service and administrative views. Those operations make a reviewable attendance record more useful than a free-text note. Their use still depends on the applicable policy and configured authority.
| Connection | What it helps explain |
|---|---|
| Employee | Whose record is being reviewed |
| Time definitions and schedule assignment | Which working pattern and attendance type apply |
| Events | Which relevant occurrences or attendance events accompany the record |
| Work and project context | What activity the organisation has explicitly related to that period |
| Lifecycle decisions | How the submitted record was handled |
HR Time Management supplies the definition layer for schedules, types, holidays, and quotas. Calendar Events describes occurrences. Presence records the attendance account that is reviewed against that context.
A team reviewing flexibility can examine the working styles represented in its records and compare them with the arrangements it intended. That can inform a discussion about scheduling or coordination. It cannot establish how connected a remote colleague feels, or why an absence occurred, from attendance alone.
The visibility boundary applies to any cultural use. Observation scope, access, and purpose must be explicit; participant experience remains another source of understanding.
HR and operational owners agree types, submission responsibilities, and correction procedures. Implementers configure the supported lifecycle and access. Walk a representative record through submission, approval or rejection, and any contest or correction, then check how the result appears to the participant and the reviewer.
The useful result is an attendance account the organisation can coordinate around and examine in context.