Local government and councils
Keep public works moving, and keep the reason for each decision easy to find
A council decision is read later by people who were not there, under access and probity rules.
The agreement and rules behind the work
The works agreement, delivery items, evidence and recorded decisions
Illustrative engagement
A regional stormwater upgrade after provider appointment
A council and civil works provider record an awarded stormwater upgrade through delivery items, evidence, payment claims, variations and defects.
- Delivery
- Items, owners, dates, dependencies and evidence
- Money
- Budget, stated GST basis, payment claims and certified amounts
- Change
- Variation reason, cost impact, time impact and recorded response
- Close-out
- Completion items, defects and current engagement report
Product example
Nebula workspace
Project
A regional stormwater upgrade after provider appointment
The works agreement, delivery items, evidence and recorded decisions1 variation needs review.
ReviewWhere it stands
Road programme is active
5 of 7 milestones acceptedWhat needs you
Your decision1 variation
Stormwater scope changeWho is involved
Delivery position
Current delivery positionDelivery items
Public works delivery recordCommunity communication item
ActivePavement inspection evidence
VerifiedCompletion evidence
Needs evidenceThe engagement lifecycle
How Nebula carries this work through delivery
01
Form
Record the awarded delivery position
Project members can upload the works agreement and create delivery items. Each item records its owner, counterparty and due date; an item read from the document can also show its clause reference.
What stays connected
Agreement file, item, owner, counterparty, due date and source clause.
02
Mobilise
Connect mobilisation tasks and dependencies
Site access, design, utility and communication tasks can be recorded as delivery items. Dependencies connect each prerequisite to the work that follows, while the current item state and evidence remain visible.
What stays connected
Prerequisite item, owner, due date, dependency, current state and evidence.
03
Deliver
Record the payment claim and decision
The item owner can claim completion and submit supporting evidence. A payment claim records its claimed amount, currency, stated GST basis and evidence before a member with Nebula's recorded payment authority records the certified amount.
What stays connected
Completion claim, evidence, payment claim, claimed amount, certified amount, currency, stated GST basis and decision.
04
Change
Record a proposed works change
A variation records its description, reason, cost impact, time impact and clause reference. The other project party can place it under review, approve it or reject it, and Nebula checks the responder's recorded permission and value limit before the decision lands. A recorded approval includes an effective date.
What stays connected
Variation, reason, cost impact, time impact, clause reference, response, responder and effective date.
05
Review
Prepare a current project report
Authorised project members can generate a current engagement report from the records Nebula reads. It includes delivery items, variations, payment claims, project risks and open defects.
What stays connected
Report period, audience, source snapshot, delivery items, variations, payment claims, risks and defects.
06
Close
Keep close-out records together
Completion items keep their current state, evidence and decision history. A defect notice records its description, location, rectification deadline and evidence, with later status decisions attributed to their acting user and organisation.
What stays connected
Completion item, current state, evidence, defect notice, rectification deadline, acting user, organisation and decision history.
One connected engagement
What Nebula keeps connected as work changes
Delivery
Items, owners, counterparties, due dates, dependencies, current states, evidence and defect notices with their rectification deadlines.
Commercial
Budget and stated GST basis, payment claims, certified amounts, and variations with each response deadline held against the counterparty.
Collaboration
Questions, answers, workspace entries, project-party messages and attached files.
Review
Current engagement report, project risks, served suspension notices, and the engagement archive with its audit trail and proof references.
Delivery trust
Keep verified delivery history available
Verified work counts in an organisation's delivery history only when two separate organisations are party to it. The council decides whether that record is relevant to a later procurement.
See how record verification worksUse Nebula to carry this work through close-out
Nebula reads the documents that define the work into a delivery plan, carries approved changes and evidence forward, and prepares reports and handovers. Your people decide what is accepted and what happens next.
Nebula's assistant. Questions about Nebula.