Legal Intake Forms
How to design intake forms that collect useful information without creating friction for the requester.
An intake form is the first real interaction between the business and legal. Ask for too little, and the request arrives incomplete — the lawyer has to follow up, wait, and lose time before work can even begin. Ask for too much, and requesters abandon the form, route around it, or fill it out carelessly just to get through it.
Good intake form design isn't about collecting more information. It's about collecting the right information, from the right requester, with the least possible friction.
Why One Generic Form Doesn't Work
Most legal departments start with a single intake form meant to cover every type of request. It rarely works well for any of them.
An NDA request and a commercial contract negotiation don't need the same fields. A privacy review and an employment question don't share the same context requirements. A single generic form either asks everyone the same long list of questions — creating friction for simple requests — or asks too few questions to be useful for complex ones.
The core issue
The problem isn't that intake forms ask for information. The problem is that one form asking the same questions for every request type can't serve simple and complex requests well at the same time.
What Well-Designed Legal Intake Forms Do
Adapt to Request Type
The form asks different questions depending on what's being requested, rather than applying the same fields to an NDA and a litigation hold.
Use Conditional Logic
A question only appears if it's relevant. Selecting "contract request" reveals contract-specific fields; selecting "privacy question" reveals different ones.
Capture Just Enough to Triage
The form collects what's needed to categorize, assess urgency, and route the request — not every detail a lawyer might eventually want.
Reduce Requester Effort
Fields are clear, minimal, and easy to complete without legal expertise, so the business doesn't need to know legal terminology to submit a request.
Building a Form by Request Type
Tailoring forms by request type doesn't mean building dozens of unique forms from scratch. Most departments can cover their volume with a handful of templates.
Identify your highest-volume request types
Start with the categories that make up most of what legal actually receives — often contracts, NDAs, and routine compliance questions.
Define the minimum information needed to triage each type
What does a reviewer need to know to assess urgency, risk, and ownership — not everything that might eventually be useful.
Add conditional fields for complexity
Build in follow-up questions that only appear when a request has risk indicators, high contract value, or other complicating factors.
Test the form with actual requesters
A form legal thinks is simple can still be confusing to someone outside the department. Watch someone who isn't a lawyer fill it out.
Revisit as request patterns change
New request types emerge, and fields that once mattered stop being useful. Forms need periodic review, not a one-time build.
Comparing Approaches to Legal Intake Forms
| Capability | Single Generic Form | Request-Type-Specific Forms |
|---|---|---|
| Fields relevant to the request | No | Yes |
| Conditional logic by request type | No | Yes |
| Complete information on first submission | Limited | Yes |
| Low friction for simple requests | No | Yes |
| Sufficient depth for complex requests | No | Yes |
Looking for intake forms that adapt automatically?
mot-r Q uses configurable, branching questionnaires that ask different questions depending on the type of legal request being made — routing requesters to the right fields without a lawyer having to design a separate form for every scenario.
Common Mistakes in Legal Intake Form Design
Asking Legal Questions in Business Language
Requesters aren't lawyers. A field asking for "governing law preference" will confuse someone who just needs a standard NDA reviewed.
Making Every Field Required
Marking optional context as mandatory forces requesters to guess at answers just to submit the form, producing inaccurate information.
Never Revisiting the Form
A form built once and never updated accumulates fields nobody uses anymore, while missing questions the department now actually needs.
Frequently Asked Questions
How many intake forms does a legal department actually need?
Most departments can cover the majority of their volume with a handful of templates built around their highest-frequency request types, supplemented by conditional fields for complexity rather than entirely separate forms for every scenario.
Should intake forms be built by legal or by IT?
Legal Ops is best positioned to design intake forms, since form logic needs to change as request patterns and risk criteria evolve — waiting on IT for every adjustment slows the form down as much as no form at all.
How much information should an intake form collect?
Enough to categorize, assess urgency, and route the request — not every detail a lawyer might eventually want. Additional information can be gathered after triage, once the right person owns the request.
How does mot-r support legal intake form design?
mot-r Q uses configurable, branching questionnaires that adapt the questions asked based on request type, so requesters only see fields relevant to what they're actually submitting.
Well-designed intake forms are what make triage and routing possible in the first place. Return to the Legal Intake Resource Center for the full guide.
Ready to modernize your legal intake?
Whether you're exploring legal intake software, redesigning your legal front door, or simply looking for a better way to manage legal requests, we'd be happy to learn about your current process and discuss how mot-r can help.