Law firm client intake and matter-opening checklist
Coordinate a prospective-client inquiry through firm-controlled conflict review, engagement approval, matter opening, minimum access, and a documented closeout without turning the task board into the client file.
The public downloads are plaintext. After import, readable project content is encrypted on your device, while operational metadata remains visible to the service.
Reuse is governed by the Public Template license.
Already use SealTask? Open this template in SealTask.
⚖️
Complete template · v1
Law firm client intake
Sections
5
Tasks
14
Schedule anchor
Target matter-opening date
Coordinate a prospective-client inquiry through conflicts, engagement approval, matter opening, and accepted or declined closeout.
Target matter-opening date: The date an accepted matter should be operationally ready; review and engagement gates are scheduled before it.
01
Inquiry
Establish a neutral intake record, ownership, response timing, and minimum inputs.
Immediately route potential deadline or emergency issues
On receipt, if an inquiry may involve an urgent deadline or emergency issue, use the firm’s approved immediate intake procedure and do not wait for the target matter-opening date or this task board.
Urgent priority
□ Firm-authorized immediate-response owner is alerted
□ Required status is recorded in the approved intake system
Create a neutral intake reference
Create the authoritative inquiry in the approved intake system and use only its neutral reference for operational coordination here.
High priority7 days before target matter-opening date
□ Authoritative intake record is created
□ Operational checklist uses a neutral reference
Assign the intake owner and response target
Name the coordinator accountable for routing the inquiry and set the next-response deadline under the firm’s service expectations.
Medium priority7 days before target matter-opening date
□ Intake owner has accepted the handoff
□ Next-response target is recorded
Confirm minimum intake inputs in the source system
Verify that the approved system contains only the information required to route conflict review and the initial fit decision.
High priority6 days before target matter-opening date
□ Required routing inputs are present
□ Unnecessary sensitive detail is not requested
02
Conflicts
Route the inquiry through the firm-authorized conflict search and decision path.
Submit the authorized conflict search
Route approved names and relationships through the firm’s conflict system without copying search terms or results into this checklist.
High priority6 days before target matter-opening date
□ Search scope follows the firm-approved process
□ Search is recorded in the authoritative conflict system
Route any conflict escalation to the decision owner
If the authorized search identifies an issue, assign it to the designated lawyer or committee and pause downstream opening work.
High priority5 days before target matter-opening date
□ Authorized conflict decision owner is named
□ Opening work remains paused until a decision exists
Record the conflict gate outcome
Confirm only that the authoritative conflict process produced an outcome and that any conditions have accountable owners elsewhere.
High priority4 days before target matter-opening date
□ Outcome is preserved in the authoritative system
□ Any approval conditions have accountable owners
03
Engagement decision
Confirm fit, capacity, terms, approvals, and the authoritative acceptance decision.
Confirm fit, capacity, and jurisdiction review
Route the prospective matter to the responsible lawyer for the firm-specific fit, capacity, and jurisdiction decision.
High priority4 days before target matter-opening date
□ Responsible lawyer records the authoritative decision
□ Fit, capacity, and jurisdiction outcome is recorded
Approve engagement terms and commercial setup
Coordinate the firm-authorized scope, rates, billing arrangement, required approvals, and engagement-document owner in source systems.
High priority3 days before target matter-opening date
□ Terms have the required authoritative approvals
□ Engagement-document owner is named
Confirm signed terms and formal acceptance
Verify in the document and billing systems that required terms, signatures, deposits, or other firm conditions are complete.
High priority1 day before target matter-opening date
□ Required signed record is complete
□ Formal acceptance is authorized under firm policy
04
Open or close
Open an accepted matter with minimum access or complete the approved decline path.
Create the authoritative matter record
Open the accepted matter in the practice-management and document systems with the approved identifiers, ownership, and classifications.
High priorityOn target matter-opening date
□ Official matter record and identifier exist
□ Responsible lawyer and operational owner are recorded
Provision minimum matter access
Grant only the access required for assigned work and confirm that ethical walls or other firm restrictions are applied by authorized owners.
High priorityOn target matter-opening date
□ Access is limited to current responsibilities
□ Required restrictions are confirmed in source systems
Schedule the first accepted-matter step
Schedule the first meeting or deliverable in approved systems and assign preparation without copying substantive client detail here.
Medium priority1 day after target matter-opening date
□ First accepted-matter step is scheduled
□ Preparation tasks have accountable owners
Complete the approved decline closeout when applicable
Promptly after a decline decision, confirm authoritative notice, record disposition, access removal, and retention or deletion actions under firm policy; do not wait for the target opening date.
High priority
□ Authoritative notice status is recorded
□ Required record and access handling is complete
05
Done
Verified intake work moves here after its authoritative outcome is recorded.
Completion stage — move finished work here.
Who this template is for.
Law-firm operations teams coordinating prospective-client intake and matter opening.
Responsible lawyers and intake owners who need visible handoffs without duplicating the client file.
Small firms replacing an informal email-based opening process with a repeatable operational checklist.
When to use it.
When a new prospective-client inquiry has enough minimum information to enter the firm intake process.
Before substantive work begins or anyone represents that an engagement has been accepted.
When conflict review, approval, engagement documentation, billing setup, and access require several owners.
How to put it to work.
Anchor on the target opening date
Choose the date the approved matter should be operationally ready. The checklist schedules conflict review and engagement steps before that point.
Use neutral references
Keep names, facts, documents, conflict evidence, and legal analysis in firm-approved systems. Use a neutral intake or matter reference in task titles when needed.
Respect every approval gate
Assign the firm-designated decision owner for conflicts, fit, terms, and matter opening. A completed coordination task never substitutes for the authoritative decision.
Customize before you commit.
Replace generic decision gates with the exact reviewers required by firm policy and applicable professional obligations.
Add practice-area or jurisdiction steps only after the responsible lawyer or firm compliance owner approves them.
Use a neutral intake number throughout the checklist and resolve identity only in the authorized intake system.
Create separate accepted and declined closeout paths that match the firm’s notice, retention, and deletion rules.
Keep the system boundary clear.
SealTask coordinates operational handoffs only. The firm’s intake, conflicts, document, billing, and practice-management systems remain authoritative for identities, facts, advice, evidence, and decisions.
Legal advice, privileged communications, evidence, substantive work product, and client documents.
Engagement or decline letters, signatures, trust or billing records, retention decisions, and the official matter file.
Common mistakes to avoid.
Starting work before acceptance
An inquiry is not an engagement. Preserve explicit firm-controlled conflict, fit, terms, and acceptance gates before substantive work or access begins.
Copying conflict details into tasks
Conflict inputs and analysis can be highly sensitive. Track that the authorized review is pending or complete and keep its substance in the approved system.
Leaving declined inquiries unresolved
A decline needs an accountable closeout path under firm policy, including authoritative notice status, record handling, and removal of unnecessary access.
Questions about this template.
What should a law firm client intake checklist include?
It should coordinate minimum inquiry capture, conflict review, fit and capacity decisions, engagement approval, signed terms, matter creation, billing setup, minimum access, first meeting preparation, and accepted or declined closeout.
Does this template perform a conflict check?
No. It tracks the operational handoff to the firm’s authorized conflicts process. The search inputs, results, analysis, escalation, and final decision belong in approved firm systems.
Can prospective-client names or matter facts go in SealTask?
Use the data placement approved by your firm. This template is designed around neutral references so identity, facts, documents, and privileged or sensitive content can remain in specialist systems.
Is this legal ethics or professional-responsibility advice?
No. It is a general operations template. The responsible lawyer and firm policy owners must determine the conflict, engagement, notice, retention, jurisdiction, and professional requirements that apply.
Build the next part of the workflow.
Related template
Client onboarding checklist template
Turn a signed engagement into a controlled first milestone with clear owners, minimum access, documented decisions, and visible outstanding inputs.
Coordinate an inquiry through administrative fit, practice-controlled eligibility decisions, required records, scheduling, payment setup, and first-appointment readiness without making the task board an EHR or clinical record.
A source-backed guide to coordinating matter work without treating a task manager as a docketing system, document repository, or substitute for professional confidentiality controls.
Client-side encryption means plaintext is encrypted on the user’s device before it is sent to a service. The service receives ciphertext. Whether this creates an end-to-end or zero-knowledge boundary depends on who controls the keys and whether the provider can cause or observe decryption.
Plaintext is the readable input to encryption; ciphertext is the transformed output intended to be unreadable without the correct key. Metadata is data about a record or interaction—such as who, when, how large, or which records are related—and may remain visible even when content is ciphertext.
This disclosure covers encrypted workspace content and its server-visible metadata. The workspace-content metadata inventory is complete for the enumerated current workspace persistence and SQL models, API-response models, and SSE event models. It is not a complete privacy-data inventory and excludes account authentication, billing, security and audit, abuse-prevention, and service telemetry domains; those domains are described non-exhaustively in the privacy policy. Metadata can itself be sensitive. Attachment ciphertext size usually reveals an approximation of the original file size.