Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Set up your new system

Legal software implementation

We set up your new system around the way your firm works: implementation planning, workflow configuration, document automation and staff training.

Fig. 1 · A new system, set up around the way your firm works · Illustration

Last reviewed

First step

Which system are you putting in?

Choose a system to see what its set-up involves.

Setting up Actionstep

Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.

Set-up decisions in Actionstep

  • Matter types, with workflow steps and default document folders
  • Participant types and data collections for each matter type
  • Document and email templates rebuilt with Actionstep merge fields
  • Trust accounts, chart of accounts and the optional Xero link
  • System roles and data permissions for each group of staff
  • Outlook add-in, divisions and the firm’s billing preferences

Setting up Clio Manage

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Setting up iManage Cloud

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Setting up NetDocuments

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Setting up Smokeball

A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.

Set-up decisions in Smokeball

  • Matter types in use, with default document folders for each
  • Internal Reference format and the starting number for new matters
  • Trust account details and the link to the accounting package
  • Staff roles and permissions, including who sees billing and trust
  • Firm precedents and letterhead rebuilt as Smokeball templates
  • Desktop app, Word and Outlook add-ins on every PC

The platforms we implement and support

The service

Implementation: what you get and how long it takes.

Configuration, document automation and training for your new system.

What your firm gets

  • An implementation plan, with responsibilities and acceptance criteria.
  • Your new system configured around the way your firm works, with its workflows tested on representative records.
  • Document automation set up in the new system.
  • Training built around the tasks each role performs, and guidance your people can return to.
  • A clear handover plan, and support after launch.

The stages, and how long they take

Typically 4 to 8 weeks
A small firm of 1 to 10 users.
8 to 16 weeks
A mid-sized firm of 10 to 50 users.
Can take 3 to 6 months
Larger or multi-office deployments.
  1. Plan

    We plan the configuration, data mapping and connections before cutover. Responsibilities and acceptance criteria are agreed, and your firm names a sponsor who can decide.

  2. Configure

    We set up the system around the way your firm works: workflow configuration and document automation. Your firm decides the set-up questions for its system, such as matter types, templates, billing and permissions.

  3. Test

    Representative records and workflows are used to check the result. Exceptions are recorded, and we agree with you how the team will move into the new system.

  4. Train

    Training is built around the tasks each role performs, with guidance the team can return to.

  5. Support after launch

    We stay on for support after launch. Unresolved questions are made visible and responsibility for support is assigned.

Implementation timelines vary by firm size and complexity.

What happens after you get in touch

  1. Tell us about the system

    The system you’re considering, how many people will use it and when you’d like to go live. You don’t need a complete brief to start.

  2. A conversation about your systems and priorities

    We reply within one business day and arrange a conversation about your systems and priorities.

  3. Scope and timing, agreed

    The scope, deliverables and timing depend on your requirements and are agreed for the engagement. There’s no obligation to proceed.

The path

Choose, move, set up, put AI to work.

Implementation is the third of four. Data migration comes before it, and AI advisory and enablement after it.

How we do itDiscovery to rollout, step by step

Start with the part that isn’t working.

No obligation. You don’t need a complete brief to start.

We reply within one business day.