Torrens by Writ
New Zealand property settlements still rely on fragmented manual coordination. Title registration is digital through Landonline, but settlement still depends heavily on solicitor trust accounts, professional undertakings, and manual communication between firms.
Too much practitioner time is spent on coordination rather than judgment. Too much process knowledge lives in the heads of experienced operators. That creates execution risk: matters fall through the cracks, deadlines are missed, and scale depends on institutional memory.
The compliance engine enforces deterministic workflow rules derived from practice requirements, lender instructions, Landonline requirements, and applicable legal obligations. Above it, AI handles work that requires interpretation: reading agreements, coordinating multi-party workflows, and surfacing matters that require professional judgment.
The compliance layer constrains the agent so it can operate only within defined steps, gates, permissions, and escalation thresholds.
Critical actions — settlement sign-offs, trust account movements, Landonline submissions — always require explicit human confirmation. This is a hard constraint in code, not a setting. No amount of configuration can remove your team from these checkpoints. The system also cross-references extracted data across documents to surface discrepancies before they reach a reviewer.
Between those fixed checkpoints, your firm controls how much the agent handles independently. At the conservative end, your team reviews every proposed action. At the confident end, you pre-approve categories of routine work — document extraction, status updates, checklist progression — so they execute automatically while higher-stakes actions still surface for individual review.
Each firm can configure its preferred level of automation, with an audit trail across user actions, system actions, approvals, and exceptions.
Every transaction generates a bespoke workflow shaped by its attributes — transaction type, conditions, property type, transaction structure, and more. The result is more than 160 tasks, gates, and milestones mapped to the specific requirements of that deal.
28 compliance controls enforce dependency chains across the workflow. Downstream tasks remain blocked until their prerequisites are satisfied or a permitted exception path is invoked and recorded.
Torrens reads the contract, builds the workflow, prepares or initiates routine steps where enabled, follows up outstanding items, and surfaces the decisions that require human judgment. It reduces manual chasing of settlement figures and repetitive re-keying from lender instructions.
Real-time visibility into participating matters where the borrower's lawyer uses Torrens, without requiring banks to adopt a new settlement workflow.
Borrowers and vendors get a dashboard showing transaction status, outstanding items, dependencies, and the expected settlement timetable.
Append-only audit records are designed to preserve user actions, system events, approvals, and exceptions in a tamper-evident history. This supports evidential retention obligations, including record-keeping requirements under the Land Transfer Act 2017 and AML/CFT Act 2009.
Application infrastructure and databases are hosted in Australia (Sydney region). Where data is sent to AI subprocessors, it is handled under those providers’ enterprise security and data-handling controls.
Each firm’s data is isolated by row-level security policies enforced within PostgreSQL itself, not by application logic alone. A bug in application code cannot bypass these boundaries.
Documents are immutable at the database level. They cannot be modified or deleted through the application. Access is granted through time-limited signed URLs, scoped to participants on the relevant transaction. Retention and eventual deletion are managed in line with your firm’s obligations.
Single sign-on via your identity provider, with role-based access controls across application and data-access layers.
Authentication endpoints are rate-limited with automatic soft lockout after repeated failures. API credentials are hashed using scrypt with timing-safe verification. Password changes invalidate all active sessions across devices. Error responses are designed to prevent user enumeration.
The compliance engine is derived from the New Zealand Law Society Property Law Section Guidelines (January 2024), Landonline requirements, lender instructions, and related legal and operational obligations relevant to residential conveyancing.
The name comes from the Torrens title system, which originated in South Australia in 1858 and was adopted in New Zealand's land transfer system from 1870.