Preliminary project-review conversations

Define the review boundary

Explain the stage of the project and the decision the review should support. A concept summary, assumption-based budget and list of known constraints may be relevant inputs if a scope is agreed. Identify the source and status of each document. A contractor quotation, an owner estimate and an old reference figure should not be treated as equally reliable simply because they occupy the same spreadsheet column.

Follow assumptions through the business case

Consider a hypothetical preliminary model that assumes a particular unit count and a short approval period. The useful review question is which evidence supports those assumptions and what changes if either proves wrong. An agreed output could be an annotated assumptions list, an issue-priority memo or a preliminary decision brief with unresolved questions. It should distinguish gaps in the supplied materials from findings established by a qualified specialist.

• Identify inputs that could materially change the conclusion.
• Connect each open issue to a responsible source of verification.
• Explain which next decision the available evidence can and cannot support.

Use the result as a starting point for diligence

A preliminary business review is not an appraisal, engineering report, environmental assessment, legal opinion or securities recommendation. It does not validate title, guarantee approvals or obtain financing. Further investigation may remain necessary even when the initial business logic is coherent. Scope, document permissions, deliverables and fees require a bespoke agreement. Begin with a nonconfidential project summary and the specific decision you need to support, not a full sensitive document package.