Corrections firstExisting camerasEarlier awarenessFaster responseStructured proofSafety Intelligence Corrections firstExisting camerasEarlier awarenessFaster responseStructured proofSafety Intelligence

General operational and educational information for corrections professionals. Not legal, medical, or compliance advice, and not a certification of compliance with any law or standard. Policies and standards vary by agency and jurisdiction; follow your facility's policy and your own legal, medical, and professional advisors.

// Proof and incident review

What a Safety Intelligence Proof Report Includes

A proof report is a periodic, structured account of what a facility observed and did. It is not a performance scorecard and not a marketing document. Its purpose is to let a jailer answer, with evidence, the three questions that follow any serious incident: what did you see, when did you see it, and what did you do.

// Why a facility needs a periodic record, not just an incident file

Incident files are built after failures. They describe the exception. A facility whose entire safety record is a stack of incident reports has documented only its worst days, and that is the collection a plaintiff will read.

A periodic record establishes the baseline. It shows an organization that observes, responds, reviews, and adjusts as ordinary practice. That context is what makes an individual bad outcome look like an event rather than a pattern.

It also serves an entirely practical purpose. Jailers are asked by county officials, by insurers, and by the public what they are doing about safety. A dated document beats a verbal assurance every time.

// What the report contains

Coverage. The areas designated as high consequence, what is covered, and any known gap with its compensating practice. This section is useful even when it reports a gap, because a documented gap is a managed one.

Events raised and dispositioned. What was surfaced during the period, timestamped, with acknowledgement and disposition. Most entries are routine. The routine entries are the evidence of a working process.

Response timing. Elapsed time from event raised to acknowledgement, and where applicable to staff on scene. This is the most operationally useful number in the document and the one most worth watching over time.

Observation integrity. Evidence of coverage during the periods observation was assigned in designated areas, including the overnight hours.

Findings and open items. What the period surfaced that warrants attention, and what remains open from prior periods with owner and date.

Narrative. Plain language from a corrections perspective on what the numbers mean, written for a jailer rather than for an analyst.

// What it deliberately does not contain

No claim that anything was prevented. A near miss is a near miss. Stating that a system prevented a death is not provable and should not be written down.

No detection or accuracy performance figure. Numbers of that kind require a defined denominator and an independent method, and in this category they are usually presented without either.

No clinical conclusion about any individual. Assessment belongs to clinicians.

No identification of individuals by face. Facial recognition is not used.

No comparison ranking against other facilities. Facilities differ in population, plant, and staffing to a degree that makes casual comparison misleading.

// How facilities use it, and where Safety Intelligence fits

With the county. It converts a funding conversation from opinion into evidence, particularly the coverage section and the open items list.

With counsel and the risk pool. It supplies the contemporaneous record that incident review depends on and that video alone does not provide.

Internally. It is the natural input to a monthly executive safety review, which turns leadership time from reconstruction into judgment.

Virtual Patrol produces this record as the output of ongoing monitoring: what was raised, who reviewed it, what they did, and what coverage existed. A person reviews every event before action, and the document reflects human decisions rather than automated ones.

// Frequently asked

Is this a compliance document?

No. It supports documentation, discipline, review, and proof. It does not certify compliance with any standard and no vendor document can.

Does it prove incidents were prevented?

No, and it does not claim to. Prevention is not provable from a near miss. What is provable is what was observed, when, and what was done.

Can it be shared with the fiscal court?

Facilities do share summaries, particularly the coverage and open-items sections. Discuss the right level of detail with your county attorney first.

Who writes the narrative section?

It is written from a corrections operations perspective for a corrections audience, not as an analytics summary.

How often is it produced?

Monthly is the common cadence, which aligns with a standing executive safety review.

Does it include video?

It references and indexes relevant material rather than embedding it. Video handling follows the facility's own access and retention policy.

Request a Safety Intelligence Audit   Back to the Library
// Related
Proof, not just alerts → Monthly Executive Safety Review agenda → The Safety Intelligence Score → The Gold Seal → Documentation and defensible records → What a Near Miss Proves, and What It Does Not → How to Build a Jail Incident Timeline → How Unknown Time Becomes Exposure →