Frequently Asked Questions

IncidentDraft is a police reporting platform designed to help officers capture incident details, generate structured report drafts, identify missing information, and support supervisor review workflows. The system helps improve documentation quality while keeping officers in control of the final report.

No. IncidentDraft provides AI-assisted draft generation, but officer review is required. Officers remain responsible for the accuracy, completeness, and final content of all reports. The system does not replace professional judgment or investigative decision-making.

Yes. Narratives can be reviewed and edited before RMS handoff. Officers may modify generated content to ensure it accurately reflects the facts, observations, statements, and investigative findings of the incident.

Officers can review, edit, revise, or replace AI-assisted draft content before RMS handoff. Generated drafts should always be reviewed for accuracy. The officer remains responsible for the final report.

The platform performs quality and completeness checks before handoff. Officers can be alerted to missing required fields, incomplete incident details, inconsistent information, or workflow requirements that may need attention before supervisor review.

Agency report content is not used to train public AI models. Final terms are documented in the agency agreement and deployment configuration.

The AI provider and model configuration may vary by deployment and agency requirements. Provider details, data-use terms, and configuration settings are documented during implementation and in the applicable agency agreement.

Agency workflows determine how reports are reviewed. Officers review and edit drafts before handoff, and supervisors can review, provide feedback, and request revisions according to department procedures.

Yes. Supervisors can review drafts, add comments, request revisions, and support supervisor review workflows configured for the agency.

Yes. IncidentDraft supports configurable templates, reporting workflows, review processes, required fields, and agency-specific documentation requirements.

IncidentDraft is designed with security controls intended to protect agency data, including access controls, auditability features, encryption measures, and role-based permissions. Security configurations may vary depending on deployment requirements.

Yes. The platform maintains audit records of actions such as report creation, edits, reviews, and workflow activity to support accountability and administrative oversight.

IncidentDraft is designed to support CJIS-aligned deployment review. Final CJIS readiness depends on the complete deployment environment, infrastructure, operational controls, and agency procedures. Agencies should evaluate requirements as part of implementation planning and agency security review.

Agencies retain ownership of their report content and agency data. IncidentDraft does not claim ownership of agency report narratives, draft content, or supporting report information.

IncidentDraft is designed to support draft preparation, review, and RMS handoff. The agency RMS remains the official system of record unless a specific deployment agreement states otherwise. Draft content may be stored in IncidentDraft to support workflow, review, auditability, and export features.

Export and retention options depend on deployment configuration and agency agreement. IncidentDraft is designed to support draft export and agency-controlled data handling workflows, with deletion and retention requirements documented during implementation.

Draft visibility is controlled by role-based access and agency configuration. Typically, access is limited to the assigned officer, authorized supervisors, agency administrators, and other approved users according to agency workflow and permissions.

Retention depends on agency policy, deployment configuration, and agreements. Configurable retention controls may be deployment-specific or planned depending on implementation.

Yes. IncidentDraft can support copy/export workflows before a full RMS integration is in place. Agencies can evaluate guided capture, draft preparation, quality checks, supervisor review, and RMS handoff without requiring immediate API integration.

IncidentDraft does not replace an agency RMS. It helps officers prepare review-ready draft content that can be copied or exported into RMS workflows depending on agency configuration.

IncidentDraft supports RMS copy/export handoff workflows where configured. Agencies control how review-ready draft content moves into their Records Management System. There is no automatic RMS submission from IncidentDraft.

Yes. Departments interested in evaluating IncidentDraft can request a demonstration to review workflows, reporting capabilities, security topics, and agency-specific requirements. Pilot programs may be discussed based on deployment needs.

Agency-controlled deployment options can be discussed during security and implementation review. Availability depends on agency requirements, hosting model, integration needs, support scope, and final agreement terms.

Yes. IncidentDraft includes a dark mode interface designed to improve usability in low-light environments, including patrol vehicles, night shifts, and field reporting situations.