HR — Add a retroactive attendance entry

Employees forget to punch. When they do, HR adds the event on their behalf with the actual time, and the work session rebuilds correctly. The audit trail is preserved — every retroactively-added or deleted event is stamped with the HR member's name and a timestamp, so the change is traceable.

Opening the modal

1. Click HRMS in the sidebar → "For HR" → Workspace attendance (or visit /hr/attendance directly). Click the employee whose record needs fixing.
2. On their per-employee page, click + Add retroactive entry in the top right.

The modal fields

1. Event type. One of Clock In, Clock Out, Break Start, Break End. Pick what the employee forgot to press at the time. The most common entry is Clock Out for the previous day.
2. Date. The calendar day the missed event belongs to.
3. Time. The exact time in the workspace timezone — e.g. 19:35 for someone who left at 7:35 pm. Use the time you and the employee agree was real, not "now".
4. Note (recommended). One sentence on why the event was added retroactively — "Forgot to clock out Friday, confirmed via Slack". This shows up in the day's event log and helps anyone reading the audit trail later.

Click Save. The session for that day rebuilds immediately — if it was open because the original clock-out was missing, it now closes at the time you entered. Worked-hours totals on the calendar update automatically.

Deleting a wrong event

When the original event was logged but at the wrong time (employee accidentally clocked in at 9am for a 2pm shift), the fix is two steps:

1. Open the day drawer by clicking the day on the employee's calendar.
2. Click the trash icon next to the wrong event. The system writes an internal HR_EDIT_DELETE sentinel so the deletion is tracked, then rebuilds the session without the bad event.
3. Add the corrected event using the modal above.

Edge cases

• Adding a Clock In to a day that already has one. The validator rejects this — only one clock-in per day is allowed. Delete the existing one first if you mean to replace it.
• Adding a Break End without a Break Start. Rejected — breaks must come in pairs. The error message tells you the missing event type.
• Adding events out of order in time. Allowed (the session builder sorts events by timestamp), but the resulting timeline only makes sense if the times themselves are coherent. Double-check before saving.
• Cross-midnight sessions. Currently a session is one calendar day. If someone worked 10pm to 4am, create two day's worth of events — clock out at 23:59 on day one, clock in at 00:00 on day two. We'll revisit this in a future phase.