Remote project management and evidence controlBuildPath management templateUsually requiredRemote management across all stagesProject-controlledReviewed 11 August 2026

Chat-to-Formal-Record Register

Use the Chat-to-Formal-Record Register to convert a precise remote information need into traceable evidence and, only after review, a controlled project record. It is a control aid, not a substitute for the current official, contractual or professionally prepared document where one governs.

Who initiates it

Remote project manager or authorised reviewer

Who fills it out

Client/developer, project manager or delegated document owner

Who reviews it

The project manager and the person with technical, contractual or commercial authority for the subject

Who approves it

Authorised project decision-maker or competent reviewer for the underlying subject

Applicability

Use where remote coordination is suitable. It does not replace physical inspection, authority records, testing or professional observation.

Who needs it

The project owner and the person controlling remote management across all stages, including each reviewer, approver or recipient named by the live project process.

Who signs it

Only the person with the authority or professional competence required by the source document, contract, insurer, lender or authority process.

When it is needed

Prepare before the related remote management across all stages decision or activity. Update it when scope, revision, cost, programme, responsibility, evidence or approval status changes.

Information needed

Project/group/batch/message source identity
Exact claim, question, location, drawing revision and evidence requirement
Truth state, confidence, reviewer, conflict and formalisation status

Where to find the information

Original WhatsApp export/message/media metadata
Controlled project drawings, approvals, programme and registers
Returned evidence, inspection/test and competent-person response

Step-by-step

How to prepare, review and file it

01Confirm whether this record applies to the project and who has authority to prepare, review, sign, submit and approve it.
02Download or open the current official form or source requirements when an authority, insurer, lender or contract controls the format.
03Gather the latest controlled source documents and confirm their revisions before entering information.
04Complete every field using project-specific facts; mark not applicable with a reason and clearly label unverified assumptions.
05Cross-check names, addresses, legal description, consent numbers, dates, values, drawing references, policy details and attachments.
06Have the appropriate project owner and qualified adviser review technical, legal, financial, insurance, safety and compliance content.
07Submit or issue it through the required channel, save proof of issue and record any response or RFI.
08Track actions to close-out, then save the final signed/accepted record and attachments in the controlled project file.

Where to submit or store it

Keep as a controlled internal project record and issue by the contract or project communication method when another party must review, approve or act on it.

Submission channels

Controlled project document system
Contract communication or document transmittal
Email only where the project communication plan permits it

Documents to attach

Current drawings, specifications, reports or approval documents referenced in the record
Marked-up plans, photographs, quotes, correspondence, inspection results or certificates that support the entries
Required signatures, declarations, schedules, evidence or authority-generated receipt/acknowledgement

What happens after issue or submission

Send the evidence request, retain source IDs, review returned material, flag conflicts and create a formal record only after explicit user review/approval.

Controlled storage

Save the controlled output in the project document system and link the source WhatsApp batch, message IDs, evidence records and resulting tasks/RFIs/variations/decisions.

Source applicability

Use the current project documents and formal authority records. Chat is evidence of what was communicated, not automatic proof or approval.

Common mistakes

Using an old template, superseded drawing, expired certificate or outdated authority process.
Copying generic wording without checking the specific property, consent, contract, policy or work package.
Leaving ownership, dates, revision, status, attachments or close-out evidence unclear.
Treating an internal checklist as an official authority, insurance, lender, legal or professional form.

Red flags and stop points

Required information conflicts between title, consented plans, consultant reports, contracts or site conditions.
A person is being asked to sign, certify or approve outside their authority or competence.
Work, purchase, payment, submission or occupation is proposed before a required approval or insurance confirmation is recorded.
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.

Connected project controls

Related quote package: Relevant consultant, authority, supplier or trade package
Related checklist items: Remote management across all stages; Prepare and review Chat-to-Formal-Record Register; File evidence and close outstanding actions
Related software tool: WhatsApp Project Control / Remote Inbox / Evidence / Commitments
Example completed version: Example: Chat-to-Formal-Record Register for 12 Example Road, Auckland; prepared by the named project owner; current source documents listed by number and revision; assumptions marked; two actions assigned with dates; reviewed by the appropriate adviser; final version and evidence filed in the controlled project record.

Connected Workspace record

WhatsApp Project Control / Remote Inbox / Evidence / Commitments

Open Workspace area

Blank editable template

Complete a project-specific record

Free · saved in this browser

1. Chat-to-Formal-Record Register: identity and statusEnter the controlled reference, revision, status, prepared/reviewed dates and exact project/work area.Where this information comes from: Project document register, project details and the current source process2. Source identityRecord project, group, import batch, exact message/media ID, sender and source timestamp.Where this information comes from: Original imported source metadata3. Claim and required proofSeparate the reported claim from the exact evidence needed to support it.Where this information comes from: Source message and hold-point protocol4. Truth and conflict stateRecord MENTIONED/REPORTED/EVIDENCE-BACKED/VERIFIED/FORMALLY APPROVED and any SOURCE CONFLICT.Where this information comes from: Reviewed evidence and controlled records5. Formalisation and next actionName the resulting RFI/task/variation/decision, reviewer, deadline and site-visit trigger.Where this information comes from: Authority register and linked workspace record6. Actions, owner and deadlineAssign every missing, failed, conditional or conflicting item to one named owner and decision deadline.Where this information comes from: Issue, decision, responsibility and programme records7. Review, approval and close-outRecord reviewer/approver authority, outcome, conditions, linked evidence and final controlled location.Where this information comes from: Authority register, signed/portal response and close-out evidence

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.

Open connected workspace module

Verification

Source / where to check

Use current official information and the controlled documents for the actual project.

Project-controlled documents

Use the current project brief, approval authorities, issued drawings, specifications, contracts, consultant reports, programme, correspondence and controlled registers.

Consented drawings and specifications

The issued consent drawings, stamped specifications, engineering drawings, RFIs, minor variations, and amendments control the specific project.

MBIE Build to the consent

MBIE guidance explains that work should be built to the issued building consent, inspections must be managed, and records/certificates should be kept for CCC.

WorkSafe NZ construction

Use WorkSafe NZ for construction health and safety duties, risk management, and practical guidance for residential construction work.

Project-specific consented documents and professional advice override generic guidance.

Educational resource and verification warning

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.