Building a Legal Front Door: A Nine-Step Matter Intake Playbook for In-House Teams
Email, chat and hallway requests leave legal with no data and no defensible headcount case. Nine steps to one intake channel: form fields, routing rules, a build-vs-buy call and four metrics for the GC.
What a legal front door has to fix before you pick a tool
If your department still takes work through personal inboxes, Teams or Slack messages and corridor requests, you can't answer the questions a CFO eventually asks the general counsel. How much work comes in? Which business units generate it? How long does it take? Is the team actually underwater, or just disorganized? A legal front door is one required channel for every request. It captures enough structured data on the way in that triage, routing and reporting happen without someone rereading an email thread.
Matter intake software is one way to build that door. It isn't the only way, and it shouldn't be the first decision. The classic waste is buying a platform before agreeing on request types, the information each type needs and who owns what. The tool then gets configured around old habits, and the business keeps emailing the lawyer it likes.
This playbook runs in nine steps. Steps one through five are design work that doesn't depend on a tool. Step six is the build-or-buy decision. Steps seven through nine cover launch, enforcement and reporting. For a department of 5 to 30 lawyers, plan on roughly 8 to 12 weeks from inventory to a live pilot. Most of that time goes to agreeing on rules, not configuring software.
Steps one to three: count the demand, name the request types, draft the form
Step one: sample real demand for four to six weeks
Before designing anything, find out what actually arrives. Ask every lawyer and paralegal to log incoming requests in a shared spreadsheet for four to six weeks: date, requester's function, a rough request type, urgency as the requester stated it, and estimated effort in hours. It's tedious, and it's the most valuable dataset you'll build all year.
Hypothetical example: say a 12-lawyer team split between London and Singapore logs about 450 requests in five weeks. Roughly half turn out to be NDAs and routine commercial contract reviews, a tenth are employment questions, and a long tail of one-off queries makes up the rest. That one finding shapes everything downstream. You now know which request types deserve templates or self-service, and which need a senior lawyer.
Step two: define eight to twelve request types, no more
Fewer than eight types and routing gets crude. More than twelve and requesters pick the wrong one. A workable starting set for most corporate departments:
- NDA or confidentiality agreement
- Sales or customer contract review
- Procurement or vendor contract review
- Employment and HR matter
- Data protection or privacy question
- Regulatory or compliance query
- Dispute, claim or litigation threat
- Corporate or entity governance (board papers, subsidiaries, signatories)
- Intellectual property
- General legal question
Keep "general legal question" so people aren't forced into a wrong category, and review it quarterly. If it holds a large share of volume (say, more than one request in seven), a type is missing.
Step three: draft the request form
The form should take about three minutes. Ask a short common core, then use conditional questions so each request type shows only the fields it needs. Sample core fields:
- Requester, business unit and cost center (pre-filled from the directory where possible)
- Request type (from the list above)
- Counterparty name and governing law or jurisdiction, if known
- Contract or exposure value in banded ranges, not free text
- Requested completion date, plus a required business reason if that date is under five working days away
- Does this involve personal data, a regulator, or a threatened claim? (yes/no flags that drive triage)
- Attachments (the counterparty draft, prior correspondence)
Conditional examples: an NDA request asks whether it's mutual and whether the counterparty's paper is being used. A dispute request asks when the issue arose and whether anything has been sent to the other side. Leave out anything you won't use for routing or reporting. Every extra field lowers completion rates.
Steps four and five: triage and routing rules that hold up under load
Step four: set triage tiers with explicit criteria
Triage works when tiers are defined by facts the form captures, not by how loudly the requester asks. Four tiers cover most departments:
- Self-service: standard NDAs on your paper, template letters, FAQ-type questions. The requester gets a template or playbook, with no lawyer time needed.
- Standard: routine reviews under a value threshold, with a service level of perhaps five working days.
- Priority: above the value threshold, unusual jurisdiction, personal data at scale, or a regulator involved. Two to three working days, senior review.
- Urgent: threatened litigation, a regulator's deadline, a dawn raid or a data breach. Same day, with the head of legal notified automatically.
Set value thresholds in your functional currency and adjust them by region. A threshold that suits a sales team in London or New York may cover almost every deal in a smaller market.
Step five: route to queues, not people
Routing rules combine request type, region and tier. A hypothetical rule set for a team with lawyers in three hubs:
- NDA on company paper goes to self-service and is logged without assignment.
- Sales contract under the value threshold goes to the commercial queue for the requester's region and is picked up in rotation.
- Sales contract above the threshold, or with non-standard liability terms flagged, goes to the commercial lead for that region.
- Anything with the personal-data flag set to yes copies the privacy counsel, whatever the type.
- Dispute or regulator flags go to the urgent tier and notify the GC and litigation lead immediately.
- Unassigned after one working day: escalate to the queue owner.
Three warning signs. Routing to named individuals instead of queues breaks when someone is on leave. A large share of requests marked urgent usually means the urgency field has no consequences. And rules nobody can explain without opening the configuration won't survive staff turnover.
Step six: Microsoft 365 build or dedicated matter intake software
Once the form and rules are written down, the tool decision gets much easier. You're no longer comparing demos. You're asking which option can run your rules with the least ongoing effort.
Many departments already have Microsoft 365. A build using Microsoft Forms or Power Apps for intake, SharePoint Lists or Dataverse for the matter register, Power Automate for routing and notifications, Teams for collaboration and Power BI for reporting is a credible legal operations workflow. Dedicated options include intake and workflow tools such as Checkbox, Josef and Tonkean, plus matter management platforms with intake modules such as LawVu, Xakia, Onit, Mitratech and Wolters Kluwer's Legisway. Product lines and packaging change, so check each vendor's current offering. They trade licence cost for faster setup and legal-specific features.
| Factor | Microsoft 365 build | Dedicated intake or matter platform |
|---|---|---|
| Software cost | Often already licensed; premium Power Platform licences may add a modest per-user monthly cost where needed | Typically tens of thousands of dollars a year for mid-sized departments; enterprise matter platforms often far higher |
| Build and setup | Internal IT or a Microsoft partner; often several weeks to a few months of effort | Vendor-led configuration; often a few weeks to a couple of months, sometimes with a one-off implementation fee |
| Ongoing maintenance | Falls on your team or IT; at risk if the builder leaves | Mostly vendor-managed; you maintain rules and templates |
| Legal-specific features | Little out of the box: matter numbering, conflict checks and spend linkage must be built | Matter records, templates, outside counsel and spend links, prebuilt reports |
| Data residency | Follows your Microsoft tenant region | Varies by vendor; confirm hosting regions (EU, UK, Australia, Middle East, India) before shortlisting |
| Best fit | Smaller teams, or departments with strong internal Power Platform skills | Teams that need matter and spend data together, or that lack internal build capacity |
These are indicative 2026 market ranges, and they vary considerably by contract, user count and region. Confirm current pricing with vendors and your Microsoft reseller.
Our view: for most departments of 10 to 30 lawyers that also manage outside counsel spend, a dedicated platform is the better fit. Intake data becomes much more useful once it's linked to matters, invoices and outside firms, and rebuilding that in SharePoint usually takes longer than expected. For smaller teams, or where IT already supports Power Platform well, a Microsoft 365 build is a sensible first year. Either way, ask vendors for a data export in a standard format at contract end, and test it during the trial.
Steps seven and eight: pilot with one business unit, then close the side doors
Step seven: run a four-to-six-week pilot
Choose one business unit that sends a lot of work and gets along well with legal. Sales operations and procurement are common choices. Track form completion time, misrouted requests and the most common free-text answers in "general legal question." Expect to revise the form at least twice. If requesters regularly attach documents the form didn't ask for, add the field. If a question is always left blank, remove it.
Step eight: make the front door the only door
The technology rarely fails. Enforcement does. Three moves matter most:
- Visible GC sponsorship: a short note from the general counsel to business leaders saying requests outside the channel won't be tracked against service levels.
- Auto-replies on the shared legal mailbox pointing to the form, plus a one-line reply script lawyers use when a request arrives by email or chat.
- A narrow exception path: true emergencies such as a dawn raid or breach can go by phone, but someone logs them afterwards.
Check data protection before go-live. Intake forms collect personal data about employees, customers and counterparties. That can bring in regimes such as the EU and UK GDPR, India's Digital Personal Data Protection Act, Brazil's LGPD, Singapore's PDPA and the data protection laws of Gulf states such as the UAE and Saudi Arabia. Each has its own rules on cross-border transfers, retention and access rights. Set retention periods for closed requests and restrict access to employment and dispute matters.
Privilege needs the same care. Protection for in-house advice varies widely. In EU competition investigations, for example, it is generally narrower than in many common-law jurisdictions. Label intake records consistently, and don't assume a request database is protected everywhere you operate. Have privacy and litigation counsel in each key jurisdiction review the design before launch.
Step nine: the four metrics worth putting in front of the GC
Intake data supports dozens of charts. The GC needs four, reported monthly, with a quarterly version for business leadership:
- Request volume by business unit and type. This is the basis for headcount and budget discussions, and it shows which units generate work that could move to templates.
- Cycle time by request type, reported as the median and the 90th percentile. The median shows normal performance. The 90th percentile shows where requests stall, and that's where complaints come from.
- Service-level adherence by tier: the share of standard, priority and urgent requests closed within their target. If priority adherence falls while volume rises, you have a capacity problem. If it falls while volume stays flat, look at process.
- External referral rate: the share of matters sent to outside counsel, by type. Linked to spend data, this shows where recurring work could come in-house or go onto fixed-fee arrangements.
Don't report lawyer-level productivity from intake data in the first year. It discourages honest logging, and the numbers are too noisy to support conclusions about individuals.
Decision rule: if you can't yet name your top three request types and their monthly volumes, start step one on Monday with a spreadsheet and leave vendor demos for later. If you can, write your routing rules on one page and send it to two dedicated vendors and your Microsoft partner as the brief. Whichever option runs it with the fewest workarounds is your answer.
Common questions
How long does it take to launch a legal front door?
Most departments of 5 to 30 lawyers can go from demand inventory to a live pilot in roughly 8 to 12 weeks. Tool setup is usually the shortest part. Agreeing on request types, triage tiers and routing ownership takes longer, and it's sensible to allow another month or two before the channel is used consistently across the business.
Is Microsoft 365 good enough, or do we need dedicated matter intake software?
A Microsoft 365 build with Forms, Lists, Power Automate and Power BI works well for smaller teams or departments with strong internal Power Platform support. Dedicated matter intake software makes more sense when you need intake linked to matter records, outside counsel management and spend data, or when no one internally can maintain a custom build. Run your written routing rules through both options before deciding.
What does matter intake software typically cost?
As an indicative 2026 market range, dedicated intake and workflow tools for mid-sized departments often run from the low tens of thousands of dollars a year, while enterprise matter management platforms with intake modules can cost several times that. Pricing depends on user counts, modules, hosting region and contract length, and local pricing differs. Get written quotes from vendors.
How do we stop people emailing lawyers directly after launch?
Get the general counsel to state publicly that requests outside the channel won't be tracked against service levels. Back that up with mailbox auto-replies and a consistent one-line redirect from every lawyer. Keep a narrow phone path for true emergencies and log those requests afterwards so the data stays complete.
Written by the Casestack Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.