A project can have a compelling purpose, experienced people, and a credible market opportunity, yet still be difficult to evaluate if the supporting record is fragmented. Project finance due diligence is the work of turning the idea, asset, contracts, assumptions, and delivery plan into a package that can withstand disciplined review.
This is not a promise of financing, and it is not a substitute for legal, tax, technical, financial, or regulatory advice. It is a practical way to organise the questions that typically need clear answers before a serious capital conversation can progress. The objective is simple: make it easier for a qualified reviewer to understand what the project is, what it needs, who bears each material risk, and what evidence supports the request.
Start with the project, not the capital request
Begin by defining the asset and the business case in plain language. State what is being built, acquired, expanded, or refinanced; where it is located; what stage it has reached; and what must happen next. A reviewer should not have to reconstruct the project from a pitch deck, a model, and a collection of attachments that tell slightly different stories.
Include the sponsor group, ownership structure, decision-makers, delivery partners, and the intended sources of revenue. For an operating asset, distinguish historical performance from projections. For a development-stage project, distinguish signed rights and contracts from targets, assumptions, or commercial discussions still in progress. That distinction is not a weakness. It is basic transaction hygiene.
1. Build one controlled project summary
Create a concise summary that becomes the reference point for the file. It should cover the project purpose, location, scope, development or operating status, required capital, proposed use of proceeds, anticipated timeline, and key counterparties. Add a version date and name the person responsible for keeping it current.
The summary should reconcile to every major document. If the cost estimate says one thing, the financial model another, and the implementation schedule a third, that inconsistency will consume time before the substantive merits are even reached. A clean summary gives advisers, lenders, and potential partners a shared starting point.
2. Show the capital need and sources of repayment
Explain what the capital will fund and how the requested amount was derived. A useful sources-and-uses schedule identifies equity, debt, grants, vendor support, or other funds that are committed, expected, or still being sought. It also separates funds already spent from remaining cost to complete.
Then connect the request to the project’s revenue logic. For a contracted infrastructure project, that may mean the underlying revenue agreement, tariff mechanism, customer credit, and payment timing. For real estate, it may mean leasing, sales, operating income, or an exit plan. For an acquisition, it may mean the target’s actual cash generation and the conditions required for a successful transition.
Reviewers will usually test the downside, not just the base case. The U.S. Department of Energy’s project-finance primer illustrates the value of bringing together feasibility work, financial modelling, site rights, permits, contracts, and performance support before presenting a financing case. The detail will differ by sector, but the principle holds: the funding story must be evidenced by the project story.
3. Treat the financial model as a decision document
A useful model is transparent enough for a qualified reviewer to understand its drivers. Document the forecast period, the source of key assumptions, construction or transition timing, operating costs, tax treatment, financing costs, contingency, and debt-service logic where applicable. If the model relies on a future contract, price, volume, or approval, identify that dependency clearly.
Stress tests should be proportionate to the project. Delayed completion, lower revenue, higher costs, changes in interest rates, foreign-exchange movement, or a slower ramp-up can all matter. The point is not to create a dramatic spreadsheet exercise. It is to understand which assumptions are decisive and what mitigation exists if those assumptions move.
4. Map commercial contracts and counterparties
List the agreements that allow the project to be built, operated, supplied, sold, or serviced. Depending on the transaction, that may include customer or offtake arrangements, construction and operations contracts, supply agreements, leases, concession rights, purchase agreements, and material amendments.
For each material counterparty, note its role, the status of the agreement, its term, termination rights, payment obligations, performance security, and any consent or assignment requirement. A contract is not useful merely because it exists. The question is whether it supports the financial structure and whether the counterparty can perform under the scenario being presented.
5. Confirm site control, permits, and legal structure
Document who owns or controls the asset, land, concession, licence, or other relevant right. Identify permits already held, permits in process, key conditions, and the realistic path to remaining approvals. Where a project spans jurisdictions, be especially clear about governing law, entity structure, local approvals, foreign-investment restrictions, and the advisers responsible for each workstream.
Environmental and social matters should be reviewed in a manner proportionate to the asset and jurisdiction. The International Finance Corporation’s Performance Standards are a useful reference point for the types of risk-management themes institutional participants may consider. They are not a substitute for project-specific legal or technical advice.
6. Make the execution plan testable
Show the route from today to the next value-creating milestone. The schedule should identify major dependencies, decision gates, procurement steps, funding conditions, and responsible parties. For projects under construction, include cost-to-complete, contingency, contractor status, and the evidence supporting expected completion. For operating assets, include maintenance, key personnel, licences, and any transition requirements.
Technical claims should be supported by the right independent evidence where it is material. That might include engineering, appraisal, reserve, environmental, insurance, market, or operational reports. Keep the underlying reports available, but use a short index to explain what each one addresses and whether it is current.
7. Keep a risk register that leads to action
A strong package does not claim that the project is risk-free. It identifies material risks, names the owner of each risk, explains the potential impact, and describes the current mitigation. For example, a construction gap may lead to a revised contingency, completion support, or an amended contract. A permitting dependency may become a condition before any funding is advanced.
This format helps distinguish manageable issues from unresolved ones. It also prevents avoidable surprises. If an item is not yet complete, say what remains, who owns it, and by when it is expected. Serious reviewers generally value clarity over artificial certainty.
How JPI Global Holdings helps prepare the conversation
JPI Global Holdings facilitates strategic introductions across private credit, business financing, real estate, commodities, and selected cross-border opportunities. For a project that may fit its Strategic Capital focus, a concise, well-organised initial brief helps establish whether there is a credible basis for a further conversation. JPI does not act as a direct lender, and any opportunity remains subject to independent review, diligence, documentation, and the requirements of the relevant parties.
When the core materials are ready, principals can use the funding inquiry to outline the project, requested capital, intended use, and timeline. The first submission does not need to carry every sensitive document. It should give the right decision-makers enough clarity to determine whether a more detailed review is worthwhile.
Frequently asked questions
What is project finance due diligence?
It is the structured review of a project’s commercial, financial, legal, technical, regulatory, and execution evidence before financing is considered. The precise scope depends on the asset, capital source, jurisdiction, and transaction structure.
Do all documents need to be final before an initial review?
No. Early-stage opportunities can be discussed with a clear plan for outstanding items. The important point is to state the current status, responsible party, and timing for each material item rather than presenting an assumption as completed work.
What makes a project package credible?
The project description, model, contracts, permits, schedule, and requested capital structure should reconcile. Material risks should be identified with realistic mitigations, and the package should make clear which statements are supported by executed documents or independent evidence.