Help Center
Everything you need to get the most out of Total Circumstance AI.
Total Circumstance AI reviews officer-written narratives for probable cause strength, clarity, and legal sufficiency. The officer stays the author — this tool makes sure the report holds up before it leaves the building.
1
Paste your narrative
Copy your written report and paste it into the narrative field. Select the incident type and state/jurisdiction to get jurisdiction-specific analysis.
2
Run the analysis
Click Analyze Narrative. The app scores your report against three fixed rubrics: Probable Cause, Narrative Clarity, and Legal Sufficiency — each scored 0–100.
3
Review your results
See exactly where points were lost, what elements are missing, how a defense attorney would attack the report, and what to fix before filing.
4
Revise and resubmit
Update your narrative based on the feedback and run it again. Every analysis is saved to your case history so you can compare before and after.
Three scores are generated for every narrative. Each is based on a fixed rubric — the same narrative will always receive the same score.
Strong
75–100
Narrative is well-articulated and legally sufficient in this area.
Moderate
50–74
Some gaps or weak articulation. Review recommendations before filing.
Needs work
0–49
Significant elements are missing or poorly articulated. Do not file without revising.
Note: Scores reflect the narrative as written — not the strength of the underlying case. A legally sound arrest can still receive a low score if the narrative fails to articulate the facts correctly.
Seven elements make up the probable cause score (100 points total). These elements reflect the legal requirements under Illinois v. Gates and the totality of the circumstances standard.
The legal standard from Terry v. Ohio requiring specific, objective facts — not a hunch — that justify initiating contact or a stop.
✓ Strong
"At 2300 hours in a documented narcotics area, I observed the subject conduct three hand-to-hand exchanges within 10 minutes, each lasting under 5 seconds with no conversation."
✕ Weak
"I observed the subject acting suspiciously in the area."
The narrative must describe what the officer personally saw, heard, or smelled — not conclusions or assumptions.
✓ Strong
"I observed the subject reach into his waistband with his right hand, look directly at me, then quickly turn and walk in the opposite direction at a pace faster than normal foot traffic."
✕ Weak
"The subject appeared nervous and was acting like he was hiding something."
The connection between what the officer observed and the specific crime alleged must be clearly articulated.
✓ Strong
"These hand-to-hand exchanges, consistent with narcotics transactions I have observed in over 200 prior arrests, combined with the subject's immediate flight upon seeing my patrol vehicle, established probable cause for possession with intent to distribute."
✕ Weak
"Based on the above, I believed criminal activity was afoot."
Courts give weight to an officer's training and experience when interpreting ambiguous behavior. This must be explicitly articulated.
✓ Strong
"Based on my 8 years as a patrol officer, specialized narcotics training in 2019, and participation in over 150 narcotics arrests, I recognized the described hand-to-hand exchange as consistent with a street-level drug transaction."
✕ Weak
"Based on my training and experience, I knew this was drug activity."
Additional facts, evidence, or information beyond the officer's direct observations that support probable cause.
✓ Strong
"Dispatch confirmed two prior calls for narcotics activity at this location within the past 30 days. My partner, Officer Davis, independently observed the same hand-to-hand exchanges from a position 50 yards north."
✕ Weak
"I observed the above and made the arrest."
A strong probable cause narrative anticipates and addresses why the observed behavior is not consistent with innocent activity.
✓ Strong
"While the subject could have been conducting a legitimate transaction, the location (a known drug corner), time (0200 hours), brevity of contact (under 5 seconds), and immediate flight upon seeing police are inconsistent with a lawful exchange."
✕ Weak
"There was no innocent explanation for what I observed."
The time between observations and the arrest/search must be close enough that probable cause has not gone stale.
✓ Strong
"At 2247 I observed the transaction. I maintained visual contact throughout. At 2249 I initiated the traffic stop — approximately two minutes after observing the hand-to-hand exchange."
✕ Weak
"Later that evening I conducted a traffic stop of the vehicle."
Six elements make up the clarity score (100 points total). Clarity ensures the report is easy to follow in court and on the stand.
Events should be presented in the order they occurred, making the narrative easy to follow and testify to.
✓ Strong
Clear timestamps at each key event, events described in the order they occurred from initial observation through arrest.
✕ Weak
Describing the arrest, then going back to explain why the stop was initiated, then jumping forward again.
Narratives should be written in first person ("I observed") using active voice, making clear what the officer personally did and saw.
✓ Strong
"I observed the subject reach into his waistband. I ordered him to show his hands. I conducted a pat-down of his outer clothing."
✕ Weak
"This officer observed the subject. A pat-down was then conducted by this officer."
Exact times and precise locations anchor the narrative factually and help establish the timeline in court.
✓ Strong
"At 2247 hours I was traveling southbound on Highway 231 near mile marker 14 in Cannon County when I observed..."
✕ Weak
"That night I was on patrol when I saw a vehicle near the highway."
Conclusory language tells the reader what to think instead of showing them facts that lead to that conclusion. Courts disregard it.
✓ Strong
"The subject's eyes were glassy and bloodshot, his speech was slow and slurred, and he swayed side to side while standing still."
✕ Weak
"The subject appeared to be under the influence of alcohol."
The narrative should present facts objectively, without characterizations, opinions, or language that suggests a predetermined conclusion.
✓ Strong
"The subject stated, 'I don't have anything on me.' His hands were visibly shaking as he handed me his license."
✕ Weak
"The obviously guilty subject nervously tried to hide what he had done."
The narrative should tell the complete story — from initial observation through disposition — without unexplained gaps.
✓ Strong
A narrative covering: initial observation → basis for contact → development of PC → arrest → Miranda → search → evidence → transport → booking.
✕ Weak
A narrative that jumps from initial stop to arrest without explaining what happened in between.
Five elements make up the legal sufficiency score (100 points total). These elements ensure the report meets the legal requirements for the charged offense.
Each element of the charged offense must be supported by facts in the narrative.
✓ Strong
"Tillman was operating a motor vehicle (element 1) on a public roadway (element 2) with a BAC of 0.11% (element 3), exceeding the legal limit of 0.08% (element 4)."
✕ Weak
"Tillman was arrested for DUI based on the above observations."
The narrative should demonstrate that constitutional requirements were met — particularly Fourth and Fifth Amendment compliance.
✓ Strong
"I advised Tillman of his Miranda rights per Miranda v. Arizona at 2308 hours. Tillman stated he understood his rights and agreed to submit to a breath test per Tennessee's Implied Consent Law."
✕ Weak
"I read Tillman his rights and he agreed to the breath test."
Evidence must be properly documented from discovery through booking to be admissible.
✓ Strong
"The firearm was rendered safe, photographed in place, assigned evidence item E-001, placed in an evidence bag, sealed, and transported to Fresno PD evidence storage at 2014 hours by me."
✕ Weak
"The gun was taken as evidence."
Any use of force must be documented with the specific threat or circumstance that justified it, evaluated under Graham v. Connor. If no force was used, this element is not applicable.
✓ Strong
"Subject actively resisted handcuffing by pulling his arms away and turning toward me. I applied a single arm bar takedown to gain control. Subject was handcuffed without further resistance."
✕ Weak
"Subject resisted so I took him to the ground."
Any statute cited in the narrative should be the correct one for the offense charged in the applicable jurisdiction.
✓ Strong
"Tillman was charged with T.C.A. § 55-10-401 — Driving Under the Influence, First Offense."
✕ Weak
"Tillman was charged under the applicable Tennessee DUI statute."
These landmark U.S. Supreme Court cases establish the legal standards your narrative is evaluated against. Understanding them helps you write more defensible reports.
Terry v. Ohio
392 U.S. 1 (1968)
Established that a police officer may stop and briefly detain a person based on reasonable articulable suspicion that criminal activity is afoot — even without probable cause for arrest. The officer must be able to articulate specific, objective facts, not just a hunch. Applies to every narrative involving an investigative stop.
Illinois v. Gates
462 U.S. 213 (1983)
Established the "totality of the circumstances" test for probable cause. Courts look at the overall picture created by all available facts — no single element is required. This is the standard your PC score is measured against and the origin of our name.
Miranda v. Arizona
384 U.S. 436 (1966)
Required that suspects in custodial interrogation be advised of their rights before questioning. If Miranda was given, document it in the narrative — when it was given, what method was used, and what the suspect's response was. Failure to document is one of the most common gaps in narrative review.
Katz v. United States
389 U.S. 347 (1967)
Established the "reasonable expectation of privacy" standard for Fourth Amendment protections. Relevant to any narrative involving a search — document why the subject had no reasonable expectation of privacy, or what exception to the warrant requirement applied.
Chimel v. California
395 U.S. 752 (1969)
Defined the scope of a lawful search incident to arrest — limited to the person of the arrestee and the area within their immediate control. Relevant to any narrative involving a search following an arrest. Document the basis for any search that extends beyond these limits.
Graham v. Connor
490 U.S. 386 (1989)
Established the "objective reasonableness" standard for use of force. Courts evaluate force based on the perspective of a reasonable officer on the scene at the time of the incident — not hindsight. Relevant to any narrative involving use of force. Document the specific threat and why the force was objectively reasonable.
The Defense Challenge Preview is a unique feature of Total Circumstance AI — no other narrative review tool offers it. After your rubric analysis, the app generates a list of specific arguments a defense attorney would likely make against your report, each rated by severity.
🔴 High risk
A significant vulnerability that a skilled defense attorney would almost certainly raise and that could directly impact the admissibility of evidence or the outcome of the case. Address these before filing.
🟡 Medium risk
A weakness a defense attorney may raise. May not defeat the case but could create reasonable doubt or be used to impeach the officer on the stand. Worth addressing if possible.
🟢 Low risk
A minor issue that is unlikely to significantly impact the case but is worth being aware of. A thorough narrative minimizes even low-risk challenges.
How to use the defense challenge preview: For each challenge, the app provides a specific counter — what language or information added to the narrative would defeat that argument. Use these counters to strengthen the report before filing.
Does this constitute legal advice?
No. Total Circumstance AI is a reference and review tool only. Analyses are based on general legal standards and do not constitute legal advice. Always consult legal counsel regarding specific cases, charging decisions, and jurisdiction-specific requirements.
Are my narratives stored?
Yes — your analyses are saved to your personal case history so you can reference them later. Your narratives are associated with your account and are not visible to other users. We recommend not including personally identifying information beyond what is necessary for the analysis.
Is Total Circumstance AI CJIS compliant?
Not currently. CJIS compliance is a formal certification requiring dedicated government-cloud infrastructure, audit logging, background-checked personnel access, and a signed security addendum with your state's CJIS Systems Agency — it's a target as the product grows, but it isn't accurate to claim today. Note that report narratives are generally subject to public records law once filed, so this isn't restricted data in the way an NCIC query or active investigation file would be — though some content (victims, juveniles, confidential informants, ongoing investigations) may remain exempt even after filing. Treat the narrative field like any tool outside your agency's RMS: avoid pasting identifying information beyond what's needed for the analysis. All accounts are scoped so you only see your own case history, and all traffic is encrypted in transit.
Will the same narrative always get the same score?
Yes. The rubric is fixed — the same narrative will receive the same score each time it is analyzed. Scores reflect the narrative as written against defined criteria, not AI interpretation.
How accurate are the statute citations?
Statutes are verified via live search of official legal sources at the time of analysis. If a statute cannot be confidently verified, the app will say so rather than guessing. Always independently verify any statute before including it in a report or charging document.
What incident types are supported?
Traffic stop, Arrest, Search & seizure, Search warrant, Use of force, Domestic violence, Drug offense, Property crime, DUI/DWI, Weapons offense, and Other. Select the closest match to get the most relevant analysis.
What jurisdictions are supported?
All 50 states, Federal, and Military (UCMJ). Select your jurisdiction from the dropdown to receive jurisdiction-specific statute verification and legal standards.
How do I manage my billing?
Click "Manage billing" in the app header to access your Stripe customer portal where you can update your payment method, view invoices, or cancel your subscription.
Something isn't working — how do I report it?
Click "Report an issue" in the app header. Describe what you were doing and what went wrong and we'll follow up at info@totalcircumstance.com.