San Bernardino County Fire Protection District β€” Staffing Dashboard
Department Business
πŸ“‹ SUBMIT πŸ“… CALENDAR πŸ” TRACK
--:-- --
Open Seats
SUP 0 / AO 0
Suppression / Ambulance Op Β· 0 total
Planned / Closed
28
Authorized but unfilled positions
Total Positions
748
Funded positions Β· across 52 fire stations
Current OC
28
Occupational injuries active
Temp Assignments
8
Personnel on temp detail
Overall Vacancy Rate
13%
Open positions / total seats
28-Day Forward Recall Avg
β€”
Loading…
Dept Business Today
β€”
Loading…

Division Status

Vacancy by Rank
A/B/C Shift Breakdown
Rank A-Shift B-Shift C-Shift Total

Department Summary β€” Rank Vacancy %

Rank Positions Filled Open Closed OC Temp Vac % (Open) Vac % w/ OC+Temp
✏️ Admin Edit Mode β€” Hover any name slot and click the pencil to transfer, mark OPEN, or update personnel. Changes apply to this session.

Next 28 Days β€” Recall Availability

Next 28 Days Avg
β€”
Today through +27 days forward
Today
β€”
β€”
Recallable Today
β€”
of 634 line personnel
Theoretical Ceiling
66.7%
3-platoon max (1/3 on duty)
DAILY BREAKDOWN β€” NEXT 28 DAYS
Loading…
DATE DAY PLT UNAVAIL RECALLABLE FG4 FG3 FG2 FG1 PCT STATUS
Loading recall data…
Source: TeleStaff via BigQuery. Refreshed daily at 5am PT. Roster is set ~35 days in advance with minor day-to-day adjustments.

FireGuard Recommendations

1
EXTREME
2
SEVERE
3
MODERATE
4
GUARDED
5
NORMAL
βš™οΈ Scenario Inputs β€” Adjust to Model Projections
Promotional Process
↑ cascades: fills that rank, opens one below
Capβ†’BC ↑
Engβ†’Cap ↑
FF/PMβ†’Eng ↑
FF/PM Hire βœ“ net fill
FF/EMT Hire βœ“ net fill
Lateral ENG Hire ↔ eng only
FF/EMTβ†’FF/PM Reclass ↑ reclass
AOPM Hire βœ“ net fill
AOEMT Hire βœ“ net fill
Attrition / Retirements
BC Retirements
Captain Retirements
Engineer Retirements
FF/PM Attrition
FF/EMT Attrition
AOPM Attrition
AOEMT Attrition
New Positions Created
Bat. Chief
Captain
Engineer
FF/PM
FF/EMT
AOPM
AOEMT
Suppress Positions
↓ removes authorized positions (Current + Projected) Β· vacancies unchanged Β· EMACS not affected
Bat. Chief
Captain
Engineer
FF/PM
FF/EMT
AOPM
AOEMT

Saved Scenarios

No saved scenarios yet.
Current vs Projected β€” Vacancies Only
RankPositions Current VacCurrent % Projected VacProjected %
Current vs Projected β€” Including OC/Temp
Rank Current VacCurrent % Projected VacProjected %
πŸ“‹ True Vacancy/Positions (EMACS)
Manually-set baseline from EMACS Β· Projected applies scenario inputs
RankFunded Positions Current VacCurrent % Projected VacProjected %

Deployment Authorization Matrix

Live Authorization β€” Based on Current FireGuard Level
54-engine baseline Β· Hard cap: 3 strike teams
FG Level Vacancy Threshold Engines Deploy Strike Teams BCs Deploy FF Recall BC Recall % Recall Pool
⚑ Live Deployment Status
STRIKE TEAMS COMMITTED
Hard cap: 3 Β· 5 Cap Β· 5 Eng Β· 5 FF per ST
βœ… Within authorized cap
DEPLOYMENT TYPE
OUT-OF-COUNTY
IN-COUNTY
AUTHORIZATION REQUIRED
β€”
πŸš’ Single Resource Deployment
Track individual personnel deployed outside of strike teams β€” adds to projected vacancy on top of strike team commitments
CAPTAINS
ENGINEERS
FF / PM
FF / EMT
No single resources deployed
πŸŽ–οΈ Battalion Chief Availability
28 total BCs Β· 9 per-shift IMT-assigned
28
TOTAL BCs
0
IMT ASSIGNED
0
ON STRIKE TEAM
28
AVAILABLE
BCs ASSIGNED TO IMT
of 28 total
BCs ON STRIKE TEAM
STL deployed
BINDING CONSTRAINT
Engine math β€” BCs not limiting
πŸ“ž Recall Requirements
366-person off-duty pool Β· 15 FF per strike team Β· BCs tracked in BC Availability
Balanced First Deployment Rule: First strike team draws 1 engine from each of the 5 divisions before additional resources are committed from any single area.

Department Business β€” 35-Day Forward

Today β€” DBON
β€”
On duty (incl. PM school)
Today β€” DBOFF
β€”
Off duty (incl. PM school)
35-Day Peak DBON
β€”
β€”
35-Day Peak DBOFF
β€”
β€”
DAILY BREAKDOWN β€” NEXT 35 DAYS
Loading…
DATE DAY PLT DBON DBOFF STATUS
Loading dept business data…
Source: TeleStaff via BigQuery. DBON = DB_ON + DBON-PM. DBOFF = DBOFF + DBOFF-PM. Refreshed daily at 5am PT.

βš™οΈ Admin Settings

πŸ”’
Admin Access Required
Sign in with an authorized account to access settings.

πŸ“‹ DB Requests

DB Request management β€” review, approve, deny, and manage all department business requests.
βœ… Approval Queue
Review and decide pending DB requests. Per-person or bulk actions.
β–Ά
βš™οΈ Manage Categories
Categories shown in the request form's dropdown. Lower priority number = higher priority for approval queue sort.
β–Ά
πŸ“ Submit New Request
Request DB time off. Submit at least 35 days ahead when possible.
β–Ά
πŸ“Œ My Recent Requests
Your submissions and their decision status (last 60 days).
β–Ά
πŸ“… Request Calendar
Person-days submitted per date. Click a day for details.
β–Ά
Coming next: Approval queue Β· My requests
πŸ“Š Color Legend
Under 7/11 Approaching cap (annual 7-8 OR total 11-13) At/over cap (annual β‰₯9 OR total β‰₯14)
ℹ️ Note: The TOT number represents the total number of leave requests for the day β€” it does not represent the actual number granted or approved. Please reference the Kronos Roster for approved-leave details.
Loading…

πŸš’ MS/FMS AT A GLANCE

FMS (top) + TOT MS (MS+FMS, bottom) Β· 35-day window Β· Colored by % of per-shift auth Β· <15% green Β· 15-35% yellow Β· β‰₯35% red
Loading…