Professional obligations that shape the deployment
What the sector will not let an agent do.
A firm's licence to operate rests on obligations that an agent cannot hold. Each one below is a boundary the deployment is built around rather than a risk to be managed later.
- The advice remains the firm's
- Agents draft structure, gather evidence and prepare the pack. Conclusions, opinions and recommendations are authored by the practitioner who is accountable for them. Nothing generated is presented to a client without a named person releasing it.
- Client confidentiality across engagements
- Access is scoped per engagement rather than firm-wide, so an agent working one file cannot read another. Where independence or information barriers apply, the agent's access reflects them the same way a person's would.
- Documented review and quality control
- Every draft carries the source of each figure and each extracted fact, and the release step records who reviewed it and when. That is the evidence a quality review asks for, produced as the work happens.
- Client verification and acceptance
- The agent collects and checks documents against your checklist. It does not verify identity or accept a client. Those decisions stay with a person and are recorded as decisions, which is what makes the file defensible.
- Lodgements, filings and client money
- Out of scope by default. Anything with a regulatory or financial consequence stays approval-gated, and we would advise leaving it there however accurate the workflow becomes.
This is a description of how the deployment is built, not legal, financial
or compliance advice. Your own obligations should be confirmed with your
own advisers.
The security page
sets out hosting, model choice, retention and access in full.