Use case · Software, operations
Anonymised, like all our use cases
The shift plan, without spreadsheet chaos.
A customer service department with several teams plans phone, email and second level week by week. For them we built a shift planner: managers plan in drafts and only publish once the plan is settled. Holidays, sick leave and shift requests run through the same application.
Deployed in
Customer service, several teams
Services
Software, operations
Roles
Employees, managers, admins
Languages
German, English, Ukrainian
The plan in your pocket.
Employees see their month on their phone, request holidays and download their shifts into their calendar. Planning happens in drafts, only what is published is visible.
How a shift plan comes together.
- Plan Managers enter shifts with working time and break, drag them onto other days or copy whole periods, repeated weekly if needed.
- Coordinate Employees request holidays, sick leave and extra shifts themselves. Managers and admins decide. An email reports on holiday requests.
- Publish One click makes all drafts in the period binding, for individual teams if required.
- Work Everyone sees their team’s plan and their own month and downloads their shifts into their calendar.
- Evaluate Admins see the hours worked per person, split into weekdays, Saturday, Sunday and weekend shifts.
3
roles: employees, managers and admins
4
types of absence, only holiday counts against the allowance
0
shifts overwritten when copying or transferring
1 click
to add the public holidays of a federal state
One application, six areas.
From the weekly plan to the hours report in one place, on the same platform as the service desk and ticket system.
Software
Shift plan
Week or month, grouped by team, with staffing and hours per day. Tabs for the final plan, planning and your own plan.
Automation
Transfer and copy
Drag shifts onto further days, copy and repeat periods, take over shifts between colleagues.
Software
Holidays and absence
Requests in a side panel, with a holiday account showing allowance, used, requested and remaining.
Software
Shift requests
Employees ask for extra shifts. A calendar shows open requests and overlaps.
Automation
Reports and calendar
Hours per person by week or month, your own shifts as a calendar file, key figures on the cockpit.
Platform
Administration
Employees, contracts, working days, teams and public holidays by state, with help and short demos inside the application.
What makes the difference.
Drafts before the plan
Employees only see what has been published. Unfinished planning stays with the planners.
Nothing is overwritten
Copying and transferring skip occupied days and absences and report what could not be done.
Holidays that add up
The allowance is prorated from the contract. Only the person’s own working days count, public holidays never do.
Rights follow the hierarchy
Managers plan their direct reports. Nobody decides their own requests.
What we built it with
- .NET 10
- Blazor
- .NET Aspire
- PostgreSQL
- Redis
- iCalendar
- Docker
- GitLab CI
- Ansible
- OpenTelemetry
Where is your team still planning in Excel?
In an intro call we look at which processes in your business deserve an application of their own.