Three Reports You Couldn't Build Before Custom Fields

A custom field is worth adding only when a report can group by it. Three examples make that concrete: profitability by referral source, realization by practice area when your chart of accounts isn’t organized that way, and matter performance by responsible attorney across a mixed book of work.

Firms tend to add fields the other way around: something feels worth tracking, so a field gets created, and the reporting question that would justify it never gets asked out loud. A year later, the field is inconsistently filled in, nobody remembers why it exists, and it can’t answer the question it was quietly meant to answer anyway. Working through three concrete reports first, and only then deciding which fields they require, avoids that trap.

Profitability by referral source

Say, hypothetically, a firm tags every new client at intake as either an attorney referral or a paid marketing lead. A quarter later, a report grouped by that field shows attorney referrals billing a hypothetical $10,000 and collecting $9,000, while marketing leads bill the same $10,000 but collect only $7,000 — invented figures, not a benchmark. Nothing about that gap was visible before the field existed; it was sitting inside a pool of invoices with no way to separate them.

Adding the field to a client record takes a minute. The part worth planning is whether your team will tag every new client with it, consistently, starting now, because the report six months out is only as good as the tagging behind it. A field added retroactively can’t recover data about clients who came in before it existed; it can only make the picture clearer going forward, which is a real reason to decide early rather than waiting for the question to become urgent.

The same logic extends past referral source. A firm might just as easily want to know profitability by lead channel, by practice niche, or by which partner originated the relationship. The mechanism is identical in every case: a field on the client record, and a report willing to group by it.

Realization by practice area, when the chart of accounts isn’t organized that way

Most charts of accounts group revenue by income type, not by practice area, because that’s how QuickBooks Online is built to report to an accountant, and an accountant’s first concern is the tax return, not which kind of legal work is more profitable. A firm running both litigation and estate planning out of one entity often can’t answer “which practice area realizes more of what it bills” from the general ledger alone; the income accounts don’t carry that distinction, and restructuring the whole chart of accounts around practice area is a heavier change than most firms want to make just to answer one question.

A custom field on the matter sidesteps that trade-off. Tag each matter with its practice area, and a realization report can regroup the same billed and collected time by that tag instead of by income account, a gap the ledger structure was never built to show on its own. The chart of accounts keeps doing its job for the accountant; the field does a different job for the firm.

This matters more the longer a firm has run mixed practice areas without a way to separate them. A firm that has always bundled two practice areas into one set of numbers has no historical baseline to compare against once it starts tagging, which is its own argument for starting the tagging now rather than waiting for a reporting need to become pressing.

Matter performance by responsible attorney, across a mixed book

A firm where attorneys carry a mix of flat-fee and hourly matters has a harder productivity question than a firm that bills one way. Averaging hours or revenue per attorney across both fee types flattens the picture: an attorney whose flat-fee matters are running long against the fee can look identical, on paper, to one whose hourly matters simply run bigger. Neither number, on its own, tells a managing partner whether that attorney’s book is actually healthy.

A field marking fee type per matter lets a report split the two apart before comparing attorneys, so the comparison sits between like matters instead of an average that hides which fee type is actually driving a given attorney’s numbers. Once fee type is a field rather than something someone has to remember matter by matter, the same split can extend to comparing responsible attorney against originating attorney, or to isolating one practice area’s book from the rest of a mixed firm’s.

The field is the small part of the work

Adding a field takes a minute; getting a year of matters tagged consistently enough for a report built on that field to mean something takes discipline from everyone entering new records. That’s true whether the field lives on the client, the matter, or a time entry. Custom fields, and the reporting built around them, sit on LeanLaw’s Pro plan; see LeanLaw’s plans for what’s included at each tier.

Before adding one, it’s worth checking whether the grouping you want already exists. LeanLaw’s WIP, realization, and velocity reports already group by attorney and by matter; a custom field only earns its place next to those when the axis you need is specific to your firm and isn’t already built in.

The question to answer before the field, not after

The three examples above share a structure worth naming directly: a report you want, a variable your existing records don’t capture, and a field that closes the gap only if it’s filled in consistently from here forward. Skip the middle step, and a firm ends up with fields that were created because something felt worth tracking, rather than because a specific report needed them. Those fields tend to get abandoned first, because nobody can point to what they were for.

Working backward from the report is also how to tell whether a field is worth the effort at all. If nobody would actually change a decision based on knowing profitability by referral source, or realization by practice area, or attorney performance split by fee type, the field isn’t worth maintaining, no matter how quick it would be to add. The test worth applying is whether a report built on the field would tell a partner something they’d act on, not whether the field is technically possible to create.

What this depends on

• Whether your reporting need fits inside a standard grouped report or needs something built around your specific field
• How consistently your team tags every new client or matter with the field, not just the ones already on your mind
• Which plan your firm is on, since custom fields are a Pro-tier capability
• How your matter structure lines up with the chart of accounts in QuickBooks Online, since that’s what most reports are grouping underneath the field

Worth asking before you add one

LeanLaw already supports custom fields. What decides whether adding one pays off is simpler: can you already name the report you’d run six months from now, and are you willing to tag every matter between now and then to make it real?