Incident response & on-scene documentation
From the first push through clearing the scene, responders, officers, and dispatch share one live picture.
Push alerts carry CAD notes and activity context. Members decide station, scene, or unable; navigate en route; and see who is rolling. On scene: status board, notes, EMS patient care documentation, working-fire tools, request help, and disregard—then clear with narrative that feeds reporting.
- Push notifications with incident context and CAD notes
- Decide, respond, navigate, and track who is en route or on scene
- On-scene notes, patient care documentation, and working-incident tools
- Watch-only access for dispatch and officers monitoring without responding
Benefit: Faster, clearer response with shared situational awareness—from the first tone through scene clearance.
incident-respond.gif · tone → decide → map
Modes & notifications
Alerting that respects how members actually serve—career, combination, or volunteer.
A mode is a saved profile: available, unavailable, or watch per organization, with tones and optional auto-response. Members switch as life changes; dispatchers can watch multiple departments without appearing as responders.
- Available, unavailable, and watch categories per mode
- Custom alert tones and critical alert overrides
- Dashboard summary of availability at a glance
Benefit: The right people get the right alerts for the shift they are on.
modes-switch.gif · availability change
Dispatch & CAD / wall displays
Consoles and station boards show the same live incident picture as crews on mobile.
Dispatch Web for active calls, responder status, chat, and manual dispatch. Monitor CAD for TVs and kiosks—shared feed across dispatch, wall displays, and phones.
- Active incident dashboard with responder status and chat
- Monitor CAD for wall displays and secondary monitors
- Ops CAD and calendar kiosk setups for the bay
Benefit: Dispatch and officers see the same live picture as crews—less radio clutter, clearer status.
dispatch-monitor.webp
Organizations, roster & units
Membership should scale from a single volunteer station to a county-wide account—without losing control of who can see what.
RunReady groups departments under shared accounts with one or more organizations—your fire department, EMS squad, police agency, or dispatch center. Each member has a rank, unit number, employment type, and security roles that determine what they can do in mobile and web apps.
Leaders invite members with links or QR codes—fast for volunteer nights and onboarding drives. Ops Web supports bulk roster work: imports, rank adjustments, security role edits, and unit assignments. Multi-org accounts let career systems, combination departments, and regional dispatch centers operate under one tenant while keeping each agency’s data appropriately scoped.
- Multi-organization accounts for regional and multi-agency setups
- Ranks, units, employment types, and leader qualifications
- Invite links and QR codes for rapid member onboarding
- Role-based security access across mobile, Ops, and Dispatch
- Ops Web roster management at department or county scale
Benefit: Controlled membership and permissions at the scale you actually operate—whether you run one volunteer hall or a multi-station municipal system.
Assets, checklists, maintenance & water sources
Station readiness without spreadsheets and sticky notes.
Locations, equipment registry, scheduled checklists, maintenance follow-ups, and hydrant/water sources—in the same system as response.
- Location hierarchy from station to compartments
- Scheduled checklists with history
- Maintenance tasks and hydrant / water tracking
Benefit: Compliance-style inspections and apparatus readiness without spreadsheet chaos.
ops-assets.webp
Calendar & shifts
Coverage, training, meetings, and time off belong on one calendar—not a patchwork of paper sign-up sheets and third-party schedulers.
The shared department calendar combines events, training sessions, meetings, visitors, time off, and shift openings on unified month, week, quarter, and year views. Members filter by type, subscribe via ICS on mobile, and acknowledge assigned shifts. Leaders publish open shift slots, collect availability, assign coverage, and send reminders when slots still need bodies.
Training sessions link to the Training module so a drill on Tuesday appears where members already look for their schedule. Ops Web supports display kiosks—calendar boards for the watch desk or training room—using the same data members carry in their pockets.
- Events, training, meetings, visitors, time off, and shifts in one place
- Shift publishing, bidding, assignment, and reminders
- ICS subscription for personal calendar apps
- Display kiosks for station and training-room boards
- Integration with scheduled training sessions
Benefit: Coverage and department activity aligned with how your organization actually staffs—career rotations, volunteer sign-ups, and combination schedules in one authoritative calendar.
Training
Training administration belongs next to operations—not in a separate silo that nobody checks until audit season.
Training officers build curricula from a department catalog of topics, reusable taskbooks, and training plans with due dates and assignees. Members complete assignments from mobile or web; instructors approve practical skills through a sign-off queue. Scheduled training sessions appear on the shared calendar and roll into member training logs.
Personal certifications—EMT, ACLS, state credentials, and department-specific cards—live alongside assigned training so officers can see expirations before they become a coverage problem. Packaged SCORM 1.2 eLearning launches directly from My Training on web or phone, so online modules sit in the same workflow as hands-on drills and sign-offs.
- Training plans, taskbooks, and catalog-driven curricula
- My Training assignments with instructor sign-off workflows
- Scheduled sessions linked to the department calendar
- Personal certification tracking with issue and expiration dates
- SCORM eLearning launched from assigned training
Benefit: Training compliance and skill development managed where members already work—reducing “did you finish that module?” chase-downs and keeping credentials visible to officers.
Chat & broadcasts
Operational communication should live where the work already happens—not in a consumer messaging app your IT team cannot govern.
RunReady separates three channels by purpose. Organization chat is your department’s standing channel for shift coordination, training reminders, and non-emergency discussion. Incident chat ties directly to an active call’s activity feed—on-scene coordination that dispatch can join when permitted. Broadcast messages push urgent announcements to selected members or entire organizations, with optional critical alerts for weather or all-hands situations.
Because chat is scoped to organizations and incidents, leaders and dispatch can reach the right audience without exposing unrelated agencies. Message history persists in context—org chatter stays with the department; incident chat feeds into post-incident documentation.
- Standing organization chat for day-to-day coordination
- Per-incident chat tied to the activity feed
- Leader and dispatch broadcasts with optional critical alerts
- Dispatch console participation on active incidents
- History retained for operational and reporting context
Benefit: Operational communication in the same platform as dispatch and response—so critical messages reach members who are already logged in and alert-enabled.
Ops web for leaders & reporting
Chiefs and staff officers need a command layer for roster, assets, training, calendar, and incident documentation—without logging into five different admin portals.
Ops Web is where leaders manage the organization: roster and security roles, assets and checklist templates, training plans and sign-offs, calendar publishing, and CAD or calendar display setup for station kiosks. It is the administrative home for the same data members touch on mobile—so changes propagate immediately to the field.
Post-incident, officers can work from structured incident reports rather than chasing paper narratives. RunReady is building toward NERIS-oriented incident documentation workflows—helping fire departments capture the fields and narratives national reporting programs expect, without claiming certifications or mandates we have not earned. EMS agencies can document patient care in the mobile workflow where protocols apply, with privacy controls appropriate to protected health information.
- Centralized org administration: roster, assets, training, calendar
- CAD and calendar kiosk configuration for wall displays
- Post-incident reports with structured narratives
- Direction toward NERIS-oriented fire incident documentation
- Role-based access so leaders see what their rank allows
Benefit: Officers manage and document operations from one web console—less paper chase, clearer accountability, and reporting workflows that align with where national fire data programs are headed.
One platform, not a stack of silos
When alerting, CAD monitors, checklists, training, calendar, and reporting live in separate products, departments pay twice—for licenses and for the integration work that never quite keeps up. RunReady unifies the work of the street and the station so a tone on mobile, a wall display in the bay, and a training due date in Ops Web all draw from the same account.
Shared situational awareness
Incidents, dispatch, and chat reference the same live data—crews, officers, and communication centers stay aligned.
Readiness meets response
Assets, hydrants, training credentials, and shift coverage inform who is qualified and available before the next tone.
One account, many agencies
Multi-org accounts and role-based security scale from volunteer departments to regional dispatch centers without fragmenting membership.
Mobile-first, web-complete
Responders live on mobile; leaders and dispatch work on web—same sign-in, same data, no duplicate entry.