Enterprise DNA

Instead of CS-VUE

Stop renting CS-VUE. Own your consent compliance system.

We build your version around your sites, your consents and your councils, bring your CS-VUE conditions register across and run it for you. Start with the conditions due this quarter and the consents coming up for renewal.

CS-VUE does not publish a price on its own site. Directory listings show a yearly price for each feature, with larger plans quoted per client.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The recurring bill

What your CS-VUE subscription pays for

CS-VUE quotes privately. Here is what that agreement covers, set against owning the list of your own conditions.

Layers

A price for each feature

Directory listings price CS-VUE per feature, per year. Consents, monitoring, management plans and reporting each add to the bill for one list of obligations.

FileText

Your own conditions, typed into their system

Every condition on every consent is already written down by the council. You pay to hold your own obligations on someone else's platform.

Bell

Reminders when something falls due

Due-date alerts are the heart of the product. A due date is one line of arithmetic once the condition says how often.

Activity

Sensor feeds and dashboards

CS-VUE connects environmental sensors and charts them. The compliance question is simpler: was the daily total recorded, and was it under the limit?

RefreshCw

Rules that keep changing

Water metering rules reached every take of 5 litres a second or more in September 2026, and the government has said it will replace the Resource Management Act. Each change has to land in a system you rent.

Database

History held on their platform

Twenty years of evidence, incidents and inspection grades is what a renewal hearing asks for. Renting means that history sits under someone else's agreement.

Your compliance record

The monthly compliance meeting, run from your own records

Conditions

Every condition with its due date worked out

Each condition carries its owner, how often it falls due and the evidence that met it last time.

  • check Overdue and due-this-month conditions by site and owner
  • check Evidence recorded once and never edited, so an auditor sees the full trail
  • check Calendar dates like "by 30 September each year" set once and repeated
  • check One printable compliance calendar for the site meeting

Limits

No breach without someone owning it

Each monitoring result is held against the limit in the consent the moment it is recorded.

  • check A result over a limit opens an incident in the same step
  • check The date the council or EPA must hear by, from the consent itself
  • check An incident cannot close until the regulator has been told
  • check The notification drafted from the record, ready to check and send

Renewals

The right to operate, protected

Expiry and lapse dates sit with every consent, with the date the law says to act by.

  • check The six-month renew-by date under section 124 of the Resource Management Act, flagged 120 days ahead
  • check Consents not yet given effect, flagged before they lapse
  • check A renewal pack with the conditions and the full compliance history
  • check Abatement and infringement notices tracked to their comply-by date

Your records

Answers your current reports were never built for

Ask in plain words and get the answer from your own history, with the rule behind every flag.

  • check Days from a breach to telling the regulator, by site
  • check Water meters missing daily records, and meters due for verification
  • check Inspection grades and the actions still open after each one
  • check Branded consent summaries and incident reports for every site

Make it yours

Design your own CS-VUE replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from CS-VUE. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your CS-VUE replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your CS-VUE data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Consent Compliance for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Consent Compliance for Claude Code

Connected to your own database

What needs attention across our consents this week?

1

Site
TAF
Item
TAF-WP1
Rule
renewal window missed
Detail
expires 2027-03-06, renew-by date 2026-09-06 ...
Days
61

1

Site
TAF
Item
TAF-OUT TSS 2026-10-25
Rule
breach with no incident
Detail
74 g/m3 against max 60 (TAF-DP1-6)
Days
12

1

Site
RQY
Item
RQY-BORE1 VOLUME 2026-10-29
Rule
breach with no incident
Detail
1084 m3 against max 1000 (RQY-WP1-6)
Days
8

1

Site
KRY
Item
NC-0002
Rule
regulator not told
Detail
spill found 2026-11-03, NSW Environment Prote...
Days
3

1

Site
TAF
Item
AN-001
Rule
notice deadline
Detail
abatement notice AN-2026-0412: Cover the slud...
Days
-10

2

Site
RSD
Item
PL-002
Rule
plan review overdue
Detail
Erosion and sediment control plan v2, last re...
Days
430

2

Site
KRY
Item
PL-003
Rule
plan not tested
Detail
Pollution incident response management plan v...
Days
400

2

Site
RQY
Item
RQY-LU1 cond 9
Rule
condition overdue
Detail
Annual quarry compliance report to the counci...
Days
35

2

Site
TAF
Item
IN-001
Rule
inspection actions overdue
Detail
moderate grade on 2026-09-17: Sludge stockpil...
Days
20

2

Site
RQY
Item
RQY-LU1 cond 5
Rule
condition overdue
Detail
Read the boundary dust deposition gauges ever...
Days
10

2

Site
RQY
Item
RQY-BORE1
Rule
water records missing
Detail
4 of the last 30 days have no daily volume (l...
Days
4

2

Site
KRY
Item
KRY-EPL cond M2
Rule
condition overdue
Detail
Monthly stormwater sampling at discharge poin...
Days
3

2

Site
KRY
Item
KRY-EPL cond R1
Rule
due within 14 days
Detail
Annual return to the EPA, due 2026-11-16 (Yar...
Days
-10

2

Site
RSD
Item
RSD-LU1 cond 7
Rule
due within 14 days
Detail
Erosion and sediment control plan certified b...
Days
-10

2

Site
RQY
Item
RQY-DP1
Rule
renewal due soon
Detail
lodge the new application by 2026-11-25 (expi...
Days
-19

2

Site
RQY
Item
RQY-BORE1
Rule
meter verification due
Detail
verified 2021-12-02, due by 2026-12-02
Days
-26

2

Site
RSD
Item
RSD-LU1
Rule
lapse date close
Detail
not given effect yet; lapses 2027-05-01
Days
-176

3

Site
RQY
Item
NC-0003
Rule
incident not closed
Detail
missed_monitoring open 45 days
Days
45

3

Site
RQY
Item
CP-001
Rule
complaint not answered
Detail
dust at 14 Kowhai Road since 2026-11-02
Days
4

Ask it anything

Ten questions your consent records answer

These run against the working demonstration today. Your own version asks them of your sites, your consents and your history.

chat_bubble Which breaches of a consent limit has nobody raised an incident for?
chat_bubble Which consents are past the six-month renewal date with no application lodged?
chat_bubble Which incidents has the council or EPA not been told about, and how late are we?
chat_bubble Which conditions are overdue right now, and who owns each one?
chat_bubble Which water meters are missing daily records this month, and how many days?
chat_bubble How many days, on average, do we take to tell the regulator after a breach, by site?
chat_bubble Which abatement notices fall due in the next fortnight?
chat_bubble Which consents will lapse soon because we have not given them effect?
chat_bubble Which inspection actions are overdue, and what grade did each site get this year?
chat_bubble Which complaints from neighbours has nobody answered yet?

Switching

How to switch from CS-VUE

The move usually involves exporting your conditions register and monitoring results, testing the import, and checking the new records against CS-VUE before you switch.

  1. 1

    Export your records

    Ask CS-VUE how to export the records available for your account. Exports differ by client, so check with CS-VUE and export what your account allows, usually as CSV or Excel. Start with your conditions register and monitoring results, which are the two record types the importer accepts.

  2. 2

    Test the import

    Load the conditions register and monitoring results into the new system, and run the offered test before importing records. The test checks whether the columns in your exports match what the importer can read. It reports rows it cannot match rather than guessing, so use the results to identify anything that needs attention before loading.

  3. 3

    Review flagged records

    Check every row the import could not match, then review the imported breaches. Breaches are listed for review rather than raised as new incidents, because CS-VUE may already hold them. Confirm the records are right and decide what other history you need to bring across, including open incidents and inspection history.

  4. 4

    Run both side by side

    For a short period, keep CS-VUE available while you check the new records against it. Compare conditions, monitoring results, due dates and any history you brought across. Review anything that differs before relying on the new system. This gives you a chance to resolve gaps while you can still refer to your CS-VUE records.

  5. 5

    Switch off CS-VUE

    Once you have checked the records you need and are ready to work from the new system, stop using CS-VUE for your compliance work. Keep any CS-VUE records you still need according to your own requirements. The new system keeps your compliance history in a database you own.

construction

Where the real effort goes

The real work is usually mapping your fields and rules to the new system, then deciding which history to bring across. Conditions and monitoring results have an import path, but exports differ by client, and limits, open incidents and inspection history need attention too. If Enterprise DNA installs and runs it for you, they handle this mapping and migration work.

Not ready for a call?

Get your CS-VUE switch plan by email

We will send you the step-by-step plan for moving your business off CS-VUE, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask what needs attention
  3. 3 Add your sites, consents and conditions, then test your CS-VUE export with a dry run
  4. 4 Put your logo on the consent summaries and incident reports in brand.json
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your sites, consents, conditions and limits set up from the consent documents
  • check Your CS-VUE conditions register and monitoring history mapped and checked
  • check A phone form for site staff or a web front end if your team wants one
  • check A daily feed from your water meter telemetry and your laboratory
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and ownership agreed
  • check The monthly compliance review prepared for your operations meeting
  • check Overdue conditions, unreported breaches and renewal dates chased the same week
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a compliance review

Questions

Instead of CS-VUE, answered

What does CS-VUE cost compared with this? expand_more

CS-VUE does not publish a price on its own site, and directory listings show a yearly price for each feature, so bring your own agreement. The free version has no licence fee; hosting and your agent subscription are separate. Enterprise DNA builds and runs your version for one setup fee, then a retainer.

Can you bring our CS-VUE conditions across? expand_more

Yes. The free version reads a spreadsheet export of your conditions register and your monitoring results, reports every row it cannot match, and does a test run first. Exports differ by client, so mapping yours, along with your limits, open incidents and inspection history, is part of what we do for an installed version.

Does this keep us compliant with our consents? expand_more

It records what your consents and the law expect you to show: each condition met on time, results against their limits, incidents and when the council or EPA was told, renewal and lapse dates, inspections and notices. Each check cites the rule it comes from. It supports your own review; it does not lodge anything or decide for you whether to tell the regulator.

What about our sensors and water meter telemetry? expand_more

Live trends and alarms stay with your telemetry provider. This holds the daily totals and the results that matter for compliance, and flags any day with no record. If you want the feed connected, we bring it into your version on the database you own.

What do we keep if we stop working with you? expand_more

Everything. The database, your version and the full history of conditions, evidence, results, incidents and notices are yours. A complete snapshot exports in one step, and we agree access, backups and recovery with you when it is set up.

Bring your consents and your CS-VUE agreement

Spend 30 minutes with Sam. We will look at how your conditions are tracked and reported today, what is coming up for renewal, and what your own version should do first.

Book a 30-minute call with Sam Get the free version

Consent Compliance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for CS-VUE?

Get your version built