Disclosure amplification: when the building report is provided, don't re-amplify

The mechanism

A competent residential building report is a professional document written for readers with technical context. Findings are embedded in a narrative that includes:

• Scope notes and access limitations.
• Proportionate language ("recommended where needed," "routine maintenance for this era").
• Mitigating context alongside defects.
• Page-level structure that lets the reader see each finding in relation to the whole.

When the same findings are extracted into a standalone disclosure document as bullet points, the context is stripped. The reader sees a concentrated list of concerns without the surrounding framing. Rustling through a list of "additional pile-to-bearer connections required," "borer exit holes in subfloor and roof," "corrosion on exterior vent," "Dux Quest pipework (disconnected)," and "asbestos possible given era" produces a different impression than reading the same items in a 60-page report that also documents functioning roof, upgraded electrical, new hot water cylinder, and a Healthy Homes compliant dwelling.

The findings are the same. The impression is not.

Why it happens

Two forces produce the pattern:

• Agency liability management. Rule 10.7 of the Professional Conduct and Client Care Rules 2012 requires the licensee to disclose known defects to a customer (in the PCCC, a person who is not the licensee's client — typically the prospective purchaser). Creating a standalone document that lists the defects creates a piece of paper with the vendor's signature on it — a clearer record of disclosure for the agency's own Rule 10.7 compliance. The same disclosure could be achieved by simply providing the building report, but a separate document is easier to point to if the agency is later accused of insufficient disclosure.
• Negotiating framing. Buyers reading a concentrated list of concerns have a clearer anchor for price reduction than buyers reading the same items in context. The amplified disclosure produces lower offers. Lower offers close faster. Faster close means faster commission.

Neither force requires malice. Both are rational responses to the agency's incentive structure. The aggregate effect is that the same disclosure information is packaged in a way that tends to transfer value from the vendor to the buyer and to the agency.

Detecting amplification: four tests

Apply these tests to any standalone disclosure document the agency drafts.

Test 1 — Source traceability

For each item in the disclosure, ask: what is the specific source? If it is a building report finding, the disclosure should reference the page: "refer to page 17 of the building report." If the item has no traceable source — it appears only in the disclosure document, not in the building report — it is an agency addition rather than a report finding.

Test 2 — Duplication of a supplied document

If the underlying document (building report, LIM, Healthy Homes report) will be provided to purchasers as part of the listing, does the disclosure duplicate items from that document? Duplication amplifies without adding information. A reasonable compromise is to state in the disclosure: "The building report will be provided; refer to it for details on specific building-condition items." This satisfies Rule 10.7 without extracting items that strip context.

Test 3 — Property-specific vs era-generic

Is each item specific to this property, or is it a general statement about the era, suburb, or construction type? "Asbestos may be present given the era of construction" is true of every NZ home built before ~1970. It is not a disclosure about this specific property. It is an era category statement. Rule 10.7 requires disclosure of known defects, not recitation of statistical background risks.

Test 4 — Language proportionality

Does the disclosure language match the actual condition? A building report saying "some hairline cracks in bath base surface; resurfacing recommended" is different from a disclosure saying "bath requires replacement." A report saying "localised drainage improvement recommended" is different from a disclosure saying "full exterior repaint required." Language that inflates severity or scope is amplified language.

The response — request a cleaner draft

When the draft disclosure amplifies items, request specific changes. Template language:

Hi [agent], thank you for the updated disclosure draft. Before I approve, I'd like to request several specific changes based on the underlying building report.

1. Since the building report will be provided to purchasers as part of the listing materials, items that are detailed in the report do not need to be duplicated in a standalone disclosure. Instead, the disclosure can reference the report directly: "Refer to pages [X, Y] of the attached building report." This satisfies Rule 10.7 without duplicating content.

2. Item [Z] appears to be an era-category statement rather than a specific finding about this property. As the building report will be provided, a generic statement adds no information. Please remove item [Z] from the standalone disclosure.

3. Item [W] uses language ("replace," "significant") that overstates the building report's actual description ("resurface," "minor"). Please match the disclosure language to the report.

4. Please confirm that all items in the final disclosure are traceable to specific sources — the building report (with page numbers), council records, the LIM, the Healthy Homes report, or my own stated disclosures. If any item is not traceable to a specific source, please identify the basis on which it is included.

Please send the revised draft for my review. I'll sign once these points are addressed.

The request is specific, respectful, and grounded in the applicable rule. It gives the agency a clear path to comply. The written exchange becomes a record.

The "Steve encouraged me to add this" scenario

Occasionally the agent will volunteer that a specific item was added on the recommendation of a sales manager or branch leader ("Steve encouraged me to include this one"). The provenance matters. An item added at the direction of the agency's management, rather than at the vendor's instruction or the direct text of the building report, is structurally an agency-policy addition. Under Rule 9.1, agency management's risk preferences cannot displace the licensee's duty to act in the vendor's best interests.

The response is the same as for any amplification: ask for the source. If the source is "our management suggested it," the item is an agency addition. The vendor is entitled to decline inclusion of agency additions that do not correspond to known defects or vendor-provided information.

When amplification is appropriate

Not every extraction from the building report into a disclosure is amplification. Some situations justify a standalone list:

• The building report is long (40+ pages), and key items should be highlighted for purchasers who will receive the full report but are unlikely to read it end to end.
• A specific finding requires affirmative acknowledgement by the purchaser, such as a known defect that the vendor is not remediating.
• The disclosure summarises items from several source documents (building report, LIM, Healthy Homes report) into a single reference.

In these cases, the disclosure is additive — it makes the information more accessible. The distinction is whether the extraction preserves or strips context. A disclosure that says "Refer to pages 15-17 of the building report for detailed assessment of foundation piles" is a signpost. A disclosure that says "Foundation piles require upgrading" is an amplification.

Where this guide sits in the section

Previous: Who drafts your disclosure document?.

Related: The building inspection report: what NZS 4306 requires, Selective Approval Theatre.

Rules cited: PCCC Rules 2012 (Rules 6.2, 9.2, 10.7), Fair Trading Act 1986 (section 9), NZS 4306:2005.