A firm’s case management system is usually the biggest practical concern when considering outsourced support: will this person actually be able to work inside what we already use.
How does this work across common systems?
Whether a firm runs Clio, LEAP, Osprey Approach, Actionstep, or a bespoke in-house system, the paralegal works inside that system directly, updating it as the firm’s own staff would, rather than working in a separate tool that needs reconciling afterward, exactly as described on our How It Works page.
Why does this matter more than it might seem?
A parallel system or workaround creates duplicate records and reconciliation work, which erodes the time savings the arrangement was meant to create, undermining the efficiency covered in our article on what a dedicated team does day to day.
What should a firm confirm before starting?
That access can be provisioned properly within its existing system, matter-limited, before the first task begins, a step covered in our article on onboarding timelines.
What does access provisioning actually look like on Clio?
A user account scoped to the specific matters a firm assigns, with permissions set so the paralegal sees only what’s relevant to the work in hand, not the firm’s full client list. Clio’s permission structure supports this kind of matter-limited access natively, which is exactly the control our data processing agreement requires before any file work begins.
Setting this up correctly takes a firm’s IT or practice manager a short amount of time, well within the onboarding window covered in our onboarding timeline article.
How does this differ on LEAP or Osprey Approach?
The mechanics vary slightly by platform, but the principle is identical: a scoped user account, matter-level permissions, and activity that’s visible to the firm throughout. Both LEAP and Osprey Approach support granular permission settings that a firm’s administrator can configure before granting any access, so nothing needs to be built from scratch to accommodate an outsourced team.
Firms unfamiliar with their own system’s permission settings should check with their platform’s support resources or their practice manager before onboarding, so access is scoped correctly from day one.
What about Actionstep or a bespoke in-house system?
Actionstep’s workflow and permission tools work the same way as the platforms above. A bespoke in-house system needs a slightly closer look at the outset, since permission structures vary firm to firm, but the underlying requirement, matter-limited access, visible activity, doesn’t change regardless of the specific software.
Our embedded support article covers how the team adapts to a firm’s existing tools rather than asking the firm to adopt something new.
Does working inside the firm’s own system change how tasks are assigned and tracked?
No, if anything it simplifies things. Tasks get assigned the same way a firm would assign them internally, and returned work sits directly in the matter file rather than in a separate document that needs reconciling back into the case management system afterward. That single-system approach is what keeps the arrangement efficient day to day, covered in our day-to-day article.
A provider working outside the firm’s own system, requiring a separate portal or duplicate record-keeping, adds friction that erodes most of the time saving the arrangement is meant to deliver.
What should a firm check before the first task goes into the system?
That the permission scope is genuinely matter-limited, that access can be revoked cleanly once a task or engagement ends, and that the platform’s own activity logs give the firm visibility into what’s been done. Our contact page and Pricing page are the place to talk through how this works for a specific system before onboarding begins.
Does remote access raise any specific technical concerns?
The same considerations apply as for any remote user accessing a cloud-based system: secure login, ideally with multi-factor authentication enabled, and device security standards consistent with what a firm would expect of its own remote staff. Clio, LEAP, Osprey, and Actionstep are all cloud-hosted platforms designed for remote access, so there’s no technical barrier to a properly provisioned account being used securely from anywhere.
The device and password hygiene standards each team member is bound by, covered in our DPA article, apply regardless of where the person accessing the system happens to be located.
Does time recording work differently under a fixed-fee arrangement?
Most firms don’t need the paralegal to log time in the system at all, since the fixed monthly fee doesn’t depend on billed hours the way an hourly arrangement would. Work still gets tracked task by task for the firm’s own visibility, but without the hourly time-recording overhead that would apply to an internal fee earner billing by the hour.
That simplicity is one of the quieter practical benefits of a fixed-fee structure, covered more fully in our fixed-fee billing article.
What happens to system access once a task or engagement ends?
Access is revoked cleanly, following the deletion and access-termination terms in the engagement’s data processing agreement. A firm should confirm this can be done promptly and verified, not left as an assumption, particularly for firms that scale a team up and down with caseload.
Our back-office operations article covers how access scales cleanly alongside the flexible capacity a Complete Back Office arrangement provides.
Does this work for firms running multiple systems across different practice groups?
Yes. A firm running litigation on one platform and private client matters on another can have the outsourced team provisioned across both, scoped separately to each system’s own matters. There’s no requirement to consolidate onto a single platform before bringing in outsourced support.
How much IT support is needed from the firm’s side to set this up?
Usually very little beyond creating the scoped user account itself, since the outsourced team works with the system’s own login and interface rather than requiring new software installed or a custom integration built. Most firms can complete this step in under an hour once they know which permissions to set.
Our How It Works page walks through exactly this step as part of the standard onboarding sequence.
What if a firm’s system doesn’t support granular permission settings?
This is worth checking before onboarding, since it affects how tightly access can be scoped from day one. Most modern case management platforms, including all four named above, support matter-level permissions, but an older or heavily customised bespoke system may need a closer look. Our provider selection guide covers what to ask about before assuming access can be scoped as tightly as a firm would like.
Does working directly in the firm’s system make supervision easier or harder to evidence?
Easier, generally. Because the work happens directly inside the firm’s own system, the platform’s own activity log becomes part of the supervision record, showing what was entered, when, and by whom. That’s a more complete evidence trail than a parallel workflow would produce, and it supports exactly the kind of documented supervision covered in our COLP checklist article.
Firms concerned about evidencing supervision properly should see this single-system approach as an advantage, not a risk, since it removes the need to reconcile separate records after the fact.
Is there a preferred case management system for outsourced arrangements to work best?
No. All four platforms named here, and most modern bespoke systems, support the access controls and workflow patterns an outsourced arrangement needs. The choice of case management system is a firm’s own decision made independently of whether it uses outsourced support, and switching systems isn’t a prerequisite for bringing in a dedicated team.
Where should a firm start if it wants to test this on its own system?
Scope a single task on the firm’s actual platform as the first trial, rather than a generic exercise disconnected from how the firm really works day to day. That gives the clearest read on whether access provisioning, workflow, and returned work all fit together smoothly before any wider commitment.
Talk it through on our contact page, naming the specific platform in use, and we’ll walk through exactly what access provisioning looks like before the first task begins.
Whichever system a firm runs on, the goal is the same: work happening where it already belongs, not in a separate tool that needs reconciling back later.
Want to confirm your system is a good fit before starting?
We’ll assign a dedicated paralegal to your matter for 7 days, no charge, so you can see the standard of work before deciding anything.
Confidential · No obligation · Typically a 20-minute call
Frequently Asked Questions
Does working inside our case management system require extra training on our end?
No. Access is provisioned to the specific matter, and the paralegal adapts to your existing setup rather than requiring changes from your team.
What if our firm uses a bespoke or unusual in-house system?
The same principle applies. Access is scoped to the actual system in use, with onboarding covering any specific workflow it requires.
Is there a cost difference depending on which case management system a firm uses?
No. Packages are priced flat regardless of the specific system, as set out on our Pricing page.
