Home Case Studies Legal Operations
Legal Operations Case Study

Brasher Law Firm Automates Matter Folder Creation Across Clio and SharePoint

Inevia connected Clio and SharePoint through Zapier to automatically create document folders for new legal matters, heling teams manage automation failures.

Primary Result Achieved
5

Connected platforms

The Challenge

Brasher Law Firm’s previous Clio–Dropbox integration automatically created a document folder whenever a new matter was opened. After the move to SharePoint, the firm needed to recreate this process without introducing manual folder setup.

The workflow also needed to distinguish between Company and Individual clients, follow the appropriate naming conventions and check for existing client folders before creating new ones.

Brasher also needed automation failures to reach the support team without relying on employees to discover and report missing folders.

The Methodology

Inevia implemented two Zapier workflows connecting the firm's matter management, document management and support systems.

01

Clio Trigger

A new matter in Clio triggered the workflow and supplied the client type, client name and matter number required for folder creation.

02

Client-Type Routing

The workflow identified Company and Individual clients and applied the appropriate SharePoint folder structure and naming logic.

03

Folder Check and Creation

Zapier checked SharePoint for an existing client folder. It created only the new matter folder when one existed, or created both folders when the client was new.

04

Failure Reporting

Zapier failure alerts were detected through Outlook and automatically created Jira Problem tickets for the support team.

The Outcomes

The automated workflow reduced the administrative work involved in setting up document folders for new legal matters and created a more consistent process between Clio and SharePoint.

  • No manual folder setup: New SharePoint matter folders are automatically provisioned from Clio.
  • Consistent folder structure: Folder names are derived from Clio data using defined naming rules.
  • Fewer duplicate client folders: The workflow checks SharePoint for an existing client folder before creating one.
  • Less administrative work: Staff no longer need to manually create, name and organize SharePoint folders for new matters.
  • Faster failure visibility: Runtime automation failures can generate Jira tickets for the support team, reducing dependence on end users reporting missing folders.

“We had no downtime during work hours. It was a huge success.”

– Christina Correia | Office Manager, Brasher Law Firm