At a glance
- Separate evidence from assumptions.
- Connect the project story to delivery requirements.
- Ask the relevant institution what it needs to review.
Explain the project in plain language
Describe the problem, intended audience and proposed activity before introducing a financial model. A reader should understand what the project would do, where it would operate and which decisions remain open. Avoid relying on an ambitious headline to carry the explanation.
Identify the sponsor and the people responsible for preparing each part of the brief. A consistent version of the project story helps technical, commercial and professional advisers discuss the same proposal.
Make assumptions visible
Organise the information behind the proposal into established facts, working estimates and questions still to be answered. Include the source and date of material inputs so reviewers can understand their context. A visible gap is more useful than a precise-looking number with no explanation.
Connect delivery dependencies to the narrative: access to a site, partner roles, technical work and the sequence of decisions. The appropriate specialists should determine the assessments required for the specific project.
Prepare for the right review
Different institutions and programmes request different information. Confirm the current requirements directly with the relevant organisation rather than treating a generic checklist as an application standard. Keep a record of what has been requested and who will supply it.
The resulting brief should make the next conversation more productive. It does not establish eligibility, an approval, financing availability or an expected return. Those determinations belong to the relevant institution and authorised professionals.
