How to stop being the first call for every business question (3 of 8)

Your diagnostic is done. You now have a map: where the hours are going, who is carrying the load, and which business units are generating the most noise.

One finding will have jumped out almost immediately.

A significant slice of your team’s time is being spent answering the same questions. Different requester. Slightly different wording. Identical answer, every single time.

There is a question I ask every Chief Legal Officer or General Counsel I work with, usually in the first week: ‘What are the five questions your team gets asked most often by the business?’

Every single time, the answer comes back immediately. No hesitation. Because every legal team has them.

• “Can we sign this NDA without legal review?”
• “What is our standard payment term?”
• “Do we need a data processing agreement for this vendor?”
• “What is the contract approval threshold for my level?”
• “What is our policy on gifts received/offered?”
• “How do I report a suspected misconduct or compliance breach?”

Ring any bell?

These questions are not complex.

They do not require a lawyer.

They require an answer that already exists, it just has not been made accessible to the people who need it.

And yet, somewhere in your organization right now, a lawyer is typing that answer for the fourteenth time this month.

Self-service is not about removing lawyers from the global equation. It is about removing lawyers from the mundane answers that do not require them.

The Cost of Being the Default Answer

When the business has a legal question, the path of least resistance is to call the lawyer they know. Not because the answer is complex, but because that is the habit.

And legal teams accommodate this habit because they care and want to be helpful.

But helpfulness without structure creates dependency, and dependency scales in only one direction.

Every time your team answers a recurring question in real time, three things happen:

• First, they spend time they could have spent on higher-value work.
• Second, the business learns that calling legal directly is the right process.
• Third, the answer exists nowhere on record, so the next person with the same question starts the cycle again.

Multiply that across a team of 10 lawyers, 5 recurring questions per week, at least 15 minutes per interaction. That is more than 12 hours a week of answering questions that could have been answered by a well-designed FAQ page.

That is a fourth of a full-time legal position. Gone. Every week. And it does not show up on any budget line.

The Three Layers of Self-Service

Effective self-service for a legal department is not a single tool. It is a layered infrastructure, with each layer handling a different level of question complexity.

Layer 1: The Process Library

The first thing to build is a clear, accessible guide to your standard processes.

Not a policy document: those are written for compliance, not usability.

A practical guide that tells someone in procurement or HR “Here is what you do when you need X”.

This content already exists: in lawyers’ heads, in email threads, in onboarding documents no one reads.

The task is to extract it, make it readable – ideally visual – and put it somewhere findable. SharePoint is the most natural home for this if your organization uses Microsoft 365.

Layer 2: The FAQ

A FAQ is different from a process guide.

It answers specific questions in plain language. Short. Direct. No legal caveat padding every sentence.

The questions to include are the ones from your diagnostic, i.e. the recurring questions you identified in the time audit and intake analysis. Start with ten. Build from there.

The discipline here is writing answers the way you would actually explain them to a business colleague, not the way you would write a legal memo.

If you would say “You can do that without review as long as the value is under fifty thousand euros”, that is the FAQ answer. Not three paragraphs with a disclaimer at the end.

Layer 3: The GAI Chatbot

For legal departments that have the basics in place (a process library, a FAQ, a structured intake per article 4), a simple GAI chatbot is increasingly within reach, and the ROI is significant.

This is not a hallucinating general-purpose AI answering legal questions with invented confidence. It is a retrieval-based assistant trained on your existing documentation that surfaces the right answer from the right source, every time.

When a question exceeds its scope, it routes to legal intake, it does not guess.

The chatbot does not replace legal judgment. It replaces the administrative act of transmitting information that already exists.

The Common Mistake: Building for Lawyers, Not for the Business

Most self-service legal initiatives fail not because the content is wrong, but because it is not designed for the person who needs to use it.

When you write “Subject to applicable regulations and depending on the nature of the processing and the jurisdiction involved, you may in certain circumstances be required to…” you have answered nothing. The business colleague will close the page and call the lawyer for an actionable answer.

Instead, when you write, ask yourself if the answer is clear and direct so that it provides value to the reader.

My advice is to test every piece of self-service content with someone from the business before you publish it. Ask them to find the answer to a specific question. Watch what they do.

If they cannot find the answer in ninety seconds, redesign it.

If they ask you follow up questions after reading the answer, redesign it.

Implementation: A Realistic Timeline

• Weeks 1 – 2
  Gather / Document your standard processes.
  Design a business-oriented 1-pager visual for each.
• Weeks 2 – 3
  List your top 10 recurring questions using your diagnostic data (see article 2).
  Draft plain-language answers for each.
• Week 4 – 5
  Build a basic SharePoint Legal page with a process overview section and a FAQ section.
• Week 5
  Communicate it to the business, not with a policy email, but with a short walkthrough from a lawyer explaining what it is and when to use it. You could even record a short video.
• Months 1 – 3
  Monitor usage, add the next ten FAQ items, refine process visuals based on what questions are still coming in.
• Month 4
  Evaluate readiness for an AI chatbot layer based on volume and FAQ maturity.

Measuring Whether It’s Working

Before you launch, capture a baseline: how many direct legal queries is your team receiving per week, from which business units, on which topics?

Three months after launch, measure again. A well-designed self-service layer typically reduces direct queries by 30% to 50% in the first quarter.

The metric that matters most is not page views: it is how often lawyers are asked questions the FAQ already answers. When that number approaches zero, you have built something that works.

What This Unlocks

Getting recurring questions off your team’s plate changes the nature of the work legal does. When lawyers stop being a helpdesk, they start being a strategic resource. And the business starts relating to them differently.

**********

But self-service handles questions that already have answers. There is still the challenge of managing the requests that do not: the new work that comes in every day, often without structure, without priority, without context. Every piece of that work lands on your team the same way: directly, with no filter, no routing logic, and no information attached.

That is not a legal problem, it is an architecture problem. And fixing it requires building a proper front door to your legal department.