What to put on a contract review dashboard

A contract review team needs two dashboards, and most teams try to build one screen that does both jobs badly. The queue view your reviewers check every day is not the same thing your ops leader or general counsel wants in a monthly update, and forcing one screen to serve both audiences is why half these dashboards get built once and quietly ignored by month three.

The queue view

This is the one your review lead opens most days. It answers a narrow question: what's stuck, and who's carrying too much. Useful columns are contracts open right now by stage (intake, first pass, redline, signature), the age of the oldest contract sitting in each stage, and open work per reviewer. None of this needs to be pretty. A spreadsheet that updates daily beats a polished chart that updates monthly. The point is to catch the contract that's been sitting untouched for eleven days before the counterparty calls asking where it went.

The leadership view

This is a smaller, different set of numbers, reviewed monthly or quarterly, built to answer the questions your GC or procurement lead actually gets asked: is review getting faster, is the team keeping up with volume, and where is risk creeping in. Cycle time is the obvious one, but it only earns its place broken into stages rather than reported as a single blended number, because "review takes six days on average" hides whether those six days went to legal analysis or to a contract sitting in someone's inbox before anyone opened it. A second number worth carrying is the share of contracts that clear on your standard playbook without an attorney escalation. If that share climbs while volume holds steady, your process is doing more of the work. If it's flat while volume climbs, the team is just getting busier, not more efficient.

What doesn't belong here is raw contract count as the headline. Contracts processed per month feels like progress because it's easy to pull, and a KPI breakdown aimed at in-house teams calls this out directly: matter counts and tickets closed measure team activity, not business value, and they survive on dashboards mainly because they're easy to count. Cycle time earns its place instead because it can actually be tied to outliers. The Association of Corporate Counsel has made a version of this point for years, noting that tracking cycle time on a matter type, a contract review matter, for example, lets a department flag outliers early and show that cycle times are coming down over the years, rather than just asserting it.

Where the numbers get gamed

Cycle time is also the easiest metric on this list to fake without meaning to, and it's worth knowing how before you build the report. One breakdown of legal KPIs lays out the mechanism plainly: if turnaround is measured from first lawyer touch to sent to counterparty, a team learns to delay that first touch until the contract is nearly done, which makes the number look great and the actual business experience worse. The practical fix is to start the clock at intake, not at whoever finally opens the file, and to spot-check it now and then by asking a handful of requesters when they actually submitted a contract versus when the system logged it.

The data problem underneath both dashboards

Neither dashboard holds up if the underlying data is a mess of email threads, shared drives, and whatever a reviewer happened to type into a spreadsheet that week. This is where a lot of teams quietly give up on reporting altogether, because cleaning that data by hand every month isn't anyone's actual job. If intake and review already run through a system that tags contract type, flags terms against a playbook, and timestamps when a contract entered the queue on a first pass, those tags become the raw material for both dashboards without someone doing it manually every week. goHeather's AI contract review app does that kind of first-pass tagging and flagging, and it's worth treating as a way to get cleaner inputs into whatever dashboard you build rather than as a replacement for someone deciding what the numbers mean once they're in front of you.

Build the queue view first. It's the one your team will actually open every morning, and it forces you to define what "stuck" means before you try to explain velocity to anyone upstairs. Once that's stable, pull three or four numbers out of it for leadership and leave the rest alone. If you're still working out what those upstream numbers should even measure, how to track two numbers for contract review turnaround is a reasonable place to start before building either screen.

Try goHeather free and see whether cleaner first-pass tagging makes your own numbers easier to trust.

This is legal information, not legal advice; consult a lawyer for legal advice.