One member record, everywhere

The roster problem nobody talks about

Most departments maintain their roster in several places at once: the records system, the alerting app, a training spreadsheet, and a scheduling tool. Every one of them drifts. A member leaves in the spring and is still getting alerts in the fall. A certification expires and nobody notices because the certification list and the response roster are different files.

In RedAlert there is one member record. It holds contact information, response history, training, certifications with expiration tracking, attendance, duty hours, and any documents you attach to it. It's also what controls access: who's on Responder, who can check in at the Kiosk, what they see in RedAlert Mobile, and what permissions they hold in Desktop. Security is configured to your command structure, down to the field level.

Scheduling built for the reporting on the other end

RedAlert handles any repeating rotation: 24-hour shifts, Kelly Shifts, 10-14s, Monday-through-Friday admin schedules, light duty, and dispatcher rotations, running simultaneously across different groups. Rosters generate from the calendar, personnel assign to apparatus and riding positions, and you can view who's on duty by station or by unit.

Where it earns its keep is what comes out the other end. Time codes are built to your department's definitions, accrual banks track sick and vacation time and draw down as it's used, and shift types cover overtime, comp time, education, training, and leave. That structure exists so the reports work. Custom payroll reports get built to match the format your payroll system imports, so an administrator picks a date range, pulls the report, and hands it off. Duty rosters and minimum staffing reports are built to your requirements too.

Shift trades, time-off requests, and coverage changes are entered by members in RedAlert Mobile and confirmed in Desktop. Departments running large career staffs sometimes pair RedAlert with a dedicated scheduling tool for automated coverage workflows, and keep the personnel record, payroll reporting, and everything else here.

Duty crews and the volunteer shift problem

Volunteer and combination departments often run optional duty shifts, where members sign up for station coverage in exchange for points, a stipend, or another incentive. That only works if you know who actually showed up.

Build the shift in Desktop or RedAlert Mobile, and members clock in and out at the RedAlert Kiosk. Because the Kiosk is in the station, that's a true clock-in rather than a self-report, and the scheduled time gets measured against the actual time. A shift set for ten to six with a member arriving at ten thirty is a half hour you can see, credit correctly, or address. Those hours flow into the member record and into your award program calculations, and the current duty crew displays on the RedAlert Station Board so the whole firehouse knows who's on.