Who is accountable when software fills in the form?
The licensee. No vendor agreement changes that, which makes verifiability a professional requirement rather than a product preference.
Every conversation about automation in real estate eventually reaches this question, usually late and usually in the wrong context: after something has gone wrong.
The answer is short. The licensee is accountable. Software is a tool. No terms of service transfer professional responsibility to a vendor, and no regulator has ever been interested in which system generated a document.
What is worth working through is what that implies for how you should use these tools.
The risk does not disappear, it moves
Before automation, the dominant failure was work not getting done: the deadline nobody extracted, the disclosure nobody sent, the package nobody ordered.
After automation, that class of failure largely goes away. The extraction happens, the documents generate, the reminders fire.
The replacement failure is work getting done without anyone checking it. Volume goes up, each individual output looks correct, and the rate of review per document falls, because nothing is visibly demanding attention.
That is a genuinely different risk profile and it deserves a genuinely different control. The control is not more caution. It is verifiability.
Automation does not create liability. It creates volume, and volume without verification is where the liability was always going to live.
Why provenance is the professional requirement
If a generated document contains fifty fields and you have no way to know where each came from, your only options are to trust the whole thing or re-derive the whole thing. The first is negligent at scale and the second defeats the purpose.
Provenance collapses that: each field points at the document and location it was extracted from. Verification becomes a scan rather than a reconstruction, and the fields that came from nowhere, which is the failure that actually matters, become visible.
This is why "show me where this value came from" is the right vendor question, and why a confidence score is not an acceptable substitute. A confidence score asks you to trust a claim about the system. Provenance lets you check the system's work.
The line between generate and send
The distinction that holds up under scrutiny is not how confident the software is. It is whether the action can be taken back.
Generating a document is reversible. It exists in the file, it can be corrected, superseded, regenerated. Making generation wait for a human approval gate mostly produces idle files, and an idle file is its own harm: deadlines run while a document sits in a review queue.
Sending something outside the file is not reversible. An email to a client, a form to a lender, a notice to a counterparty. Once it has left, correction is a conversation rather than an edit.
So: generate automatically, and put the human decision at the boundary where the consequence becomes external and permanent. That is where accountability actually attaches, and it is where the review effort should be concentrated.
What a brokerage should require
- Provenance on every generated field, checkable in seconds
- Immutable history, so what was produced and when is not rewritable after the fact
- A human decision point before anything external is sent, recorded as a decision rather than implied by absence of objection
- An audit trail of the review itself, so supervisory diligence is evidenced rather than asserted
- Retention that outlives the vendor, because the accountability period outlasts most software contracts
That last one is quietly important. If your record of who approved what lives only in a vendor's system, and you leave that vendor in three years, your evidence of diligence leaves with it.
The uncomfortable part
None of this makes the accountability shared. It stays with the licensee, and the correct response is not to avoid the tools, which just returns you to the older and more common failure of work not getting done.
The correct response is to insist on tools that make checking cheap, and then to actually check. The professional exposure comes from the second half, and it is the half no vendor can supply.