Mentioned
Someone referred to a possible fact, intention or future event.
Boundary: Do not treat this as completed work or a confirmed date.
Remote construction management
Manage an Auckland building project remotely without losing control
BuildPath NZ connects fast site communication to a controlled project record. It helps a project manager decide what can be checked remotely, what evidence to request, what must be formally approved and when a competent person needs to inspect or attend site.
36 control topicsWhatsApp → formal recordEvidence hold pointsSite-visit triggersLast reviewed 11 August 2026
Remote control boundary
Communication is an input. Controlled evidence and formal records are the result.
Use WhatsApp for speed, then preserve the sender, time and group; request usable evidence; verify it against the current project sources; formalise instructions, costs and approvals; and close the action. A remote review cannot establish hidden work, technical compliance, safety or an official approval that the evidence does not prove.
Project truth model
Five states prevent a report becoming a false fact
Reported
A named person explicitly reports that something happened or is true.
Boundary: Keep the person, time and exact wording. A report is not independent verification.
Evidence-backed
Dated photos, video, a document or another traceable record supports the report.
Boundary: Check that the evidence shows the right project, location, date, revision and work item.
Verified
The project manager or appropriately qualified person has reviewed the relevant evidence.
Boundary: Record who verified it, their role, the source reviewed, the date and any limitations.
Formally approved
The required authority, consultant, contract administrator or authorised decision-maker has issued the formal approval.
Boundary: Keep the actual approval. A WhatsApp message saying it passed is not the formal record.
Remote-control toolkit
Turn site communication into a controlled project action
These tools create structured records. They do not replace a required council inspection, consultant observation, contract instruction or other authorised approval.
Evidence Request Builder
Define the exact location, views, measurements, references, provider and due date before asking site for evidence.
Open tool →Remote Hold Point Packs
Request a sequenced before-cover pack and keep the work on hold until the required evidence and authorised review are recorded.
Open tool →Remote Site Visit Recommendation
Record why remote material is insufficient, the consequence of being wrong and who should inspect the work in person.
Open tool →Chat-to-Formal-Record
Move a material chat item into the correct task, RFI, variation, decision, budget, risk or inspection workflow.
Open tool →Source hierarchy
Resolve conflicts before work continues
1
Current approved or consented project document
Check document number, revision, approval status and the exact work it controls.
2
Formal council or authority record
Keep the portal record, issued decision, inspection outcome, condition, sign-off or certificate.
3
Formal consultant instruction or certification
Confirm the author, discipline, authority, scope, revision and any conditions.
4
Executed contract or approved variation
Check the signed scope, price, time effect, notices and approval authority.
5
Written project instruction
Confirm who issued it, their authority, the controlled documents and the formal process still required.
6
Site evidence
Check date, location, context, authenticity, completeness and whether hidden work remains unverified.
7
WhatsApp report
Preserve sender, timestamp, group, batch and exact message. Treat it as reported until corroborated.
8
Unverified comment or assumption
Keep it visibly unverified and prevent it from silently driving work, cost or programme decisions.
Physical presence
When the project manager should go to site
- Major work cannot be confidently verified from the available evidence
- Conflicting site reports or source documents
- Major defect, structural uncertainty or repeated quality failure
- Serious safety concern or critical work about to be covered
- Major client complaint, subcontractor dispute or neighbour/boundary issue
- Programme is substantially behind and recovery evidence is weak
- Evidence quality repeatedly fails the agreed protocol
- A consultant, authority or responsible contractor requests PM attendance
Remote PM playbook
Search 36 project-control topics
Each topic separates remote actions, site-person actions, required evidence, inspection triggers and the point where a physical visit is safer.
Remote project manager
- Define the expected outcome for set up the project for remote management and name the person who owns the next action.
- Issue the current controlled project references and state what is known, reported, missing and awaiting approval.
- Set a realistic response time, review the returned evidence and formalise any instruction, approval, cost or design consequence.
On-site person
- Confirm the exact unit, location, trade, work item and current drawing or instruction before reporting.
- Provide a signed project brief, roles, current approvals, contact list, programme and reporting rules.
- State what cannot be seen or confirmed, stop at any applicable hold point and escalate conflicts or safety concerns immediately.
Evidence required
- A signed project brief, roles, current approvals, contact list, programme and reporting rules
- Sender or author, local date/time, project, lot/unit/location and source group or controlled document reference
- The verification state, reviewer, unresolved limitations and any required formal approval
Safe to check remotely
- Completeness, internal consistency, identifiers, visible condition and whether the requested views or documents were supplied.
- Whether reported dates, people and references align with saved project records.
- Whether the matter needs a task, RFI, decision, risk, quote, variation, inspection, evidence request or formal approval.
Cannot be confirmed remotely
- Hidden work, dimensions, material properties, structural adequacy, workmanship outside the captured views or compliance not proved by the evidence.
- Council, consultant, contractual, legal or safety approval without the issued authoritative record.
- Conditions on site that require physical measurement, testing, observation or competent professional judgement.
Inspection / hold-point triggers
- The consent, inspection schedule, consultant scope, specification, quality plan or contract requires an inspection, witness or hold point.
- Evidence identifies a possible deviation, failed check, covered work risk or unresolved technical question.
Physical visit triggers
- The available evidence is incomplete, inconsistent, poor quality or cannot identify the work and location.
- There is a serious safety concern, major defect, repeated quality failure, source conflict, client complaint or critical work about to be covered.
- A consultant, authority, contractor or stakeholder reasonably requests the project manager's presence.
Common mistakes
- Accepting a confident chat message as verified fact.
- Using screenshots or forwarded documents without checking the controlled revision and source.
- Giving an informal instruction without recording authority, cost, programme, consent and contract consequences.
Ready-to-send WhatsApp evidence request
BuildPath evidence request — Set up the project for remote management Please confirm the project, lot/unit and exact location. Provide a signed project brief, roles, current approvals, contact list, programme and reporting rules. Include the current drawing/document reference and state whether any item is incomplete, hidden, changed or awaiting inspection/approval. Do not cover or proceed past a project hold point until the authorised person confirms the next step.
Check: Current consented drawings and specifications · Project contract, inspection schedule and quality plan · Relevant Auckland Council, MBIE, WorkSafe, Watercare or consultant requirements
Evidence before cover-up
Hold-point evidence packs
Excavation before backfill
Request excavation extents, founding/soil observations, services, drainage, retaining/shoring and required engineer/council records.
Drainage before cover
Request wide route context, pipe type/size, bedding, fall/levels, connections, testing, inspection and as-built information.
Foundations before pour
Request set-out, dimensions, founding, reinforcement, cover/chairs, hold-downs, penetrations, DPM and approvals.
Slab before pour
Request whole slab, set-out, formwork, reinforcing, mesh laps, chairs, DPM, services, penetrations and inspection records.
Retaining before backfill
Request wall, foundation, reinforcement/connections, tanking, drainage, filter media, outlet, engineer observation and approval.
Framing before lining
Request wide room elevations, framing, bracing, lintels, hold-downs, structural connections, services, moisture and inspections.
Structural connections before cover
Request each identified connection, fasteners, welding/bolting, bearing, product markings and engineer requirements.
Wall underlay and cavity before cladding
Request wide elevations, laps, tapes, openings, cavity battens, flashings, penetrations and cladding clearances.
Flashings before cover
Request location context, head/sill/jamb or roof interface detail, laps, stop-ends, kick-outs, tapes and consented reference.
Waterproofing before tiling
Request substrate, falls, junctions, penetrations, upstands, product/batch, installer evidence, test and producer statement where required.
Services before lining
Request plumbing/electrical/HVAC routes, penetrations, supports, testing, fire/acoustic treatment and trade certificates.
Insulation before lining
Request all walls/ceilings/floors, product labels, R-values, fit, gaps, compression, services and H1/consented references.
Final completion
Request external and internal completion, testing, defects, final inspections, certificates, as-builts, warranties, manuals and keys.