
Proprietary Analysis. Unmatched Depth.
Every contract triggers a comprehensive multi-dimensional analysis pipeline. Each capability is purpose-built for a specific dimension of contract risk in Australian construction.
Risk Transfer Analysis
Scores every clause for liability, indemnity, and financial exposure transfer. Identifies where risk sits unfavourably against the contractor. Extracts dollar amounts, day counts, and cap percentages from clause text.
Clause-LevelHow It Works
Each clause is assessed against a proprietary risk taxonomy that identifies how contractual risk is transferred between parties. The engine evaluates the language of every clause against multiple risk vectors — not just obvious indemnity clauses, but also subtle mechanisms like deemed acceptance provisions, fitness-for-purpose obligations, and uncapped consequential loss exposure.
What Gets Analysed
The risk transfer engine examines:
- Liability allocation and limitation mechanisms
- Indemnity scope, triggers, and carve-outs
- Financial exposure including liquidated damages, caps, and uncapped obligations
- Insurance adequacy relative to risk allocation
- Warranty and defect liability provisions
- Consequential loss exclusions or inclusions
What You Receive
Per-clause risk scores with severity ratings (Critical, High, Medium, Low), confidence levels, extracted monetary values, and a clear explanation of which party bears the risk and why it matters commercially.
Ambiguity Assessment
Flags clauses with unclear, contradictory, or incomplete drafting across 14 ambiguity types — temporal, referential, definitional, conditional, syntactic, and more. Dual-type classification with confidence scoring.
Clause-Level14 Ambiguity Types Detected
The engine classifies ambiguity into precisely defined categories — not vague observations, but specific, actionable findings that explain exactly what type of drafting deficiency exists and why it creates commercial risk.
- Temporal ambiguity — unclear timeframes, deadlines, or sequencing
- Referential ambiguity — unclear cross-references or pronoun targets
- Definitional ambiguity — undefined or inconsistently defined terms
- Conditional ambiguity — unclear trigger conditions or prerequisites
- Syntactic ambiguity — sentence structure that permits multiple readings
- Scope ambiguity — unclear boundaries of obligation or entitlement
Dual-Type Classification
Each finding is classified with up to two ambiguity types, capturing clauses where multiple drafting deficiencies compound. Confidence scores indicate the engine's certainty in each classification, enabling teams to prioritise review effort where it matters most.
Unfair Contract Terms
Assesses terms against the Australian Consumer Law unfair contract terms framework (s.23–28). Applies the statutory three-limb test per term: significant imbalance, not reasonably necessary, detriment if relied upon.
Clause-LevelStatutory Framework
Following the 2022 amendments to the Australian Consumer Law, unfair contract terms in standard form contracts are now void and carry significant penalties. Stact applies the full statutory test to every clause, identifying terms that may be at risk under the current legislative framework.
Three-Limb Test Applied Per Term
Each term is assessed against the three statutory requirements:
- Significant imbalance — does the term create a material imbalance in the parties' rights and obligations?
- Not reasonably necessary — is the term necessary to protect the legitimate interests of the advantaged party?
- Detriment — would the term cause detriment (financial or otherwise) if relied upon?
Why It Matters
Since November 2023, unfair contract terms carry penalties of up to $50 million per contravention for corporations. Stact's UCT analysis identifies exposure before it becomes a dispute — giving principals, contractors, and legal teams a clear picture of enforcement risk in their standard form agreements.
Risk Interaction
Detects how risk findings in one clause amplify or contradict findings in another. Builds cross-clause reference graphs showing dependency chains, circular references, and transitive risk paths.
Cross-ClauseBeyond Single-Clause Analysis
Most contract review tools analyse clauses in isolation. But real commercial risk rarely lives in a single clause — it emerges from the interaction between clauses. A liability cap in one section may be undermined by an indemnity in another. A time-bar provision may conflict with a notice regime elsewhere in the contract.
What Gets Detected
The interaction engine identifies:
- Amplification — where risk findings in separate clauses combine to create greater exposure than either alone
- Contradiction — where clauses allocate risk in conflicting directions
- Dependency chains — where clause A modifies clause B, which in turn affects clause C
- Circular references — where cross-references create logical loops
- Transitive risk paths — where risk propagates through multiple clauses via indirect connections
Output
A cross-clause dependency graph showing how risk flows through the contract, with interaction severity ratings and clear explanations of the commercial impact of each interaction.
Ambiguity Interaction
Identifies where vague language in one clause creates interpretive conflict with another. Detects compounding ambiguity where two individually tolerable issues combine to create material uncertainty.
Cross-ClauseCompounding Ambiguity
A clause that is slightly unclear in isolation might be perfectly manageable. But when that same clause interacts with another ambiguous clause, the combined uncertainty can create material interpretive risk — the kind that leads to disputes, delays, and cost overruns.
What Gets Detected
The ambiguity interaction engine identifies:
- Definitional conflicts — where a term is defined differently (or left undefined) across clauses
- Temporal misalignment — where timeframes in different clauses create impossible or unclear sequences
- Scope overlap — where the boundaries of obligations in different clauses are unclear or contradictory
- Conditional chain breaks — where conditions in one clause depend on triggers in another clause that are themselves ambiguous
Why It Matters
Ambiguity interactions are the hidden risk in construction contracts. They are invisible to single-clause review methods and are frequently the root cause of interpretation disputes that end up in adjudication or litigation.
Security of Payment
Assesses payment provisions against state/territory SOP legislation. Checks progress payments, timing, reference dates, interest, suspension rights, and pay-when-paid voidability.
Contract-LevelJurisdiction-Specific Analysis
Security of Payment legislation differs significantly across Australian states and territories. Stact analyses payment provisions against the specific legislation that applies to your contract's jurisdiction — not a generic national standard that doesn't exist.
What Gets Checked
The SOP engine examines:
- Progress payment entitlements — are statutory rights to progress payments preserved or undermined?
- Payment timing — do contractual payment periods comply with legislative maximums?
- Reference dates — are reference dates properly established for payment claim purposes?
- Interest on late payment — does the contract address interest entitlements consistently with legislation?
- Suspension rights — are statutory suspension rights for non-payment preserved?
- Pay-when-paid clauses — are conditional payment provisions void under applicable legislation?
All 8 Jurisdictions Supported
Full coverage across NSW, VIC, QLD, WA, SA, TAS, NT, and ACT — each with jurisdiction-specific legislative references, thresholds, and compliance requirements built into the analysis engine.
Benchmark Scoring
Compares the contract clause-by-clause against a scored benchmark corpus of comparable Australian construction contracts. Multi-stage assessment with percentile computation. Benchmark score 0–100, grades A–F.
Contract-LevelCorpus-Grounded Comparison
Stact maintains a curated benchmark corpus of Australian construction contracts — scored, classified, and structured at the clause level. Your contract is compared against this corpus to determine where it sits relative to market norms, not against abstract best practice that no one can define.
Multi-Stage Assessment Pipeline
The benchmark pipeline runs four stages:
- Clause matching — each clause is matched to comparable clauses in the benchmark corpus by topic and function
- Score computation — clause-level scores are computed based on how the clause compares to the benchmark distribution
- Percentile ranking — each clause is assigned a percentile position relative to comparable clauses in the corpus
- Aggregate scoring — clause scores are aggregated into an overall Benchmark Score (0–100) with letter grade (A–F)
What You Receive
An overall Benchmark Score and grade, per-category percentile breakdowns, and clause-level comparisons showing exactly where your contract is better or worse than market norms — with the actual corpus language as evidence.
Omission Detection
Detects protective clauses that should exist but are absent. Checks across EOT, delay costs, LD caps, payments, liability caps, insurance, latent conditions, force majeure, dispute resolution, and much more.
Contract-LevelWhat's Missing Matters as Much as What's There
Traditional contract review focuses on what the contract says. But some of the most dangerous risks come from what it doesn't say. A missing force majeure clause, an absent liability cap, or a gap in the dispute resolution framework can create more exposure than a poorly drafted clause.
Contract Types Covered
Omission checks span nine contract types:
- Design & Construct (D&C)
- Construct Only (Traditional / DBB)
- EPC (Engineering, Procurement, Construction)
- EPCM (Engineering, Procurement, Construction Management)
- PPP / Concession (DBFM, DBFOM)
- Alliance Contracting
- Managing Contractor / Construction Management
- Early Contractor Involvement (ECI)
- Lump Sum / Fixed Price
Standard-Form & Contract-Type Aware
Omission checks are calibrated to both the standard form and the contract type. What's expected in an AS 4000 construct-only contract is different from a GC21, a FIDIC Silver Book EPC, or a bespoke D&C agreement. Stact applies the right checklist across 100+ standard form varieties and all major contract types.
Negotiation Playbooks
Generates structured negotiation strategy grounded in real corpus clause language. Three modes — pragmatic, balanced, and aggressive. Per finding: fallback, compromise, walk-away line, and talking points.
StrategyNot Generic Advice — Corpus-Grounded Strategy
Stact's negotiation playbooks don't offer vague suggestions. Every recommendation is grounded in actual clause language from the benchmark corpus — showing you what comparable contracts actually say, at different quality levels.
Three Negotiation Modes
Select the strategy that matches your commercial position:
- Pragmatic — minimum viable improvements using commonly accepted language. Designed to succeed in competitive tender situations where aggressive pushback risks disqualification.
- Balanced — meaningful improvements that bring the contract to a fair middle ground. Suitable for negotiated contracts and repeat client relationships.
- Aggressive — maximum contractor protection using the strongest available language. Appropriate where the contractor has leverage or the risk profile demands it.
Per-Finding Strategy
For every risk finding, the playbook provides:
- Recommended position — the ideal clause language, sourced from the corpus
- Fallback position — the next-best alternative if the primary ask is rejected
- Compromise language — middle-ground wording that addresses the core risk
- Walk-away line — the minimum acceptable outcome below which the risk is unmanageable
- Talking points — plain-English arguments to support each position in negotiation
Chat with ARI
Meet ARI — your personal contract assistant. Ask a question about your contract in plain English and get a precise, clause-referenced answer in seconds. It's like having a senior contract specialist on your team, 24/7.
InteractiveMeet ARI
ARI is your Artificial Risk Intelligence — but think of ARI less as a feature and more as a member of your team. ARI has read every clause, knows every cross-reference, and understands the legislation that applies to your contract. When you have a question, you don't search — you ask ARI.
How ARI Works
ARI provides contextual, clause-referenced answers:
- Ask anything — "What happens if the contractor is delayed by a force majeure event?", "What are my notice obligations under clause 34?"
- Grounded in your contract — every answer is sourced directly from the actual clause text, with references
- Context-aware — ARI understands the relationships between clauses, cross-references, and defined terms
- Jurisdiction-aware — ARI incorporates relevant state and territory legislation, especially for SOP and UCT matters
When to Chat with ARI
ARI is designed for real-time contract intelligence:
- You're in a tender meeting and need a quick answer — ARI is already across the contract
- You're on site and need to check a notice obligation — ARI responds in seconds
- Your legal team is reviewing an unfamiliar contract form — ARI knows it inside out
- A junior team member needs to understand a complex clause — ARI explains it clearly
Member Discussion Forum
Start clause-level discussions with your project team — raise concerns, flag risks, and resolve issues directly against the contract terms that matter.
CollaborationTeam Review, Clause by Clause
The Member Discussion Forum is Stact's built-in team collaboration layer. It lets project members post comments, raise concerns, and have structured conversations against specific clauses — so nothing gets lost in email threads or disconnected chat channels.
How It Works
The forum is designed for clause-specific collaboration:
- Clause-specific threads — every discussion is pinned to a specific clause, sub-clause, or finding
- Category-based notifications — team members assigned to a contract category are automatically notified when a discussion is raised in their area
- Cross-functional visibility — commercial leads see the payment discussions, legal sees the liability threads, project directors get the full picture
- Audit trail — every comment, response, and resolution is timestamped and attributed
Use Cases
The forum supports the full contract lifecycle:
- A contract manager flags a payment term and the commercial team discusses the risk before negotiation
- Legal raises a concern about an indemnity clause — the project director weighs in with commercial context
- During tender review, the team collaboratively works through flagged issues without switching between tools
- Post-award, the delivery team uses clause discussions to track and resolve contract administration questions
Contract Health Score
A single aggregated score that captures the overall risk position of your contract — computed using a weighted-average-with-floor methodology across all analysis packs.
DashboardHow the Score Works
The Contract Health Score is not a simple average. It uses a weighted-average-with-floor methodology — meaning a catastrophic score in any single category cannot be hidden by strong performance elsewhere. If one pack identifies critical exposure, the overall score reflects that reality.
What's Included
The score report provides:
- Overall Contract Health Score with letter grade (A–F)
- Per-pack weighted scores showing contribution to the overall picture
- Severity distribution across all findings (Critical, High, Medium, Low)
- Risk category breakdown — liability, payment, time, scope, and more
Per-Clause Risk Reports
Every clause receives individual risk, ambiguity, and UCT scores with severity ratings, confidence levels, and extracted commercial data points — dollar amounts, dates, and percentages.
Clause-LevelGranular, Clause-by-Clause Findings
Each clause in the contract is assessed independently across three analysis engines. The output is not a paragraph of commentary — it's a structured finding with machine-readable fields designed for filtering, sorting, and prioritisation.
Per-Finding Data Points
Every finding includes:
- Severity rating — Critical, High, Medium, or Low
- Confidence score — how certain the engine is in its classification
- Risk vector — which category of commercial risk is affected
- Extracted values — dollar amounts, day counts, cap percentages, dates
- Clause reference — exact location in the contract with cross-references
- Plain-English explanation — what the finding means commercially
Filterable & Sortable
All findings can be filtered by severity, analysis type (risk, ambiguity, UCT), clause number, or risk category. Sort by severity to see the worst issues first, or by clause to review sequentially.
Benchmark Report
How your contract compares to real Australian construction agreements — not abstract best practice. Overall score, per-category percentile rankings, and clause-level corpus comparisons.
Market PositionMarket Context for Every Clause
The Benchmark Report tells you where your contract sits relative to comparable Australian construction contracts. Instead of 'this clause is risky,' you see 'this liability clause is more contractor-adverse than 85% of comparable clauses in the benchmark corpus.'
What's Included
The benchmark report provides:
- Overall Benchmark Score — 0–100 with letter grade (A–F)
- Per-category percentile rankings — liability, payment, time, scope, etc.
- Standard Form Deviation analysis — how far your contract has drifted from the standard form it's based on
- Clause-level comparisons — side-by-side with actual corpus language at different quality tiers
- Corpus grounding — every comparison backed by real contract language, not generated text
Why It Matters
Knowing that a clause is 'risky' is not enough. Knowing that it's worse than 90% of comparable contracts gives your negotiation team the evidence they need to push for better terms — with data, not opinions.
Negotiation Playbook
A structured negotiation strategy for every finding — grounded in real corpus clause language, not generic advice. Three modes, per-finding positions, and ready-to-use talking points.
StrategyActionable Negotiation Strategy
The Playbook doesn't just tell you what's wrong — it tells you exactly what to ask for, what to accept, and when to walk away. Every recommended position includes actual clause language sourced from the benchmark corpus.
Three Modes
Each finding generates strategy at three levels:
- Pragmatic — minimum viable improvements for competitive tenders
- Balanced — fair middle ground for negotiated contracts
- Aggressive — maximum protection when leverage permits
Per-Finding Output
Every finding includes:
- Recommended position with corpus-sourced clause language
- Fallback position if the primary ask is rejected
- Compromise language addressing the core risk
- Walk-away line — the minimum acceptable outcome
- Plain-English talking points for each position
Omission Report
76 checks across all major standard forms identifying protective clauses that should exist but don't — covering EOT, delay costs, LD caps, payments, insurance, force majeure, and more.
CompletenessWhat You Receive
A structured report identifying every protective clause or provision that should be present in your contract but isn't. Each omission is assessed individually, severity-rated, and linked to its commercial impact — giving you a clear, prioritised picture of what's missing.
Per-Omission Finding
For every identified gap, the report provides:
- What's missing — the specific protective clause or provision that is absent
- Why it matters — the commercial risk created by the absence
- Expected provision — what comparable contracts typically include, drawn from real corpus data
- Severity rating — critical, high, medium, or low — based on the likely commercial exposure
- Suggested language — recommended clause wording sourced from the benchmark corpus
How It Connects
Every omission finding feeds directly into the Negotiation Playbook. Where a protective clause is missing, the playbook provides ready-to-use insertion language at three strategy levels — pragmatic, balanced, and aggressive — so you can negotiate the gap closed, not just identify it.
Obligation Timeline
Every contractual obligation extracted with jurisdiction-aware date computation. Gantt-style visual timeline plus structured list — with Australian state business day calendars built in.
Post-AwardEvery Obligation, Every Deadline
Once a contract is signed, the obligations begin. The Obligation Timeline extracts every time-bound commitment from the contract and maps it against real calendar dates — accounting for weekends, public holidays, and state-specific business day rules.
What's Included
The timeline provides:
- Gantt-style timeline — visual representation of all obligations across the contract duration
- Structured obligation list — every obligation with clause reference, trigger, deadline, and responsible party
- Jurisdiction-aware dates — computed using Australian state/territory business day calendars
- All 8 jurisdictions — NSW, VIC, QLD, WA, SA, TAS, NT, ACT with public holiday awareness
- Dependency mapping — which obligations trigger or depend on other obligations
Why It Matters
Missing a notice deadline by one business day can cost millions in lost entitlements. The Obligation Timeline ensures your project team knows exactly what's due, when, and what the consequences of missing it are — before it's too late.
See Every Analysis in Action
Walk through a live contract analysis with our team. 30 minutes, no obligation.
Book a Demo