A Paramedic calls off for Saturday night. Your supervisor needs to see which unit is short, find someone qualified to work it, and confirm coverage so the crew knows who’s reporting. That’s a good test for your new scheduling platform before it becomes the schedule everyone relies on.
Start with your roster and build from there. By the time you publish, your team should be able to answer three questions at a glance. Who’s working? What still needs coverage? What happens when a shift changes?
Start with your roster and how supervisors look at coverage
Import your staff roster and verify who’s active, which locations or departments they work in, and which qualifications you’ll use to staff shifts. Then decide what to name your schedules and how to organize the units.
Those choices should reflect how your supervisors work. A North Base supervisor might filter by location to see their units. A transport supervisor might filter by department to see interfacility crews across multiple bases. Within either view, grouping Frontline, Peak Coverage, and Event shifts can make coverage easier to scan. Labels like Days, Nights, and Midshift help distinguish when those crews work.
Put the units supervisors check first at the top. That could mean listing Medic 1 and Medic 2 before Float, or keeping 1st Out, 2nd Out, and 3rd Out in dispatch order if those are the names your crews use.
Build the shifts before assigning rotations
Define the roles you schedule, such as EMT, AEMT, and Paramedic, and document which certifications qualify someone for each role. Then list the units those roles staff and build reusable shifts that specify the unit, role, and hours. For example, Medic 1 Nights · Paramedic · 6 p.m.–6 a.m. gives schedulers more to work with than a label that just says “Nights.”
Once the shifts are defined, build the rotations your crews actually work.
| Pattern | What it might look like |
|---|---|
| 24 on / 48 off | A, B, and C crews take turns covering a unit from 6 a.m. to 6 a.m. the following day. |
| 12-hour 2-2-3 | Day crews work 6 a.m.–6 p.m. and night crews work 6 p.m.–6 a.m., with alternating weekends. |
| Front half / back half | A back-half crew works Wednesday through Friday, plus every other Saturday. |
| Fixed weekdays | An interfacility transport crew works four 10-hour shifts, Monday through Thursday. |
Assign employees to their patterns and generate a draft that covers a full rotation. Check the start dates, overnight end dates, and alternating weekends. A rotation can look right in week one and still put the wrong crew on Saturday in week two.
Set staffing requirements and decide how to fill openings
A rotation tells you who’s assigned. A staffing requirement tells you how many people you need in each role. Set the requirements by unit, shift, and day of the week so you can compare them with the schedule you generate.
For example, Medic 1 might need one EMT and one Paramedic every night, while Peak 3 Midshift only runs noon to midnight on Fridays and Saturdays. If Saturday’s Peak 3 has a Paramedic assigned and still needs an EMT, create an opening for the EMT position. The weekday gaps on Peak 3 are expected because the unit isn’t scheduled to run.
Decide how staff should fill those openings before you publish. Can eligible employees claim certain shifts directly, or should they submit a bid for supervisor review? Can they pick up part of a shift? Who gets notified when coverage is still missing near the start time? Test the answers with one actual opening so your schedulers and crews know what to expect.
Publish the schedule and walk crews through their first week
Have a scheduler and a field supervisor review the draft together. Check regular assignments, approved time off, and open positions. Then tell crews the exact date and time the new schedule becomes official and where to check for changes.
Use an upcoming shift to show staff how to find an assignment, bid on an opening, request a trade, and submit time off. Have a supervisor test one of those requests from submission through approval so both sides can see what happens to the schedule.
If timekeeping is changing at the same time, test that handoff too. An overnight crew that clears a late call after its scheduled end time is a good example to walk through from clock-out to timecard review.
How this works in VAIRKKO
In VAIRKKO Scheduling, you can filter by location or department, organize shifts with shift groups and shift types, and set the order in which jobs appear in the schedule editors. A job can represent a unit like Medic 1 or a staffing assignment like Float.
Staff Roles tie positions to qualifications, and Shift Templates combine the job, role, and hours. Shift Patterns define when shifts repeat, and Pattern Assignments connect employees to those rotations. Workloads set how many positions are required by job, shift, and weekday.
In Generation & Publishing, you generate the schedule for the dates and locations you’re preparing. Then Open Shift Creation checks the schedule against those workloads and creates openings where required positions are missing. Once you publish the schedule for staff, they can view assignments, bid on openings, request trades, and submit time off based on your agency’s settings.
Join the conversation
If you've switched scheduling platforms, what's one thing you wish you'd tested before publishing the first schedule?
