The feasibility chapter records the studies, consultations, site visits, pilots, expert reviews, and prior work that shaped the project. It should make the path from idea to design visible.
Study Or Consultation Date Preparer / Source Scope Key Findings Project Design Implication Atlas / Data Room Location Confidence Level [Study name] [Date] [Source] [Scope] [Findings] [Implication] [Location] Low / Medium / High
Evidence Type Purpose Minimum Standard Site visit records Confirm physical context and constraints. Dated notes, photos, map references, and attendees. Technical studies Test design assumptions. Method, preparer, findings, limitations, and design response. Stakeholder consultations Confirm local participation and risk. Participant list, issues raised, response, and follow-up actions. Pilot or operating data Validate performance assumptions. Period, sample size, data quality, and relevance to scale-up. Expert inputs Strengthen design and risk review. Expert identity, qualifications, recommendation, and sponsor response.
Sponsors must not present missing diligence as complete. Each unresolved item must have an owner, target date, financing relevance, and interim assumption.
Gap Why It Matters Interim Assumption Owner Target Date Financing Relevance [Gap] [Risk or decision affected] [Assumption] [Owner] [Date] Condition / Covenant / Monitor
Feasibility evidence should explain design choices. A study that does not affect the asset, operating model, financial model, or risk register belongs in an appendix rather than the core case.
Question Reviewer Test Is the evidence recent and local enough? Confirm dates, geography, and project relevance. Are third-party studies independent? Identify sponsor-prepared materials versus independent review. Do findings flow into design? Trace each major finding to scope, cost, risk, or monitoring changes. Are weak areas disclosed? Check gaps register and assumptions register.