Skip to main content

Resources & energy

Prove the conditions
were kept.

Approval conditions, offsets and native title engagement commitments, each with its evidence linked. A portfolio view for corporate legal and compliance, and site-level detail for the teams on the ground.
  • Multi-site portfolio view
  • Role-based access for sensitive records
  • Hosted in AWS Sydney

The questions you’ll be asked

Four people, four versions of “show us”.

The regulator, Traditional Owners, your own lawyers and the neighbours all ask the same thing in different words: prove the commitment was kept.
  1. 01

    From: Compliance officer, state regulator

    “Provide evidence that conditions OFF-3 and CH-2 were met at both sites for this year’s compliance return.”

    Without a connected record
    Each site keeps its own spreadsheet. Head office stitches them together and hopes the versions match.
    With VivoAI
    Every condition carries its linked evidence at every site, so the gaps show up before the regulator sees them.
  2. 02

    From: Traditional Owner representative

    “The agreement says we are consulted before any ground disturbance. Show us when that happened at the northern laydown.”

    Without a connected record
    The meeting happened, but the notes are in a notebook that left with the previous superintendent.
    With VivoAI
    Native title and cultural heritage commitments sit with the meetings, letters and surveys that evidence them, visible only to the people who should see them.
  3. 03

    From: Group general counsel

    “Across all our sites, which approval conditions are we exposed on before the board meets?”

    Without a connected record
    Someone emails every site manager, waits a week, and builds a slide from the replies.
    With VivoAI
    A portfolio view shows evidenced conditions, gaps and what falls due next, site by site.
  4. 04

    From: Neighbouring landholder

    “You said dust results would be shared every month. We haven’t seen one since June.”

    Without a connected record
    Promises made at the fence live in one person’s memory, and nobody notices the month that was missed.
    With VivoAI
    The commitment is linked to every send. A missed month shows as a gap, not a surprise.

One record, two altitudes

Head office sees the portfolio. The site sees the detail.

Corporate legal and compliance need exposure across every site. Project teams need to know what is due this week and what evidences it. Both read the same record.

Corporate legal & compliance

Every site, one view

Evidenced conditions, open gaps and what falls due next, rolled up across operating, construction and exploration sites.

Site project team

Every record behind a condition

The meetings, letters and field records that evidence a condition, in date order, with anything out of sequence flagged.

On record

What VivoAI keeps for a resources project.

Each item is linked to the people, properties and conversations behind it, so the record still makes sense after the roster changes.

Approval conditions
Every condition, per site, with an owner and the records that evidence it.
Offset obligations
Offset commitments tracked alongside the approval they belong to.
Native title & heritage
Agreement commitments, consultation and cultural heritage protocols, with role-based access for culturally sensitive records.
Community commitments
What was promised to neighbours and community groups, by whom and when, and whether it was kept.
Land access
Access history for each property that survives staff turnover and contractor changes.
Complaints & enquiries
Calls, emails and field reports linked to the property, the issue and the condition they relate to.
Where it lives
Australian data residency in AWS Sydney, with the region enforced in code and offshore processing paths disabled by default.

How it works

Start with one site.

Run it alongside the system you already use, then add sites once the register is earning its keep.
  1. 01

    Set up the conditions

    Approval conditions, offset obligations and agreement commitments for one or two sites, each with an owner.
  2. 02

    Capture as work happens

    Meetings, calls, emails, letters and field visits land in one place. AI suggests the condition or commitment each relates to; your team confirms.
  3. 03

    Check the gaps, export the pack

    See what is evidenced and what is not, at site or portfolio level, and export an evidence pack when the regulator asks.

Questions buyers ask

What resources and energy teams ask first.

  1. How do we prove approval-condition compliance across multiple sites?

    VivoAI holds every approval condition, per site, with an owner and the meetings, letters and field records that evidence it. A portfolio view shows evidenced conditions, open gaps and what falls due next across every site, so gaps show up before the regulator sees them. When the regulator asks, you export an evidence pack instead of stitching site spreadsheets together.

  2. Can VivoAI track offset obligations and native title commitments?

    Yes. Offset commitments are tracked alongside the approval they belong to, and native title and cultural heritage agreement commitments sit with the meetings, letters and surveys that evidence them. Role-based access keeps culturally sensitive records visible only to the people who should see them.

  3. Will the record survive staff turnover and contractor changes?

    Yes. Every condition, commitment and property’s land access history is linked to the people, properties and conversations behind it, so the record still makes sense after the roster changes. Calls, emails, letters and field reports land in one place rather than in a notebook or one person’s inbox.

  4. How does the AI help without replacing our people?

    As meetings, calls, emails and field visits are recorded, VivoAI’s onshore AI suggests the approval condition or commitment each one relates to. Your team confirms or rejects every suggestion, and the record shows who did.

  5. Can VivoAI run alongside the stakeholder system we already use?

    Yes. Most teams start on one or two sites alongside their existing system, then add sites once the register is earning its keep. Nothing has to be replaced to begin.

  6. Where is our data stored?

    In Australia, in the AWS Sydney region (ap-southeast-2), with the region enforced in code. AI inference runs onshore, and offshore processing paths are disabled by default. VivoAI is not IRAP-assessed; the AWS Sydney infrastructure we run on is IRAP-assessed, which covers our infrastructure.

Next step

See your conditions register with the evidence attached.

Start on one or two sites, alongside the system you already use. Published, flat pricing with no per-seat charges.