Embracing Complexity: The Integrated Architecture of Safe Facilities
Author: Felice Upton | Connect on LinkedIn
Published November 3, 2025
Any seasoned leader in any type of locked facility can tell you within minutes of walking into a unit if it is safe. You feel it before you analyze it. The cleanliness. The tone of voices. The predictability of routines. The body language. The way staff carry themselves. The way residents move through space.
Safety is not an abstraction. It is the lived experience of everyone in that environment, and it depends on everything working together.
The False Binary That Fails Us
Too often, correctional and residential systems operate as if these elements are in competition:
Security teams focus on control and compliance
Clinical teams focus on treatment and rapport
Operations teams focus on efficiency and function
Programming teams focus on engagement and education
Each operates in its own silo. Each has its own metrics. Each believes the others don't quite understand the "real work."
But here's the truth: You cannot have one without the others.
A facility cannot be therapeutic if it isn't safe. It cannot be safe if it isn't predictable. It cannot be predictable without functioning systems. And those systems cannot function without staff who are supported, residents who are engaged, and leadership that understands complexity as a feature, not a bug. Training employees to have the confidence and support to operate outside of a binary also matters.
We must embrace complexity. Not as a burden, but as the reality of what it takes to create environments where human beings can actually heal, grow, and change.
What Real Safety Looks Like
Every environment where people live, learn, and work, especially carceral ones or involuntary mental health- depends on a simple truth: human beings cannot grow in fear or unpredictability.
That's as true for a child in school as it is for a staff member walking into a housing unit at shift change.
When systems fail to maintain order, consistency, and reliability, they fail to create the conditions for rehabilitation, accountability, and hope. A facility can't be therapeutic if it isn't safe. And it can't be safe if it isn't trustworthy. Programming relies on predictability and reliability.
Safety and security are not administrative checkboxes. They are the moral architecture of a just system. Each day of inaction, neglect, or delay carries consequences for someone's safety, someone's healing, someone's life.
The Seven Pillars of Integrated Safety
Below are seven essential factors that must be tracked, analyzed, and tended to, continuously, not occasionally, to ensure any facility is not just secure, but truly capable of supporting growth. Notice how each one touches security, programming, wellness, and culture simultaneously.
1. Incident and Use-of-Force Trends
What to Track: Frequency, severity, location, and timing of incidents. Break down by shift, unit, staff member, and type of trigger. Track patterns over time, not just totals. Are there themes? Are you clear about your expectations?
Why It Matters: These numbers reflect culture more than compliance. When they rise, it signals a loss of predictability, people no longer trust that calm and fairness will prevail. This isn't just a security issue; it's a therapeutic breakdown.
How to Track: Use real-time incident reporting systems that capture not just what happened, but what preceded it. Include de-escalation attempts, environmental factors, and time of day. Analyze weekly, not just monthly or quarterly.
How to Address:
Transparency: Share incident data with all staff in regular briefings. Discuss patterns openly without blame.
Clarity: Make expectations for intervention crystal clear. Define what de-escalation looks like in practice, not just policy. Train to it. Support the change.
Data-Driven Response: When incidents spike, convene rapid response teams to analyze root causes. Look at staffing patterns, programming schedules, environmental stressors, and relationship dynamics. Adjust in real-time based on what the data reveals.
The principle: Every spike in incidents must prompt inquiry, not punishment. Each event is data, and each data point is a story about what's working, or what's hurting.
2. Staff Retention and Sick Leave
What to Track: Turnover rates by unit and role, exit interview themes, sick leave patterns (especially patterns of callouts), and anonymous survey data on safety, belonging, and leadership support.
Why It Matters: No facility can be safe if the people responsible for safety are exhausted, fearful, or disengaged. Burnout is not weakness, it's warning. And when staff are struggling, residents feel it immediately. The therapeutic relationship depends on staff who have the capacity to show up fully.
How to Track: Conduct quarterly anonymous surveys on workplace safety, morale, and support. Track not just who leaves, but when they leave (probationary period vs. veteran staff). Analyze sick leave by day of week and shift, patterns reveal stress points.
How to Address:
Transparency: Share retention data with supervisors and teams. Make it clear that workforce wellness is a leadership priority, not an HR afterthought.
Clarity: Define what support looks like. Create clear pathways for staff to report concerns, request backup, or access peer support without stigma.
Data-Driven Response: When turnover or sick leave spikes on specific units or shifts, investigate immediately. Look at supervision quality, workload distribution, and unit culture. Adjust staffing ratios, improve supervision, or provide additional training based on what staff tell you they need.
The Principle: Leaders must treat workforce wellness as operational infrastructure, not an afterthought. Your staff are your most important safety system.
3. Grievances and Complaints
What to Track: Number filed, themes and categories, resolution times, who filed (demographics, unit, length of stay), and outcomes. Track whether grievances are substantiated and what changes result. Does the population think the process has credibility? Do employees feel empowered to name when they have a conflict of interest in review? Are themes noted? Addressed?
Why It Matters: Grievances tell you who feels unseen. When people lose faith that harm will be addressed, they find other ways to be heard, and those ways often involve risk. An unresolved grievance is a crack in the therapeutic alliance, a gap in security, and a failure of programming to meet people where they are.
How to Track: Create a centralized database that codes grievances by type, tracks time from filing to resolution, and captures outcomes. Review aggregate data monthly with leadership and quarterly with the broader community.
How to Address:
Transparency: Publish summary reports on grievances, what was filed, what was found, what changed. Let people see that the system responds, even when the answer is "no."
Clarity: Make the grievance process simple and accessible. Ensure everyone knows how to file, what to expect, and what timelines to anticipate.
Data-Driven Response: When similar grievances emerge repeatedly, treat it as a system failure, not individual complaints. Convene stakeholders to address root causes. When resolution times lag, investigate bottlenecks and adjust processes.
The Principle: Transparency is oxygen. Publish outcomes. Own mistakes. Every unanswered complaint becomes a seed of resentment that will eventually grow into something larger. Meet with employee groups, resident groups, community groups.
4. Emergency Response Readiness
What to Track: Response times from call to arrival, coordination effectiveness between teams (medical, custody, mental health), post-incident debriefs, and near-miss events that could have become emergencies.
Why It Matters: Emergencies are the purest test of a system's reliability. If people can't count on a quick, coordinated response when lives are on the line, safety becomes performative, not real. And when people don't trust the system to protect them in crisis, they cannot trust it to support them in growth.
How to Track: Timestamp every emergency call and response. Conduct structured after-action reviews within 48 hours of every significant incident. Track near-misses with the same rigor as actual emergencies, they're warnings.
How to Address:
Transparency: Share emergency response data with all staff. Discuss what went well and what didn't. Create psychological safety for honest debriefs.
Clarity: Define roles in advance for every type of emergency. Ensure everyone knows who leads, who supports, and who communicates. Eliminate role confusion before crisis strikes.
Data-Driven Response: After every emergency, identify one thing to improve. Drill that improvement. When response times lag or coordination breaks down, bring teams together for joint training. Simulate scenarios until responses become automatic.
The Principle: Each drill should lead to one refinement. Readiness is not a checklist it's a living practice that requires every part of the system to work together.
5. Programming and Engagement
What to Track: Enrollment numbers, attendance rates, completion rates, program waitlists, and behavioral outcomes (incidents before/during/after programming). Track who isn't engaging and why.
Why It Matters: Engagement is the most visible measure of safety. When people disengage, they're telling you they don't trust the environment. Programming isn't separate from security it is security. Meaningful activity, connection, and purpose are the best violence prevention tools we have. One of the best committees I ever got to help with was a violence reduction committee with members of the population as equal partners. More on this one in another article or 17....
How to Track: Monitor enrollment and attendance daily, not just monthly. Conduct focus groups with participants and non-participants. Track correlation between programming schedules and incident rates.
How to Address:
Transparency: Share engagement data publicly. Celebrate what's working. Acknowledge what isn't without shame or blame.
Clarity: Make programming accessible and relevant. Explain why programs exist, what participants will gain, and how programs connect to individual goals. Remove bureaucratic barriers to enrollment.
Data-Driven Response: When engagement drops, investigate immediately. Is it the content, the timing, the facilitator, or the environment? Survey non-participants about barriers. Adjust offerings based on actual needs and interests, not assumptions.
The Principle: Ask not "why aren't they participating?" but "what have we done to earn their trust?" Programming works when safety, structure, and relationship are already in place. Also, review what is available and link it to what the areas of risk and need are for the population. (I developed a framework for this years ago if you need help here.)
6. Environmental Conditions
What to Track: Lighting functionality, noise levels, cleanliness scores, temperature complaints, maintenance work orders (submitted, pending, completed), and time-to-repair metrics.
Why It Matters: Physical environment shapes psychological safety. A neglected space tells people, "you don't matter." Order and care restore dignity and calm. You cannot run effective therapy groups in rooms with broken chairs and peeling paint. You cannot expect people to regulate their emotions in environments that are sensorily overwhelming.
How to Track: Conduct monthly environmental audits using a standardized checklist. Track maintenance requests from submission to completion. Survey staff and residents about environmental concerns quarterly.
How to Address:
Transparency: Post maintenance work orders publicly. Let people see what's been requested, what's in progress, and what's been completed. Explain delays honestly.
Clarity: Create clear standards for cleanliness, maintenance, and environmental quality. Make everyone responsible—not just facilities staff.
Data-Driven Response: When environmental scores drop or maintenance backlogs grow, escalate to leadership immediately. Prioritize repairs that directly impact safety and dignity. Involve residents and staff in co-creating solutions where possible.
The Principle: Care for the space, and it will care for the people in it. Every light bulb and door hinge is part of the culture. Every repair is a message about what we value.
7. Communication and Climate Feedback
What to Track: Survey response rates and themes, frequency of staff-resident meetings, rumor logs (what's being said in the informal channels), and communication satisfaction scores.
Why It Matters: Silence in a facility is never peace it's suppression. Real safety exists only where people believe they can speak truth without retaliation. Therapeutic relationships require honest communication. Security depends on information flow. Programming thrives when people feel heard.
How to Track: Conduct regular climate surveys with both staff and residents. Track attendance and quality of community meetings. Monitor informal communication channels (not surveillance listening for themes and concerns).
How to Address:
Transparency: Share survey results with the community. Report back on what was heard and what will change as a result. Close the feedback loop visibly.
Clarity: Create multiple, accessible channels for communication—formal and informal. Make it clear who receives feedback, how it will be used, and what people can expect in return.
Data-Driven Response: When satisfaction scores drop or rumors increase, treat it as a communication breakdown. Increase touch points, create forums for dialogue, and empower leaders at every level to listen actively. When people feel heard, respond with action even if the action is explaining why something can't change.
The Principle: Feedback loops require humility. The question isn't "Did we listen?" It's "Did they feel heard?" And when people feel heard, they invest in the community's safety and success.
The Integration Imperative
Here's what I've learned working in leadership in some of the most challenging environments in our system through successes that changed lives and failures that taught me what not to do:
The facilities that succeed are the ones that refuse the false binary.
They don't pit security against treatment. They don't separate programming from safety. They don't pretend that environmental conditions are unrelated to behavioral outcomes. They don't depend on blame and deflection. They are places that permit healthy disagreement and hard conversations.
I've seen units transform when leadership finally stopped treating these as competing priorities. I've also seen facilities collapse when they didn't, when security became about control without care, when therapy happened in spaces that felt unsafe, when programming existed on paper but not in practice.
The pattern is clear: facilities that thrive build systems where:
Security staff understand trauma and can de-escalate with empathy
Clinical staff understand the realities of custody and can work within structure
Programming staff understand that safety creates the space for engagement
Leadership understands that all of these roles are interdependent
We must embrace complexity. Not because it's comfortable, but because it's true. Human systems are complex. Healing is complex. Safety in the context of coercion and care is extraordinarily complex.
I don't pretend to have mastered this. No one has. But I've learned that the only way to navigate complexity is to see it clearly, respect it fully, and build accordingly. The answers exist not in perfection, but in integration. Oh, and remember culture change and any/all of this do not happen overnight. Step one is to name and put light on issues. If one cannot identify issues, you cannot actually solve them.
The Human Imperative
Safety and security aren't just management priorities they're moral responsibilities. The people who live and work in these facilities are part of our communities. Their safety is our safety. Their healing is our collective future.
Every day of inaction compounds harm. Every ignored indicator is a missed opportunity for trust. Every failure to integrate security, programming, and care is a failure to create the conditions where change is possible.
I've spent my career in these systems not as an outsider who visits and leaves, but as someone who has led teams through crisis, redesigned broken processes, and sat in rooms where the stakes were life and death. I've made decisions that worked and decisions that didn't. I've learned from both.
What I know now what the data, the stories, and the scars have taught me is that we must treat the stewardship of safety as sacred work. Because it is.
And we must stop pretending that security, programming, and therapy are separate endeavors. They are one system. They require one vision. They demand one commitment: to create environments where every person, resident and staff alike, can be safe enough to grow.
The work is hard. The complexity is real. But the answers exist, and they're within reach for any leader willing to see the whole system, embrace its interdependence, and lead accordingly.
Felice Upton is the founder of Just Us Consulting LLC and has spent decades leading transformational change in corrections and residential care systems. Her work centers on the integration of safety, dignity, and growth and the leadership required to make it real.
For consultation or speaking engagements, reach out.
