← All practice areas

Legacy load: Medium · Track: AI-Native Transformation

In-House Legal Operations

Not a practice area but an operating model: an in-house department is judged on throughput and visibility as much as legal judgment. adnah's read: this is the purest primitives problem on the list.

Ceremony, safe to remove

  • Manually routing contract intake requests from business units to the right reviewer based on informal knowledge of who handles what
  • Rebuilding matter status summaries from scratch for every board or audit committee update
  • Tracking outside counsel spend and matter status across separate email threads and spreadsheets per firm
  • Re-triaging the same categories of recurring business unit requests (a standard NDA, a routine vendor amendment) as if each were novel

Irreducible, stays with the lawyer

  • Deciding when a matter is significant enough to escalate to the general counsel or the board, and how to frame that escalation
  • Negotiating the handful of contract terms that carry real business risk, as opposed to the boilerplate around them
  • Choosing which matters go to outside counsel versus stay in-house, and which firm is right for which kind of risk
  • Judgment calls on regulatory or reputational exposure that require weighing legal risk against business strategy

Primitives most in play

MatterActionTeamTime

The usual failure mode

The department-level failure mode is different from a law firm's: the risk is not bad legal work, it is invisible legal work. An in-house team that automates intake and triage without also fixing how that work becomes visible to the business ends up faster but no more trusted, because the business units still cannot see what legal is doing with their requests or why some take longer than others. The transformation has to make the operating model legible to the rest of the company, not just faster for the legal team itself.

What changes

  • Before: contract intake requests land in a shared inbox and get routed based on who happens to see them first. After: requests are triaged and routed automatically by type and risk level, with routine requests resolved without a human touch.
  • Before: matter status for the board or audit committee is compiled manually from scattered records days before the meeting. After: status reflects the live state of the matter portfolio and the update is a review pass, not a reconstruction.
  • Before: outside counsel spend and matter progress are tracked per firm in disconnected spreadsheets. After: spend and status are visible across all outside counsel in one place, so budget conversations start from real data.
  • Before: standard requests like a routine NDA or vendor amendment are handled as one-off legal reviews. After: standard requests resolve against a known playbook automatically, and attorney time goes to the requests that deviate from it.

What a working transformation looks like here

A working transformation looks like a legal department where a business unit can see, without asking, where its request sits and roughly when it will be resolved, and where the general counsel can answer a board question about matter exposure or outside counsel spend from current data rather than a scramble. The department's headcount stays flat or shrinks relative to the business it supports, while the things escalated to senior lawyers are, more consistently than before, the things that actually deserved escalation.

Next practice area

Litigation & Disputes