Law enforcement
How to Brief Command After a Suspected Officer TBI
Command needs fast, usable information after a suspected head injury. This briefing framework keeps updates factual, confidential, and actionable.
A poor command brief creates two problems at once: leadership cannot manage operations, and trust erodes because rumors fill the gap. A strong brief is short, factual, and privacy-aware. Supervisors do not need to diagnose. They need to describe what happened, what actions were taken, and what command decisions are needed next. After suspected TBI, that discipline protects the officer and the organization.
Use a six-line incident brief structure
- Incident summary: where, when, and mechanism of head impact
- Observed indicators: objective signs and symptom timeline
- Immediate actions: removal from duty/contact and monitoring
- Medical pathway: referral destination or emergency transport status
- Operational impact: staffing gap and mitigation steps in progress
- Next update time: when command should expect follow-up
This structure keeps leadership informed without drifting into speculation. It also creates a durable written record if the case later involves workers' comp, fit-for-duty review, or litigation.
Keep language objective and non-diagnostic
Say "suspected concussion" or "suspected head injury" unless diagnosis is confirmed by a qualified provider. Avoid minimizing words like "minor bump" or credibility judgments like "seems dramatic." Research in law-enforcement populations shows underreporting is already common. Command communication should encourage protocol adherence, not social pressure to self-clear.
Separate privacy from operations
Command needs operational status, not full medical detail. Share duty restrictions and readiness implications broadly, but limit symptom specifics and clinical notes to authorized channels. This reduces gossip risk while preserving managerial visibility. If union processes are involved, follow contract and policy steps consistently so the officer perceives fairness rather than selective handling.
For supervisor action before command notification, use the first-hour sergeant checklist.
Brief the risk, not just the incident
Command decisions should be driven by role risk profile. Public safety tasks involve driving, high stress, physical confrontation, and rapid judgment, all of which can be compromised during concussion recovery. Include that context in your brief so executives understand why temporary restrictions are operationally necessary, not discretionary caution.
Add objective recovery milestones to updates
Subsequent command updates should include milestone status: evaluation complete, restrictions defined, staged return initiated, and full-duty clearance pending/confirmed. If baseline data is available, note that objective comparison is being used as part of clinical decision-making. Objective milestones reduce "how long will this take?" frustration and improve staffing planning.
If command asks about clearance authority, direct them to who can clear a concussion and maintain one policy-wide standard.
Template your briefing process now
Agencies should template command briefs inside CAD or supervisor reporting tools so communication quality does not depend on writing style under stress. Combine templates with training and after-action review for every suspected head injury. Over time, your command channel becomes faster, calmer, and more defensible.
For documentation practices that help downstream claims and duty decisions, review workers' comp baseline data.