What Councils Expect From Structural Reports

What Councils Typically Expect

Councils expect structural reports to be clear, well structured, and technically sound. They also expect the report to be prepared and signed by a suitably qualified Chartered Professional Engineer.

At a minimum, a structural report should include:

• A clear description of what was designed or reviewed

• Identification of all primary structural elements such as foundations, walls, roof framing, beams, and columns

• Confirmation that the design complies with the New Zealand Building Code and the approved consent plans

• Explanation of how loads were assessed including wind, seismic, and gravity effects

• Identification of defects, risks, or non compliant construction where applicable

• Detailed design information such as reinforcement layout, member sizes, material specifications, and fixing requirements

• Site and geotechnical considerations including ground conditions and natural hazards

• Clear recommendations and actions where remediation or further investigation is required

• Producer Statements, including PS1 for design and PS4 where construction review is involved

• Supporting material such as site notes, photographs, and calculations where necessary

Councils also expect reports to use plain language wherever possible. While technical accuracy is important, the document must still be understandable to non engineers who are involved in decision making.

Where Reports Often Fall Short

Many reports fail not because the engineering is wrong, but because information is incomplete, inconsistent, or difficult to follow. Common issues include:

• Calculations that do not clearly link to the drawings

• Member sizes that appear in plans but not in calculations

• Missing design assumptions

• Unreferenced site conditions

• Unclear descriptions of what has changed from the approved consent

• Producer Statements that do not match the scope of work

• Reports that are difficult to review due to poor formatting or structure

These gaps often result in RFIs, delayed approval, and unnecessary back and forth between engineers and councils.

How Nodey Helps Engineers Meet Council Requirements

Nodey is designed to keep drawings, calculations, and reports in sync from the beginning of a project to final documentation.

Nodey automatically links every structural element you mark up on a plan with its design checks and outputs. This ensures there is never a disconnect between what is drawn and what is reported. As you update the design, Nodey updates the calculations and documentation at the same time.

For compliance, Nodey applies the correct standards such as NZS3604 and NZS1170 during the design process. Each calculation includes traceable logic and references so design decisions are not just presented as results but as verifiable engineering steps.

When reports are generated, Nodey compiles calculation summaries, schedules, producer statements, and consent documentation into structured formats that councils expect. The information is presented clearly, with supporting evidence available from the same environment.

Nodey also helps by:

• Keeping version control for design changes

• Recording assumptions, loads, and methodologies

• Maintaining an audit trail through all updates

• Producing consistent report formatting across projects

• Reducing manual errors caused by copying and retyping data

Better Documentation Means Faster Approvals

A structural report is as much about communication as it is about engineering. When documentation is consistent, traceable, and aligned with consent expectations, councils can review applications more efficiently and ask fewer questions.

By centralising design, calculations, and reporting in one system, Nodey helps engineers produce documentation that is easier to check, easier to follow, and easier to trust.

This does not just speed up approvals. It improves confidence across the entire project team and leads to better outcomes for everyone involved.