Why Cultural Impact Assessments Are Hard

Cultural Impact Assessments sit at one of the more demanding intersections of practice in Aotearoa. They carry cultural weight, statutory weight, and project weight, often all at once. They are asked to honour mātauranga held over generations while meeting the consenting timelines of a project that wants to move next quarter. And, in our experience, most of the people writing them are doing so without a settled structure to lean on.

That tension is worth talking about openly. Not because the work is going to get easier, but because there is a real difference between a CIA that has been built well and one that has been stitched together under pressure and the difference shows up in the document, in the consent process, and in the trust held between mana whenua and project teams long after the report is filed. The frustrating thing with Planners is often they will try to avoid a CIA or engagement with mana whenua - even when they know its needed.

What a CIA actually is

A Cultural Impact Assessment is a document prepared by, or with, mana whenua that records their values, concerns, and recommendations in relation to a specific proposal. It describes the cultural relationship between an iwi or hapū and the area in question. It assesses the effects of the proposal on that relationship. And it sets out what would be required for the proposal to be acceptable to mana whenua (if it is acceptable at all).

That is a precise role. A CIA is not an environmental report with a chapter on Māori interests added at the back. It is not a checklist of statutory references. It is a document with its own authority, written from the standpoint of those who hold mana whenua. The role of a practitioner working alongside is to support, organise, and document — not to determine cultural significance on anyone's behalf.

Held to that standard, a CIA is a serious piece of work.

The bar is rising

Expectations around CIA quality have lifted considerably over the past several years. Consent authorities now expect documentation that engages clearly with sections 6(e), 6(f), 6(g), 7(a) and 8 of the RMA, with relevant settlement legislation, with iwi management plans, and with the cultural landscape in which a proposal sits. Applicants increasingly recognise that a thin CIA — or a CIA prepared too late in the process — exposes them to risk at hearing and on appeal. Iwi and hapū entities are, rightly, less willing to put their names to documents that do not reflect the standard of work they expect to issue.

The bar is moving in the right direction. The challenge is that the supporting infrastructure for the work has not always kept pace. Many practitioners are still starting each new CIA from a blank page, or from a heavily marked-up version of the last project, or from a Word file that has been passed around and rebuilt by three different people.

The blank page problem

If you have ever opened a fresh document at the start of a CIA, you will know the friction that follows. The structure has to be built from scratch. Front matter, confidentiality wording, intellectual property clauses, the statutory framework, the methodology, the appendices — all of it has to be assembled before any cultural content can be drafted.

That work is necessary. It is also the work that quietly absorbs hours, days, and sometimes weeks of practitioner time per project. It makes junior staff anxious, because they cannot tell whether their structure is right until a senior reviewer has been over it. It gets compressed when the consenting timetable slips. And it is, almost always, the part of the report that is least visible to the client.

The challenges most practitioners recognise

Across the practitioners and organisations we work with, the same patterns surface again and again.

Structure is one. Decisions about heading hierarchy, section order, how to handle limitations, and where to place the statutory framework feel small until they are being made for the fifteenth time on the fifteenth document.

Consistency is another. Without a settled template, the same organisation can produce five CIAs that read like they came from five different consultancies. That undermines the credibility of the practice over time, and it makes review and quality control harder than it needs to be.

Covering all of the required sections is a real risk under time pressure. Statutory acknowledgements get missed. Iwi management plan references get cited inconsistently. Appendices that should travel with the report — engagement logs, photo registers, recommendation trackers — get assembled in a rush at the end.

Balancing cultural integrity with technical requirements is the most subtle challenge of all. A CIA needs to sit comfortably alongside an AEE in a consent bundle, but it cannot read like an AEE. The voice of mana whenua needs to come through clearly. That voice can be drowned by templated language that has not been thought through.

Time and budget pressure compound everything. Most CIAs are commissioned with timelines that assume the practitioner has the structural side already sorted.

What a good template actually does

A useful template does not replace any of the substantive work. It does not generate cultural content, and it should not pretend to. What it does is take the structural load off the practitioner so that the substantive work has somewhere to land.

A well-built CIA template carries the front matter, the confidentiality and intellectual property clauses, the version control logic, the statutory framework, the methodology section, the assessment of effects structure, the recommendations format, and the appendices. It holds the boilerplate language that should be consistent from project to project, and it leaves clearly marked space for the content that should never be boilerplate — the mana whenua voice, the cultural values, the place-specific assessment of effects.

In our work, the difference is significant. Practitioners using a settled structure spend less time on document architecture and more time in engagement. Junior staff have a clear scaffold to learn from, which shortens the time it takes for them to contribute meaningfully. Senior reviewers spend less time fixing structure and more time engaging with substance. And the documents themselves read more consistently, which builds credibility with both iwi partners and consent authorities over time.

A template also makes it easier to defend the report. When the structural decisions have been made deliberately and applied consistently, it is far easier to explain why the document looks the way it does, and far easier to update it as policy and practice evolve.

The operational case

There is a practical financial dimension to this that often goes unspoken. A template is a one-off investment that becomes part of the cost of goods sold on every CIA delivered after it. The hours saved per project — a meaningful slice of the structural and administrative work — pay the investment back quickly, often within the first one or two assignments. Reduced rework, improved workflow, and stronger junior staff confidence are harder to quantify but real.

For small consultancies and iwi entities producing CIAs in-house, the benefit is most visible. The infrastructure of a larger firm — house style guides, precedent libraries, internal templates — is not always available, and building it from scratch is rarely warranted for one or two projects a year. A well-built template closes that gap.

What a template will never do

It is worth saying clearly: a template does not replace cultural knowledge. It does not replace engagement. It does not replace the relationship between mana whenua and a project team. It will not write a cultural values section, and it should not try to.

What it does is provide structure and operational support so that the cultural work — the engagement, the kōrero, the careful drafting alongside mana whenua, the review and authorisation — can be done with the time and care it deserves.

That is the right division of labour. Structure where structure helps. Cultural authority where it belongs.

A practical next step

If you are working on a CIA at the moment, or expect to be in the months ahead, it is worth giving the structural side of the work some deliberate thought before the next project arrives. A clearer template makes for clearer documents, less administrative drag, and more time for the parts of the work that matter most.

We have built a CIA template that reflects the way we approach this work in practice — structurally complete, professionally formatted, and designed to leave cultural authorship and content firmly with mana whenua. It is available as a standalone resource for practitioners, consultancies, and iwi entities who want to lift the floor on the structural side of their CIA delivery. If that sounds useful, we would encourage you to take a look.

Whichever template you end up with, ours or your own, the principle is the same. Build the structure once, build it well, and free up the time to do the substantive work properly. That is what the people whose values these reports describe deserve from the practice.