FEATURES — EVERYTHING BELOW IS LIVE TODAY

Everything the contract requires, in one system of record

Thirteen capabilities, one platform. Anything still on its way is badged NEXT — nothing here oversells.

01 · CONTRACTS & THE RULEBOOK ENGINE

The contract sets the rules. Gnosis binds to them.

Every contract binds at creation to its jurisdiction and standard form — NZS 3910, AS 4000 per state, AIA/EJCDC in the US. That one choice drives the terminology on every screen, the working-day calendars behind every clock, tax, retention rules and the clause library Gnosis Intelligence cites.

  • Drop the executed contract PDF — the form fills itself, you verify and create
  • NZ says Payment Claim and Engineer; AU says Progress Claim and Superintendent — automatically
  • Separable portions with their own values, dates and retention
  • Delegation gates: who certifies, who authorises, to what value

02 · SCHEDULE OF RATES & AI IMPORT

The backbone, imported in minutes — not retyped over a weekend

Drop the pricing spreadsheet — messy tabs included. Gnosis Intelligence returns groups, items, units, rates and computed subtotals for you to verify. Every claim certifies against it; every variation extends it.

  • Item groups, account numbers and separable portions assigned in bulk
  • Paste from Excel into a spreadsheet-grade grid — sticky heads, pinned totals
  • Live/locked states so the schedule can't drift once claims begin
  • Groups, accounts and portions flow through to claims, variations and reports

03 · PAYMENT CLAIMS → CERTIFICATES

Certify the claim, not the spreadsheet

The contractor submits (free), quantities land against your schedule, and every line certifies cumulatively — claimed vs scheduled, previous vs this claim. Anything over 100% is flagged with the evidence beside it. The Certificate of Payment computes retention bands, GST and the payable amount under your rulebook, and issues through your delegation gate with the statutory clock counted.

  • Cumulative columns: qty, amount, previous claim — the dialect engineers expect
  • Over-claim flags with site-record evidence, not just a red number
  • Scheduled-amount reasons drafted for you when certified < claimed
  • One certificate schedule per separable portion, automatically

04 · VARIATIONS & TIME

Scope changes. The record keeps up.

Raise the Variation Order, tag the clause, price it against scheduled rates — items inherit their groups, accounts and portions. The approval chain routes it through the same delegation gates as your certificates, and a granted extension moves every downstream clock.

  • Escalate an RFI to a variation — question, answer and references carried, nothing retyped
  • EOT claims tracked with statutory response windows
  • Certificates absorb authorised variations automatically

05 · COMMUNICATIONS HUB

Instruments, not email threads

Notices, RFIs, NCRs and transmittals live in one hub — numbered automatically, role-tagged, every reply on the record, every statutory clock counted on your contract's calendar. Resolve a thread and it locks into the audit trail.

  • Numbering like 008-BSO-NTC — server-side, never duplicated
  • Working-day countdowns per instrument, overdue escalated to your inbox
  • Connected records: the notice, the VO it references, the claim item it touches

06 · GNOSIS INTELLIGENCE

One intelligence, six surfaces — and it never issues anything

Gnosis Intelligence reads your contract's rulebook and your project's documents, then works wherever you are. Every draft lands as a draft; a named person approves it through a delegation gate. That rule has no exceptions.

Universal intake

Drop any document anywhere — claim, variation, register, contract. Classified, extracted, routed. Nothing exists until you review.

Command bar

⌘K from anywhere: jump to any instrument, run gated actions, or ask.

Assistant rail

Ask anything about the contract — answers cite the bound rulebook, clause by clause.

Radar

Deadline risks, over-claims and anomalies flagged with evidence — before they bite.

Drafts, gated

Notices, certificates, assessments — drafted in your contract's language, issued only by you.

Voice

Say it instead of typing it — parsed to a confirm card. Gated actions never run unconfirmed.

Metered in actions, never tokens: an import extract is 5 credits, an assist is 1. Nothing ever auto-bills.

07 · REPORTS & AUDIT TRAIL

Prove the maths at month-end

Build the report you actually need: pick from a catalogue of sources — contract position, certified to date, retention held, open instruments — watch the live preview compose, and export. Everything assembles from the same records that produced the certificates, so the report and the contract can never disagree. Every action is on the audit trail with who, when and what changed.

  • A builder, not a fixed pack: choose the sources, see the live preview
  • Branded, exportable — board-ready PDF or Excel for the analyst, on demand
  • Role-aware: each side sees its own figures, never the other's
  • Locked threads and issued instruments are immutable record

08 · SUBCONTRACTS & SUPPLIERS

The head contract flows down. The record follows.

Run every subcontract under its head contract — its own scope, rates, retention and gates. Your subcontractor works in a free portal scoped to exactly their subcontract: they submit claims and see their own record, never the head contract and never another sub. Suppliers sit alongside, each with their own record.

  • The portal is free on every plan — a subcontractor never needs a paid seat
  • Scoped by design: each sub sees their own subcontract and nothing else
  • Subcontract claims certify through the same delegation gates as the head contract

09 · PURCHASE ORDERS & 3-WAY MATCH

Three documents, one truth — matched at the PO rate

Raise supplier purchase orders, receipt what actually arrives, and match the invoice line by line at the PO rate. Where the invoice runs over, the short-pay routes through your approval gates like everything else. Gnosis records and matches; it never executes payments.

  • 3-way match: purchase order, delivery docket, invoice — variances surfaced, not buried
  • Matched at the PO rate — an invoice can't quietly reprice the order
  • Short-pays go through approval gates, with the reason on the record

10 · PROGRAMME

The programme comes in. The claims answer to it.

Import the programme from MS Project XML or Primavera XER and map its milestones to the contract. Binary .mpp we refuse by design — it's a closed format we won't pretend to read; export XML from MS Project first and it imports cleanly. From there the record does the watching: slippage against the baseline, honest revision diffs, and claims checked against what the programme says should be built.

  • Slippage radar: drift against the baseline, flagged milestone by milestone
  • Rev-diff on every revision: slipped, resequenced, new, removed
  • Claim sanity: claimed vs programmed, side by side
  • A granted EOT re-baselines the programme, not just the completion date

11 · DRAFTING STUDIO & REQUIRED PLANS

Required plans, drafted and governed — never applied for you

Every contract carries its required plans, Category 1 to 5, and Gnosis governs them the way it governs everything: a suggestion is never applied on its own. Draft in the Studio or upload the docx you already have. Gnosis Intelligence drafting here is metered Studio document work — it draws credits like any other action; nothing is quietly free.

  • Required plans by category, Cat 1–5 — the contract decides what's required, the record shows what's approved
  • Suggestions are suggestions: nothing is ever applied without you
  • Upload a docx or draft in the Studio — GI drafting is metered document work
  • Approved plans land in the Library; transmittals compose from drafts — composing is not sending

12 · ENGAGEMENTS & TIMESHEETS

Timesheets in, fee claim out — nothing retyped

Run professional-services engagements beside the construction contracts. Timesheets keyed to the Monday week, and a T&M-to-fee-claim bridge that turns the hours your team recorded into the claim you submit — the same figures, end to end.

  • Timesheets keyed to the Monday week — one rhythm across every engagement
  • The T&M bridge: recorded time becomes the fee claim, nothing retyped
  • Engagements live in the same workspace, on the same audit trail

13 · REGISTER IMPORT

Ten claims in? Bring the history with you.

Mid-contract is the normal case, not the exception. Drop the registers you've been keeping — variations, claims, EOTs, any spreadsheet, .xlsm included: we read the cells and never run the macros. Rows land as numbered instruments in their terminal states, wearing a Migrated badge, and none of the live machinery fires — no notices sent, no clocks started. New instruments simply continue your sequence.

  • Any spreadsheet — including .xlsm; macros are never run
  • Migrated rows land in terminal states with a Migrated badge — history, not live work
  • Import never triggers the live machinery: no notifications, no statutory clocks
  • Cumulative maths is right from day one; numbering continues your sequence