Technology can expand legal help by supporting people representing themselves, reducing repetitive work for lawyers, and making courts easier to navigate. This 2017 essay explores those possibilities through guided interviews, client participation in gathering information, automated documents, and emerging intake tools. It also addresses the funding and organizational barriers that can keep promising projects from […]
Blog
Using Powershell to manage large HotDocs interviews
Large HotDocs interviews can require a lot of repetitive scripting to keep related questions and components in sync. This walkthrough shows how PowerShell can read a component file's XML and generate code for showing, hiding, setting, and summarizing groups of variables. Based on an eviction-defense form library, it focuses on reducing manual copying and omissions […]
Using Office 365 SharePoint as a Litigation Support Tool
A small law firm may need a practical way to organize discovery without a complex litigation-support system. This 2017 example shows how a legal aid program used SharePoint Online's document libraries, metadata, keywords, filters, and search. It also explains limits around page-level indexing and PDF annotation. The emphasis is on making useful use of existing […]
How legal technology can help your legal services program and your client base
This 2017 overview makes the case for using technology to help legal services programs reach more people. It looks at tenant-facing tools, guided document assembly, and early AI-assisted intake, with examples from JustFix, LawHelp Interactive, and legal aid organizations. Community-led design and reducing repetitive work are recurring themes. The article captures an early stage of […]
WriteClearly: Developing a Google Apps Add-on to Promote Plain Language in the Legal Community
Plain-language tools are most useful when they fit into the place where lawyers already write. This account of the 2017 TIG hackathon explains how a hackathon team connected WriteClearly to Google Docs, bringing readability feedback into a word processor. Alongside the technical walkthrough, it describes the team's limited scope, reuse of existing code, and plans […]