Skip to main content

Product

Follow one agreement from signing day to finished work

Nebula reads the agreement, builds the plan and holds every deadline, claim and clause while the work is delivered.

Get started

The sample agreement

Signing day

Transformer delivery and commissioning

A supply and commissioning agreement between a principal and a provider, eighty pages of promises, dates and money.

From the obligations

The Provider shall complete commissioning by the end of week 36.

The agreement's own words, kept

Nebula takes it from here.

Reading assurance

People decide what changes the record.

See results

The walk begins

Signing day. Nebula reads all of it

Most agreements are read twice: the day they are signed and the day something goes wrong. This one is about to be read for good.

Reading

Read the work as a whole

Nebula finds responsibilities, dates and amounts, each carrying a source quote.

Source quote
required for each reading result
Clear actions
drawn from the documents
Product / ReadingSwipe to inspect
WHAT NEBULA READSWHAT NEBULA FOUNDTransformer delivery and commissioning80 pages / Section 4 / obligationsTHIS AGREEMENT is between the Principal and the Providerfor the supply, delivery and commissioning of thetransformer described in Schedule 1, on the terms below.2.DELIVERY2.3The transformer is delivered to site in week 30.Transport, access and cranage are in Schedule 2.2.6Risk passes to the Principal on delivery.4.OBLIGATIONS4.7The Provider shallcomplete commissioning by the end of week 36.The commissioning tests are set out in Schedule 5.6.CLAIMS AND PAYMENTEach claim is made against the Payment Schedulewith a valid tax invoice, exclusive of GST, and:6.2The Principal responds to a claim in 10 business days.The response and its reasons stay on the record.6.4The responded amount is payable in 30 days.8.VARIATIONSA variation is priced and approved before the workproceeds, and its programme effect is stated.12.GENERALWarranties, insurance and notices are in Schedule 6.readingOBLIGATIONDeliverableTransformer to site, week 30OBLIGATIONMilestoneCommissioning, end of week 36DETAILResponse windowRespond within 10 business daysDETAILPaymentResponded amount, 30 days

Week 1The reading becomes the shared delivery plan.

Delivery plan

Build a plan from supported requirements

Supported requirements become plan items, so the plan starts from the documents rather than a blank page.

Supported readings
eligible to become plan items
Draft for review
unresolved ownership or confidence
What stays in draft

A requirement with uncertain ownership or a low-confidence reading stays in draft for review rather than entering the plan unchecked.

Product / Delivery plan
/projects/transformer-delivery/plan

The agreement’s delivery plan

Plan items

6

Draft

2

Accepted

4

Plan changes

  • 09:12Plan item acceptedM1 · Design and shop drawings
  • 08:40Responsibility assignedCalder Transformer Services
  • 06:00Draft held for reviewOutage window · Schedule 1
  • Week 1Plan built from the reading6 milestones · clause 4.7
  • Week 1Deadline registeredCommissioning · end of week 36

Week 9The switchgear slips a fortnight. The planned path rebuilds from the movement.

Schedule

See the planned critical path

Nebula calculates planned dates from dependencies and shows the path that sets the finish.

Critical work
the path that sets the scheduled finish
Unscheduled
work with incomplete dates
What scheduling draws on

Planned dates come from the dates and durations the documents provide. Work with incomplete dates stays unscheduled rather than guessed.

Product / ScheduleSwipe to inspect
CRITICAL PATHIllustrative scheduleWk 061218243036planned finish · wk 36 · 4.7Design and drawingsM1Switchgear supplyPO-02Transformer build and FATM2Delivery to siteM3InstallationM4CommissioningM5 · wk 36Controls the scheduled finishHas scheduling flexibilityThe fortnight slip recalculates later work

Week 12The first claim arrives. The money is watched before it moves.

Money

Track claims, payments and budget

Track claim states, payment records, budget values and retention.

Claim status
submission, review and payment records
Budget
recorded value and changes
How retention is estimated

Retention is estimated from the rate the documents state. Without a usable rate, Nebula holds no figure rather than inventing one.

Product / MoneySwipe to inspect
PAYMENT AND BUDGETIllustrative claim pathClaim progress to paymentClaim submittedmay be linked to a payment milestonePayment duecertified amount recordedPaidpaid amount matches the certified amountIllustrative budget positionUsed to dateAgreed budgetBudget change recordedcompare the current figureProgress comparison shown when inputs are availableDocument terms inform payment schedules and retention estimatesSubmitted to payment due to paid

Week 14A response window opens, and it is watched for you.

Deadlines

Check trusted deadlines

Scheduled every 15 minutes, checks record reminder stages and apply the configured next step for trusted deadlines.

15 min
configured check cadence
Trusted dates
required for automatic action
Product / DeadlinesSwipe to inspect
DEADLINE CHECKScheduled every 15 minutesTime allowed to respondNebula can record each configured reminder stagewindow opensREMINDER50% of windowWARNING75% of windowFINAL90% of windowReminder attempt recordedREMINDER at 50%Warning attempt recordedWARNING at 75%Final notice attempt recordedFINAL at 90%Responsiveness -5NO RESPONSE OUTCOME RECORDEDConfigured stages at 50 / 75 / 90 percentTrusted missed responses can affect responsiveness

Unsupported timing stays unknown

When a payment notice has no source-stated calendar response date, Nebula keeps the response-window state UNKNOWN and tells the user to check the notice and source document.

If it tightensA response can harden into a dispute. The record is ready without drama.

Formal notices

Builds notices from agreement requirements and records acknowledgement.

Disputes

Keeps grounds, positions, evidence, timelines and outcomes together.

Exports

Creates CSV, PDF, Word and ZIP files with audit and proof references.

YOUR CONTROLS

Week 17 · A variation arrives

You stay in control

Choose the read, steer another pass, correct the record and confirm consequential work.

These controls do not bypass authority. Scope, cost and time changes still use the authorised change process.

  1. CHOOSE

    Choose the read

    Select an available model and scope before a reading begins.

  2. STEER

    Steer another pass

    Point the next pass to a clause, risk or missing fact.

  3. CORRECT

    Correct the record

    Save a correction within your authority. The original words and author remain.

  4. CONFIRM

    Confirm what changes

    Review consequential work before it enters the shared record.

Any morningOf everything in motion, a few things need you.

Companion

See a short delivery brief

Nebula summarises recorded work, deadlines, disputes and payment status in an engagement brief and a portfolio summary.

Engagement brief
linked back to the work
Portfolio summary
across recorded engagements
Product / Companion
An illustrative Companion cycles through managing, needs-attention, at-risk and verified engagement states.

All along

Keep the tools. Connect the engagement

Before connection, administrators see Connect or Platform setup required. Nothing here claims a working link until one is made.

Microsoft 365
Identity, documents and team collaboration
Google Workspace
Identity, files, mail and calendar context
Xero
Financial context and payment records
QuickBooks Online
Invoices, payments and time activity
MYOB
Company files, invoices and timesheets
Procore
Projects, documents and field activity
Oracle Aconex
Document revisions and correspondence

Other connected systems send approved events through webhooks

Nebula view

One current view of delivery

Source attached, visible to the right people and kept current.

Week 36Commissioning completes. Delivery becomes proof.

Proof

Check an event record

A recorded event creates records on two networks, each publicly checkable with its anchor ID.

Up to 2
external confirmation records
No account
needed for a public check
When anchoring runs

Anchoring runs where the engagement's configuration enables it. The two submissions are independent, and each record is checked on its own anchor ID.

Product / ProofSwipe to inspect
CONFIRMATION RECORDSConfirmation reported independentlyRECORDED EVENTAccepted status recordedtwo records, made independentlyPUBLIC NETWORKPublic confirmationanyone can check itno account neededINDEPENDENT RECORDNebula confirmationthe event’s details, keptlinked back to the workBoth checks completeEach available confirmation is checked separately.

Reputation

See a recorded reputation profile

Nebula keeps one five-area reputation profile for each organisation, moved only by recorded events.

5 areas
in one organisation profile
Recorded events
the input to a score change
Product / ReputationSwipe to inspect
REPUTATIONUpdated from recorded activityElite90Established80Trusted70Emergingstarting point 75Reliability96Timeliness90Responsiveness83Collaboration78Documentation76OVERALL8575798285EstablishedSCORE95+90+80+70+<70Five areas combine into one organisation score.Marketplace directory: tier first; approved detail on request

See recorded activity and retained standing

The record separates the last 30 days of recorded activity from retained standing across current engagements. It lists records to review, uses no estimates and offers the same evidence through Take this record.

After the finish

The next work finds you

A finished engagement rolls into the next one with its history intact.

Find work and continue together

Opportunities and tenders

Browse or post. Tender and revise in one trail. An award opens a shared engagement; agreement still requires acceptance.

Browse opportunities

Marketplace choice

Start with the tier, then ask for the detail

In the signed-in marketplace, Nebula groups organisations by recorded reputation tier and identifies those with no recorded history. Ask for the scores out of 100 and recent reputation events; an owner or administrator at the other organisation approves or declines the release.

  1. 01 Recorded tier
  2. 02 Request detail
  3. 03 Approved release

You have walked one agreement, and yours is next

Start with the documents. Work privately, invite collaborators or run parallel engagements with Business.

Sign upTalk to us