Most legal client intake forms grow the same way. Someone builds a short one. A case goes sideways because a detail was missed, so a field gets added. A paralegal gets tired of chasing the same follow up, so another field gets added. Two years later the form asks forty questions, nobody remembers why half of them are there, and the people most likely to abandon it are the ones in the worst shape.

The useful reframe is this. An intake form is a decision tool, not a filing cabinet. Its job at first contact is to answer one question: can this firm help this person, and who should touch it next. Everything that does not serve that question is costing you something, and the cost is invisible because you never meet the people who gave up halfway.

The form exists to make one decision, not to build a file

A good test for any field is to ask what would change if the answer came back differently. If a field cannot change the routing, the priority, or the decision to decline, it does not belong at first contact. It belongs in the second conversation, once the firm has decided the matter is worth having.

This sounds obvious and it is routinely violated, usually with the best intentions. Billing preferences, referral sources, detailed employment history, and document uploads all look harmless sitting in a form builder. Each one adds friction to a moment when the person filling it in may be in pain, may be on a phone in a hospital car park, and has almost certainly opened three other firms in other tabs.

The fields that actually decide viability

For a personal injury matter, a small set of facts does nearly all the work. They are worth stating plainly because they are the ones that determine whether the rest of the conversation is worth having.

The date of the incident. This drives the limitation analysis and it is the single most common field to be captured loosely. "A few months ago" is not a date. Ask for the actual day, and accept an approximate month only if the caller genuinely does not know.

What happened, in the caller's own words. An open text box, or on the phone, thirty seconds of not interrupting. Structured fields are efficient and they are also very good at hiding the fact that this was a commercial truck and not a sedan, or that the fall happened at work rather than in a shop. Let the person narrate before you start categorising.

Whether they sought treatment, and when. Not the diagnosis, not the provider list, not the bills. Whether they were seen, and roughly how soon after. A long unexplained gap between an incident and any treatment changes how a matter is assessed, and it is better known at minute one than at week three.

Who else was involved. Names matter here for two reasons. They are the input to a conflicts search, and they are the first indication of whether there is anyone to recover from.

The state where it happened. Not the caller's home address, which is a different question and frequently a different state. Jurisdiction determines deadlines, thresholds, and in some categories whether a claim exists at all.

Whether they have already spoken to another firm. This is uncomfortable to ask and it saves an enormous amount of wasted effort. A caller who has already signed a retainer elsewhere is a different conversation, and one that should be handled carefully rather than enthusiastically.

A reliable way to reach them again. Two channels if you can get them. The most expensive intake outcome is a viable matter attached to a phone number that never answers.

What to leave out, and why leaving it out is not laziness

Full social security numbers, dates of birth, insurance policy numbers, and document uploads are all things a firm will eventually need. None of them helps decide whether to take the matter. Collecting them at first contact means holding sensitive personal data about people you have not agreed to represent and may never speak to again, which is an obligation with no matching benefit.

Long medical histories fall into the same category. At first contact, whether someone was treated is decision relevant. Which orthopaedic surgeon they saw in 2019 is not, and asking for it produces either a blank field or an unreliable answer given from memory.

Detailed damages questions are worth singling out. Asking a caller to estimate what their claim is worth invites a number that will later be treated as an expectation. It is a field that creates a problem rather than capturing one.

The web form and the phone script are not the same instrument

The most common structural mistake is writing one set of questions and deploying it in both places. They fail differently, so they should be built differently.

A web form cannot ask a question it did not anticipate. It has no way to notice that an answer was strange, and no way to follow up. That makes conditional logic essential and brevity non negotiable: branch on matter type early, then ask only the fields that matter for that branch. A form that asks about vehicle damage after someone has selected a dog bite tells the person that nobody is really reading this.

A trained person on the phone has the opposite profile. They can hear hesitation, ask the question that was not on the list, and pick up that the caller is describing an employer's vehicle. That flexibility is the entire value of a live conversation, and a rigid script throws it away. The script should define what must be established, not the exact words used to establish it. This is the same distinction that separates a legal answering service from a generic one, covered in more depth in our guide to what law firms should expect from a legal answering service.

Both routes should arrive at the same conclusions. They should not use the same fields to get there.

Conditional logic beats a longer form

Matter type should be the first branch, and it should change what comes next. A motor vehicle matter needs questions about vehicles, insurance, and a police report. A premises matter needs questions about ownership, notice, and whether an incident report was made. A medical matter needs questions about providers and timing. Asking all of them of everyone is how a form reaches forty fields.

Done properly, conditional logic makes the form feel shorter while capturing more of what matters, because every question a given person sees is relevant to the thing they just described. Our personal injury intake checklist breaks down what belongs in each branch.

Consent and contact language belongs on the form, not in an afterthought

Whatever your firm's position on contacting people who submit a web form, that position needs to be reflected in the form itself, in language the person can actually see before they submit. Consent captured vaguely is worth very little later, and consent captured after the fact is worth nothing.

This is genuinely a compliance question rather than a design preference, and the rules differ depending on how you intend to follow up. Our overview of TCPA compliance in legal intake covers what to think about before you write that line, and it is worth having someone qualified review the wording rather than copying a competitor's.

Conflicts screening starts at the form

A conflicts check runs against names. If the intake form does not capture the names of other parties, the search cannot happen until someone goes back and asks, which is usually after the firm has already given some form of preliminary view.

Capturing adverse party names at first contact is a small change that moves the check to the point where a conflict is still easy to handle. It costs one field.

The form's real output is a handoff

A completed intake form that sits in an inbox has not accomplished anything. The question that matters is what lands in front of the person who acts next, in what format, and how quickly.

That means deciding, before the form goes live, which system receives the data, which fields map to which records, and what the attorney or case manager actually sees first. A form that produces a wall of undifferentiated text has moved the sorting problem rather than solved it. We go deeper on this in our piece on the intake handoff to the attorney.

Common failure modes worth checking for

Required fields that are not actually required. Marking a field mandatory because it would be nice to have is how forms get abandoned. If someone can be helped without it, it is optional.

Free text where a date belongs. Dates entered as prose are unusable for any deadline logic and have to be re-asked.

No path for the caller who does not fit. Every form should handle the person whose matter is not on your list. Sending them into a dead end is both a poor experience and a lost referral opportunity.

Mobile that was never tested on mobile. A large share of first contact happens on a phone, often one handed. A form that works on a laptop and not on a phone is a form that works for the wrong half of your callers.

No record of who abandoned. Partial submissions are the most actionable data an intake form produces, and most firms discard them. Knowing which field people quit on tells you exactly what to cut.

How to shorten a form you have already built

Take the existing form and, field by field, ask what decision the answer changes. Move everything that fails that test into a second stage. Then look at what is left and ask which of those could be inferred rather than asked, since a state can often be derived from a location already captured.

Run the shortened version alongside the old one if you can, and compare completions rather than opinions. The argument for a field is almost always made by someone inside the firm, and the cost of it is paid by someone outside who never gets to make their case.

What good looks like

A legal client intake form is working when a person in a difficult moment can finish it without help, when the output tells whoever picks it up what they need to know without a second call, and when a matter that should be declined can be declined quickly and kindly.

None of that requires a long form. Most of it requires being ruthless about which questions have earned their place, and being clear that the goal at first contact is a decision, not a complete file. Firms looking at how the rest of the process fits together may find our guide to qualifying personal injury leads a useful next read.

Common questions