- Assign each unresolved issue an owner, evidence and a decision date.
- Tie the programme to dependencies and decision deadlines.
- Use reporting to explain action, cost and time implications.
Use a decision gate before releasing more scope
At each stage, write down the commitment being proposed. It may be an investigation, design phase, application, procurement package or construction agreement. State the evidence you have and what still depends on an assumption.
A gate review should answer three questions: what has been established, what could change the decision and what work is justified next? Keep a dated record. The purpose is to make a deliberate commitment, not to pretend that all uncertainty has disappeared.
Create an issue register
Use one row per unresolved issue: description, possible consequence, person responsible, evidence needed, action and review date. Useful discussion topics include boundaries, servicing, existing conditions, approvals, design interfaces and product availability.
Separate facts from concerns and decisions. A concern such as “utility upgrade may be required” needs investigation. A confirmed requirement needs scope, pricing and programme coordination. An accepted decision needs to be recorded in the documents used for the work.
Understand sequence before asking for speed
Ask which activities depend on earlier information or completion. A selection might be needed before fabrication, a confirmed detail before a trade can price, or an approval before the next commitment. Make those dependencies visible in the schedule.
Use a short look-ahead discussion to identify the next decisions, information, materials and access requirements. Ask what is preventing a task from being ready. Do not treat additional activity on site as evidence that the overall completion date has improved.
Review the interfaces
Ask your designers and construction team to review where systems and trades meet: window openings and wall build-ups, roof and wall junctions, structure and services, cabinetry and appliances, or retained and new construction.
For each important interface, ask which drawing or detail controls it, who resolves conflicts and when clarification is needed. Request coordinated instructions before work is committed. A product selection is not a complete installation detail.
Ask for useful owner reporting
Agree a concise reporting structure: work completed, next activities, decisions required, approved changes, cost-plan movement, schedule changes and unresolved issues. Each action needs a responsible person and a due date.
Ask how photographs, site observations and relevant records will support updates. Review reporting examples and available tools with the actual project team. The value lies in clear evidence and timely action; a software name alone does not establish a reliable process.
A better first conversation.
- What evidence is needed before the next spending commitment?
- Which decisions or approvals could delay the next stage?
- Who resolves the interfaces between consultants, systems and trades?
- What will an owner update tell us about cost, time and open issues?
Use these guides to prepare your questions. Confirm property-specific requirements, scope and pricing with your project team.