Create a manual staff attendance shift
Create a planned attendance shift for a staff member at Harbor Soho. The flow records a manual `staff_shift` calendar event with a staff member, planned start, planned finish, location timezone and manual source.
In this article
Use this guide when a manager needs to add an attendance shift manually before or after planning coverage. In the Harbor Soho demo, the example staff member is Olivia Hart and the location timezone is Europe/London.
Manual attendance creation is part of the calendar flow. It creates a `calendar_events` item with `kind=staff_shift`; it is not the correction-request flow and it is not documented as a direct `staff_shifts` record creation.
Before you start
- You are signed in with Harbor Demo Group and Harbor Soho selected.
- Your location role allows staff shift management with `staff-shifts:manage`.
- Your location role allows staff viewing with `staff:view`, so the staff selector can load.
- At least one staff member exists at Harbor Soho, for example Olivia Hart.
Instructions
- 1.
Open the attendance form
Open the create-calendar flow with `kind=staff_shift`. From a general calendar entry point, the form lets you choose the staff member. From a staff profile or staff calendar entry point, the route can fix the staff member and show the employee as read-only.
- 2.
Select or confirm the staff member
Choose the employee whose attendance you are planning, such as Olivia Hart. If the form was opened from that employee's profile or staff calendar, confirm that the fixed employee shown on the form is correct.
- 3.
Set planned start and finish
Enter the planned clock-in and clock-out date and time. The form uses the location timezone, Europe/London for Harbor Soho, and the time controls move in 15-minute steps. If only a start time is seeded, the form starts with a one-hour shift.
- 4.
Review the attendance source
Check the read-only attendance source. For normal manual creation, the source stays `manual`; operators do not change it in this form.
- 5.
Save the shift
Save the form. The app sends the selected staff member, planned start and finish, `all_day: false`, Europe/London timezone and `payload.source: manual`. If the form has no title, the app generates an attendance title from the staff member's name.
- 6.
Confirm it on the staff calendar
After the save succeeds, the app shows a success message, refreshes calendar event lists and returns to the requested route. Confirm the new attendance shift on Olivia Hart's staff calendar for the selected day.
Validations and limits
- Organisation and location must be selected before saving.
- A staff member is required.
- Start and finish must be valid date and time values, and start must be earlier than finish.
- The normal form requires a planned finish, even though other attendance flows can represent open shifts.
- Users with view-only access cannot create the shift; `staff-shifts:manage` is required.
- Staff shifts do not support recurrence.
- Do not document overlap prevention for same-staff shifts; the verified analysis did not find that validation in `CreateCalendarEvent`.
- This flow creates a `calendar_events` item with `kind=staff_shift`, not a direct `staff_shifts` record.
Expected result
The manual attendance shift is saved as a Harbor Soho calendar event for the selected employee, visible in calendar surfaces after cache refresh, with manual source and no recurrence.