For officers and agencies

Police report writing app

BlueLineNote is a police report writing app for officers who document the incident on the device while they are still working it, instead of rebuilding it from notes and memory at a station computer hours later. Incident reports come out NIBRS-coded, crash reports MMUCC-coded, on the agency’s letterhead.

The report gets written twice

Once in a notebook at the scene, and once at the station from whatever survived the rest of the shift. The second version is the one records receives, and it is where missing elements, rounded times, and paraphrased statements come from.

Memory does not fail all at once. The shape of the call survives; the details attach themselves afterward. Sequence compresses, quotes smooth into paraphrase, descriptions drift toward the typical. The officer is not aware of any of it happening.

Anything captured while the officer is still standing there is fixed. Anything written afterward is reconstruction, however good the officer is.

BlueLineNote is built for the first version. Structured fields walk the officer through incident, person, vehicle, property, and narrative information on the device, on scene, while the information is still in front of him.

How it works

Capture, organize, review, export

Step 01

Capture

Scan identification, dictate notes, photograph what matters, and record structured incident or crash information on scene.

Step 02

Organize

People, vehicles, narrative, codes, and attachments group into a consistent case workflow instead of scattering across apps.

Step 03

Review

A review pass surfaces missing fields and incomplete sections before the draft reaches a supervisor.

Step 04

Export

A clean PDF on agency letterhead, plus a NIBRS-structured HTML file for records personnel to review.

What it does not do

The officer writes the narrative

BlueLineNote does not generate the narrative. Every field in the application starts blank and is populated by the officer. What the application contributes is structure — coded fields, consistent organization, and a check for what is missing.

That is a deliberate design decision rather than a missing feature. A narrative has to be something the officer can source, explain, and testify to, sentence by sentence, possibly years later. Anything that puts words in the report the officer cannot account for moves the cost of the paperwork rather than removing it.

More on this: what makes a police report narrative defensible.

Standards

NIBRS-coded incidents, MMUCC-coded crashes

Officers select from NIBRS-coded offenses, and a matching narrative template populates to help structure the write-up. Crash documentation covers collision, harmful-event, vehicle, person, and injury-severity fields through a guided mobile workflow built on MMUCC.

Alongside the PDF, the application produces a NIBRS-structured HTML file. Records personnel review it and, subject to the RMS’s link capabilities, may use it for injection into the system of record. BlueLineNote does not submit to NIBRS and does not write to the RMS. Final validation, acceptance, and submission requirements vary by state and agency.

Data handling

What the device holds is a draft

An officer drafts on the device. A supervisor may sign on the officer’s device, or after the draft is transmitted — either way, a signed draft is still a draft. It leaves the device as a PDF for supervisor review and agency processing. The report exists when the agency files it, in the agency’s systems, not on the phone.

  • No connection to CJIS systems. BlueLineNote does not connect to NCIC, III, or any CJIS system and receives no data from them.
  • No server-side copy. BlueLineNote’s servers validate licensing — a device identifier and, for metered features, usage counts. Not draft content, not attachments.
  • Offline capable. Core documentation works in dead zones. Functions depending on external services or email require connectivity.
  • Agency policy governs the rest. Retention, discovery, records handling, and device management remain subject to applicable law and agency policy.
Who it is for

Individual officers and licensed agencies

An individual officer can download BlueLineNote from the App Store or Google Play and use it on their own device. Agencies license seats directly, which adds department branding and letterhead on exported reports, custom case-number formatting, and a private portal where the agency’s own point of contact assigns and reclaims seats without going through a vendor.

Common questions

What officers ask first

Does the app write the report for me?

No. You write the narrative. BlueLineNote provides the structure, the coded fields, and a review pass that flags what is missing. Every field starts blank and is populated by you.

Does it work without a signal?

Core documentation works offline. Functions that depend on external services or email availability require connectivity.

Is it a replacement for our RMS?

No. BlueLineNote is a mobile reporting system that sits in front of the RMS. The RMS remains the system of record, and retention, validation, and submission continue through the agency's established process.

What stays on the device?

Your draft. It leaves the device as a PDF, with a NIBRS-structured HTML file for records personnel to review. The report exists once the agency processes and files it.

Can I use it if my agency has not licensed it?

Yes. Individual officers can download it directly from the App Store or Google Play. Agency licensing adds letterhead, configuration, and the management portal.

Does it guarantee NIBRS or MMUCC acceptance?

No software can guarantee acceptance across every jurisdiction and RMS. BlueLineNote provides structured workflows informed by national standards; final requirements remain controlled by the applicable state, agency, and system.

Run it in your agency for 30 days.

Full product, your branding, your own management portal. No commitment, and the contract term starts after the pilot ends.

Start a 30-day agency pilot
BlueLineNote is a mobile reporting system used ahead of an agency’s records management system. It is not a records management system, an evidence management platform, or an official law enforcement system of record. Officers and agencies remain responsible for following agency policy and official reporting procedures.