Contract intelligence

Every obligation in your contracts. Structured, watched, answerable.

Every recommendation cited to its clause. Every action owned by a named person.

A grid connection agreement, a handful of PPAs and an O&M contract hold more dates and duties than a small team can carry in its head. Most of them sit in PDFs nobody re-reads until one is missed. This system reads them once, carefully, checks its reading with your people, and then keeps watch.

  1. Connect

    Point it at the folder your contracts already live in.

    SharePoint, a shared drive, an inbox export. No migration, no new filing system.

  2. Structure

    Every party, obligation, date and clause is pulled into one structured record, each citing its source page.

    Dates, dollar values, notice periods, renewal triggers, key clauses. Nothing retyped.

  3. Confirm

    Your people approve what the system read before any of it is trusted.

    Anything borderline queues for a person, shown beside the highlighted clause.

  4. Ask

    Ask in plain English and get answers that cite the clauses they rest on.

    Across the whole portfolio too: “which agreements reference the connection milestone?”

  5. Ahead of the date

    Renewals, notice windows, price reviews and compliance obligations surface weeks before they bite, each with an owner.

    A weekly email: what is coming, who owns it, what happens if it is missed.

Portfolio sight

Looking across every contract at once, the system raises what no single document shows: clauses that contradict each other, agreements that could be consolidated, too much resting on one counterparty. These arrive as questions for a named person, with the evidence attached. Never as decisions made for you.

The Intelligence map screen: a knowledge-graph view of the whole contract estate. Three gold counterparty hubs, Callowarra Wind Partners, Harwick Field Services and Broadmere Transmission, each sit at the centre of a cluster of teal agreement nodes, dated obligation nodes and a fine outer ring of clause nodes, with the three named owners drawn in as person nodes linked to what they own. One amber line marks a clauses conflict between the Connection works deed and the Grid connection agreement. Three dashed lines join the clusters as cross-contract dependencies: two amber risk links (an O&M contract held back-to-back against the power purchase agreement, and a grid connection whose energisation feeds the PPA commencement date) and one gold opportunity link where the power purchase and balancing services agreements share indexation. A side panel inspects the Broadmere hub and its dependency.

Twenty-three agreements, three counterparties, one map. Every line runs to a clause, every cluster to the person who owns it.

The portfolio screen: 23 agreements across three counterparties in one table, each row showing expiry, next date and the named owner, one row flagged amber where clauses conflict, and a Coming up panel listing the next obligations by date.
The Ask screen: the question ‘What are our termination rights with Broadmere?’ answered in plain English, the answer cited to two clauses, and the source clause opened below with the key phrase highlighted. A follow-up question sits ready in the composer.

Every answer rests on a clause you can open. The next question stays in the same thread, across the whole portfolio.

Weekly obligations digest · Tuesday 14 July

Ancillary services review · Callowarra Wind Partners PPA

19 days

Annual review of ancillary services pricing is due in 19 days (2 August).

Clause 6.4, page 12 · Owner: CFO

Insurance certificate · Harwick Field Services O&M

3 weeks

Current certificate of currency expires in 3 weeks (4 August). Replacement is due before expiry.

Clause 9.6, page 23 · Owner: Operations lead

Connection notice · Broadmere Transmission

45 days

Notice of revised energisation date is due in 45 days (28 August). Missing it triggers a connection re-study at your cost.

Clause 12.3(b), page 17 · Owner: Company secretary

Price review · Callowarra Wind Partners PPA

120 days

Review window opens in 120 days (11 November). Notice must be served inside the window or current pricing rolls over for two years.

Clause 14.2, page 41 · Owner: CFO

This is the Tuesday email. Nobody searched for anything. The dates came to the people who own them, with the clause attached.

AUSTRALIAN REGION Document store Managed models kept in an Australian region YOUR BOUNDARY Document store Models nothing crosses the boundary

Runs in an Australian region

Your contracts, and everything read from them, stay in an Australian region, in a tenancy set up for you. The system uses the strongest managed models available there. Data never leaves Australian jurisdiction.

Runs entirely inside your infrastructure

The same system, installed in your own tenancy or on your own servers. The models run where the documents are. Nothing crosses your boundary.

This matters in the NEM: AEMO-confidential market data cannot be sent to third-party cloud AI, and this system is built so it never has to be.

Before anything it reads is trusted, its reading is tested against a quality bar on your own documents.

Anything it is not sure of waits for one of your people to confirm, shown beside the highlighted clause.

Every answer cites the clause it rests on, so you can check it yourself.

The Review screen: a confirm queue of two items awaiting a person’s approval, the selected obligation shown as an extracted record with obligation, due date, owner and a confidence marked review suggested, set beside its source clause with the key phrase highlighted, plus Confirm and Correct actions and a counter reading approved today 14.

See it working on a contract set like yours.

Ask the person who sent you this for a walkthrough. It takes under an hour.