Law Firm Intake Forms: What to Ask Before a Consultation

A practical guide to deciding what a law firm website intake form should ask, what to collect later, and how form purpose, wording, privacy, accessibility, and testing affect routing and consultation preparation.

A law firm website form is often the first structured contact a prospective client makes with the firm. What the form asks, how it asks it, and what happens after submission all shape whether an inquiry becomes a consultation or disappears. This guide focuses specifically on form purpose, fields, wording, sequencing, privacy, accessibility, testing, and internal use. For the broader visitor journey from arrival to contact, see our Law Firm Website Conversion Guide. For the complete operational workflow from first contact through consultation attendance, see our Law Firm Intake Process Checklist.

What a Law Firm Intake Form Is Supposed to Do

An initial website form may help the firm identify the person, obtain reliable contact information, understand the general type of matter, identify a possible jurisdiction or service area, record preferred communication methods, identify language or accessibility needs, route the inquiry internally, determine the next administrative step, prepare for a conflict-screening handoff, and offer scheduling when appropriate.

The initial form generally should not attempt to reach a legal conclusion, predict case value, determine liability, guarantee eligibility, confirm representation, replace an attorney's evaluation, collect a complete case file, request every potentially relevant document, or treat every inquiry as a qualified matter. A general website form is a routing and preparation tool, not a case evaluation.

Contact Form, Intake Form, and Client Onboarding Form

Firms sometimes use one form for every stage, but the purposes differ. A general contact form captures basic reachability. A consultation request form signals interest in scheduling. A preliminary intake form collects enough detail to route and prepare. A conflict-screening form gathers the names and details the firm needs for its approved conflict process. A detailed matter questionnaire collects case-specific information after the firm has a reason to request it. A client-onboarding form formalizes information after the firm accepts the matter.

These are practical operational distinctions. They are not official definitions that apply identically in every jurisdiction or firm. The table below summarizes common form types and their purposes.

Decide What Happens After Someone Submits the Form

Before recommending questions, the firm should define where the submission is stored, who receives the notification, who owns the inquiry, who serves as backup, whether acknowledgment is automatic or manual, whether a conflict-screening step occurs before scheduling, whether consultation scheduling is offered immediately, how urgent submissions are handled, how language needs are routed, how duplicate submissions are handled, what happens if an integration fails, how the status is recorded, and when information is deleted or retained according to firm policy.

A well-written form does not solve an undefined intake process. If submissions land in an unmonitored inbox or no one owns follow-up, the form design matters less than the missing operational ownership. For a broader view of how Smartzilla connects website forms to follow-up workflows, visit our How It Works page.

Essential Questions for an Initial Law Firm Intake Form

Practical initial fields may include full name, phone number, email address, preferred contact method, general matter category, general location such as county, state, or jurisdiction, a short non-sensitive description, preferred language, an accessibility or communication accommodation request, general availability, how the person heard about the firm when useful, consent or communication preferences when applicable, and names needed for the firm's approved conflict-screening process when appropriate.

Not every field belongs on every form. Some fields may be required, some optional, some conditional, and some better collected later. Firms should evaluate whether each field has a documented operational use. A field with no clear owner, routing purpose, or downstream use may create friction and risk without adding value.

Questions That Depend on the Practice Area

Supplemental questions may vary by practice area. The examples below are high-level and administrative. They are not legal advice and should be reviewed by the firm under the rules and procedures applicable to it.

• Personal injury: general matter type, relevant location, whether an incident date is approaching, whether another attorney currently represents the person, preferred language.
• Immigration: general matter type, relevant location, whether a deadline or appointment is approaching, preferred language, whether immediate accessibility assistance is needed.
• Family law: general matter type, relevant jurisdiction, whether a hearing or appointment is approaching, whether another attorney currently represents the person, preferred language.
• Criminal defense: general matter type, relevant jurisdiction, whether a hearing or appointment is approaching, preferred language, whether immediate assistance is needed.
• Estate planning: general matter type, relevant jurisdiction, general relationship to the matter, preferred language, whether another attorney currently represents the person.
• Bankruptcy: general matter type, relevant jurisdiction, general relationship to the matter, preferred language, whether a deadline is approaching.

These examples should not be used to provide legal advice, determine eligibility, predict outcomes, ask the article reader to automatically reject matters, present legal deadlines, invent limitation periods, or recommend collecting extensive sensitive details through a general form. Practice-area questions should be reviewed by the firm under the rules and procedures applicable to it.

Information That May Be Better Collected Later

Some information may be better collected through an approved later-stage or secure process when genuinely needed. This may include medical records, financial records, tax documents, immigration documents, government identifiers, Social Security numbers, payment information, detailed criminal histories, full case files, photographs containing sensitive information, extensive privileged or confidential communications, information about children, detailed opposing-party information, and signed agreements.

This does not mean these items can never be collected electronically. The appropriate collection method depends on necessity, security controls, access, retention, and the firm's approved procedures. A general website form is rarely the right place for sensitive documents because the firm may not yet have a relationship, a conflict clearance, or appropriate secure storage in place.

Conflict-Screening Information and Internal Procedures

Conflict procedures should be established by the firm. An initial form may collect names required for the firm's process. Intake staff should know when to pause and escalate. Access to conflict information should be limited appropriately. Spelling variations and incomplete names can create matching problems. Software can organize and search information, but software does not replace the professional judgment required by the firm. Requirements and procedures may vary by jurisdiction and matter.

Do not provide a universal conflict-check method, and do not suggest that AI can independently clear a conflict. Conflict screening should follow the firm's own approved procedures, preferably with guidance from qualified ethics counsel.

How to Ask Questions Without Providing Legal Advice

Question wording can use plain language, avoid legal conclusions, avoid suggesting the matter has been accepted, avoid asking the person to prove the case in a small text box, explain why sensitive information should not be submitted, clarify which fields are required, explain what happens next, provide an alternative contact method when appropriate, avoid implying guaranteed confidentiality, security, or representation, and avoid promising a response time the firm cannot consistently meet.

Three short examples follow. These are operational wording samples, not legal advice, and should be reviewed by the firm's responsible attorney for the jurisdiction and circumstances.

"Please briefly describe the general type of legal matter and your location. Do not include sensitive details, documents, or confidential information in this field.

"Please do not submit Social Security numbers, medical records, financial records, or case documents through this form. If we need additional information, we will provide instructions through an approved method.

"Thank you for contacting us. We have received your inquiry and will review it during normal business hours. Submitting this form does not create an attorney-client relationship and does not guarantee that the firm will represent you. If this is an emergency, please contact appropriate emergency services.

Intake Form Disclaimers and Expectations

Intake-form language may appropriately clarify that submission does not necessarily mean the firm has accepted the matter, that the person should not assume representation has begun, that the firm may need to complete additional review, that the person should avoid sending sensitive information unless instructed through an approved method, that electronic communications can have limitations, that the person should seek immediate assistance through appropriate channels in an emergency, and that communication consent and opt-out terms should be reviewed when email or text follow-up is used.

Avoid saying that a disclaimer always prevents duties from arising. The legal effect of communications may depend on the jurisdiction, circumstances, communications, conduct, and the prospective client's reasonable understanding. The American Bar Association's Model Rule 1.18 discusses duties to prospective clients. ABA Model Rules are models, and adoption or modification varies by jurisdiction.

Privacy, Confidentiality, and Data Minimization

Privacy practices worth reviewing include collecting only information with a defined use, limiting staff access, managing user permissions, securing transmission and storage, reviewing vendor access, defining data retention, planning data deletion, maintaining audit logs, controlling exports and downloads, limiting email notification contents, understanding SMS limitations, securing devices, removing former-employee access, reviewing integration access, preparing incident-response procedures, publishing privacy notices, and following applicable jurisdictional requirements.

Accessibility and Mobile Usability

Practical accessibility considerations include visible labels, instructions that do not rely only on placeholders, keyboard navigation, logical focus order, clear error messages, sufficient contrast, large enough controls, screen-reader compatibility, descriptive button text, mobile-friendly field sizes, avoiding horizontal scrolling, avoiding unnecessarily long dropdowns, saving progress when appropriate, clear required-field indicators, alternatives for people who cannot use the form, and testing with real devices and assistive technologies when possible.

The W3C Web Accessibility Initiative provides official guidance on accessible forms, including labels, instructions, and error handling. Following a short checklist does not guarantee ADA compliance or full accessibility, but official WAI guidance is a reliable starting point for factual accessibility claims.

Conditional Logic and Multi-Step Forms

Conditional logic and multi-step forms may offer advantages such as showing only relevant questions, breaking a long form into understandable stages, reducing visual overload, routing practice-area questions, and collecting details progressively. They also carry limitations such as hidden logic errors, inaccessible transitions, lost progress, unclear step counts, mobile problems, incorrect routing, integration failures, and difficulty returning to an earlier answer.

Do not assume multi-step forms always outperform single-page forms. Test both the user experience and the resulting internal record. A form that feels smoother can still produce incomplete or misrouted data if the logic is wrong.

Connecting the Form to the Firm's Intake Workflow

The form may connect to an intake inbox, a CRM or intake system, a responsible team member, backup notification, a conflict-screening handoff, a consultation calendar, task creation, an approved acknowledgment, status tracking, source attribution, reporting, and closure or follow-up procedures. The form should not silently create a record nobody monitors.

For guidance on how law firms can build a connected visibility and intake system, review our full service overview. A form that routes correctly into a monitored workflow is more valuable than a polished form that feeds an empty inbox.

Using Automation and AI Carefully

Appropriate automation uses may include confirming receipt using approved language, creating a contact or inquiry record, assigning ownership, creating an internal task, applying a matter-category tag, routing by language or location, detecting missing fields, sending an approved scheduling link when permitted, flagging a submission for human review, and recording the inquiry source.

Automation has limitations. Free-form text can be misunderstood, records can be duplicated, notifications can fail, integrations can disconnect, contact details can be incorrect, AI-generated summaries may omit or distort information, automated messages can imply more than intended, urgent matters can be misclassified, and software should not reach legal conclusions. Automation should support an approved process and appropriate human or attorney review.

Testing the Complete Submission Experience

A practical testing process should cover desktop submission, mobile submission, keyboard-only navigation, required-field errors, invalid phone or email entries, conditional logic, long names, accented characters, preferred-language selections, file uploads if used, the confirmation page, confirmation email or text, internal notification, CRM record creation, source attribution, duplicate submissions, calendar connection, backup owner, failed integration, spam handling, and data visibility and staff permissions.

Recommend periodic testing and testing after meaningful website, form, CRM, calendar, or automation changes. Do not prescribe a universal testing frequency. The right cadence depends on how often the firm changes its systems and how much risk a silent failure would create.

Common Law Firm Intake Form Mistakes

• Using one form for every stage instead of separating contact, intake, conflict, and onboarding purposes
• Asking for too much information immediately, before the firm has a reason to request it
• Collecting information with no operational use or documented owner
• Requesting sensitive documents through a general website form
• Relying only on placeholder text instead of visible labels
• Having unclear required fields or inconsistent required indicators
• Using vague submit buttons such as a single word with no context
• Providing no explanation of what happens after submission
• Promising an unrealistic response time the staff cannot consistently meet
• Suggesting the matter has already qualified or been accepted
• Treating a disclaimer as complete protection against all prospective-client duties
• Sending submissions to an unmonitored inbox
• Giving every employee access to all submission data
• Leaving former staff access active after their role changes or ends
• Broken conditional logic that hides required questions or misroutes inquiries
• Broken calendar connections that cause missed or double-booked consultations
• Automatic legal conclusions generated by software without attorney review
• Untested AI-generated responses sent to prospective clients
• No mobile testing of the form on real devices
• No accessible alternative for people who cannot use the form
• Measuring submissions without tracking downstream consultation and retention outcomes

Smartzilla's Staged Intake Form Framework

The following table is an original Smartzilla practical framework for organizing form-based intake in stages. It is not an official State Bar process, a legal standard, a universal workflow, a security standard, an accessibility standard, a software requirement, or a guarantee of consultations or retained clients.

Smartzilla's 20-Point Intake Form Checklist

This is an original Smartzilla practical framework, not an official legal, ethical, privacy, security, accessibility, or platform standard. Use it to identify where an intake form may have gaps.

• 1. Form purpose documented: Confirm whether the form is for contact, consultation request, preliminary intake, or another purpose.
• 2. Next operational step defined: Document what happens immediately after submission.
• 3. Primary owner assigned: Confirm a specific person owns submissions from this form.
• 4. Backup owner assigned: Confirm a backup is available when the primary owner is unavailable.
• 5. Required fields justified: Evaluate whether each required field has a documented operational use.
• 6. Optional fields clearly identified: Mark optional fields so visitors understand what is truly required.
• 7. Sensitive-data requests minimized: Remove unnecessary requests for medical, financial, or privileged information.
• 8. Conflict-screening handoff documented: Confirm the process for routing submissions to conflict screening.
• 9. Question wording reviewed: Ensure prompts avoid legal conclusions and do not imply acceptance.
• 10. Disclaimers reviewed: Verify disclaimers set expectations without making overly broad legal promises.
• 11. Communication consent reviewed: Confirm consent and opt-out language for email or text follow-up.
• 12. Mobile experience tested: Test the form on real mobile devices, not just a resized desktop view.
• 13. Keyboard navigation tested: Confirm the form is usable without a mouse.
• 14. Error messages tested: Verify required-field and invalid-format errors are clear and accessible.
• 15. Conditional logic tested: Confirm branching shows and hides the correct fields.
• 16. Confirmation message reviewed: Verify the post-submission message is accurate and does not imply representation.
• 17. Internal notification tested: Confirm the right people receive and act on submissions.
• 18. CRM or intake record verified: Confirm submissions create a complete, correctly routed record.
• 19. Staff permissions reviewed: Confirm access is limited to those who need it, including former staff.
• 20. Complete submission journey tested: Walk through the full path from form to internal follow-up.

Frequently Asked Questions

What is a law firm intake form?

A law firm intake form is a structured website form used to collect information from a prospective client so the firm can route, acknowledge, and prepare for the inquiry. It is an operational tool, not a legal evaluation or a confirmation of representation. Its purpose is to help the firm determine the next administrative step.

What questions should a law firm intake form ask?

An initial form may ask for full name, phone, email, preferred contact method, general matter category, general location, a short non-sensitive description, preferred language, accessibility needs, and availability. It may also collect names needed for the firm's approved conflict process. The right questions depend on the practice area, jurisdiction, staffing, and approved firm procedures.

How many questions should an intake form contain?

There is no universal ideal field count. The right number depends on what the firm needs to route and prepare the inquiry. Each field should have a documented operational use. Firms should test different lengths against their own baseline rather than following a generic rule that shorter or longer forms always perform better.

Should every field be required?

Not necessarily. Some fields, such as name and a reliable contact method, are typically required. Others, such as how the person heard about the firm, may be optional. Required fields should be justified by a clear operational use, and optional fields should be marked so visitors understand what is truly needed.

Should a law firm ask for case details through its website?

A general website form may collect a short, non-sensitive description to help with routing. It generally should not request extensive case details, documents, or sensitive information. Detailed matter information is usually better collected through an approved secure process after the firm has a reason to request it.

Can a law firm collect documents through an intake form?

It can, but document collection should use an approved secure method and should generally occur after the firm has a reason to request the documents. A general website form is rarely the right place for sensitive files because the firm may not yet have a relationship, a conflict clearance, or appropriate storage in place.

Does submitting an intake form create an attorney-client relationship?

Not automatically. Completing an intake form or contacting a law firm does not, by itself, necessarily establish an attorney-client relationship or mean that the firm has accepted the matter. However, the legal effect of communications can depend on the jurisdiction, the circumstances, the parties' communications and conduct, and the prospective client's reasonable understanding.

A written engagement agreement is commonly used to document the scope and terms of representation, but it should not be described as the only way an attorney-client relationship could arise. A person may also qualify as a prospective client, and the firm may have certain duties regarding information received, even when no attorney-client relationship follows. The American Bar Association's Model Rule 1.18 discusses duties to prospective clients, although each jurisdiction may adopt or modify its own rules.

Law firms should use carefully reviewed intake disclaimers, avoid providing legal advice or suggesting that representation has begun during automated intake, and have their intake language and procedures reviewed under the rules applicable to their jurisdiction. This article provides general operational information, not legal advice.

Should a law firm include a disclaimer?

A carefully reviewed disclaimer may help set expectations by clarifying that submission does not confirm representation, that the firm may need to complete additional review, and that sensitive information should not be sent through the form. A disclaimer should not be treated as a guarantee that no prospective-client duties can ever arise. Disclaimer language should be reviewed under the rules applicable to the firm's jurisdiction.

Can AI review or qualify intake-form submissions?

AI and automation may help route inquiries, detect missing fields, tag matter categories, and flag submissions for human review. Software should not independently determine case merit, liability, eligibility, or likely outcomes. AI should not provide legal conclusions. Administrative routing is not a legal determination, and attorney review may be required before accepting or declining a matter.

Should an intake form connect directly to consultation scheduling?

It depends on the firm's practice area and procedures. Some firms offer a scheduling link after basic qualification. Others require conflict screening or attorney review before scheduling. Do not state that every firm should connect a form directly to attorney-calendar booking. The right approach depends on how the firm evaluates inquiries and what the intake team can support.

What is the difference between an intake form and client onboarding?

An intake form collects information to route and prepare an inquiry before the firm decides whether to accept the matter. Client onboarding happens after the firm accepts the matter and the client signs an engagement agreement, and it may include collecting detailed information, setting up the matter in the case-management system, and beginning substantive legal work. Intake comes first, onboarding comes later.

How should a law firm test its intake form?

Test the complete submission journey on desktop and mobile, including keyboard navigation, required-field errors, invalid formats, conditional logic, long names, accented characters, confirmation messages, internal notifications, CRM record creation, source attribution, duplicate handling, and staff permissions. Test after meaningful website, form, CRM, calendar, or automation changes, and on a regular schedule appropriate to the firm.

Create a Clearer First Step for Prospective Clients

Smartzilla helps law firms connect their website forms, intake workflows, consultation scheduling, and visibility data into a more organized system. See where prospective clients may be encountering friction and which improvements deserve priority.