What “jurisdiction-specific” actually means.
How to interrogate vendor coverage of HMRC manuals, statute, statutory instruments, FTT and UTT case law — and what to do when a vendor relies entirely on third-party commentary.
Ask which primary sources are available for the jurisdiction and period relevant to your work. Bring a question with a known source, then open the authority cited in the response. Record any gaps for the pilot.
How to test citation behaviour.
A short test protocol you can run in any demo. The questions that separate tools that cite primary sources from tools that paraphrase commentary as authority.
Can you open the source? Does the cited passage support the claim? Is the relevant context visible? What happens when the available documents do not contain an answer? Use the same questions when comparing tools.
Security and data handling.
What to ask about model training, data residency, audit logs, SSO, subprocessors, and data segregation.
Ask for the security documentation and contractual terms that explain each commitment. Review how uploads, prompts, and outputs are handled, who can access them, and how retention and deletion work.
Procurement, pricing, and contract terms.
Pricing models, the shape of a pilot, and the terms your team needs to understand before committing.
Set out the expected users, workflows, and supporting services. Agree what success looks like for the pilot and identify who will assess it. Make implementation requirements and ongoing support part of the discussion.
Adoption and change management.
Plan how a tool becomes part of everyday practice, from the first working session to wider rollout.
Begin with a representative group and real work. Define a review process, give the team time to learn, and collect feedback on both quality and usability. Use that evidence to shape the next stage of adoption.
