Start with the destination, not the form

Many firms begin their Clio Grow setup by creating intake forms first.

That is understandable. Intake forms feel like the obvious starting point. A prospect needs to fill something out. The firm needs information. Someone says, “Let’s make a form.”

Simple enough.

But here is where things can go sideways.

The firm creates a beautiful form asking for addresses, dates, opposing parties, incident details, referral sources, emergency contacts, business names, estate planning details, court information, and maybe the prospect’s blood type if everyone gets too excited.

Then the prospect becomes a client.

Now someone opens the matter in Clio Manage and realizes that half the information from the intake form has nowhere useful to go.

So what happens?

Copy. Paste. Re-type. Re-check. Mutter things under your breath that are not part of the firm’s brand voice.

That is not automation. That is a treadmill with a login screen.

The golden rule: Build Clio Manage first

Before building Clio Grow intake forms, the firm should first decide what information it wants to preserve in Clio Manage.

This usually means reviewing and setting up:

Practice areas
Matter custom fields
Contact custom fields
Custom field sets
Matter stages
Task lists
Matter templates
Naming conventions

The goal is to create the structure that will receive the information later.

Think of it like building a courthouse. You do not invite everyone in first and then decide where to put the judge, the jury, the files, and the coffee machine. You design the rooms before people start wandering around with subpoenas.

Clio Manage custom fields allow firms to capture additional information that is not part of the standard contact or matter fields, and those custom fields can be organized into field sets for specific situations, such as practice areas.

That matters because different practice areas need different information.

A family law intake may need spouse information, children’s names, date of separation, existing court orders, and custody concerns.

An estate planning intake may need family members, fiduciaries, asset information, prior wills, and health care documents.

A business law intake may need entity names, ownership percentages, contract details, registered agent information, and who has authority to sign.

A personal injury intake may need accident dates, injury details, insurance information, treatment providers, and claim numbers.

If we treat all matters the same, the intake process becomes a buffet where every practice area is handed the same sad little plate.

Custom fields are not decoration

Custom fields should not be created just because someone thought of another question.

Every field should have a job.

A good custom field should help the firm do at least one of these things:

Qualify the lead
Prepare for the consultation
Check for conflicts
Open the matter correctly
Assign the right workflow
Prepare documents
Track useful business data
Serve the client better

If a field does none of those things, it may just be clutter wearing a tiny hat.

Before creating a custom field, ask:

Will we need this after the prospect becomes a client?
Will this help us decide whether the lead fits the firm?
Will this save time later?
Will this help with documents, tasks, or reporting?
Will anyone actually look at this again?

If the answer is no, the field may not belong in the system.

Or at least not in the first version.

Contact fields vs. matter fields

This is one of the most important setup decisions.

Some information belongs to the contact. Some belongs to the matter.

A contact field is about the person or company.

Examples:

Preferred name
Preferred language
Referral source
Date of birth
Employer
Company name
Best contact method
Emergency contact

A matter field is about the legal issue.

Examples:

Date of incident
Opposing party
Court name
Case number
Type of legal issue
Urgency level
Consultation notes
Estate plan type
Contract value
Date of separation

This distinction matters because a person can have more than one legal matter.

For example, Maria Lopez may first contact the firm about a divorce. Two years later, she may come back for estate planning. Her phone number and preferred language belong to her contact record. Her date of separation belongs to the divorce matter. Her trustee selection belongs to the estate planning matter.

Mix those up, and your database starts behaving like a junk drawer with Wi-Fi.

Build field sets by practice area

Field sets can make custom fields easier to manage by grouping related fields together. Clio’s documentation explains that custom fields can be grouped into field sets to manage several fields that apply to particular situations, such as specific practice areas.

This is where firms can make intake feel organized instead of overwhelming.

For example:

Family Law Field Set

Date of marriage
Date of separation
Children involved?
Existing court orders?
Opposing party name
Opposing counsel
Urgent hearing date

Estate Planning Field Set

Marital status
Children
Prior estate plan?
Real property owned?
Preferred fiduciaries
Special needs beneficiary?
Business ownership?

Personal Injury Field Set

Date of incident
Location of incident
Injury type
Insurance company
Claim number
Medical treatment started?
Police report?

When the fields are grouped thoughtfully, the firm can build intake forms that feed clean information into the right places.

No scavenger hunt. No mystery fields. No “why is the dog bite question showing up in the probate matter?”

Then sync the fields into Clio Grow

Once the custom fields are created in Clio Manage, the next step is to sync them into Clio Grow.

This is the step that makes the later intake forms much more powerful.

Clio’s help materials explain that firms can sync Clio Manage custom fields to Clio Grow. Clio also notes that most custom field types sync from Clio Manage to Clio Grow, although some field types do not sync, including Contact Select, Matter Select, Integer, and Time fields.

That means you should not assume every field will behave exactly the way you want. A little planning here saves a lot of “why is this not showing up?” later.

Also, when converting a matter from Clio Grow to Clio Manage, Clio states that custom fields and field sets convert if they were created in Clio Manage and then synced to Clio Grow.

That sentence is the whole ballgame.

Read it again, but this time with feeling:

Created in Clio Manage. Synced to Clio Grow. Used in the intake process. Converted back into Clio Manage.

That is the clean path.

That is how information flows instead of splashing everywhere.

Do not make Clio Grow carry the whole piano

Clio Grow is excellent for prospective client intake. It helps firms collect information, schedule consultations, manage leads, and move prospects through the intake process.

But Clio Manage is where the actual client matter will live after the firm is hired. Clio describes matters in Clio Grow as matters for prospective clients, while matters in Clio Manage are for clients whose cases the firm has agreed to take on.

That distinction is important.

Clio Grow helps you decide whether the person should become a client.

Clio Manage helps you manage the client’s legal matter.

So the setup should respect that journey.

Do not ask Clio Grow to become a second case management system. And do not ask Clio Manage to clean up a messy intake process after the fact like a parent following a toddler with paper towels.

Let each system do its job.

A simple setup order for new Clio Grow users

For a firm starting fresh, the setup should look something like this:

First, define the firm’s intake goals.

What types of matters does the firm want? What information helps qualify a lead? What information is needed before a consultation? What information should survive into the client file?

Second, build the structure in Clio Manage.

Create the needed contact custom fields, matter custom fields, and field sets. Organize them by practice area where appropriate.

Third, review field types before syncing.

Make sure the fields you create in Manage are field types that can sync into Grow. Not all field types sync.

Fourth, sync Clio Manage custom fields into Clio Grow.

This makes those fields available for use in Grow’s intake process.

Fifth, build Clio Grow intake forms using those synced fields.

Now the form answers have somewhere useful to go later.

Sixth, test the process before using it with real prospects.

Create a fake lead. Fill out the form. Convert the matter. See what lands in Clio Manage and what does not.

Testing is not glamorous, but neither is apologizing to a partner because “the system ate the opposing party.”

The test lead is your friend

Before launching any form, create a test prospect.

Use a name that makes it obvious the matter is fake, such as:

Testy McTestface
Fictional Client
Demo Divorce
Not A Real Human

Then fill out the intake form like a prospect would.

After that, walk the matter through the process:

Did the information land in the right place?
Did the contact fields update correctly?
Did the matter fields appear correctly?
Did the field set apply as expected?
Did anything fail to sync?
Did any question create duplicate information?
Did the form ask anything unnecessary?
Did the intake team understand what to do next?

A test run is where you find the plumbing leaks before the dinner guests arrive.

The real goal: less retyping, more lawyering

The purpose of this setup is not just to make the software look tidy.

The purpose is to reduce friction.

When information flows cleanly from Clio Grow to Clio Manage, the firm can respond faster, prepare better, and create a more professional experience for the prospect.

The intake person does not have to ask for the same information three times.

The attorney walks into the consultation with better context.

The new client does not feel like the firm is making them repeat their life story at every doorway.

And the matter opens with structure instead of chaos.

That is the difference between a form and an intake system.

A form collects answers.

An intake system moves the right information to the right place at the right time.

Final thought

Clio Grow intake should not begin with, “What questions do we want to ask?”

It should begin with, “What information do we need later, and where should it live?”

Once you know that, everything gets easier.

The fields in Clio Manage become the foundation.
The sync to Clio Grow becomes the bridge.
The intake form becomes the front door.
The conversion back to Clio Manage becomes the handoff.

Build the destination first. Then build the road.

Otherwise, your intake process may still collect information, but it will do what too many law firm systems already do beautifully:

Create more work while pretending to save time.

And frankly, law firms already have enough of that.

Coming Next

In the next blog, we’ll move from the foundation to the front door: building smarter Clio Grow intake forms.

We’ll cover how to ask the right questions, use synced Clio Manage fields, qualify leads earlier, and avoid turning your intake team into professional copy-and-paste athletes.

Because not every prospect needs a 47-question form. Sometimes the best question is the one that tells you, politely, “This is not our client.”

Need Help With Clio Grow?

2b1 Inc. helps law firms build cleaner intake workflows, smarter forms, and better handoffs from Clio Grow to Clio Manage.

Call 2b1 Inc. at 415-284-2221 or fill out the form below.

Your intake process should not feel like a junk drawer with a calendar invite.