01 A clearer start
The job plan, from what you agreed
Nebula turns agreement details into linked work, responsibilities and dates for the people doing the job to review.
Defend the intent you already gave
Who acts on it when you are not in the room?
A machine, an agent or another person will spend what you allowed if that intent lives in their system. Nebula holds it. On a signed job that is the work and the spend, kept on the agreement until close-out.
Project
Prepared and connected.
Where it stands
What needs you
Human steerWho is involved
Delivery items
6 commitmentsOn the job
Nebula helps turn project documents into a plan, useful drafts, current dates and a record the next person can pick up.
01 A clearer start
Nebula turns agreement details into linked work, responsibilities and dates for the people doing the job to review.
02 A useful first draft
Start a scope of work or technical report from an editable draft, with requirements, responsibilities and source references ready for specialist review.
03 Changes stay connected
When both parties approve a variation, Nebula updates affected work and recalculates the schedule. The change and its history stay together.
04 A handover with context
Decisions, evidence, approvals and recorded payment status stay with the job. Both parties can follow what changed and what still needs doing.
14 public agreements and terms read across Australia, United States and New Zealand. Each reading keeps its source and a checkable hash.
For machines and for people
The running record stays up when people change. Ask it directly. Reuse what is already known, trace it to the source and share a record others can check.
Structured information your tools can use, without someone rebuilding the story.
“The Provider shall complete commissioning by the end of week 36.”
Keep the source beside the work. See where a requirement came from, not just a summary of it.
Share the record, not a rewrite. Print the hash on the page. If you give permission, another person or another agent can look that hash up in Nebula and see the current record.
Paste a hash at Verify. That check confirms the hash. It does not open the private job.
Illustrative record. Private work stays permission-controlled.See the readings the record is built on
The work
The documents write when the record begins. Delivery is not the start.
Scope, schedule, change and payment live together. When a lead is away, that record is still the place to look.
Work, money and time move together, or the change is not in.
Payment follows verified events. Warranty can keep living after handover.
Source · clause 4.7
“The Provider shall complete commissioning by the end of week 36.”
Exact wording stays attached
Project
Prepared and connected.
ReviewWhere it stands
What needs you
Human steerWho is involved
Find obligations, dates and money. Steer the reading and correct the record.
Explore readingReview requirements, set the plan and produce supported deliverables. Nothing becomes accepted without your decision.
See plan and productionSee what changed and who acts next. Keep the basis for each decision visible.
See delivery controlKeep reviewed evidence with the work. Some events become checkable records, not verdicts.
See proof and records
Decisions
Use your experience to guide and make decisions.
Project Agreement · clause 4.7
The Provider shall complete commissioning by the end of week 36.
Prepared for your review
The commissioning requirement is ready to enter the plan. Accept it or send it back with a correction.
Possible outcomes
Who it is for

You are the name on the delay and the certificate. The record stays up when you are not in the room.
See the record
Do not certify a claim off a chat. Hand over the record, the decisions and the unfinished work.
See what carries forward
See the same story the contractor sees when a delay hits delivery, deadlines and payment.
See a changePlanned buying
These plans come from Australia. The State of Queensland publishes them on data.qld.gov.au. Schools, ICT and works. Forward plans, not tenders you answer today.