Cumulative impact gets assessed. Cumulative consultation often goes unrecorded.
Each project has its own engagement plan, timetable and participation report. The community experiences them together. A transport proposal, a park upgrade, a housing strategy and a utility project may all ask the same residents for time within a few months. Each request can be reasonable. Together, they can become a substantial demand.
When participation falls, the next project team may interpret the result as disinterest. But without a record of earlier asks, it cannot tell whether this is a community that is disengaged or a community that has already been asked repeatedly.
The project is the unit of reporting. The community is the unit of experience.
Consider a hypothetical neighbourhood. In January, residents complete a survey about traffic. In February, they attend a workshop about a local centre. In March, they receive invitations to comment on a park design and a water infrastructure proposal.
Each team records its own reach and responses. The fourth team sees fewer submissions than expected and discusses a better invitation or another channel. None of those reports shows the full sequence of requests residents have received.
This is the blind spot: a strong record within each project can coexist with a weak record across projects. The missing information sits between teams, budgets and organisations.
A lower response rate is a signal, not a diagnosis
Repeated consultation is one possible explanation for lower participation. Other explanations include an inaccessible process, an unclear decision, poor timing, limited trust or a topic people do not see as relevant. A consultation register would not prove that fatigue caused a particular result.
It would make one currently hidden explanation available for examination. Before deciding that a community needs more promotion, a team could check what else people have been asked to do, how recently and whether earlier processes have reported back.
The depth of the request matters too. A short survey, a written submission and a series of evening workshops are different demands. Counting consultations is a useful start, but the count needs enough context to support judgement.
What a shared register should record
The practical starting point is a shared record of completed, current and planned engagement. It should be simple enough for project teams to maintain as part of their normal work.
Project and responsible team: who is making the request, with a contact for coordination.
Community and location: the geographic area and stakeholder groups being asked, including groups that cross postcode boundaries.
Timing: when engagement opens and closes, with proposed dates visible before invitations go out.
Topic and decision: what people are being asked about and what their input can influence.
Participation demand: the methods, expected time commitment and any repeated sessions.
Feedback status: whether participants have been told what happened with their previous input.
A postcode can provide a first view of geographic overlap. It is not a measure of individual exposure: the same postcode may contain very different communities, and a single group may participate across several areas. The register should describe who was invited, rather than assume every resident received or responded to every request.
This can begin with project information and aggregate participation data. It does not require building a central record of individual residents.
Who should own it?
Within a council, the central engagement function is a sensible accountable owner. Project teams should maintain their records, while the register owner checks completeness and uses the information in planning discussions. Where there is no central engagement team, that responsibility needs to sit explicitly with an organisation-wide function such as corporate planning or governance.
Ownership needs more than responsibility for a spreadsheet. The owner needs a place in the planning process where overlapping requests can be raised and resolved. Otherwise, the register becomes another report that describes a problem after it has happened.
Across agencies, the task is harder. A council's register cannot reveal utility, state agency or private project activity unless those organisations contribute. A regional arrangement needs an agreed host, named contributors and a clear expectation that planned engagement will be shared. A council may convene it, but it cannot maintain the whole record alone.
Measure it so you can change the next ask
The value of the register is the decision it enables. Before approving another consultation, teams can identify overlapping requests, discuss timing, coordinate invitations or explain clearly how the new decision differs from the last one.
Previous findings may provide useful context. They should not be treated as consent for a different proposal or used to bypass a required consultation. Coordination should preserve people's opportunities to influence distinct decisions.
Start with one practical question at the planning review: what else has this community been asked in the past six months, and what will it be asked while our engagement is running? If nobody can answer, establish the record before debating the invitation.
Better communications can make an ask clearer. A shared record can help determine whether the ask should happen now, how it relates to earlier engagement and what needs to be reported back first.
The next question is an organisational one: who has the responsibility, and the authority, to hold that view?