Designing for the Edge: Guided Protective Order Drafting

A protective order is one of the most direct legal protections a survivor of domestic violence can ask for, but putting one together is hard. The forms are long, the instructions are dense, and the rules are local. If you make a mistake, or miss a detail, or cannot explain what happened in the way the court expects, the filing can be delayed or rejected. A survivor trying to do this under stress is working against a system that was not designed for them.

This is an independent Prosocial Coding LLC project, separate from my day job. My years in the domestic violence field shaped the standard I built Protectly to meet. In this space, software cannot just be useful; it has to be safe. If a tool overclaims what it can prove, or exposes sensitive details, it would fail the standard. The question that runs through every design decision is the same one I would apply to any crisis service: could this harm someone? In a protective order tool, that question changes how you handle data and how you design the flow.

What it does

Protectly is a guided drafting tool for Texas protective order materials. The app walks a user through a guided intake, step by step: who they are, who they are filing against, the relationship, who needs protection, what happened, and what they are asking the court to prohibit, keeping key facts organized.

Who it is for

Protectly is designed for self-represented filers putting together protective order materials and advocates or lawyers reviewing a case before it is filed. The tool routes case review and filing actions to trained professionals via an Advocate Workbench, ensuring that human judgment remains central to the process.

The safety work

Safety and privacy are built into the architecture. User and incident information are validated at multiple layers before any action is taken. A privacy pipeline redacts personal identifiers from data before processing, swapping them back in locally. Input moderation blocks requests containing personal data or unexpected patterns, and generated output is validated to ensure safety. Draft data is encrypted on the device, and the system maintains a zero-tracking posture with no client-side analytics.

What it does not prove

Protectly is a drafting assistant, not a live filing service. It does not guarantee legal filing, and it has not been through formal legal review, environment certification, or independent penetration testing. Simulation mode is the default, and it should not be relied upon for active court cases without professional legal review and verification of all generated outputs.

Where it is going

Next priorities include survivor-informed UX testing, accessibility reviews, Spanish-language support, external legal review, and independent security testing. The goal is to support responsible drafting while leaving room for human judgment.