Skip to main content
Industries

Grants and community funding

Keep grant delivery records and recorded decisions connected

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

Operating contextThe grant agreement and its stated delivery, reporting and evidence requirements

Landcare workers planting tube stock on a coastal reserve
09Delivery items, evidence, payment claims and recorded variation decisions stay in the engagement record.

Illustrative engagement

A two-year community youth outreach grant

A granting entity and community organisation record the funded work through delivery items, evidence, payment claims, variations and reports.

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
Review
Report period, audience, source snapshot and current engagement records

Product specimen

Nebula workspace

NebulaGrants and community funding

Engagement

A two-year community youth outreach grant

The grant agreement and its stated delivery, reporting and evidence requirements

2 delivery items need evidence.

Review

Where it stands

Grant delivery is active

3 of 5 delivery items verified

What needs you

2 items

Expenditure and outcome evidence

Who is involved

Coastal Resilience FundGranting entity
Bay Landcare NetworkGrantee

Engagement performance

Current delivery position
70/100

Schedule72

Cost76

Risk64

Delivery items

Grant delivery items and evidence
5 delivery items

Planting milestone evidence

Verified

Expenditure evidence

Active

Outcome report

Needs evidence

The engagement lifecycle

How the engagement moves through delivery

  1. 01

    Form

    Record the grant delivery position

    Project members can upload the grant 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

    Plan

    Connect activities, questions and dates

    Activities and evidence requests can be recorded as delivery items, with dependencies between prerequisites and later work. Project members can add dated journal entries and questions, including an optional answer-by date.

    What stays connected

    Activity item, owner, due date, dependency, journal entry, question and answer-by date.

  3. 03

    Deliver

    Separate claimed delivery from verification

    The item owner can claim completion and attach supporting evidence. The other project party can review the evidence and record verification or a dispute against the delivery item.

    What stays connected

    Completion claim, supporting evidence, acting organisation, verification or dispute.

  4. 04

    Money

    Record a payment claim and decision

    Where the parties use a payment claim, Nebula records the claimed amount, currency, stated GST basis and supporting evidence. A member with Nebula's recorded payment authority can record the certified amount.

    What stays connected

    Payment claim, claimed amount, certified amount, currency, stated GST basis and evidence.

  5. 05

    Change

    Record a proposed grant change

    A variation records its description, reason, cost impact, time impact and clause reference. The other project party can place it under review and record its response, responder and effective date.

    What stays connected

    Variation, reason, cost impact, time impact, clause reference, response, responder and recorded effective date.

  6. 06

    Report

    Prepare a current engagement report

    Authorised project members can generate a current engagement report from the records Nebula reads. It includes delivery items, variations, payment claims and project risks for the selected period and audience.

    What stays connected

    Report period, audience, source snapshot, delivery items, variations, payment claims and risks.

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

    Money

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

  3. Connected record 03

    Collaboration

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

  4. Connected record 04

    History

    Current engagement report, variations, risks 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 granting entity decides whether that record is relevant to a later grant assessment.

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 startedSee how Nebula runs an engagement