The intake queue is full. A court navigator program makes a “warm handoff.” A partner says they’ll follow up. Then the trail goes quiet, disrupting access to justice. In justice support networks, that quiet can mean a self-represented litigant missed a deadline, lost housing, returned to harm, or showed up alone to a hearing. These […]
An intake specialist scrambles. A client with Limited English Proficiency (LEP) is on the line with a time-sensitive issue, but the on-call interpreter is unavailable. The resulting delay leads to a missed deadline, a critical miscommunication, or worse, a denial of service. This scenario isn't a hypothetical; it's an operational reality that widens the justice
12 Remote Interpretation Tools for Legal Nonprofits: A 2026 Field Memo Read More »
Your intake queue is exploding. A grant report is due. A partner needs a file today. Then someone gets phished, or you notice a login from a remote work location no one recognizes, and suddenly MFA becomes urgent. This is where “big bang MFA” goes wrong. Staff get blocked mid-task, workarounds appear, and IT becomes
You have a problem that shows up in every conversation about AI adoption. Leaders know they need to explore it. They see the potential. They read the articles about productivity gains and cost reduction. Then they sit in a meeting and someone asks where to start, and the room goes quiet. The gap between knowing
How Non-Profits Can Use AI By Using “The Goal” to Find Where AI Actually Helps Read More »
The intake queue is up. A partner needs a same-day handoff. A client is waiting on a document that can’t be found because it’s “in someone’s email.” That’s what the backbone looks like in real life: intake forms, case notes containing bulk sensitive personal data, documents, and the quiet glue between staff and partners. For
It’s 8:05 a.m. on a Monday. Your self-help intake form won’t load, your scheduling portal throws errors, and the “download the packet” links on your website point to blank pages. Staff try the usual fixes. Someone messages a vendor. Someone else restarts a browser and hopes. By 10:30, the phone line is jammed. Community partners
It’s the end of the quarter, and a crucial grant report is due. Your team is in a full-blown scramble, trying to pull data from a dozen different partner organizations, each with its own incompatible spreadsheets and bespoke case management systems. This frantic fire drill isn't just an IT headache; it's a deep-seated operational failure
A Guide to Technology Standards for Access to Justice Networks Read More »
Your intake queue is swelling amid the justice gap. A partner referral went cold because no one saw it. A funder report is due, and three spreadsheets disagree. That’s not a staff problem. It’s a workflow problem. Spreadsheets are good duct tape, until they quietly become the system of record for intake, eligibility, case status,
The intake queue is climbing. A funder report is due. A vendor is pushing a “must-sign-this-week” renewal. Someone asks about AI tools. Another person asks, quietly, “Are we safe if there’s a data breach involving client personal information?” In moments like that, leaders don’t need more opinions. They need a decision they can explain, defend,
If you're leading an access-to-justice organization, you know the feeling. The constant, low-grade anxiety about data breaches after a funder sends another intimidating security questionnaire. The weight of protecting incredibly sensitive client information—from immigration status to incarceration records—is exhausting. The grant reporting deadlines feel like a recurring fire drill, fueled by data scattered across tools
A Guide to a Virtual CISO for Access to Justice Organizations Read More »
