Crew rotations should be a source of truth, not repeated setup
FireHousePal uses configured shift patterns to build crew coverage across the calendar. Station rotations remain station-scoped, while personal events stay personal. The goal is to reduce the repeated question of who is working and give other workflows a reliable date context.
The schedule connects real objects instead of fake calendar entries
Training planned from the schedule opens the real Training planner. A workout request opens the Fitness workflow. Meal activity can appear in the same date context. This keeps the calendar from becoming a second copy of systems that already have their own data and lifecycle.
Useful layers for station and personal planning
- Month and week calendar views.
- Crew rotation visibility for station context.
- Personal overtime and personal events.
- Training and workout handoffs into their real planning systems.
- Day-level detail for the events that matter on a specific shift.
Why schedule context matters across the app
A schedule is most valuable when it improves other decisions. FireHousePal can use shift context to make meal planning, training, Today, and fitness more relevant without forcing every user to live inside the calendar.