For law enforcement agencies

Better documentation, before the report becomes scattered notes and memory work.

BlueLineNote catches missing fields before a report reaches a supervisor—so reports come in more complete the first time, supervisors return less work, and officers spend less time redoing paperwork and more time proactive and visible in the community, where agencies need them most. What the device holds is a draft — the report exists once your agency processes and files it.

  • Incident reports come out NIBRS-coded
  • Crash reports come out MMUCC-coded
  • Officers pick from NIBRS-coded offenses and a matching narrative template populates to help
  • A NIBRS HTML file your RMS personnel review before submission — requirements vary by state
  • Cleaner data for faster crime stats, so command can deploy where it’s needed most
  • A private agency portal where your own staff assign and reclaim seats
Structured field documentation
BlueLineNote application dashboard
One field workflow Capture, review, organize, and export without switching between multiple apps.
Example BlueLineNote exported report
iOS + Android
Offline-capable
Agency self-service portal
30-day agency pilot
MMUCC-informed crash fields
See it work

Watch the workflow, start to finished report.

A short walkthrough of the application — capture in the field, review for missing information, and export an agency-ready report.

Operational outcomes

Built to improve the quality and consistency of field documentation.

BlueLineNote is designed to help officers capture the right information earlier, reduce avoidable omissions, and hand off clearer documentation through established agency procedures.

01 · Completeness

Capture important details before they are forgotten.

Structured fields guide officers through incident, person, vehicle, crash, and narrative information while they are still working the call.

02 · Review

Identify missing information before supervisor review.

Built-in report review helps surface incomplete sections and documentation gaps before the report enters the agency workflow.

03 · Consistency

Give the entire shift one repeatable process.

Officers use the same organized approach across incident reports, crashes, investigations, and supporting documentation.

04 · Efficiency

Reduce retyping and unnecessary app switching.

Scan, dictate, photograph, organize, review, and export from one mobile workflow rather than piecing the report together later.

Step 01

Capture

Scan IDs, dictate notes, photograph supporting details, and record structured incident or crash information.

Step 02

Organize

BlueLineNote groups people, vehicles, narrative content, codes, and attachments into a consistent case workflow.

Step 03

Review

Check the report for missing fields, incomplete sections, and documentation issues that may require attention.

Step 04

Export

Generate a clear PDF or supported export for handoff through your agency’s existing review and records process.

BlueLineNote dashboard
BlueLineNote crash reconstruction screen
BlueLineNote report review screen
One mobile field kit

The tools officers normally split across multiple apps.

BlueLineNote combines documentation, scanning, voice capture, crash workflows, report review, saved records, and export in one field-focused application.

01

Structured incident documentation

Organized incident, victim, witness, suspect, vehicle, property, and narrative capture.

02

OCR scanning and voice dictation

Reduce manual entry by scanning identification and dictating notes directly into the case workflow.

03

Crash documentation and V.E.R.A.

Capture crash details and create structured scene diagrams from the same application.

04

Report review and PDF export

Review report readiness and produce a clear document for supervisor or agency handoff.

05

On-device insights

Cross-reference information against an officer’s own saved reports without using an external database.

Security and data handling

What the device holds is a draft. The report is your agency’s.

Agencies need a clear answer about where information lives, and the answer starts with what a phone is actually holding. 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, alongside a NIBRS-structured HTML file for your RMS personnel to review. The report exists when your agency processes and files it, in your systems — not on the phone.

Related reading: what makes a police report narrative defensible.

On-device

The device holds the officer’s draft.

Draft content, photos, scans, diagrams, and narrative stay on the officer’s device until the officer transmits them. BlueLineNote does not receive or keep a copy.

Separated systems

Licensing does not require content access.

BlueLineNote’s servers validate individual purchases and agency seats. They receive a device identifier and, for metered features, usage counts — not draft content, report content, or attachments.

External systems

No connection to CJIS systems.

BlueLineNote does not connect to NCIC, III, or any CJIS system, and receives no data from them. Every field in the application starts blank; all information in a draft is entered by the officer. The device remains subject to your agency’s mobile device management, encryption, and access-control policy, as it already is for every application on it.

Field use

Core documentation works without dependable signal.

Officers can continue capturing field information in areas with weak or unavailable connectivity.

Agency policy

Retention remains an agency responsibility.

Discovery, retention, records handling, and device-management obligations remain subject to applicable law and agency policy.

National reporting standards

Structured around the information agencies already need.

BlueLineNote includes workflows informed by NIBRS and MMUCC concepts to help officers organize report information more consistently. Final validation, acceptance, and submission remain subject to each state, agency, and RMS environment.

NIBRS-informed

Incident documentation

Organize offense, victim, offender, property, and related information in a structure that supports more complete report preparation.

More on NIBRS documentation →
MMUCC-informed

Crash documentation

Capture collision, harmful-event, vehicle, person, injury-severity, and other crash fields through a guided mobile workflow.

More on crash reporting →
A defined role

A mobile reporting system

The DOJ Bureau of Justice Assistance Standard Functional Specifications for Law Enforcement Records Management Systems, developed by LEITSC, lists a mobile reporting system as a standard internal data exchange for incident reporting and traffic accident reporting. That is the role BlueLineNote occupies. There is no federal certification program for this category, and the specification describes a role rather than endorsing any product.

More on the report writing app →
Your RMS stays the record

In front of the RMS, not in place of it

BlueLineNote produces a NIBRS-structured HTML file alongside the PDF. Your RMS personnel review it and, subject to your RMS’s link capabilities, may use it for injection into your system of record. BlueLineNote does not submit to NIBRS and does not write to your RMS.

For agencies

A field documentation platform your department can evaluate and control.

BlueLineNote supports seat-based agency access, centralized activation, customizable branding, and a consistent officer workflow — while drafts stay on each device until the officer transmits them.

A private agency portal your own staff control
Agency code activation and seat assignment
Ability to reclaim or transfer seats
Department branding and report letterhead
Custom case-number and workflow configuration
Small-team evaluation and deployment support

Request an agency introduction

Tell us who you are and the approximate size of your agency. We will use the information to start the conversation.

Prefer email? Contact support@bluelinenote.app

Agency portal

Your department controls its own seats.

Licensed agencies get a private portal. Your authorized point of contact signs in and manages the agency’s roster directly — assign a seat the day a new officer needs it, reclaim one the day someone transfers out. No support ticket. No waiting on a vendor. No phone tag.

Self-service

Assign a seat when the officer needs it.

Your point of contact assigns an open seat and passes the officer their activation key. New hire on Monday, working on Monday — your roster does not sit in someone else’s queue.

Turnover

Reclaim a seat the day someone leaves.

Transfers, retirements, separations. Cancel the seat and it returns to your available pool. The seat is re-keyed automatically, so the departing officer’s key stops working.

Accountability

Every action is on the record.

Who asked, what they asked for, when, and what happened. Your agency sees its own full activity trail. Nothing changes without a record of who requested it.

Controlled access

Only the people your agency names.

Portal accounts are created only by BlueLineNote, only for contacts your agency authorizes, and only on a work email address. Up to two contacts, so coverage does not depend on one person.

Growth

Request seats or branding without a meeting.

Need seats next quarter? Updating your letterhead? Submit it from the portal with your artwork attached, and the request is on file with the date and the person who made it.

Boundaries

Seat administration only — never report content.

The portal manages licensing. It has no path to officer drafts, reports, photos, or narratives. That content stays on the officer’s device until transmitted to your agency, where neither the portal nor BlueLineNote can reach it.

Requests submitted through the portal are reviewed and applied by BlueLineNote, then reflected back to your agency — so your roster stays accurate and every change stays documented.

Request an agency demonstration
Agency pilot program

Run BlueLineNote in your agency for 30 days.

Put it in your officers’ hands on real calls, on your own terms. The full product, your agency branding, your own management portal — for 30 days, extendable to 45. No commitment, and nothing to uninstall from a squad car if it isn’t the right fit.

If your agency decides to continue, the pilot converts to a subscription and your contract term begins after the pilot ends — so none of your paid time is spent evaluating. If you decide not to, that’s the end of it. We only ask that you tell us what worked and what didn’t.

Start a pilot
Everything included

The full product, not a trimmed trial.

Full Pro features, your agency branding on exported PDFs, and your own self-service portal for assigning and reclaiming seats — the same deployment a paying agency runs.

30 days, extendable to 45

Enough time to see real calls.

A full cycle of shifts, incidents, and crashes — long enough for your officers and supervisors to judge it on the work, not on a demo. Need a little longer? Extend to 45.

No commitment

Continue only if it earns its place.

No obligation to buy. If you continue, it becomes a subscription and your contract term starts after the pilot, so your evaluation time is never billed. If you don’t, you owe nothing.

Any size agency

From a single shift to the whole department.

Pilot with one squad or roll it out agency-wide. We will help you set up seats, branding, and your point-of-contact access so your officers are working on day one.

Agency-ready output

Clear documentation that can carry your department’s identity.

Custom agency presentation

Agency deployments can use department branding, letterhead, case-number formatting, and configured report presentation so exported documents look consistent with the organization using them.

Discuss agency configuration
Sample report page one
Sample report page two
Sample report page three
Sample report page four
Agency licensing

Seat-based pricing your department can budget against.

BlueLineNote is licensed per seat, per year. Every seat includes the full product, your agency branding on exported reports, and access to your private management portal — there is no separate setup fee, portal fee, or per-report charge.

1 – 24 seats
$149 / seat / year

For a single squad, a shift, or a small department licensing every officer.

100+ seats
Contact us

Large agencies, multi-agency, and county-wide deployments are quoted directly.

Every seat includes

  • Full Pro features — no trimmed agency edition
  • Agency branding and letterhead on exported reports
  • Setup and onboarding — seats, branding, and portal access configured for you
  • A private portal where your point of contact assigns and reclaims seats directly
  • A full activity trail — every seat change recorded with who requested it and when
  • Seat transfers at no cost when officers join or leave
  • Custom case-number formatting and workflow configuration
  • Email support for your point of contact

No setup fee. No onboarding fee. No portal fee. No per-report or per-export charge. Seats are transferable, so turnover does not cost your agency a license.

Agencies that need a formal quote, W-9, or vendor documentation for procurement can request it at sales@bluelinenote.app. Individual officers can download BlueLineNote directly from the App Store or Google Play.

Frequently asked questions

What agencies usually ask first.

How does the 30-day agency pilot work?

Your agency runs the full product — complete Pro features, your branding on exported PDFs, and your own management portal — for 30 days, extendable to 45, with no commitment. If your agency decides to continue, the pilot converts to a subscription and your contract term begins after the pilot ends, so none of your paid time is spent evaluating. If you decide not to continue, you owe nothing. To start one, email sales@bluelinenote.app.

Does BlueLineNote work without reliable signal?

Core field documentation is designed to work offline. Functions that depend on external services or email availability may require connectivity.

What is actually stored on the officer’s device?

The officer’s draft. An officer drafts on the device; a supervisor may sign on that device or after the draft is transmitted, but a signed draft is still a draft. It leaves the device as a PDF, with a NIBRS-structured HTML file for your RMS personnel to review. The report exists once your agency processes and files it — in your systems, not on the phone. BlueLineNote stores no server-side copy of either.

Does agency licensing allow BlueLineNote to read officer drafts or reports?

No. Licensing validates access and seat status. BlueLineNote’s servers receive a device identifier and, for metered features, usage counts — never the content an officer enters.

Who manages our seats once we are licensed?

Your agency does. Licensed agencies get a private portal where your authorized point of contact can view every seat and activation key, assign an open seat to an officer, reclaim a seat when someone leaves, and request additional seats. Canceled seats are re-keyed automatically, so the old key stops working. Every action is recorded and visible to your agency.

Can the agency portal see our officers’ reports?

No. The portal administers licensing and seats only. It has no access to draft or report content, photos, or narratives — that content stays on the officer’s device until it is transmitted to your agency.

Is BlueLineNote a replacement for an RMS?

No. BlueLineNote is a mobile reporting system that sits in front of your RMS. It can capture officer and supervisor sign-off on the device and carry that approval block into the exported document, but a signed draft is still a draft — the RMS remains the system of record, and the report exists once your agency files it. Retention, validation, and submission continue through your established process and systems.

How does BlueLineNote relate to CJIS?

BlueLineNote does not connect to NCIC, III, or any CJIS system and receives no data from them. Every field starts blank and is populated by the officer. The CJIS Security Policy applies to entities that access, process, store, or transmit Criminal Justice Information; BlueLineNote’s servers receive no draft or report content. The device itself stays under your agency’s existing mobile device management, encryption, and access-control policy. The FBI CJIS Security Policy, version 6.0 and later, is publicly available and may be shared without restriction — we are glad to work through it with your LASO or your state CJIS Systems Officer, who are the authorities on how it applies in your state.

Does BlueLineNote guarantee NIBRS or MMUCC acceptance?

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

Can an agency test BlueLineNote with a small group?

Yes. Agencies can discuss a limited evaluation, deployment approach, seat count, branding, and workflow configuration through the agency contact form.

Privacy

Your reports stay on your device.

Last updated: June 2026

Your reports stay on your device

All reports, notes, scans, and other content you enter into BlueLineNote remain on your device and are never transmitted to the developer or any external server. The developer does not have access to your notes, reports, scans, or any content you create in the app. BlueLineNote does not provide cloud storage or remote databases for your content.

Backup and restore

You can create a password-protected backup of your saved records and scans. The backup is a single encrypted file, locked with a password that only you know — the developer cannot open it. You choose where to save it (your own Files, your own cloud storage, or email) using your device’s share sheet, and you restore by selecting that file. Backup files are never sent to or stored by the developer.

Licensing and feature limits

To validate Pro purchases, activate agency seats, and enforce free-tier usage limits, the app sends a device identifier — and, for metered features, a count of how many times those features have been used — to the developer’s server (api.bluelinenote.app).

This information is used only to operate the free, Pro, and agency licensing. It contains no personal information and none of your report content, and it is never sold or shared with advertisers or other third parties for advertising or tracking.

Agency portal

Licensed agencies may be given access to an agency portal for seat administration. The portal handles licensing information only — seats, activation keys, and the requests an agency’s authorized contact submits. It contains no report content and provides no access to notes, reports, scans, or narratives, which remain on each officer’s device. Portal accounts are created only by BlueLineNote for contacts the agency authorizes.

Anonymous usage analytics

The app collects a small amount of optional anonymous usage data — for example, which features are opened, how long the app is used, your subscription type, device model, operating system version, and app version. This data is not linked to your identity, contains no personal information and none of your report content, and is identified only by a random value that resets if the app is reinstalled. It is not sold or shared with advertisers. You can turn it off at any time under Backup & Restore → Anonymous Usage.

Legal requests

We may disclose the limited information we hold if required by law or in response to a valid legal request. That information is limited to a randomly generated device identifier and licensing or usage records — it is not your name, account, or any personal identifier. Your reports, notes, and scans remain on your device, are never transmitted to us, and are not accessible to us — we cannot produce that content.

Data retention

We keep the limited licensing and anonymous usage data described above only as long as needed to operate the free, Pro, and agency licensing and to keep the service working. Because this data is tied only to a random identifier and contains no personal information, it is not linked to you. You can stop analytics collection at any time under Backup & Restore → Anonymous Usage.

Security

We use reasonable measures to protect the limited data we collect in transit to and on our server. No method of transmission or storage is perfectly secure, but because your reports, notes, and scans never leave your device, the most sensitive information you create is never exposed to us or to anyone in transit.

Platform services

The app uses platform services such as in-app purchases and speech recognition. Depending on your device, these are handled by Apple or Google under their own privacy policies.

Your responsibility

You are responsible for securing your device and for how you store, manage, and use any information you enter into the app. You are also responsible for following your department’s or company’s policies, procedures, and applicable laws governing the documentation, handling, retention, and sharing of any information you record using BlueLineNote.

Contact: support@bluelinenote.app

Support

Questions, issues, or help getting started.

BlueLineNote is built for incident documentation, crash documentation, and report preparation. If you need help, have a question, or want to report an issue, write to us directly.

support@bluelinenote.app

What we can help with

Questions about features, agency licensing and seat management, backup and restore, purchases and subscriptions, and reporting a problem with the application.

What we cannot access

For privacy and user protection, BlueLineNote does not provide cloud storage or developer access to user-generated drafts, reports, scans, or records. We cannot retrieve, restore, or view your content — including if a device is lost or an unencrypted backup is unavailable.

Your responsibility

Users are responsible for managing, exporting, backing up, and deleting their own data, and for following their department’s policies for handling and retaining any information recorded using BlueLineNote.

From LinkedIn

Notes from the field.

Perspective on field documentation, report quality, and the day-to-day realities the app is built around.

Evaluate a more consistent field documentation workflow.

Start with a conversation about your agency’s current process, the officers who would use the application, and the reporting problems you want to reduce.

Start a 30-day agency pilot