Short answer
Break every consultation, notification and complaints condition into its separate requirements, using the exact wording of the approval, and link each requirement to verifiable evidence: dated correspondence with an author and recipient, distribution records, meeting records, complaint logs and the responses sent. Capture that evidence when the work happens, not when the audit is announced. A condition is proved when someone independent can follow your records from the requirement to the outcome without relying on anyone's memory.
What do consultation conditions usually require?
They usually require several things at once, and each part has to be evidenced separately. Wording varies by jurisdiction, approval type and project, so always start from your own consent or approval instrument. Engagement-related conditions on major projects commonly fall into these types:
- Consult before acting. Consult a named agency, the council, Aboriginal stakeholders or affected landholders before preparing or submitting a management plan, or before a specified activity starts.
- Notify in advance. Tell affected residents a set period before out-of-hours work, blasting, road closures or other disruptive activity.
- Run a complaints system. Keep a phone line, email and postal address available, record complaints, and respond to them.
- Keep information public. Publish plans, monitoring results and reports on a project website and keep them current.
- Support a community forum. Establish and resource a community consultative committee or similar group. In NSW, the planning department publishes a Community Consultative Committee guideline for State significant projects.
- Implement an approved plan. Deliver the community engagement or communication strategy approved as part of the management plan suite.
- Report. Cover complaints, community feedback and engagement in periodic compliance reports.
The practical point is that one condition can hold three or four obligations: consult, consider, document how comments were addressed, and submit by a date. Each one is a place an auditor can find a gap.
How do you map a condition to the evidence that proves it?
Build a compliance table that puts each obligation on its own line, in the approval's exact words, and records the evidence against each line. In NSW this is a formal requirement for compliance reports: the planning department's Compliance Reporting Post Approval Requirements (March 2026) say the compliance table must set out each requirement with the exact wording of the condition, put each separate requirement on its own line, and record the evidence relied on. Applying the same discipline to every engagement condition, in any jurisdiction, is the most reliable way to find your gaps before someone else does.
For each line, record:
- the condition reference and its exact wording (never a paraphrase);
- the separate element being tested;
- the trigger or timing: before construction, five days before the work, at all times, annually;
- the evidence that would satisfy it, decided before the work starts;
- where that evidence lives and who owns it;
- the current status and the date it was last checked.
A worked example (hypothetical)
Take a hypothetical condition: "Before carrying out out-of-hours work, the proponent must notify all residents within 300 metres of the work at least five days in advance, and keep a record of each notification." It splits into four elements, and each needs different evidence.
| Element | Evidence that proves it |
|---|---|
| Identify every resident within 300 metres | A dated map or GIS extract of the notification area, and the address list generated from it |
| Notify at least five days before the work | The notice content and version, the send date, and the date of the shift it relates to |
| Notify all of them | A distribution record that matches the address list, with returned mail and failed messages followed up |
| Keep a record of each notification | All of the above, retrievable for any shift in the reporting period |
A copy of the letter on its own proves very little. It shows what you intended to say, not who received it or when. That is one of the most common gaps on a project that genuinely did the work.
What evidence do auditors and regulators accept?
Evidence that is verifiable: it can be dated, attributed and traced to a source without relying on someone's recollection. The NSW requirements give examples, including correspondence that notes the date, author and recipient; documents with a reference, date, revision number and author; dated photographs; inspection records; monitoring data with the period it covers; and delivery records, invoices and receipts. The NSW Independent Audit Post Approval Requirements are blunt that interviews are generally not sufficient to verify compliance with a condition, and that supporting evidence should be provided.
Applied to engagement, that means:
- Meetings: the agenda, who attended, notes with the date and who took them, any commitments made, and what happened to them.
- Consultation on plans: the request for comment, the response received, and how each comment was addressed, often as a table in the plan itself.
- Notifications: the content, the distribution list, the send date and method, and evidence of reach.
- Complaints: when the complaint arrived and through which channel, the issue and location, the action taken, the response to the complainant and its date, and closure.
- Website obligations: dated captures or a change log showing when documents were published and updated.
Be ready for a binary answer, too. Both NSW documents allow only three statuses: compliant, non-compliant or not triggered. Terms such as "partial compliance" and "administrative non-compliance" are expressly ruled out. If your evidence covers four of five elements, the condition is non-compliant, so the evidence has to be complete.
What about Commonwealth (EPBC Act) approvals?
EPBC Act approvals commonly require an annual compliance report, and the department's Annual Compliance Report Guidelines include a sample compliance table it recommends every report contains. The guidelines were revised in 2023. Conditions on newer approvals refer to the 2023 version, while many existing approvals still refer to the 2014 version, so check which one your approval names. The guidelines also point to the Act's offences for giving false or misleading information, which is a good reason to make every statement in the report traceable to a record.
Commonwealth compliance and enforcement is also changing. The 2025 reform package, including the National Environmental Protection Agency Act 2025, established a National Environmental Protection Agency, and its provisions are commencing in stages. Check the current position with the regulator rather than relying on how reporting and audits worked before the reforms.
Where do the gaps usually appear?
The consultation usually happened. The gaps are in the proof, and they follow a pattern:
- Meeting notes with no date, author or attendee list, kept in a notebook or a personal inbox.
- Letters on file with no distribution record, so reach can't be shown.
- Complaints logged, but the response to the complainant never recorded, or closed without a date.
- Comments received from an agency or council, but no record of how they were addressed before the plan was submitted.
- Contractor engagement recorded in the contractor's own system and never handed over.
- Commitments made at committee meetings or drop-in sessions that nobody tracked to completion.
- Conditions paraphrased in the register, so an element was lost in translation.
- Evidence assembled once a year, so gaps are found too late to fix.
Each of these is cheap to prevent and expensive to reconstruct, a theme we cover in the cost of poor stakeholder management.
How do you keep the evidence ready all year?
Make capturing evidence part of doing the work, and check it on a fixed cycle.
- Load every engagement condition and management plan commitment into the compliance table at approval, with an owner for each line.
- Set the evidence standard for each line before work starts, and tell field teams and contractors what "done" looks like.
- Capture records at the time, against the stakeholder, property and condition they relate to.
- Check a sample of lines each month and confirm the evidence is complete. Fix gaps while the people involved still remember.
- Bring contractor records into the project record at least monthly, and at every handover.
- Before each report or audit, run the full table and assemble the pack.
For what that pack should contain, see the engagement evidence pack checklist. If an independent audit is coming, our guide to preparing for an independent audit of engagement obligations sets out a timeline.
Where VivoAI fits
VivoAI keeps approval conditions, offset obligations and agreement commitments in one register, each with an owner and its evidence linked. Meetings, calls, emails, letters and field visits are captured in one place; AI suggests the condition or commitment each record relates to, and your team confirms. You can see what is evidenced and what is not, at site or portfolio level, and export an evidence pack when the regulator asks.
It runs alongside the system you already use, starting with one or two sites. See how it works for resources and energy projects.
Frequently asked questions
Is a consultation log enough to prove a consultation condition was met?
Usually not on its own. A log shows that contact was recorded. To prove a condition you normally also need the underlying records: what was sent or discussed, with whom, when, and what was done with the feedback where the condition requires it. Read the exact wording of your condition, because each element needs its own evidence.
Can a condition be partly complied with?
Not for reporting under the NSW post approval requirements, which allow only three statuses (compliant, non-compliant or not triggered) and expressly rule out terms such as partial compliance. Other approvals and jurisdictions set their own reporting rules, so check yours, but planning for an all-or-nothing test is the safer assumption.
Do interviews with the community relations team count as evidence?
They help an auditor understand how things work, but the NSW Independent Audit Post Approval Requirements say interviews are generally not sufficient to verify compliance with a condition and that additional supporting evidence should be provided. Treat interviews as context, not proof.
How long should we keep consultation evidence?
Your approval conditions, contracts and, for public bodies, records legislation set the minimum, and they vary. Because compliance can be examined in later audits and reports, plan to keep evidence at least for as long as the approval is active, and confirm the required period with your legal team or records authority.
Sources
- Compliance Reporting Post Approval Requirements, March 2026 (NSW Department of Planning, Housing and Infrastructure)
- Independent Audit Post Approval Requirements, March 2026 (NSW Department of Planning, Housing and Infrastructure)
- Community Consultative Committees (NSW Department of Planning, Housing and Infrastructure)
- Annual Compliance Report Guidelines (Department of Climate Change, Energy, the Environment and Water)
- National Environmental Protection Agency Act 2025 (Federal Register of Legislation)
This article is general information, not legal advice. Check your own approval conditions and obtain advice for your circumstances.
Next step
See your conditions with the evidence attached
Each consultation, notification and complaints condition, linked to the records that prove it, with the gaps visible before the audit.