BuildPath NZ logo
Remote PMRemote management across all stagesHigh riskSource checkedReviewed 11 August 2026

Too many unanswered project items

Too many unanswered project items means the project cannot safely rely on the current assumption. Treat it as an open issue until the relevant evidence and authorised response agree.

Chat is evidence of communication, not automatic proof of physical completion, inspection, approval, price agreement or formal instruction. For too many unanswered project items, the response must follow current project documents and competent project-specific advice.

What it looks like

  • A chat claim, image, voice note, extracted item or group record lacks enough identity, context, chronology or authority to support the proposed project conclusion.
  • The current record for too many unanswered project items is missing, inconsistent, expired, failed or not supported by the required evidence.
  • A dependent decision, inspection, payment, order, cover-up, handover or site activity is approaching while the issue remains open.

Likely causes

  • The requirement or acceptance test for too many unanswered project items was not translated into an owned hold point.
  • The source document, actual condition, programme, price or approval changed without every linked record being updated.
  • Responsibility or authority was unclear, or an informal statement was treated as verified evidence.
  • The required review, inspection, test, comparison or submission was late, incomplete or based on a superseded revision.

Immediate action

  • Preserve the source batch/group/message ID and request a specific evidence pack: location, wide context, detail, current drawing reference, timestamp and responsible-person statement.
  • Keep the item in review and do not release work, payment or formal approval from an ambiguous chat record.
  • Create a dated remote evidence request for too many unanswered project items, assign one accountable owner and set the decision deadline.
  • Confirm containment, investigation, acceptance criteria and authority to resume in writing.

Should work pause?

Keep the item in review and do not release work, payment or formal approval from an ambiguous chat record.

Who to contact

  • On-site representative
  • Relevant trade/consultant/inspector
  • Project manager and authorised decision-maker
  • Client/developer or authorised project decision-maker

Forms and documents affected

  • Remote evidence request
  • Remote communication protocol
  • Evidence request/hold-point pack
  • Chat-to-formal-record and conflict registers
  • Risk, decision and action registers

Software record to update

WhatsApp Import / Remote Inbox / Evidence / Commitments

Step-by-step solution

  1. 01Open the remote communication protocol, evidence request/hold-point pack, chat-to-formal-record and conflict registers and define the exact acceptance requirement for too many unanswered project items.
  2. 02Compare exact source messages, edits/deletions, media metadata, controlled documents, authority and independent inspection/test evidence; record every conflict.
  3. 03Record verified facts separately from reports, assumptions and unknowns; create SOURCE CONFLICT if records disagree.
  4. 04Confirm who has technical, contractual and approval authority; assign one owner and decision date.
  5. 05Assess safety, consent, insurance, cost, programme, procurement and contract consequences before choosing a response.
  6. 06Obtain the required design, approval, test, price, correction or close-out evidence before releasing dependent work.
  7. 07Update WhatsApp Import / Remote Inbox / Evidence / Commitments, link every source and notify affected people of the controlled decision.
  8. 08Verify implementation against the acceptance criteria and retain final close-out evidence without deleting earlier history.

Detailed investigation

  • Compare exact source messages, edits/deletions, media metadata, controlled documents, authority and independent inspection/test evidence; record every conflict.
  • Identify the exact location, work package, responsible party, first known date and downstream dependency affected by too many unanswered project items.
  • Reconstruct the chronology from controlled documents, transmittals, messages, photographs, inspections, tests, costs and programme updates.
  • Test plausible causes with the competent reviewer; do not select a cause merely because it is convenient or cheapest.
  • Write the acceptance criteria, verification owner and evidence required before the record can close.

What not to do

  • Do not backdate a record, certificate, approval or instruction.
  • Do not tell others that insurance, consent or payment approval exists without written evidence.
  • Do not proceed with a technical workaround based only on a generic guide.
  • Do not delete earlier records; supersede them with a traceable revision and decision.

Evidence to collect

  • Source group, batch and exact message IDs
  • Original media with timestamp/context
  • Reviewed extraction, conflict record and resulting formal document
  • Updated issue/decision record and final acceptance evidence

What can be managed remotely

Containment, source preservation, questions and formalisation can be managed remotely. Verification requires sufficient evidence and the appropriate competent reviewer.

When a physical site visit is required

Recommend a visit when evidence remains insufficient/conflicting, critical work is about to be covered, safety or quality is uncertain, or the site representative becomes unreliable.

Cost impact

Record direct cost, professional fees, rework, delay, additional cover/premium, quote changes and contingency use. Obtain written pricing before approval where possible.

Programme impact

Identify the affected activity, hold point, critical-path relationship and required decision date. Update the short-term programme and notify affected trades.

Consent / compliance impact

Check the consented documents and obtain advice before changing approved work or a required inspection sequence.

Contract impact

Check responsibility, notice time, extension-of-time, variation, payment, suspension, defect and insurance provisions with the contract administrator or lawyer before asserting rights.

Safety impact

Reassess site risk before anyone investigates, protects, removes or reworks the affected item.

Construction issue → development control

Update the whole project decision, not only the site action

Feasibility effect

Re-run the live feasibility if this issue changes yield, construction/civil cost, professional fees, contingency, timing, revenue or the assumed approval pathway. Preserve the prior version and identify which values remain assumptions.

Finance effect

Check cashflow, lender/QS reporting, drawdown conditions, interest/holding cost, contingency and any covenant or valuation consequence before approving changed cost or time.

Settlement / sales effect

Check whether the issue affects a marketing statement, disclosure, practical completion, CCC/title dependency, purchaser inspection, warranty, handover or settlement date. Refer contractual/legal conclusions to the appointed lawyer.

Development risk

Carry too many unanswered project items into the development risk and decision registers until the technical response, commercial consequence and required authority are evidence-backed. Do not hide the risk by only closing a site action.

Insurance impact

Check whether the issue or resulting delay/damage could be relevant to any policy. Notify the broker/insurer promptly if the policy or broker advice requires it.

Example email or site-report wording

Subject: Too many unanswered project items — action required before proceeding. We have identified that the current project record does not confirm the required position. The affected work/decision is paused pending written confirmation. Please provide the current document, response and any conditions by [date/time]. We will update the project registers and notify the affected parties once authority to proceed is confirmed.

Escalation point

  • Escalate immediately if people, neighbouring property, public safety, consent compliance or uninsured loss may be at risk.
  • Escalate when the required authority or evidence cannot be obtained before the dependent decision.
  • 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.

Formal records and connected controls

Required formal records

  • Remote evidence request
  • Linked risk/decision/action record
  • Source transmittal or formal instruction
  • Verification and close-out evidence
Related form
Remote evidence request
Related checklist
Remote verification checklist
Workspace module
WhatsApp Import / Remote Inbox / Evidence / Commitments
Open related Workspace area

Verification

Source / where to check

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

Current project record and remote evidence protocol

Check the controlled drawings, approvals, contracts, authority register, WhatsApp source group and batch, exact message, site evidence, inspection requirements and agreed remote-reporting limitations.

Signed contract and project correspondence

Check responsibility, notice, approval, payment, programme, insurance, variation, defect and close-out requirements against the signed project contract and authorised written instructions.

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.

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.

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.

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.