Guided report entry
Incident, offense, people, property, vehicles, narrative and attachments — entered in any order, with clear prompts for what is still missing.
One platform for incident reporting, case records, approvals, search and state reporting — designed with officers, supervisors and records staff, not around them.
Request a demoIncident, offense, people, property, vehicles, narrative and attachments — entered in any order, with clear prompts for what is still missing.
Every entity is linked by a typed relationship — victim of, owner of, used by, taken in. Case sections are simply views of those links.
Statuses, approval routing and escalation are defined per agency. Reports return to officers with reviewer notes, then resubmit cleanly.
Find any person, vehicle or location across every report, with duplicate detection that keeps one master record per real-world entity.
Your agency’s printed forms rendered as PDFs from the same data — with live facsimile preview while the officer writes.
Installable on MDTs, tablets and desktops. Drafts persist on the device and sync automatically when the connection returns.
A canonical NIBRS model fed directly by the report, FBI edit rules at entry and approval, and NIEM XML or flat-file submissions.
Retention schedules, holds and purge rules managed as configuration, with every change captured in the audit log.
Patrol, campus, state and specialty units each get their forms and codes as configuration on the same core product.
Older systems were copied and modified for each customer until no two agencies ran the same software. TenCode keeps one core product and expresses every agency difference as configuration.
agency: Demo Police Department
forms:
- incident-report@v3
- supplemental@v2
routing:
submitted: [sergeant, records]
returned: owner
nibrs:
state_variant: WA
retention:
incident: 10y