Cross-Document Verification
Curia keeps the values that should agree across a contract bundle in lockstep, and flags documents whose validity has lapsed before they cause trouble at settlement.
Across a single contract you might have a front page, a title search, a planning certificate and, in Victoria, an SRO clearance, an LIC, an OC search and a Section 32. The same title reference, the same vendor name, the same address should appear in all, and several of them have currency windows you cannot afford to miss. Curia Contract Review watches both, quietly, while you work.
The problem with eyeballing it across the bundle
Cross-checking values by hand is the kind of work that's easy on a quiet morning and risky on a busy one. A vendor's middle initial drops off between the front page and the title search. A planning certificate is two months older than you remembered. An SRO clearance was current when you opened the file and isn't when you settle. None of these are hard to catch if you're looking; the trouble is needing to look in the first place, on every file, every time.
How Cross-Document Verification works
Values stay in agreement across the bundle
Curia compares the title reference, vendor name and property address wherever they appear, front page against title search, front page against planning certificate, and surfaces a finding the moment the values diverge. You see the discrepancy with a citation to the page and clause, decide whether it's a typo or something that needs an amendment request, and move on.
Currency is checked, and rechecked
Documents with validity windows are tracked against the date you'll actually rely on them. Planning certificate dates, SRO clearance, LIC, OC search currency, water information dates, all flagged before they go stale. If a certificate is out of date, Curia tells you, rather than waiting for you to notice on the day of settlement.
Findings sit alongside the section you're reviewing
Verification runs continuously, so the warning lands where the value lives. When you're in the title search section and the vendor name doesn't match the front page, the finding is there, with the page reference for both documents. No separate report to chase, no end-of-review surprise.
Tuned to Australian conveyancing
The checks are state-aware. On the NSW standard contract , Curia reconciles the front page, title search and planning certificate (s10.7), and confirms title references line up with what's on the title diagram. On Victorian contracts and Section 32 statements , Curia adds the SRO clearance, LIC, OC search and water information statement to the mix, checking each for currency and consistency with the Section 32 and the front page. The same workflow, the documents that actually appear in your jurisdiction.
Where it sits in the review
Preflight runs once at upload as the gate that says "this contract is reviewable". Cross-Document Verification is the companion that runs throughout: every time Curia extracts a value or you confirm one, the checks rerun against the rest of the bundle. Preflight tells you the file is ready to start. Cross-Document Verification keeps the file honest while you work.
See Curia in action
See Curia handle a real contract. Book a demo .