What this is
The Blueprint turns the principles in the ebook, How to Build a Board-Level Legal Scorecard, into worksheets. Part One lays out the small data model every board line feeds from: a handful of records, one status map that makes every system speak the same language, and a matter-category tag. Part Two builds each of the eight lines as a build sheet: the inputs it reads, the math in plain arithmetic, how often to refresh it, who owns it, and how to set what good looks like.
Part Three is where most readers will spend their time. It gives three tracks for standing the page up depending on how connected your systems are: Track A for an integrated platform or systems that already talk, Track B for systems that do not talk (most mid-size departments), and Track C for teams with no system that can assemble it yet. The design does not change between tracks. Only how each line gets fed is different, so you can move up from C to B to A without redrawing anything.
Throughout, it stays honest about the trade-offs: what AI can take a first pass on, where a person has to confirm, and where a line should carry a coverage or confidence flag instead of false precision.
What is inside
Four parts, about 8,100 words. Built to be worked through, not read in one sitting.
- 0Before You Start. The page you are building, in one paragraph, for anyone who arrives without the ebook.
- 1Part One, The Data Model Underneath the Page. Records, fields, where each usually lives, the status map, the matter-category tag.
- 2Part Two, Build the Eight Lines. One build sheet per board line.
- 3Part Three, Stand It Up on What You Have. Tracks A, B and C, and how to move up.
- 4Part Four, Keeping It Honest and the Operating Cadence. Follows once the page is running.
- +What LegalOperator does today. A short section, kept separate from the tool-agnostic build guidance.
The page you are building
If you arrived here without the ebook, this is the page in one paragraph. One page. Five questions the board and CEO are really asking. Eight numbers that answer them, each with what good looks like and the move when it is off. To the right of every line: a status, a trend, and a short read. Where the data is thin, the line carries a coverage or confidence flag instead of false precision.
Are we on top of the whole workload?
Is the business unblocked, and are matters moving?
Are we protected?
Are we growing capacity faster than headcount?
Is spend under control?
The small model every line feeds from
The eight board numbers look like a lot to maintain. They are not. They all draw from a handful of records with a few fields each, and most of them already live in the systems you run.
| What you track | The few fields that matter | Where it usually lives | Board lines it feeds |
|---|---|---|---|
| Request | Received time; first human-touch time; how it resolved; who asked | Your intake or front-door tool; a shared inbox if you have no intake system | Time to first response; Self-serve rate; Shadow demand |
| Matter | Open date; close date; native status; last-activity date; matter category; practice area; owner; assigned lawyer | Matter management (with eBilling, your ELM) | Work in vs. work cleared; Stalled-matter rate; Load per lawyer |
| Matter-category tag | Project, portfolio, or advisory | A field you add in matter management, or a column in the workbook | Scopes work in vs. work cleared and stalled-matter to the right work |
| Status map | Native status to one of the five standard statuses | A mapping you keep once, in the platform or a workbook tab | Every line that needs one language |
| Owner | The one person accountable for the matter or the date | Matter management; docketing or CLM for a date's owner | Critical-date coverage; stalled follow-up |
| Critical date | Date; type; the matter; owner; condition; source system | IP docketing; court dockets; CLM; a regulatory or entity calendar | Critical-date coverage |
| Invoice and accrual | Invoiced to date and accrual, per matter; the department budget, phased | eBilling; the budget set by legal with finance | Outside counsel spend vs budget, with forecast |
| Roster | Lawyer; in-house or carried by an outside provider | Matter management, or a team roster you keep | Load per lawyer |
Five standard statuses cover a whole department
Intake
It has arrived. Work has not started.
Active
Someone on your team is moving it right now.
Waiting
Open, but the next move belongs to someone else: a court, a counterparty, a signature, a government office.
Closed and Dormant
Closed is done. Dormant is open by design and resting between deadlines. Never mistaken for stuck, and never counted as cleared.
The Blueprint fills the map in across IP, litigation, contracts, employment, immigration, M&A, and entity management, so you can copy the pattern for the systems you run. The one call worth slowing down for is active versus waiting, because that is the line the stalled-matter number rides on. Ask whose desk the next move is on.
Three build paths, easiest first
- 1Path 1: lines that come from one system. Time to first response, self-serve rate, and outside counsel spend vs budget. Connect one source, define the one term that trips people up, and the line is live. If you do nothing else this month, do these three.
- 2Path 2: lines that wait on the data layer. Work in vs. work cleared, stalled-matter rate, and critical-date coverage. They need the matter-category tag and the status map, then they light up together.
- 3Path 3: lines you estimate, not measure. Shadow demand and load per lawyer. No clean feed, so you build a defensible estimate, report a direction with a confidence flag, and improve it over time.
Every build sheet has the same core fields: the inputs it reads, the math in plain arithmetic, how often you refresh it, who owns it, how you set what good looks like, and where AI takes work off your hands. A threshold is not a benchmark you import from someone else. You set it from your own promise and your own baseline.
Three tracks to stand it up
Which one is yours depends on one thing: how connected your systems are today. The design does not change between them. Only how each line gets fed is different.
| Track | You are here if | How the page gets fed |
|---|---|---|
| Track A | Your systems already connect, or a platform assembles the page for you | Live feeds. Map statuses and categories once, then the page fills itself. |
| Track B | You have the systems (matter management, eBilling, docketing, CLM) but they do not talk | Scheduled exports into one light reporting layer you own. |
| Track C | You have no system that can assemble this, which is most teams starting out | One disciplined workbook, filled on a fixed monthly routine. The free Legal Scorecard Workbook is this track, built. |
A feed replaces a tab, not the page. You design once. Moving from one track to the next never means redrawing the page.
Who this is for
Legal operations leaders and General Counsel who have read the ebook, or who already know what they want on the page, and now need to build it. If you have an integrated platform, connect and confirm. If your systems do not talk, export into one layer you own. If you have no system yet, build the workbook and run it like one. Then move up when it pays to, a feed at a time.
Take it with you. Three parts, eight build sheets, no form to fill out.
Download the BlueprintPart of The Legal Scorecard Series
Three pieces that build on each other. The ebook, How to Build a Board-Level Legal Scorecard, designs the one-page Scorecard and makes the case for it. This Blueprint turns the design into a build guide on the systems you already have. The Legal Scorecard Workbook is the fastest way to have a real page this month.
All three are free, with no form. Find them on Resources.
Want the Scorecard to fill itself?
LegalOperator captures every request at the front door, so the numbers behind the page are already there. See how it works.
Book a Demo