CAT sheets don't exist in isolation. Here's how they sit inside CCC's standards and your programme.

The IDS and the CSS, in one minute

  • IDS - Infrastructure Design Standard: sets "the technical requirements for the design of land and asset developments" in Christchurch (CCC, IDS). It's split into Parts; Part 12 is "As-Built Records," which is the Part that requires you to deliver asset data using the CAT.
  • CSS - Construction Standard Specifications: CCC's civil engineering construction specifications, which "should be read in conjunction with each other and the Infrastructure Design Standards" (CCC, CSS). The CSS specifies materials and construction detail - including asset attributes - that may not appear on the construction drawings.

Why the CSS matters for a CAT: the SAG and CAT ask for attributes like material, class and type. Where those aren't shown on the construction drawings, the CSS is your reference for the correct standard specification. (For example, IDS Part 7 Water Supply requires pipe details "in a form complying with the requirements of Part 12: As-Built, including manufacturer, diameter, type, class, date of manufacture, serial number, jointing and contractor who laid the pipe.")

The close-out lifecycle: manage CAT sheets from the start, not the end

The biggest mistake teams make with any as-built is leaving it to the end. Industry guidance is blunt: "The worst thing teams can do is to try to create a complete set of as-builts drawings at the end of construction" (Autodesk, "What Are As-Built Drawings?"). CCC's own process reinforces capturing data as you go - the CAT is meant to be populated "at the commencement of the survey," and redlines record changes as they happen (CCC, Survey As-built Guideline).

A practical sequence for greater Christchurch:

  1. At design/award: confirm with your CCC project manager which CAT template(s) the job needs, and download the latest versions. Note the project benchmarks and confirm everything is NZVD2016 / Mt Pleasant 2000.
  2. Before fieldwork: request portal access if you'll submit reticulation or parks CATs (Article 4).
  3. During construction: keep redline markups live; survey inverts, lids and bases as access allows (don't bury them and hope to capture later).
  4. At completion: compile the CAT, redline drawings and survey report; run the portal validation for reticulation/parks; email stations/land-drainage CATs with review time built in.
  5. Decommissioning: populate the Council Disposal Sheet for any removed assets (Article 7).

The same job may touch more than one council

This series focuses on Christchurch City Council. Neighbouring Waimakariri and Selwyn districts have their own engineering codes of practice and as-built requirements (e.g. Waimakariri District Council's Engineering Code of Practice; Selwyn District Council's drawing/as-built requirements). If your project crosses boundaries, check each council's standard - the datums and templates differ. (Selwyn and Waimakariri publish their requirements on their own websites, linked below.)

Sources & links