Growth

How to Set Up Clio for Your Law Firm: Implementation & Configuration Guide

kate@descansodigital.com (Kate Hudson) — Wed, 15 Jul 2026 18:01:14 GMT

Clio can manage matters, contacts, documents, tasks, calendars, billing, and client information. The quality of the system depends on how those tools are configured around the firm’s actual work.

Before changing settings, document how matters enter the firm, how work is assigned, which information must be captured, how billing is handled, and what leadership needs to report on. Those decisions should drive the Clio setup.

Map the Matter Lifecycle

Start by documenting how a matter moves through the firm from first contact through closing.

A typical lifecycle may include:

Initial inquiry
Conflict review
Consultation
Engagement
Matter opening
Assignment
Active work
Billing
Closing
Follow-up

The stages should reflect the practice area and the way the firm operates.

A litigation matter may require deadlines, discovery stages, court dates, and settlement tracking. An estate-planning matter may require document collection, drafting, review, execution, and funding. A flat-fee immigration practice may need payment milestones and document-status tracking.

For each stage, identify:

What starts the stage
Who is responsible
What information is required
What tasks must be completed
What moves the matter forward
Which exceptions need separate handling

This gives the firm a working model for matter stages, task lists, custom fields, and automation.

Define Matter Types

Matter types should reflect distinctions the firm uses in workflows, billing, staffing, or reporting.

A category may need its own matter type when it:

Uses a different workflow
Requires different information
Has a different billing arrangement
Is assigned to a different team
Is reported separately
Requires practice-specific documents or deadlines

For example, “litigation” may be too broad when the firm separately manages employment, commercial, and real estate disputes. At the same time, creating a separate matter type for every minor variation can make selection inconsistent and reporting difficult.

Use the fewest categories needed to support meaningful operational differences.

Choose the Information the Firm Needs to Capture

Custom fields should support a task, decision, workflow, or report.

Useful fields may include:

Matter subtype
Referral source
Responsible attorney
Originating attorney
Billing arrangement
Key deadlines
Jurisdiction
Adverse parties
Client requirements
Settlement or transaction value
Matter status
Closing reason

Before adding a field, identify who will complete it, when it will be completed, and how the information will be used.

Required fields should be limited to information the firm consistently needs. Optional fields should still have a defined purpose. Fields that are rarely completed or never used in reporting should be removed or consolidated.

A smaller set of reliable fields is more useful than a large set of incomplete ones.

Standardize Matter Naming

Choose one matter-naming convention and apply it consistently.

Possible formats include:

Client Name – Matter Type – Adverse Party

Client Name – Project or Transaction

The format should make matters easy to identify in search results, reports, document integrations, invoices, and calendars.

Document the convention and determine whether matter names will be entered manually or generated from existing fields. Where possible, use a predictable structure rather than relying on individual preferences.

Configure Intake and Matter Opening Together

Clio Grow and Clio Manage should be configured as one connected process when the firm uses both systems.

Determine which intake information should transfer into the contact and matter records, including:

Client contact information
Matter type
Referral source
Responsible attorney
Key dates
Adverse parties
Billing arrangement
Practice-specific information
Consultation notes that remain operationally relevant

The intake process should collect enough information to qualify the lead, run conflicts, schedule the appropriate consultation, and open the matter without unnecessary re-entry.

Do not transfer every intake note into structured fields. Separate information that needs to drive workflows or reporting from information that only needs to remain in the record for reference.

Build Workflows Around Recurring Work

Use task lists and automations for work that follows a consistent sequence.

Good candidates include:

Conflict review
Consultation preparation
Engagement follow-up
Matter opening
Initial document requests
Litigation deadlines
Estate-planning drafting
Transaction closing
Monthly billing review
Matter closing
Post-matter follow-up

For each workflow, define:

The trigger
The task owner
The due date or timing rule
Required information
Dependencies between tasks
Escalation or follow-up when work is overdue

Focus first on points where work changes hands. These are the places where assigned ownership and visible deadlines provide the most value.

For example, once an attorney approves a new engagement, the system may assign matter-opening tasks to an administrator, request documents from the client, notify the billing team, and create the initial attorney tasks.

Use Automation for Defined Processes

Automation should handle work the firm has already standardized.

Before configuring an automation, determine:

The exact trigger
The required conditions
The action Clio should take
The person responsible for the next step
The information needed to complete it
The exceptions that require manual review

Avoid automating steps that depend on undocumented attorney preferences or inconsistent judgment. Standardize the default process first, then identify where exceptions should remain manual.

Start with automations that eliminate repetitive administrative work, such as task assignment, reminders, matter-stage updates, document requests, and internal notifications.

Configure Permissions and Responsibility

Decide who can view, create, edit, and delete information in Clio.

Review access for:

Matter records
Contact information
Billing data
Trust accounts
Financial reports
Custom fields
Workflows
User management
Integrations
Data exports

Permissions should reflect job responsibilities and confidentiality requirements.

The firm should also define who is responsible for maintaining each part of the system. For example, intake may own lead data, administrators may own matter-opening standards, billing may own invoice workflows, and a designated system administrator may own configuration changes.

Configure Billing Around the Firm’s Process

Billing setup should reflect how the firm records time, reviews drafts, approves invoices, collects payment, and handles trust funds.

Document:

Time-entry expectations
Billing frequency
Flat-fee or milestone rules
Draft-generation timing
Draft-review responsibility
Invoice approval
Discount authority
Payment follow-up
Retainer replenishment
Trust accounting procedures
Write-off approval
Matter-specific exceptions

Configure billing rates, activity categories, expense categories, payment settings, invoice templates, and trust accounts around those rules.

Test the complete billing cycle before launch. Create a sample matter, enter time and expenses, generate a draft, apply a discount, approve the invoice, record payment, and confirm that the resulting reports are accurate.

Build Reports Around Specific Decisions

Each report should answer a defined operational or management question.

Examples include:

How many inquiries became consultations?
How many consultations became retained matters?
Which referral sources generate retained clients?
How long does intake take?
Which matters have no recent activity?
Which deadlines or tasks are overdue?
How much work remains unbilled?
Which invoices remain unpaid?
Which practice areas are growing?
How much revenue is associated with each attorney or matter type?
How long does it take to close a matter?

For each report, identify the fields and user actions required to produce reliable data.

For example, referral-source reporting will only work when staff use a consistent referral field. Matter-aging reports require accurate open and close dates. Pipeline reports require clear stage definitions and regular updates.

Test reports against known matters before relying on them for management decisions.

Clean and Prepare Data Before Importing It

Do not import legacy data without reviewing it first.

Prepare contacts and matters by:

Removing duplicate records
Standardizing names
Confirming required fields
Normalizing phone numbers and addresses
Separating people from companies
Reviewing matter statuses
Confirming responsible attorneys
Standardizing practice-area labels
Identifying closed or inactive records
Removing obsolete information

Map each legacy field to the correct Clio field before importing. Record which information will not be transferred and where archived data will remain available.

Run a test import with a small sample before migrating the full dataset.

Review Integrations

Evaluate each integration based on the process it supports.

Common integrations may include:

Microsoft 365 or Google Workspace
Outlook or Gmail
Document management systems
Accounting software
Payment processing
E-signature platforms
Phone systems
Intake forms
Legal research or drafting tools
Business intelligence tools

For each integration, determine:

What data moves between systems
Which system is the source of truth
Who can access the connected data
Whether records can be duplicated
What happens when the integration fails
Who is responsible for support

Do not add an integration solely because it is available. Add it when it removes a defined manual step or improves access to necessary information.

Test the Setup With Real Scenarios

Before rollout, test Clio using representative matters from each practice area.

Test scenarios should include:

A new inquiry
A failed conflict check
A retained client
A matter requiring reassignment
A flat-fee matter
An hourly matter
A matter with trust funds
A matter with an exception to the standard workflow
A closed matter
A reopened matter

Have the people who perform the work complete the test. Their feedback will identify missing fields, unclear task ownership, unnecessary steps, and permissions problems that may not be visible during configuration.

Document changes and repeat the test after revisions.

Train People by Role

Training should show each group how to complete its work in the configured system.

Attorneys

Training may cover:

Reviewing and updating matters
Completing assigned tasks
Recording time
Accessing documents
Reviewing invoices
Managing deadlines
Using mobile access

Intake Staff

Training may cover:

Creating contacts and leads
Recording referral sources
Running the intake workflow
Scheduling consultations
Updating intake stages
Transferring retained matters

Paralegals and Legal Assistants

Training may cover:

Matter opening
Task lists
Document management
Deadline tracking
Client communications
Matter-stage updates

Billing and Administration

Training may cover:

Rates and billing arrangements
Draft bills
Invoice approval
Payments
Trust accounting
Reporting
User and permission management

Use the firm’s own matter types, fields, workflows, and examples during training. Provide written documentation for recurring tasks and configuration rules.

Assign Ongoing System Ownership

Designate a person or team to manage Clio after implementation.

System ownership should include:

Reviewing configuration requests
Maintaining custom fields
Updating workflows
Monitoring integrations
Managing permissions
Reviewing data quality
Updating training materials
Testing new features
Archiving obsolete processes
Confirming that reports remain accurate

Set a process for requesting changes. A new field, workflow, or integration should have a defined purpose and an owner before it is added.

Schedule periodic reviews of matter types, custom fields, task lists, automations, reports, permissions, and integrations. The setup should change when the firm’s process changes, but those changes should remain controlled and documented.

A Practical Clio Implementation Checklist

Before launch, confirm that the firm has:

Documented the matter lifecycle
Defined matter types
Selected required custom fields
Standardized matter naming
Connected intake to matter opening
Configured recurring workflows
Defined billing procedures
Set permissions
Cleaned and mapped legacy data
Tested integrations
Built and validated reports
Completed role-based training
Assigned system ownership
Documented configuration standards

Clio should give the firm one reliable place to manage client and matter work. That requires a setup based on actual responsibilities, data requirements, billing procedures, and management needs.

Descanso Digital helps law firms plan, configure, repair, and manage Clio implementations. Our work includes process mapping, data structure, workflow configuration, intake, billing, reporting, integrations, migration, training, and ongoing system management.

Contact Descanso Digital to discuss a new Clio implementation or improve an existing setup.

Spellbook Playbooks for Law Firms: What They Do and Why They Matter

kate@descansodigital.com (Kate Hudson) — Wed, 15 Jul 2026 17:27:49 GMT

Most law firms already have preferred contract language.

The problem is that it is often scattered across old matters, email threads, personal clause banks, and individual attorneys’ files.

Someone knows which indemnification clause the firm usually accepts. Someone else has the preferred limitation of liability language. A partner may remember why a particular fallback was approved three years ago. None of that helps much if the attorney reviewing the contract cannot find it when they need it.

Spellbook Playbooks give firms a way to put that guidance into the contract review process itself.

A Playbook tells Spellbook what to look for, what the firm prefers, what alternatives may be acceptable, and when an issue should be kicked up for further review.

The attorney still decides what to do. The Playbook helps make sure they are not starting from scratch.

What Is a Spellbook Playbook?

A Spellbook Playbook is a set of custom contract review rules that runs inside Microsoft Word.

A Playbook can tell Spellbook to:

Flag a missing limitation of liability clause
Identify language that falls outside the firm’s usual position
Suggest approved fallback language
Add a comment explaining the issue
Check whether required provisions are missing
Escalate higher-risk terms to a partner
Apply standards created for a specific client
Its preferred position
Other acceptable positions
Language it will not accept
Available fallback clauses
Relevant exceptions
When the issue should be escalated
When the preferred clause should be used
Which fallback applies
What conditions make the fallback acceptable
When the issue needs partner review
Reviewing existing contracts and clause banks
Comparing different versions of the same provision
Identifying the firm’s preferred and acceptable positions
Documenting exceptions
Writing the rules
Testing the Playbook against real contracts
Revising rules that create bad flags or miss important issues
Review the same agreement types regularly
Have preferred contract language
Want more consistent work across attorneys
Need to train or supervise junior attorneys
Rely heavily on partner knowledge
Spend too much time searching for precedents
Already use Spellbook but have not built a repeatable review process
Organize existing clauses and review guidance
Identify conflicting or missing standards
Build practical Playbook rules
Create fallback and escalation logic
Test the Playbook against real contracts
Review attorney feedback
Fix rules that create too much noise
Update the Playbook as standards change

Without a Playbook, the review is based on more general contract guidance.

With one, the contract can be reviewed against the firm’s own standards.

Why Law Firms Use Playbooks

More consistent reviews

Two attorneys can read the same clause and focus on different things.

That is not always a problem. Legal work still requires judgment.

The problem is when they are working from different assumptions because one attorney knows the firm’s preferred position and the other does not.

A Playbook gives both attorneys the same instructions before they begin. They may still make different calls, but they are not relying on different source material.

Less searching through old files

Attorneys should not have to dig through prior agreements every time they need a clause the firm has already approved.

A Playbook can bring preferred language and fallback positions into the document review itself.

That saves time, but it also reduces the chance that someone grabs the wrong version from an old matter and assumes it is still current.

Easier delegation

A junior attorney can handle more of the first pass when the firm’s expectations are clear.

They can see what language is preferred, what the firm will accept, and which issues require help from a more senior attorney.

That is more useful than telling someone to “use judgment” without giving them access to the judgment the firm has already developed.

Better training

Playbooks can explain why a clause is being flagged, not just mark it as a problem.

That matters for newer attorneys.

Instead of simply seeing a redline, they can see what the issue is, why the firm cares about it, and what a reasonable alternative may look like.

Better use of firm knowledge

A surprising amount of legal knowledge lives in people rather than systems.

That works until someone is unavailable, leaves the firm, or simply cannot remember which version was used in which matter.

A Playbook makes that knowledge easier to document and easier for other people to use.

What Makes a Playbook Useful?

A useful Playbook does more than list preferred clauses.

It needs to reflect the actual decisions attorneys make during review.

For each issue, the firm may need to define:

A vague instruction such as “flag broad indemnification” leaves too much unresolved.

What makes the language too broad? Is the concern third-party claims, first-party claims, negligence, intellectual property, or something else? What language should be proposed instead? Is there a fallback the firm will accept?

If the rule does not answer those questions, the attorney still has to stop and work out what the firm meant. At that point, the Playbook has not saved much time.

A Playbook Is Not the Same as a Clause Bank

A clause bank gives attorneys language they can search and reuse.

That is useful, but it does not always explain when to use a clause or what to do when the other side rejects it.

A Playbook can connect the language to the decision.

It can tell the reviewer:

That makes the Playbook closer to a working review guide than a folder of sample provisions.

Why Playbook Setup Takes Work

The software is often the easy part.

The harder part is getting attorneys to agree on what the firm actually prefers.

A firm may have several versions of the same clause. Different partners may use different fallback positions. One attorney may treat a point as mandatory while another considers it negotiable.

Those differences need to be sorted out before the Playbook can produce reliable results.

The setup process usually includes:

A Playbook built from one clean template may work well on similar documents and poorly on everything else.

Testing matters because real contracts are not clean. They use different headings, definitions, structures, and drafting styles. The same issue may appear in several places.

Who Benefits Most From Spellbook Playbooks?

Playbooks are especially useful for firms that:

Firm size matters less than the nature of the work.

A small firm reviewing a steady stream of vendor contracts may get more value from a Playbook than a larger firm that handles very little repeatable contract work.

How Descanso Digital Helps

Descanso Digital builds and maintains Spellbook Playbooks for law firms.

Our perspective comes from years working inside a law firm and years consulting with firms on technology, operations, marketing, and business development.

That background is useful because Playbook work is not just software setup.

It requires understanding how attorneys review contracts, where the firm’s knowledge currently lives, how decisions are made, and what people are actually likely to use.

We help firms:

A smaller Playbook that attorneys trust is more useful than a large one they ignore.

Build a Spellbook Playbook That Fits Your Firm

Whether your firm is building its first Playbook or trying to fix one that produces too many flags, Descanso Digital can help.

Talk with us about your Spellbook Playbook project.