How I Structure a New Practice Area System in a Weekend

This is a narrower question than "how do I build a matter management system from zero," which I have already written a thirty-day plan for. This is the question a practice asks once it already has a working spine for one matter type and wants to add a second, a third practice area a firm is expanding into, or a new line of work a solo practitioner is testing. Once the spine exists, standing up a new practice area is genuinely a weekend project, and here is the method that makes it one.

Why a new practice area is faster than the first one

The first matter type is slow because you are designing the spine itself while also designing the practice-area logic on top of it, two hard problems at once. A second or third practice area only has one hard problem left, the practice-area logic, because the spine, matters as the hub, actions, deadlines, team, evidence, research as linked databases, already exists and does not need to be redesigned. This is the entire reason the weekend timeline is realistic rather than optimistic marketing.

Friday evening: name the practice area's specific shape

Before touching the database, spend an hour naming what makes this practice area's matters actually different from the ones already running through your spine. Not everything, specifically the differences: what counts as a matter here, what stages does it move through, what actions repeat that do not exist elsewhere, what deadlines are unique to this practice area, what evidence types matter that your other matter types do not touch. Most of the six primitives carry over unchanged from your existing spine. The work is identifying precisely which parts do not, and writing those down before opening any software, the same naming-first discipline that makes any build faster rather than slower.

Saturday morning: build the action template

With the practice area's shape named, build the action library for it as a template that populates automatically when a new matter of this type opens, exactly the same pattern your existing matter type already uses. Because the spine already exists, this is mechanical rather than exploratory: you are populating a known structure with new content, not inventing the structure itself. This is usually the fastest part of the whole weekend, two to four hours for a well-named practice area.

Saturday afternoon: wire the deadline logic

Identify which deadlines in this practice area calculate from a triggering fact, the way most procedural deadlines do, an incident date, a notice, a filing, and wire those calculations into the structure rather than leaving them as manual entries. This is the step people are most tempted to skip under time pressure, treating deadlines as something to handle "for real" later. Skip it and you have quietly reintroduced the single most common source of missed deadlines I have seen across 200 systems, a calendar that only knows what it is told, into a brand-new practice area on day one.

Saturday evening: define evidence and document categories

Name what evidence actually supports a claim in this practice area, and set up the document categories your matters will actually use, not a generic uploads folder but categories that map to what this specific practice area produces and relies on. If AI-assisted drafting will touch this practice area at all, this is also where you decide what the bounded pool looks like for evidence anchoring, before the first real matter needs it, not after.

Sunday: run one real matter through it, end to end

Take one actual matter, ideally one already sitting in your intake pipeline waiting on this new practice area, and run it through the new structure completely, open to whatever stage it has reached. This is where you find what Friday and Saturday missed. Something will not fit cleanly. Note it, fix what is genuinely necessary, and resist the urge to keep adding refinements the one test matter did not actually ask for.

What makes the weekend fail

The weekend fails, in my experience, in exactly one of two ways. Either the spine was not actually solid going in, someone tries this method as their first matter type rather than their second, and discovers on Saturday that they are really doing the thirty-day build compressed badly into two days. Or the Friday naming step gets skipped in favor of jumping straight into the database, and Saturday becomes a slower, less confident version of itself because nobody actually decided what makes this practice area different before trying to model it.

Why this is worth doing practice area by practice area

A firm that tries to expand into three new practice areas simultaneously, without a proven spine and without this discipline, is taking on the thirty-day build's full complexity three times over, at once, which is close to guaranteed to stall. Doing it one practice area at a time, one proven weekend after another, is slower in the short term and dramatically more reliable, because each weekend inherits a spine that has already been tested by the one before it.

If you are standing up a new practice area and want the starter structure already wired the way I build it, rather than reconstructing the spine pattern from scratch every time, the Matter Starter System is the same base structure, ready to adapt to a second, third or fourth practice area over a weekend rather than a redesign.