Product
Hold the agreement as one record. Bring people in. Keep changes and payment on that record, with less time spent chasing the pieces.
The sample agreement
Open the reading
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.
Words kept from the agreement
The walk begins
Start from the signed documents, not another round of copying them into tasks. Review the work, responsibilities and dates the documents wrote, then put the team to work.
Reading assurance
You decide what changes the record.
Reading
Nebula brings together responsibilities, dates and amounts from the documents, with the original wording beside each finding.
Week 1The reading becomes the shared record.
The record
When you accept a requirement, it becomes part of the record. The source stays attached.
A requirement with uncertain ownership or a low-confidence reading stays in draft.
Source review
2 readings remain in draft
Supported
4 plan items
Plan items
6
Draft
2
Accepted
4
Plan changes
Useful preparation
Reports, work orders and notice drafts can start from the job already in Nebula. For technical work, Nebula turns a prompt or your documents into a drawing to review and edit.
The electrical single-line diagram comes first, as a DWG drafted natively in AutoCAD, with mechanical and other drawings to follow. Anything the documents leave unanswered is marked for your decision.
You decide the downstream protection not stated in the source.
You see no device, rating, curve or setting in the source, so the drawing leaves this open.
Week 3One deliverable needs a specialist.
Nebula drafts a one-page work order from the accepted record. Agree the scope and terms, then bring verified work back onto the same record.
Quotes and offer terms stay private to the organisation. The head project's deadlines do not move.
The subcontract rests only on wording both parties signed.
See what is holding up delivery and awaiting a payment response. Claims, approvals and part-payments keep their history, so the next conversation starts with the position in front of you.
Weeks 9 to 14The switchgear slips, the first claim arrives and a response window opens.
Schedule
What needs to finish first, what depends on it, and which delay would move the recorded finish.
Dates come from the dates and durations the documents provide. Work with incomplete dates stays unscheduled.
Money
Claims, approvals, paid amounts and what is still unpaid stay on the same record.
Retention is estimated from the rate the documents state. Without a usable rate, there is no figure.
You submit a payment claim, record the schedule and certification, and carry any shortfall forward until it is discharged.
Every position keeps its date, and Nebula moves no money; your later dispute opens on the recorded history.
Deadlines
Trusted deadlines are checked every 15 minutes. Follow-up is prepared for review, not sent.
Unsupported timing stays unknown
When a payment notice has no source-stated calendar response date, Nebula keeps the response-window state UNKNOWN and tells you to check the notice and source document.
A missed date sends nothing by itself. You review every follow-up after Nebula confirms the current state, certainty, sender authority and notification route.
Nebula checks trusted deadlines every 15 minutes, records each reminder stage and holds every follow-up for your review.
You read the programme ahead through the forward pass, and each approaching bottleneck arrives as a finding for you to act on.
Your deliverable within five days of its deadline with no evidence attached raises its own alert. The pass writes nothing on its own, and every alert names what produced it.
A response can harden into a dispute. Your record is ready without drama.
Required notices build from the agreement, with acknowledgement recorded.
A suspension right is exercised from the clause window the agreement states.
A defect notice carries its rectification date and evidence.
Grounds, evidence and outcomes stay on one dispute.
CSV, PDF, Word and ZIP files with audit and proof references.
You serve a formal notice with its reference number, your signature and its proof reference in one act, with the notification outcome recorded beside it.
Whichever surface you serve from, the notice carries the same reference, signature and proof reference.
When an item is contested, you generate a dispute brief that holds the chronology, the agreement analysis, the submitted position and an evidence summary in one document.
The brief is marked as a Nebula reading, for your review, and it never stands as impartial evidence.
You export the agreed reading as one document that renders only what both parties signed, and an audit bundle containing its audit report, index and available proof bundles.
An insurance pack summarises the current delivery record, parties, item states, active packs and available proof references.
Week 15The slip needs more time, and the scope has grown.
When a variation is signed, work, budget and schedule update together. An unsigned change is not in.
The effect on price and programme is visible before agreement.
A lodged claim stays the stated position until the response is recorded.
YOUR CONTROLS
Week 17 · A variation arrives
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 that applies to you.
Select an available model and scope before a reading begins.
Point the next pass to a clause, risk or missing fact.
Save a correction within your authority. Keep the original words and author.
Review consequential work before it enters the shared record.
Any morningOf everything in motion, a few things need you.
Companion
A prepared brief for one project or across the portfolio, with the work behind each update a step away.
Nebula
Microsoft 365Identity, documents and team collaboration
Google WorkspaceIdentity, files, mail and calendar
XeroFinancial context and payment records
QuickBooks OnlineInvoices, payments and time activity
MYOBCompany files, invoices and timesheets
ProcoreProjects, documents and field activity
Oracle AconexDocument revisions and correspondenceConnections require setup and permission for the sources you choose. Other systems can send approved events.
Finished work leaves more than a folder behind. The delivery history stays with the business, with confirmed outcomes to support its reputation and a record the next team can build on.
Week 36Commissioning completes. Delivery becomes proof.
Proof
A recorded event creates records on two networks, each checkable with its anchor ID.
Anchoring runs where the project configuration enables it. Each record is checked on its own anchor ID.
Reputation
The five-area profile changes only when a recorded event supports it.
See the last 30 days of recorded activity apart from the standing you have retained across current engagements. Work through the records it lists for review, and take the same evidence with you through Take this record.
After the finish
Take a finished engagement into the next one with its history intact.
Your tender trail stays connected after award
Your posting, tender and revisions stay in one trail. An award opens your shared engagement; the resulting agreement still requires acceptance.
Your counterparty-confirmed delivery record can match you to opportunities by service region and engagement value. Self-reported profile fields do not affect that match.
Browse opportunitiesMarketplace choice
See organisations grouped by recorded reputation tier in the signed-in marketplace, and which have no recorded history. Ask for the scores out of 100 and recent reputation events; an owner or administrator at the other organisation decides the release.
Bring the agreement you are working from. See the instrument Nebula holds, then bring your team into the job.
