Define the requirement before choosing a tool
The Solicitors Regulation Authority, the regulator for solicitors and most law firms in England and Wales, recommends defining actual requirements and considering existing tools before purchasing. Its lawtech guidance (sra.org.uk) also recommends reviewing specifications, demonstrations and compatibility.
Start with a specific task. A firm considering appointment software has different questions from one reviewing document storage or drafting tools. Record what needs to happen, who uses the system and which existing arrangements it must work with.
Specifications and demonstrations can then be considered against that requirement. Compatibility matters because a proposed tool may need to work alongside existing systems. A particular tool’s performance still needs assessment in its intended use.
Connect client access with practical arrangements
Technology may change how clients access legal services, as discussed in the SRA’s consumer guidance (sra.org.uk). An appointment requirement might concern sending an invitation, explaining the communication channel and providing a way to raise questions about the arrangements.
Use those concrete tasks when reviewing the proposed system. A client’s preference for another communication method is also relevant to the requirement being considered.
Assign responsibility for digital work
Under the SRA’s lawtech guidance, solicitors remain subject to professional standards, confidentiality and data obligations. Responsible adoption includes oversight, risk assessments, procedures, training, monitoring and evaluation. Technology can malfunction, so responsibilities need to be clear.
For document work, questions include who reviews an output, who handles an error and what information the tool receives. Those responsibilities belong in the working procedure, alongside the task the technology supports.
Plan training and continuity
The SRA’s legal market risk report (sra.org.uk) highlights relevant staff training, continuing regulatory and information-security obligations, and continuity planning when replacing systems. It also raises accuracy and data-security concerns about AI outputs.
Include training and continuity in the change plan, rather than leaving them until the old system is replaced. Staff need to understand the procedure and where to raise unfamiliar questions.
After introduction, monitoring and evaluation should return to the original requirement. Record problems, review how the tool is being used and identify changes that need further attention.