Shift planning
Plan shifts per staff member here – as a calendar, planning board or list. Dispatch sets the demand, assigns shifts and publishes the roster; the team sees its own roster, confirms shifts and can offer shifts for swap.
Live preview — real view with sample data
M32 · Shift planning
| Person | Shift | Status |
|---|---|---|
| Entry 2 | In progress | In progress |
| Record 3 | Done | Done |
| Item 4 | Reviewed | Reviewed |
| Entry 5 | Open | Open |
| Record 6 | In progress | In progress |
Not a screenshot: the same interface you get in production.
What you do here
Use „New shift“ to capture date, shift type (early/late/night/flex), start, end, break and location and assign the shift to a person. Leave the person empty and it becomes an open shift the team can pick up. „Confirm“ makes a planned shift binding.
Demand & coverage
Set a demand (target) per day, location and shift type. The coverage view shows the actual staffing next to it – assigned, open and shortfall. That way you spot gaps before the roster is published.
Swaps & publishing
If someone cannot work a shift, they offer it via „Offer for swap“; a colleague takes it over, dispatch approves. The roster only becomes binding once „Publish“ is used – changes after that are notified to the team. In companies with a works council the roster is subject to co-determination (§ 87 BetrVG).
Working-time law
The break belongs in every shift (§ 4 ArbZG: 30 min above 6 h, 45 min above 9 h). When planning, keep the 11-hour rest period (§ 5), maximum working time (§ 3) and the night-work limits (§ 6) – the planned hours per shift help with that.
What's inside
- Roster
- Planning board
- Shifts
- Shift
- Offers & swaps
- New shift
- Set status
- Assign
- Publish
- Back to draft
- Confirm
- Offer for swap
- Take over shift
- Approve swap
- Withdraw or decline offer
Fits together with
Other blocks from the same area.
Absence
Here staff request holiday and report absences (sickness, home office, special leave, maternity, parental leave); the back office approves or rejects them – with an optional stand-in. The per-person, per-year leave account shows entitlement, taken, planned and remaining days.
M29Client master
The central client record for care: one person with everything around them – master data, home access, relatives and legal guardianship, payers, care level with history, physician's order. The basis for routes, visits and care documentation.
M30Employee master
The central employee master: maintain all staff with their core data, employment and contact details in one place – independent of the app login.
M31Member master
The central member master for clubs: core data, membership, offices and divisions in one place – plus a real fee account (charge/payment/open balance) with SEPA direct debit, independent of the app login.