The verbal direction nobody confirmed in writing. The clock that started without anyone noticing. The evidence scattered across six systems. Contract Administration Intelligence watches the contract while your team builds, and assembles the substantiation before the time bar closes.
For commercial managers at mid-tier contractors and subcontractors. Your data stays in Australia.
The system reads the executed contract, the correspondence and the site record, and runs three workflows against them. Each one ties its output back to the page it came from.
The contract sets notice obligations and time bars. The system reads them, then watches the record for the events that start each clock: directions, delays, latent conditions, payment reference dates.
When an entitlement has to be substantiated, the evidence is rarely in one place. The system assembles the chronology and the supporting record into a pack a reviewer, or an adjudicator, can follow.
Before the first claim, the system reads the executed contract against the standard form and briefs the site team on the obligations that will bind them.
You give the system one contract set in the Proof Week. In production it runs against the live projects, watching the record as it accumulates.
Special conditions, the standard form they amend, the schedules and the subcontracts. Departures and notice regimes extracted with a reference to the clause.
Tables and clause numbers preservedCorrespondence, instructions, diaries and the document control system. The events that start a clock are flagged the day they appear in the record.
Same-day trigger alertsWhen a claim has to be made, the chronology and the supporting documents are already assembled and page-referenced, ready for your commercial team to review and rely on.
Uncertain reads are marked uncertainMost AI tools flatten documents into text and hope the meaning survived. Tables become paragraphs. The clause number detaches from the clause. The chain back to the source page disappears, replaced by a confidence score.
That is acceptable for a chatbot. It is not acceptable for an option deadline, a payment claim, or anything a lawyer or adjudicator might one day read.
Every Lumen & Lever system is built on Sourcetrace, our document-structure engine. It preserves layout, tables, annotations and page evidence before anything reaches a model, so every claim the system makes carries a reference to the page it came from.
The controls are not a product we sell you. They come fitted as standard.
Every output cites its source document and page. No orphan facts.
Your environment or private Australian hosting. No training on your data. No offshore routing.
Named human review points before any output is relied on. The system drafts; your people decide.
A log of what the system read, produced and flagged, kept for the life of the engagement.
Uncertain extractions are marked uncertain. Confidence is reported, not performed.
Thirty minutes. You describe the documents and where you suspect leakage. We tell you which lane fits and whether a Proof Week is worth your money. Sometimes it is not, and we say so.
We sign your NDA, take a sample of documents, and build. Five days later you watch the system run on your own record.
Production build, or a findings register and a handshake. No retainer, no lock-in, no deck.
Or write direct: hello@lumenandlever.com · Melbourne, Australia