Use cases
Built for the projects that carry real obligations.
Construction, infrastructure, property, defence and commonwealth, insurance, energy, and the supply agreements between them. Each section states the project, what it brings, and what Nebula returns. The same engine carries any defining document with parties, money and dates.
Reads whatever defines the work
Contracts, scopes of work, technical specifications, requirements, briefs, MSAs and design documents.
01 · Construction
The head contract states the dates. The delivery runs a clause behind them.
The documents know everything. Practical completion, separable portions, liquidated damages rates, progress claim windows: the head contract, its schedules and the specifications state them all. The tracking lives in spreadsheets that drift from the signed words within a month.
See the engines that run thisThe project brings
Nebula returns
A head contract with portions, milestones and liquidated damages rates
Every commitment extracted with its clause, date and amount, then watched on a 15-minute cycle
Extension-of-time claims and variations in flight
Each change recorded against the dates it moves, signed by both parties before it takes effect
Progress claims on a contractual window
Claim windows watched; the reminder lands before the window, the escalation after it
Arguments over which version is in force
The version in force is the one both parties signed; originals preserved in the audit trail
02 · Infrastructure
Programs outlive the people who set them up.
The record must hold without a custodian. Multi-year delivery, staged approvals and regulatory acknowledgements span teams, contractors and turnover. Whatever was agreed in year one must still be provable, current and sequenced in year four.
How the record holds its shapeThe project brings
Nebula returns
A program of staged milestones and approvals
A sequenced record: each commitment linked to what depends on it, re-planned when anything moves
Regulatory acknowledgements with statutory dates
Dated obligations watched around the clock; escalation on slip
Handovers between delivery teams
One record for both parties, every version preserved with its author and time
Board and regulator reporting
The audit trail, exportable on the day it is asked for
03 · Property development
Every project is a web of consultant agreements.
The developer holds the exposure. Architects, engineers, certifiers, agents and builders each hold an agreement with their own deliverables, fees and dates. When one slips, the slip lands on the development program.
Check a claimed recordThe project brings
Nebula returns
A dozen consultant agreements on one development
Each agreement read into the same record; deliverables, fees and dates in one view
Milestones that gate finance drawdowns
Dated commitments with their dependencies; the exposure is visible before the drawdown call
Counterparties of unknown reliability
Track records built from anchored delivery events, checkable without an account
Disputes near settlement
Counter-offers bounded at three rounds, then escalation; the signed version governs
04 · Defence and commonwealth
The pack matches the sector. The engine stays the same.
Conventions are first-class. Classification levels, approval thresholds and extension-of-time conventions are built into the defence, commonwealth and infrastructure packs. The same record, sequencing and proof run underneath.
Read the security pageThe project brings
Nebula returns
OFFICIAL: SENSITIVE material in the documents
A classification recorded on every commitment; the handling posture stated plainly on the security page
Approval thresholds by delegation
Approvals tracked as dated obligations, each grounded to the clause that requires it
Extension-of-time conventions
EOTs as first-class changes, signed by both parties before effect
Procurement diligence
SOC 2 controls and IRAP-aligned matrices under NDA; data resident in Sydney
05 · Insurance
Every claim is a bundle of deadlines the insurer answers for.
The policy states the clock. Acknowledgement windows, assessor appointments and repair milestones all carry dates, delivered through a panel of builders and assessors the insurer does not control. The breach lands on the insurer either way.
See the engines that run thisThe project brings
Nebula returns
A panel of builders and assessors on service agreements
Each agreement read into one record; response times watched per claim
Code and policy response windows
Dated obligations with the reminder before the window and the escalation past it
Panel suppliers of mixed reliability
Track records from anchored delivery events, visible before assignment
Disputed scopes of repair
Counter-offers bounded at three rounds; the signed scope governs
06 · Energy and utilities
Connection dates, outage notices and restore times, across contractors.
The network does not wait. Connection agreements, planned outage notice periods and maintenance contracts with restore times span years and contractors. The dates are contractual; the tracking is usually a spreadsheet per depot.
How the record holds its shapeThe project brings
Nebula returns
Maintenance contracts with response and restore times
Every window watched around the clock; escalation on breach
Planned outage notice periods
Notice deadlines as dated obligations, reminded before they fall due
Multi-year contractor panels
Reliability scores built from delivered work alone
Variations on connection works
Each change signed by both parties before it takes effect
07 · Supply and service agreements
The service credit is only as good as the record behind it.
Credits and penalties turn on proof. Supply agreements and facilities contracts carry response times, uptime commitments and delivery windows. When the credit is claimed, the argument is over whose record counts.
Check a claimed recordThe project brings
Nebula returns
Response and restore times in a facilities contract
Each window watched; the breach record kept with its evidence
Service credits that turn on proof
Anchored events neither side can rewrite after the fact
Rolling renewals and price variations
Changes recorded and signed by both parties before effect
Supplier scorecards built by hand
Reliability scores from delivered work alone
These projects already have the documents. Start there.
Sign up and upload one, or talk to us about rolling Nebula across a portfolio.