Related
Incident documentation
For offenses and incidents, BlueLineNote uses a NIBRS-informed structure across offense, victim, offender, and property.
NIBRS documentation →MMUCC-informed crash documentation
MMUCC-informed crash documentation, captured at the scene.
BlueLineNote gives officers a guided mobile workflow for crash documentation — collision circumstances, harmful events, vehicles, people, and injury severity — plus a scene diagram built in the same app, while the details are still in front of them.
What MMUCC is
MMUCC — the Model Minimum Uniform Crash Criteria, now in its 6th edition — is NHTSA’s guideline for the data elements a crash record should contain and how they should be defined. Each state builds its own crash form, but MMUCC is the common vocabulary underneath most of them: how a harmful event is described, how vehicle roles are recorded, how injury severity is classified on the KABCO scale. Capturing crash detail in that structure at the scene makes the later transfer into a state form far less lossy.
Why the scene is the only place to get it right
A crash record depends on things that are only true at the scene — vehicle positions, points of impact, the sequence of harmful events, road surface and lighting. Rebuilding those from memory or a handful of photos hours later is exactly where accuracy and detail degrade. BlueLineNote is designed to capture the coded fields and the diagram while the officer is still standing in the roadway, not back at a desk.
How BlueLineNote structures crash documentation
Crash fields are presented through one guided workflow, with a bottom-sheet picker for coded values instead of an unreadable grid of numbers.
Guided crash fields
Collision, harmful-event, vehicle, and person fields presented in sequence rather than as a wall of codes.
KABCO injury severity
Capture injury severity per person in a structure consistent with standard crash classification.
Vehicle information
Record role, condition, and damage details for each vehicle involved in the crash.
V.E.R.A. scene diagrams
Build a structured scene diagram — vehicle positions, impact, and layout — from the same application, with aerial imagery for context.
Photos kept with the record
Vehicle and scene photos are stored with the crash record so nothing has to be matched up later.
Crash-specific export
Produce a crash PDF organized around the crash fields for handoff through your agency’s process.
What it is — and what it is not
BlueLineNote is MMUCC-informed, not a guarantee of MMUCC or state acceptance. Field definitions, required elements, and submission all remain controlled by your state, agency, and RMS. The app’s job is to help the officer capture complete, consistently structured crash information at the scene, so the version that reaches the state crash form or RMS starts stronger.
Crash content, photos, and diagrams stay on the officer’s device. Licensing is validated separately and never requires access to report content. BlueLineNote prepares the crash record; the state system remains where it is filed.
The full app
Field documentation platform
Scanning, dictation, report review, saved records, and agency-ready export in one application.
Explore the product →Capture crash detail before it degrades.
Start with a conversation about how your officers document crashes today and where accuracy is lost.
Request an agency demonstration