Public services site
A clear, reassuring site that explains the services and what to expect — written for people navigating a difficult, often court-mandated process.
Professional services · Sensitive workflows
SafePassage KC
A secure services site and intake workflow for court-ordered therapy and supervised parenting support. The mandate is simple and unforgiving: handle sensitive, court-adjacent information carefully, and keep the operation stable for the families and professionals who depend on it.
Live route proof
Current enough to cite.
This case page checks its own route brief, public freshness score, and visitor-route signal before asking anyone to trust the story.
Freshness
Checking
Public proof audit
Route brief
Checking
Assistant context
Interest
Checking
Visitor route signal
Loading the citation-safe case brief.
Snapshot pendingSoftware for a high-stakes service.
SafePassage KC provides court-ordered therapy and supervised parenting support — services where the people involved are often at the hardest point of their lives, and where the paperwork is tied to legal obligations.
My role is the technology behind it: a public services site, an intake workflow, and the back-office tooling that keeps the practice running — built so the staff can focus on people, not software.
Sensitive data, zero room for sloppiness.
This isn’t a storefront where a bug costs a sale. The information flowing through SafePassage is personal and court-adjacent. Intake has to be clear and respectful, records have to stay protected, and the system has to simply keep working — reliability and discretion matter more than features.
The constraint that shapes everything: collect what’s needed, expose nothing that isn’t, and never let the technology become one more thing for a stressed family to fight.
A calm front door and a steady back office.
Secure intake
A structured intake workflow that gathers exactly what the practice needs — no more — and routes it safely to staff.
Back-office tooling
Internal supervisor and case-support tooling that keeps day-to-day operations organized without adding overhead.
Stable operations
Hosting, maintenance, and the unglamorous reliability work that keeps a service families rely on simply available.
Getting the boundaries right.
Privacy by default
Designing every form and flow to minimize the data collected and tightly scope who can see it — the safest record is the one you never expose.
Empathy in the UX
The audience isn’t shopping — they’re often court-ordered. Tone, clarity, and a frictionless path matter as much as any technical control.
Quiet reliability
Maintenance and fixes happen without drama or downtime, because the people using this service have enough to deal with already.
Running, quietly.
Live
In daily operation
Secure
Intake & records
Minimal
Data footprint
Stable
Operations
Out of respect for the people served, no client counts, case details, or operational specifics are published here.
Boring, dependable, locked down.
Platform
PHPMySQLSecure forms
Mature, well-understood tooling for a service that values stability over novelty — fewer moving parts, fewer surprises.
Posture
Least-data intakeScoped accessQuiet maintenance
Security and privacy decisions baked into the design, not bolted on — appropriate for sensitive, court-adjacent work.
Keep it dependable.
The roadmap here is intentionally modest, and that’s by design: keep the service secure, available, and easy for staff to operate. For sensitive, court-adjacent work, “boring and dependable” is the feature.
See the service.
The public site is live.