Site Admin · Free editable form

Project start-up checklist

Establish scope, authority, contacts, controls, consent documents, budget, programme, procurement, safety, quality, and reporting before delivery.

Back to forms

When to use

At appointment and again before site mobilisation.

Completed by

Project manager/construction manager

Review / sign-off

Developer/client and project manager

Private by design

A saved draft stays in this browser’s local storage. BuildPath NZ does not receive the entries. Clear shared devices after use and place exported records in the project’s controlled document system.

1. Project nameUse the project name shown in the project document register.2. Project addressEnter the full site address and lot/legal reference if needed.3. Consent / reference numberUse the building consent, resource consent, contract, or internal project reference that applies.4. Form referenceGive this record a unique number that can be found again.5. DateRecord the date the check, event, decision, or report relates to.6. Prepared byEnter the name, role, and organisation of the person preparing the record.7. Project briefEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.8. Authority matrixEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.9. ContactsEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.10. Consent statusEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.11. Budget baselineEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.12. ProgrammeEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.13. RegistersEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.14. Reporting cadenceEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.15. Open risksEnter the exact project-specific information. If the value is technical, contractual, or compliance-related, copy it from the consented drawings, specification, contract, council record, subcontractor document, or manufacturer instruction.

Prepared by / signature

Reviewed by / signature

Date

BuildPath NZ is an educational guide and project-management resource only. It does not replace advice from Auckland Council, a planner, architect, engineer, surveyor, quantity surveyor, lawyer, accountant, lender, insurer, insurance broker, WorkSafe, Watercare, utility provider, building consent authority or other qualified professional.

Evidence to attach

Signed appointments
Brief
Budget
Programme
Consent documents

Common mistakes

Writing vague notes such as 'all good' without location, drawing reference, trade, or evidence.
Leaving signature, date, revision, or responsible-person fields blank.
Filing the form in only one person's phone instead of the project record.
Using the form to approve a technical change without an RFI, designer/engineer instruction, minor variation, amendment, or contract approval where required.

Storage and document control

Store in the project document system under the matching folder: safety, quality, contract, council/CCC, handover, or site administration. Keep photos with the same date and location reference.

Source / Where to check

Check the current consented drawings and specifications, project contract, Auckland Council records and inspection requirements, MBIE Building Performance guidance, WorkSafe NZ guidance, relevant NZ Standard, consultant instructions, producer statements, product technical information, warranties, and manufacturer installation instructions.

Insufficient data to verify — confirm against the current consented drawings, specifications, Auckland Council requirements, Auckland Unitary Plan, NZ Building Code, relevant NZ Standard, consultant advice, manufacturer instructions, insurance broker, insurer, lender, lawyer, accountant or project contract.