Ambulance station and school, bakery and pub, unit and outpatient clinic: many businesses plan areas that have nothing to do with each other - except for the people who work in both. When separate schedules make sense, what the structure needs to deliver, and how you set it up in four steps.
Whoever plans multiple areas in a business knows both dead ends. The first: everything goes into one schedule. The station, school and administration are listed one below the other, the staffing row lumps together things that do not belong together, and anyone who only plans the school scrolls past forty rows every week that are none of their concern.
The second: separate tools per area. The station has its own software, the school has an Excel spreadsheet, the pub has a wall planner. Each area is manageable on its own - but the person who teaches on Tuesdays and sits in the ambulance on the weekend now exists twice. Two vacation accounts, two time accounts, two logins, and nobody sees that they are standing in front of the class at 8 a.m. on Monday after a night shift.
Not every business with two departments needs two schedules. Kitchen and service in the same restaurant work at the same time, in the same place, and are planned by the same person - that is two workplaces in one schedule. A dedicated schedule per area pays off when at least two of these points apply:
So that separate schedules do not turn into separate worlds, the software needs a clear hierarchy: Schedule → Workplace → Shifts. The schedule is the frame that a planner opens. Inside it sit workplaces such as Ambulance 1, the classroom or Unit 3, and each workplace has the shifts that run there attached to it. Four things need to be solved here:
Create a schedule for every area with its own shifts, times or planners: “Ambulance station”, “School”, “Bakehouse”, “Pub”. Less is more: two to four schedules are the right number for most businesses.
Assign each schedule its workplaces and attach the shifts to the workplaces: Ambulance 1 with a 24-hour shift, the classroom with morning and afternoon, the bakehouse with an early shift from 3 a.m. A workplace used by two areas gets both schedules. Shifts without a fixed workplace, such as on-call, you assign directly to a schedule.
Each person belongs to one or more schedules. That belongs where you maintain the master data anyway - in the employee form when creating them, and in the personnel file when something changes later. Anyone who only drives for the station gets the station; the practical trainer gets both station and school and appears in both schedules, with one account.
Day to day, the planner just needs one switcher in the schedule that lets her move between station and school. People, workplaces, shifts and the staffing row follow the selected schedule. A person who is on both appears on both; so do their absences and conflicts.
Ambulance station with paramedic school: The station runs around the clock, the school teaches according to a course schedule. Paramedics with a teaching assignment appear on both schedules. The conflict check has to work across both: anyone who was out on the ambulance overnight on Sunday cannot stand in the classroom at 8 a.m. on Monday. Rest periods know no schedule boundary.
Bakery with pub: The bakehouse starts at 3 a.m., the pub closes at midnight. Two schedules, two planners, almost no overlap - except for the baker who helps out in service on Saturdays, and the manager who keeps an eye on both. She switches between them instead of opening two spreadsheets; the hours come together in one time account, and the DATEV export stays one export.
Hospital with units and outpatient clinic: Each unit plans for itself, and so does the outpatient clinic. The pool staff member who is deployed on Unit 2 or in the outpatient clinic is on both schedules. The outpatient clinic as a workplace sits on its own schedule and on that of the unit it helps staff during the day - on each schedule, the staffing row only counts what belongs to that schedule. Annual vacation planning still runs for the whole facility in one overview, grouped by schedule.
We built exactly this structure into Presio. An organization can run multiple schedules and everything else stays as it is:
In short: the Shift-planning software for multiple teams gives every area its own schedule and still keeps the person behind it as one person. For businesses with a single area, nothing changes - there is exactly one schedule.
Multiple workplaces in one schedule are enough when the areas are planned at the same time, in the same place, by the same person - kitchen and service in a restaurant. Multiple schedules pay off when the areas have their own shifts and times, are planned by different people, or are at different locations - ambulance station and school, bakery and pub.
Yes. People are assigned to one or more schedules in the employee form or in the personnel file. They then appear in each of these schedules but have one account, one vacation account and one time tracking. Absences and rest periods apply across all schedules.
Yes. A workplace such as a training room or an outpatient clinic can sit on multiple schedules and then appears under each one with its shifts. The shifts at this workplace automatically follow the schedules of the workplace.
Nothing - they stay one. The schedules only split up the planning, not the person. Hours from all schedules come together in one time account, vacation is deducted from one vacation account, and the payroll export stays one export per person.
No. Anyone who only needs one schedule has exactly one; the switcher only appears once a second schedule is created. All existing shifts, workplaces and people stay as they are.
Plan station and school, bakehouse and pub, unit and outpatient clinic separately - with one time tracking system, one vacation account and one login per person. Free to start until 31.10.2026, no credit card.
Try Presio for freeSign up, create your team, get started - try Presio free and with no obligation, no credit card needed.
Start your free trial