# Client Intake Form PDF: A Practical Guide for Law Firms August 31, 2026 ![CasePulse](https://secure.gravatar.com/avatar/c7f859ca85d743874d3c44940ffcad1d171ddda2e5213352070312ac88bb8cba?s=24&d=mm&r=g) CasePulse [General](https://casepulse.com/category/general/) A new personal injury lead calls after hours. By morning, the voicemail is buried, the prospective client has downloaded an intake PDF, and the returned attachment is missing the signature page. Another file includes a name and phone number but no adverse party, incident date, or insurance carrier. Your team can't run a meaningful conflict check, so the consultation moves forward on incomplete information. That pattern is familiar at firms that still treat intake as a document instead of a workflow. A **client intake form PDF** can be useful, but only when it's designed to capture the right information, completed accessibly, protected appropriately, and routed into the firm's working file. The document is only one part of the lifecycle: **design, capture, route, and reuse**. ## Why Intake Is the Real Bottleneck at Personal Injury Firms At a mid-sized plaintiff firm, intake rarely fails because nobody cares. It fails because responsibility is split across people and channels. Two intake coordinators may be triaging calls while a third person downloads voicemails, checks a shared inbox, and tries to assemble partially completed PDFs into a usable record. A scanned page may be blurred, a field may be left blank, and the attachment may contain no indication that anyone checked for conflicts. Every handoff creates another opportunity for delay. A caller gives facts by phone, staff copy some of them into an email, the prospect fills out a PDF later, and a paralegal retypes the information into the firm's internal workflow. When the form arrives, staff may have to ask the same questions again before an attorney can decide whether to pursue the matter. ![A funnel diagram illustrating the client intake process, showing lead drop-off from 100 inbound leads to 15 signed retainers.](https://casepulse.com/wp-content/uploads/2026/08/client-intake-form-pdf-intake-funnel.jpg) The funnel above is an editorial illustration, not a firm benchmark. Its point is operational: leads disappear at each stage when contact, qualification, conflict screening, and retention depend on disconnected steps. The **2024 legal industry report cited by MyCase** recorded **58,395 leads** captured through customized intake forms, with **10,286 becoming clients**, an **18% lead-to-client conversion rate**. Those figures make structured intake a useful revenue benchmark, not merely an administrative concern. See this practical discussion of [law firm lead conversion](https://www.recepta.ai/blog/law-firm-client-intake) for additional context on how intake affects the path from inquiry to signed representation. ### Where firms recover time The largest recovery often happens before a matter reaches the downstream case workflow. A form that collects the incident date, adverse parties, prior counsel, and insurance information in a consistent order lets staff screen the opportunity without reading every narrative response first. > **Practical rule:** Don't ask a paralegal to reconstruct the lead from an attachment when the form could have produced a clean intake record at submission. A useful PDF therefore needs more than attractive formatting. It needs a deliberate page-one sequence, clear field behavior, accessibility support, and a defined destination. If the finished form still lands in an unmanaged inbox, the firm has digitized the paper packet without solving the bottleneck. ## What a Client Intake Form PDF Has to Capture First Page one should help staff answer two questions quickly: **Who is this person, and can the firm safely evaluate the matter?** Put identity and contact information first, followed by the incident snapshot and conflict-screening fields. Detailed medical history and supporting documents can follow after the initial screen. Collect the full name, date of birth, address, phone, email, and preferred contact method. These fields support identity verification, follow-up communication, and conflict searches, as outlined in this [client intake form examples resource](https://casepulse.com/examples-of-intake-forms/). Then ask for the matter type, incident date, location, a short description of what happened, and the source of the referral. The conflict block should identify every adverse party, insurer, employer or other relevant organization, and any attorney who has represented the prospective client or another party. Ask about prior consultations with counsel, existing claims, and any known liens. A statute-of-limitations or filing-deadline field belongs near the top because a date buried deep in the form can delay triage. Group Fields Purpose Identity and contact Full name, date of birth, address, phone, email, preferred contact method Confirm identity and establish reliable communication Matter snapshot Matter type, incident date, location, short incident description Classify the lead and identify immediate timing concerns Conflict screening Adverse parties, employers, insurers, prior counsel, related claims Support an early conflict review Deadline risk Filing deadline information, notices received, pending hearings or appointments Flag matters requiring prompt attorney review Insurance Carrier, policy information, claim number, adjuster, contact details Organize early coverage follow-up Medical and damages Providers, treatment dates, injuries, prior related conditions, wage loss Give the team a structured starting point for evaluation Consent and representation Acknowledgment that submission doesn't create an attorney client relationship, consent and fee disclosures where applicable, signature Set expectations and document required acknowledgments The order matters. Run the conflict check using identifying and adverse-party data before asking the prospective client to spend time gathering extensive records. Overloading the first page with every possible case question increases friction and can delay the decision to accept, decline, or escalate the lead. ## Turning a Document Into a Fillable PDF Step by Step Start with the source document, not the PDF controls. Finalize the wording, headings, instructions, whitespace, required questions, and signature language in the blank document or Word file first. If the source is scanned, convert it to selectable text with OCR before adding fields. A scanned image may look complete but won't provide usable controls or reliable text for assistive technology. ### Build the controls in a fixed order 1. **Prepare the page.** Remove duplicate questions, align labels, and leave enough room for longer answers. Decide which fields are required and which can remain optional. 2. **Open the form tool.** In Adobe Acrobat, use the Prepare Form workflow to detect likely fields in an existing document or scanned form. Adobe documents this process as a way to create PDF forms, add fields such as name and email, and distribute the finished document for response collection through email or web workflows. 3. **Add the right control.** Use text fields for names and narratives, checkboxes for multiple applicable answers, dropdowns for controlled categories such as matter type, and date fields for the incident and contact dates. Don't use a free-text box where a controlled choice will improve consistency. 4. **Set field properties.** Give every field a descriptive name, a clear tooltip, an appropriate format, and a required status where necessary. Tooltip text should explain what belongs in the field, not repeat an internal database label. 5. **Create a logical tab order.** A keyboard user should move from identity to incident details, conflict information, insurance, medical providers, acknowledgments, and signature without jumping around the page. Validate the order against the visual flow, as federal accessibility guidance recommends. 6. **Configure signatures correctly.** Use a genuine signature field when the client must sign. A flat text box labeled “signature” doesn't provide the same functional control and can create confusion during review. 7. **Control editing.** Restrict document changes to form filling when distribution requires it. Keep an editable master separate from the client-facing copy. Flatten a document only when the next workflow requires a non-editable version, because flattening removes the interactive behavior that makes the form usable. ![Screenshot from https://example.com/screenshots/adobe-acrobat-edit-form-mode.png](https://casepulse.com/wp-content/uploads/2026/08/client-intake-form-pdf-form-filling.jpg) ### Save two controlled versions Keep a clean master with editable fields and a distribution copy with the intended permissions, metadata, and instructions. Test the distribution copy on a desktop and phone before sending it to a prospective client. Complete every field, save, close, reopen, and confirm that entered data remains present. If the PDF will route through a secure portal such as CasePulse rather than return by email, skip instructions that tell the client to attach the file to an email. The portal workflow should direct the user to complete or upload the form in the authenticated destination, while the firm preserves the original submission for the matter record. For firms evaluating broader form workflows, [legal document automation](https://casepulse.com/legal-document-automation/) can help frame how structured information should move beyond a static file. ## Building the Form So Anyone Can Actually Complete It Accessibility is a usability requirement before it becomes a compliance concern. A client who relies on a keyboard or screen reader must be able to understand each prompt, move through the fields, identify required information, correct errors, and complete the signature without a mouse. Set the PDF language to English, or the appropriate locale, in Document Properties. Add alternative text for meaningful logos, signature images, and graphics, while marking decorative elements appropriately. Labels and tooltips should match what the field asks for, and the tab sequence should follow the visual order rather than the order in which controls happened to be created. ![A five-step checklist illustrating best practices for creating an accessible PDF form for better usability.](https://casepulse.com/wp-content/uploads/2026/08/client-intake-form-pdf-accessible-checklist.jpg) ### Test the actual experience Run Acrobat's Accessibility Checker after the form is built. Look for missing tags, ambiguous tooltips, incorrect reading order, and insufficient contrast between field borders and the page. A successful automated check isn't the same as a successful client test, so complete the form with a keyboard and use a screen reader. Use plain language in every instruction. A field label should tell a person what to enter, such as “Date of the accident,” rather than an internal phrase such as “Loss date.” Mark required fields visibly and programmatically, and keep error messages specific enough that the user knows how to fix the problem. The verified accessibility guidance for PDF forms emphasizes **logical tab order, descriptive labels and tooltips, keyboard-only completion, and proper signature fields**. It also identifies scanned image PDFs, missing controls, and ill-ordered fields as practical barriers that can prevent assistive-technology users from completing intake. > A form that works only with a mouse isn't finished. It has only passed a visual inspection. Test the completed file with VoiceOver on iOS and NVDA on Windows before sending it to a client. Check the form on a phone as well as a desktop, because a small control, crowded page, or unclear error can turn a workable document into an abandoned intake. ## Emailing the PDF Versus Routing It Through a Secure Portal Email feels fast because staff already use it. The problem is that a completed attachment may contain a full name, address, phone number, employer, insurance details, medical information, and other sensitive case facts. Once the file reaches the prospect's inbox, the firm usually can't control whether it's forwarded, copied to another device, opened on a shared computer, or stored in a personal cloud account. A portal doesn't eliminate every risk, and CasePulse does not provide end-to-end encryption. The relevant comparison is whether the firm has a controlled workflow with authentication, encryption in transit and at rest, access records, and retention controls instead of relying on an attachment that travels through systems outside the firm's administration. Legal IT guidance recommends moving away from emailed PDFs and open web forms toward secure portals, encrypted forms, limited access windows, and deletion rules for unretained leads. Factor Email PDF Secure Portal Upload Delivery Familiar attachment sent through ordinary email Authenticated session or controlled access link Copies May be forwarded, downloaded, or backed up outside firm control Kept within a managed workflow, subject to platform controls Access visibility Often difficult to determine who opened or copied the file Can support access logging and user permissions Client friction Low at first, but download, completion, and re-upload create extra steps Requires portal access, authentication, or a secure link Retention Manual cleanup is easy to overlook Retention rules can be built into the process where supported Operational use Staff often retype or manually attach information Structured responses can be routed into the firm's workflow The tradeoff is real. Some prospects won't want to create a password or follow a magic link, and a small amount of additional onboarding friction can affect completion. The right choice depends on the sensitivity of the information, the firm's ability to monitor the process, and whether staff can respond quickly when a prospect gets stuck. Email deliverability also matters if the firm sends portal invitations or form instructions by email. A practical resource on [how to stop email from going to spam in Gmail](https://www.mailgenius.com/how-to-stop-email-from-going-to-spam-folder-in-gmail/) can help staff distinguish a delivery problem from a form usability problem. It won't solve the privacy issue, however. Improving delivery doesn't make an attachment controlled. ## Connecting the Intake Form to a Client Portal The handoff from a completed PDF to the working file determines whether the form saves time or creates another data-entry queue. The firm should treat the submission as structured information, not just as a flat attachment that someone must open and interpret. Start by defining the fields that matter downstream. In Acrobat Pro, use form field recognition to confirm the controls, then configure an export data action that writes values to a CSV or sends them through a webhook where the receiving workflow supports it. Preserve the original PDF as an auditable document, but don't make the original attachment the only usable representation of the data. ### Map fields before inviting clients Create an intake matter template in CasePulse and map each PDF field to the appropriate contact, matter, and document record. A new submission should be capable of creating or updating the contact, opening the matter under the correct practice area, attaching the original form, and notifying the assigned paralegal. The exact mapping should be tested with sample submissions before the portal becomes the default route. Conditional logic keeps routing practical. A personal injury selection can send the submission to the PI team, while a pre-suit motor vehicle claim can bypass a litigation workflow until an attorney accepts the matter. The form shouldn't ask every lead every question. Show the insurance, treatment, and records prompts that match the selected matter type, and route exceptions for human review. ![A person using a desktop computer to view a digital client dashboard interface with project progress stats.](https://casepulse.com/wp-content/uploads/2026/08/client-intake-form-pdf-client-dashboard.jpg) The practical value appears in the paralegal's next action. Instead of downloading an attachment, renaming it, opening a new contact, copying the incident date, searching for adverse parties, and sending internal notifications, the staff member reviews a routed submission and resolves exceptions. The same structured data can support conflict screening, deadline alerts, and preparation for the initial demand package, provided the firm has configured those destinations and review rules. ### Design the exception path Automation shouldn't hide uncertainty. Flag missing signatures, conflicting dates, duplicate contacts, unclear adverse parties, and incomplete insurance information for staff review. A clean handoff includes a visible status such as “needs clarification,” an assigned owner, and a client-facing request that identifies the missing item without exposing unnecessary internal notes. Firms comparing portal capabilities can review this guide to [client portal software](https://casepulse.com/best-client-portal-software/) as part of their evaluation. Integration directories such as the [Donely integrations list](https://donely.ai/integrations) can also help operations teams inventory how external tools connect, but the decisive test is whether the selected workflow preserves field meaning from submission through review. A properly routed intake can compress work that might otherwise occupy roughly a week into the point when the prospect submits the form. That outcome depends on configuration, not on the PDF alone. The field map, routing rules, notification logic, and exception queue all need an owner. ## Rolling Out Your Intake Form Without Slowing Down the Firm A rollout should protect active matters while giving staff a controlled way to test the new route. A one-week implementation works when each day has a narrow deliverable and the legacy process remains available during validation. ### A practical seven-day rollout 1. **Days one and two, finalize the form.** Review every field with intake staff, remove duplicate questions, confirm the conflict sequence, and decide which information belongs before the first consultation. Lock the page-one fields and map each destination field. 2. **Day three, build the parallel route.** Configure the portal intake path while allowing legacy PDFs to continue arriving. This gives staff a safe comparison period without forcing active leads into an untested process. 3. **Days four and five, train the people answering the phones.** Give the front desk and intake paralegals the same handoff script. Define what staff should do when a submission is incomplete, when a conflict check is unclear, or when a prospect can't access the portal. 4. **Day six, run a narrow soft launch.** Use two referring providers and one attorney team. Capture every failure point, including invitation delivery, mobile completion, signature behavior, duplicate contacts, and internal notifications. 5. **Day seven, correct the top issues.** Fix the three problems that create the most staff intervention, publish a one-page SOP, and make the portal the default route for new leads. Keep a documented exception process for prospects who need another option. Track operational signals rather than relying on impressions. Review conflict-check turnaround, the share of intakes completed before the first consultation, and portal adoption. The purpose isn't to create a dashboard for its own sake. These measures show whether the new form is helping staff make an earlier decision with cleaner information. > **Implementation standard:** A completed intake should arrive with the correct matter type, statute date, insurance carrier, adverse parties, and signature status already visible. The lifecycle is complete only when the information remains useful after intake. Demand letters, medical-record requests, referral follow-up, and attorney review should start from structured data instead of a recovered PDF. If staff still has to search an inbox and retype the same facts, the firm has improved the document but not the operation. --- CasePulse offers law firms a secure client portal where clients can complete fillable forms, share files, and communicate with the team from their devices while staff work within their existing workflow. Visit [CasePulse](https://www.casepulse.com) to evaluate a portal-based intake route for your personal injury firm and plan a practical rollout. #### Ready to see what the portal can do for your team? [Book a demo](https://calendly.com/casepulse/demo)