Skip to main content
Industries

Local government and councils

Keep public works delivery records and recorded decisions connected

A public works review can involve the recorded scope, current item states, evidence, payment claims, variations and defects. Nebula keeps those records inside the engagement.

Operating contextThe works agreement, delivery items, evidence and recorded decisions

Two council delivery professionals reviewing work on a suburban street
08Delivery items, evidence, payment claims and recorded variation decisions stay in the engagement record.

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
Closeout
Completion items, defects and current engagement report

Product specimen

Nebula workspace

NebulaLocal government and councils

Engagement

A regional stormwater upgrade after provider appointment

The works agreement, delivery items, evidence and recorded decisions

1 variation needs review.

Review

Where it stands

Road programme is active

5 of 7 milestones accepted

What needs you

1 variation

Stormwater scope change

Who is involved

Riverbend CouncilPrincipal
CivicWorks AllianceDelivery partner

Engagement performance

Current delivery position
83/100

Schedule78

Cost82

Risk90

Delivery items

Public works delivery record
7 milestones

Community communication item

Active

Pavement inspection evidence

Verified

Completion evidence

Needs evidence

The engagement lifecycle

How the engagement moves through delivery

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 06

    Close

    Keep closeout 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

  1. Connected record 01

    Delivery

    Items, owners, counterparties, due dates, dependencies, current states and evidence.

  2. Connected record 02

    Commercial

    Budget and stated GST basis, payment claims, certified amounts, variations and recorded responses.

  3. Connected record 03

    Collaboration

    Questions, answers, workspace entries, project-party messages and attached files.

  4. Connected record 04

    Review

    Current engagement report, project risks, open defects and eligible verified item events.

Delivery trust

Keep eligible verified delivery history available

For verified item events, Nebula applies its eligibility rules before it can record a reputation event in an organisation's service history. The council decides whether that record is relevant to a later procurement.

See how record verification works

Start with the documents that define the work

Build the delivery plan and manage the work, or talk to us about a portfolio.

Get startedCheck proof for a delivery record