There is no single firefighter schedule
Departments use many rotations based on staffing, labor agreements, local practice, and coverage needs. Two departments can both work 24-hour shifts and still have completely different repeating calendars.
The important part for a scheduling tool is not guessing the department. It is accurately representing the configured cycle, start date, start time, crew assignment, and any custom sequence the department actually uses.
Common repeating schedule patterns
- 24/48: one 24-hour work period followed by 48 hours off.
- 48/96: two consecutive 24-hour work periods followed by 96 hours off.
- Kelly-style rotations: repeating work/off sequences that include an additional scheduled day off within the cycle; exact implementations vary by department.
- Modified 24-hour rotations: departments may use patterns such as 24 on / 24 off blocks followed by a longer break.
- 12-hour or mixed schedules: some fire and EMS organizations use day/night blocks, mixed staffing, or non-24-hour rotations.
What a reliable firefighter schedule needs to store
- The exact repeating sequence rather than only a label like “24/48.”
- The cycle anchor date and shift-change time.
- Crew or group identity when multiple platoons rotate through the same station.
- Timezone-aware dates so a calendar does not drift around daylight-saving or travel edge cases.
- Personal events and overtime as separate layers instead of silently rewriting the station rotation.
Why the schedule matters beyond the calendar
A schedule becomes more useful when it supplies context to the rest of the shift. FireHousePal can use the configured rotation to help place meals, training, workouts, and station events on the right dates without forcing every workflow to become a calendar feature.
The schedule should remain a source of truth and a routing layer: open the real Training planner for training, the real Fitness flow for a workout, and the relevant meal or station item for its own lifecycle.
Always use the department’s actual schedule as authority
These patterns are examples, not a substitute for a department roster, collective-bargaining agreement, staffing directive, or official schedule. If a named rotation and the department calendar disagree, the department calendar wins.