Legal intake mistakes are the design and process errors that stop requests from reaching legal complete, correctly routed, and visible to the person who asked. Most departments make the same five: scattered request channels, forms that ask too much or too little, legal categories that requesters cannot choose correctly, missing deadline and risk data, and no status once a request is submitted. Each one creates rework. Together they push business users back to email, and the front door you built stops being the front door.
What are the most common legal intake mistakes?
The most common legal intake mistakes are letting requests bypass the central channel, designing forms around legal’s taxonomy, asking requesters to classify their own work, routing without priority data, and leaving requesters without status. Each shows up in your data as a specific symptom: follow-up questions, reassignments, duplicate submissions, or requests that never reach the system at all.
The good news is that every one of them is fixable in configuration and process, usually within one or two release cycles. They are worth fixing, since a 2025 survey of in-house legal teams found 58 percent lose time to repetitive, low-value tasks. The fixes below come from delivery practice across corporate legal departments, and most depend on a clear definition of what a legal front door is and why adoption so often fails.
Mistake 1: Why do scattered request channels break legal intake?
Scattered request channels break legal intake because work that arrives by email, chat, desk visits, or personal inboxes never gets a record, an owner, or a place in your reports. Shadow intake is the most expensive mistake, since it hides demand from every metric you track.
- Lost and duplicated work. A request sent to two lawyers by email may be answered twice or not at all, and nobody can see which.
- Unreliable workload data. If a third of requests bypass the portal, your volume and turnaround figures describe two thirds of reality.
- Redirect every channel. Keep familiar channels open, and route them into the front door. Shared mailboxes can create requests automatically, and lawyers can reply to direct emails with a link to the form.
Set a target of 90 to 100 percent of requests entering through the approved channel, and report the figure monthly by business unit so gaps are visible.
Mistake 2: How long should a legal intake form be?
A legal intake form should be short enough to capture only what legal needs to classify, prioritize, and route the work, usually six to eight core fields at first contact. Anything more should appear through conditional logic, only when the request type needs it.
Long forms lose people. General form guidance puts the point where form abandonment rises sharply at around 10 to 12 fields, and an enterprise legal form should treat that as a warning sign. Too short is just as costly, because every missing fact becomes a follow-up email.
The core fields are the requester and department, the request type in plain language, a description, the counterparty or subject involved, the business deadline with its reason, and attachments. Jurisdiction, legal entity, estimated value, or risk questions then appear only for the request types that need them.
Measure the share of requests needing follow-up solely for missing information, with a target below 10 percent. Enterprise intake forms work best with conditional sections built for each request type.
Mistake 3: Why shouldn’t requesters choose legal categories on an intake form?
Requesters shouldn’t choose legal categories because business users describe their need in business terms, and a list of legal subtypes, practice areas, or billing codes guarantees misclassification. A wrong category sends the request to the wrong queue, triggers reassignment, and distorts your reporting.
Let requesters pick from five to eight business-language options, and map each one to legal’s internal taxonomy behind the form.
- “I need a contract reviewed.” Maps to commercial contracts, then to the vendor, customer, or partner team.
- “I received a legal notice.” Maps to disputes and routes urgently to the claims or legal hold workflow.
- “I have an employee issue.” Maps to employment, then to HR support or employment counsel.
Legal can refine the classification after triage. Track first-routing accuracy, with a target of 90 to 95 percent reaching the right queue on first assignment.
Mistake 4: What deadline and risk data does legal intake routing need?
Legal intake routing needs the business deadline, the reason for any urgency, and a simple measure of value or business impact on every request. Without that data, legal cannot prioritize consistently, and every requester marks their work urgent.
- Deadline with a reason. Asking why a date matters separates a real board deadline from a preference, and it cuts inflated urgency quickly.
- Value or impact. A simple band, such as under $50,000, $50,000 to $500,000, or above, gives triage a consistent signal without asking requesters for a precise figure.
- Escalation rules. Route on risk, urgency, monetary value, legal entity, and jurisdiction, so a regulatory notice or a high-value deal reaches a senior lawyer the same day.
Target 100 percent of requests carrying priority data, and review high-risk requests against a triage window of one business day. A risk matrix for legal request prioritization turns these fields into consistent decisions.
Mistake 5: Why does missing status cause duplicate legal requests?
Missing status causes duplicate legal requests because a requester who cannot see progress assumes the first request was lost and submits it again, or emails a lawyer directly. Every duplicate wastes triage time and splits the conversation across two records.
- Visible status. Show the queue or owner, the next action, and the expected timeframe on every request, in plain language.
- Instant confirmation. Send an immediate confirmation with the request ID as soon as the form is submitted.
- Duplicate warnings. Show requesters their open requests, and warn when a new submission looks like an existing one.
Aim for duplicates below 3 to 5 percent of volume, and 100 percent of requests with requester-visible status.
Where does self-service fit in a legal intake process?
Self-service fits in a legal intake process for approved, low-risk, repeatable work, and it goes wrong when that boundary is left vague. Done well, it removes routine demand from lawyers’ queues without letting risky work slip past review.
- Good candidates. Standard NDAs on approved terms, approved procurement templates, basic policy questions, and routine signature or entity requests.
- Always triaged. High-value contracts, material deviations, litigation threats, regulatory notices, employment complaints, personal data questions, and new jurisdictions.
- Eligibility check. Build the test into the form, so an NDA request with nonstandard terms moves to counsel automatically.
Self-service legal portals drive adoption when the easy path is also the correct one.
Who should govern legal intake data and taxonomy?
Legal intake data and taxonomy should be governed by a named legal operations owner who controls request types, routing rules, and field mappings, with changes approved and tested before release. Without an owner, categories multiply, fields drift, and reports and automation break quietly.
Keep request types, business units, and legal entities in managed lists, and retire old values with a mapping so historical reports still work. Log every form or routing change with the requester, approver, and test result, and release changes on a set cadence, often monthly.
Watch the rate of requests filed under “other” or reclassified at triage. When it climbs above roughly 10 percent, the taxonomy no longer matches how the business asks for help, and it is time for a review with the triage team.
How do you measure whether legal intake mistakes are fixed?
Legal intake mistakes are measured through a small set of intake metrics reviewed monthly, starting with a 30-day baseline before any change goes live. Each metric maps directly to one of the five mistakes, so a movement tells you which fix is working.
- Channel and completeness. Share of requests through the front door, share complete enough for triage (target 90 percent or higher), and initial form completion (target 70 percent or higher among those who start).
- Routing and duplicates. First-routing accuracy, reassignment rate, and duplicate rate.
- Response. First response within the agreed service level, with a target of 90 percent or higher.
Review your taxonomy and form quarterly, and test every change before release. The wider set of legal intake KPIs covers volume, turnaround, and satisfaction.
Conclusion
Legal intake mistakes are predictable, and so are the fixes. Put every channel through one front door, keep the first form short and conditional, let requesters speak in business terms, capture deadline and risk data on every request, and show status from submission to closure. Measure each fix against a baseline, and the data will show you where requests still stall.
How Basla can help
Basla provides delivery teams for legal intake and request management software implementation, covering legal technology consulting, intake form and taxonomy design, routing and escalation rules, self-service eligibility logic, status workflows, testing, documentation, and hypercare. Basla teams have built a legal service request implementation with eight front doors for language and country variations, so business users in each region complete forms in their own working context.
Frequently asked questions
What are the most common legal intake mistakes?
The most common legal intake mistakes are accepting requests through scattered channels, using forms that are too long or too short, asking requesters to choose legal categories, routing without deadline or risk data, and giving requesters no status after submission.
How many fields should a legal intake form have?
A legal intake form should usually start with six to eight core fields covering the requester, request type, description, subject, deadline, and attachments. Further questions should appear through conditional logic only when the request type needs them.
Why do business users bypass the legal intake portal?
Business users bypass the legal intake portal when the form is slow, the categories are confusing, or they cannot see progress after submitting. Emailing a lawyer directly then feels faster and more certain.
How do you reduce duplicate legal requests?
Duplicate legal requests are reduced by sending an immediate confirmation, showing requesters their open requests and status, and warning when a new submission resembles an existing one.
What legal requests are suitable for self-service?
Legal requests suitable for self-service are low-risk and repeatable, such as standard NDAs on approved terms, approved templates, and basic policy questions. High-value, nonstandard, regulatory, or dispute-related requests should always go to triage.
What metrics show whether legal intake is working?
Legal intake is working when most requests arrive through the front door, arrive complete, reach the right queue first time, rarely duplicate, and receive a first response within the agreed service level.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*