Preparing an FPO DPR: From Purpose to Budget

A Detailed Project Report should explain why a project is needed, how it will operate and whether the organisation can afford it. It is more useful when the board can challenge the assumptions than when it simply contains many pages. Begin with the decision the report must support: a pilot, investment approval or a financing application.

Define the problem and proposed service

Describe the members served, location, crop or activity and the current difficulty. Use evidence such as collection delays, verified buyer demand or actual processing charges. State what the project will change and which alternatives were considered, including renting or using another service provider.

The NIRDPR business-planning guide for FPOs is a useful reference for organising the plan. Adapt the structure to the recipient's current requirements and your own data. A model project is a starting aid, not evidence that a bank will sanction your proposal.

Connect capacity with real demand

Document member supply commitments, buyer discussions, seasonality and expected utilisation. Distinguish machine-rated capacity from achievable output after operating hours, downtime, labour and quality losses. Identify which assumptions come from a supplier and which have been tested.

For an illustrative unit rated at one tonne per day, 150 operating days at 60% utilisation imply 90 tonnes of annual throughput. That arithmetic does not prove 90 tonnes will be available or sold. Attach the evidence for supply and demand, and show the result if utilisation is lower.

Build the technical and implementation section

Explain the site, layout, equipment, utilities, staffing, safety controls, maintenance and relevant permissions. Obtain comparable quotations that state capacity, installation, warranty, training and service support. Ask a competent technical adviser to check the proposed design instead of relying entirely on the seller.

Prepare a sequence of milestones: approvals, procurement, installation, trial, staff training and commercial start. Each milestone needs an owner, dependency and acceptance evidence. Include contingency time for permissions and commissioning rather than assuming every task begins immediately.

Prepare costs and funding together

Separate capital expenditure, start-up costs and working capital. Include costs often missed in a machine quote: civil work, electrical connection, transport, installation, initial consumables, insurance where applicable and the cash needed before customers pay. Explain tax treatment with professional input.

Show proposed funding by source and status: committed own funds, applied finance and any conditional assistance. Do not show an unapproved grant as confirmed. Prepare cash flow, operating surplus and repayment estimates using consistent assumptions. Add downside cases for lower sales, reduced price, higher costs and delayed receipts.

Make risks actionable

For each material risk, name an early warning, response and decision owner. A low-demand risk may require postponing expansion; a maintenance risk may require a service agreement and spare-parts plan. Avoid generic statements such as “all risks will be managed.”

End with a decision page: amount sought, purpose, approvals required, conditions before spending and milestones for review. Keep a dated assumptions register and an indexed evidence folder so changes can be traced.

Is a DPR only for a bank? No. It can help members and the board decide whether to proceed even when no loan is sought.

Can a consultant prepare it? Yes, but the FPO should understand the numbers and supply the underlying evidence. Outsourcing writing does not remove management's responsibility for the proposal.

What if the lender uses a different format? Keep the same verified facts and reconcile them to the required format. Changing headings should not create different capacity, cost or revenue figures.

Prepared with AI assistance for the CAFIC knowledge series. Examples are illustrative. Check current official requirements and local conditions before acting on regulatory or technical guidance.