CIS Reporting at Mobilisation: Building a Framework That Stands Up at Audit

The short answer

CIS reporting is how a renewable project proves to the Commonwealth that it is delivering the social licence commitments written into its Capacity Investment Scheme Agreement. At mobilisation, developers and contractors need a reporting framework that collects data from every trade partner, validates it and rolls it up into regular reports, with evidence behind every figure.

What does CIS reporting involve once the contract is signed?

The Capacity Investment Scheme (CIS) underwrites new renewable generation and dispatchable capacity, with tenders run by AEMO Services Limited (ASL). Whatever a proponent committed to under merit criteria MC4 (First Nations participation and benefits sharing) and MC5 (social outcomes and community benefit sharing) is carried into the Capacity Investment Scheme Agreement (CISA) as Social Licence Commitments.

Once the agreement is signed, those commitments are contractual obligations. For the project team, that means:

• Regular progress reporting to the Department of Climate Change, Energy, the Environment and Water (DCCEEW), which on the projects we support runs quarterly
• An annual social licence compliance report to the Commonwealth
• Possible independent audit, with access to documents and sites
• A corrective action plan where commitments are not met, and a potential right to terminate if a breach is not remedied

We have worked with contractors carrying more than 100 individual commitments that they report to DCCEEW each quarter. They span DevEx, CapEx and OpEx, and mix quantitative targets such as spend, hours and headcounts with qualitative targets such as engagement outcomes. Even so, those 100 commitments are only the high-level outcomes the Commonwealth sees.

Why does a CIS project need a reporting framework, not just a report?

Every figure in a quarterly CIS report sits on top of timesheets, invoices, certifications and engagement records supplied by the developer, the EPC or balance of plant contractor, and every trade partner on site. The report is the output. The reporting framework is the agreed way that information moves from its source to the Commonwealth.

A workable framework for CISA compliance reporting covers four things:

• Collect: defined data fields, owners and deadlines for every organisation that holds part of the picture
• Validate: checks against source records and agreed definitions before data is accepted
• Report up: a consistent roll-up from trade partner to contractor to developer to DCCEEW
• Evidence: supporting documents attached to each figure, with a record of who submitted and changed it

Without that framework, each quarter is rebuilt from scratch and the numbers cannot be traced back to where they came from. The time to set it up is mobilisation, before the first trade package is awarded and the first worker is on site.

How do you set up CIS reporting when mobilising a project?

1. Turn every commitment into a data specification

A commitment in the CISA states the outcome, not how to prove it. At mobilisation, break each commitment into a register entry: the metric, unit, definition, data source, owner, collection frequency and the evidence that supports it. A project with 100 commitments can easily need several hundred individual data points, and defining them now is far easier than reverse-engineering them before the first quarterly report.

2. Map who holds each piece of data

Most of the data sits with the EPC or balance of plant contractor and their trade partners, not the developer. Some sits with training providers, community partners and First Nations businesses. For every data point in the register, name the organisation responsible for supplying it and the person accountable for checking it, so nothing falls between the developer and the contractor.

3. Write reporting obligations into every trade package

Workforce reporting under the CIS extends to trade partners, so renewable energy social procurement obligations have to flow down the supply chain before work starts. Each trade package contract should spell out the data fields, definitions, submission frequency and evidence required. Retrofitting reporting requirements after a package is awarded is slow, contested and usually incomplete.

4. Validate data at the point of entry

A quarterly report is only as reliable as the data that feeds it. Check submissions as they arrive against payroll records, invoices, certifications such as Supply Nation registration, and the agreed definitions of local content and First Nations participation. A query raised in the month the data arrives is usually answered from the source record, while one raised at quarter end is often answered from memory.

5. Collect monthly, report quarterly

A monthly collection cycle gives the project team two chances each quarter to chase missing submissions and resolve errors before the report is due. It also spreads the workload across the team rather than concentrating it in the last week of the quarter. The quarterly report then becomes a roll-up of data that has already been checked.

6. Build the audit trail in from day one

The Commonwealth can appoint an independent auditor with access to documents and sites. An auditor should be able to take any figure in a quarterly report and trace it back through each roll-up to the original timesheet, invoice or certificate, along with who submitted it, when, and what was changed. Keep this in a single system of record so the trail survives staff turnover and contractor handovers across DevEx, CapEx and OpEx.

7. Track progress against targets from the first quarter

Set baselines at mobilisation and monitor live progress against every social licence commitment, not just the totals reported up. A shortfall spotted in the second quarter of construction can be recovered by adjusting procurement or recruitment, while the same shortfall found at year end usually leads to a corrective action plan.

Why are spreadsheets an audit risk for CIS reporting?

CIS reporting to the Commonwealth is typically submitted in a spreadsheet that condenses each commitment into a summary line. That format is fine for the final submission. The risk comes when the framework underneath it, with more than 100 commitments and months of data from dozens of trade partners, is also run in spreadsheets:

• Version control breaks down as files move between the developer, contractor and trade partners
• Evidence becomes detached from the figures it supports
• Trade partner data arrives in inconsistent formats and definitions
• Qualitative targets are reduced to a single cell with no supporting record
• There is no record of who changed a figure, or why

Under a contract with audit rights and termination provisions, that is a compliance liability rather than an inconvenience. It is also a significant drain on the team, with spreadsheet-based reporting taking more than 20 hours per month to compile, compared with around 40 minutes using Catchment. The submission can still be a spreadsheet, as long as the evidence behind it lives in a system built for audit.

What should a CIS reporting system do?

When choosing how to run CIS reporting across a project, look for a system that can:

• Hold every CISA commitment as a structured register with definitions, owners and targets
• Give each trade partner a simple way to submit data against defined fields, without spreadsheets
• Validate submissions at entry and flag gaps before quarter end
• Keep evidence attached to the figure it supports, with a full change history
• Roll data up from trade partner to project to DCCEEW report in a consistent format
• Show live progress against every target across DevEx, CapEx and OpEx

Frequently asked questions

What is CIS reporting?

CIS reporting is the ongoing reporting a renewable energy project completes to show the Commonwealth it is delivering the commitments in its Capacity Investment Scheme Agreement. It covers First Nations participation, community benefit sharing, local content and workforce outcomes across the development, construction and operations phases.

How often do CIS projects report to DCCEEW?

Reporting obligations are set in each Capacity Investment Scheme Agreement. On the projects Catchment supports, contractors report progress against their social licence commitments to DCCEEW quarterly, alongside an annual social licence compliance report. Collecting data monthly makes the quarterly cycle far easier to meet.

Are CIS social licence commitments legally binding?

Yes. Under the Capacity Investment Scheme Agreement, social licence commitments made during the tender become contractual obligations. The Commonwealth can appoint an independent auditor, and unremedied non-compliance can lead to termination of the agreement.

Who collects the data for CIS reporting on a renewable project?

The CISA holder is accountable, but most of the data comes from the EPC contractor, balance of plant contractor and their trade partners. Workforce reporting under the Capacity Investment Scheme extends to these trade partner arrangements, so reporting requirements need to be written into every trade package contract at mobilisation.

What will an auditor look for in CIS reporting?

An independent auditor will want to see how each reported figure was calculated and the evidence behind it. That means tracing a number from the quarterly report back to source records such as timesheets, invoices and certifications, and seeing who submitted and changed the data. A reporting framework with evidence attached at the point of entry makes this straightforward.

What happens if a CIS project falls short of its commitments?

The operator must prepare a corrective action plan setting out how it will remedy the shortfall, which the Commonwealth can approve or reject. If the breach is not remedied, the Commonwealth may have a right to terminate the agreement. Tracking progress from the first quarter gives the project the best chance of correcting a shortfall before it becomes a breach.

Setting up CIS reporting with Catchment

Catchment is used on large-scale renewable projects across onshore wind, solar, battery storage and transmission to run CIS reporting from mobilisation through to operations. Your CISA commitments are set up once as a structured register, trade partners submit data monthly against defined fields, and every figure is validated and stored with its evidence. Quarterly DCCEEW reporting then rolls up from records your team can stand behind at audit.

If you are mobilising a CIS project, book a demo and we will walk through how your commitments and trade partner reporting would be set up. You can also see how Catchment supports renewable energy social procurement.