Two Audiences, Two Standards
A Detailed Project Report serves two fundamentally different audiences with fundamentally different evaluation criteria. The government audit committee evaluates technical compliance: does the DPR conform to departmental formats? Are the cost estimates derived from approved schedule of rates? Is the procurement methodology consistent with GFR or Maharashtra GR requirements? Does the scope align with the government scheme parameters under which funding is being sought?
The bank or lending institution evaluates something different: project viability, revenue visibility, risk-adjusted returns, and collateral structure. The bank’s technical team asks whether the project will generate sufficient revenue to service debt. The bank’s credit team asks whether the financial model is conservative enough to survive adverse scenarios. The bank’s legal team asks whether the concession structure provides adequate security for the loan.
Most DPR-producing firms write for one of these audiences. They produce government-formatted compliance documents — technically correct, departmentally acceptable, audit-proof — but structurally inadequate for bank financing. Or they produce investment-grade documents — financially sophisticated, bank-acceptable, IRR-complete — but misaligned with government format requirements and therefore rejected at the first departmental review.
“A DPR that satisfies only one audience requires a second document before the project can proceed. That second document costs time, money, and — critically — creates a window for the project to stall.”
What Government Audit Committees Evaluate
Government audit standards for DPRs are structured around compliance verification, not investment analysis. An audit committee’s mandate is to confirm that public funds are being deployed correctly within the scheme framework — not to evaluate the project’s commercial viability independently.
The sections that a government audit committee prioritises: Schedule of Rates compliance (cost estimates derived from the current DSR or state-approved rate schedules); scope alignment (the proposed works are consistent with the scheme guidelines); procurement methodology (tendering process complies with GFR or state procurement rules); environmental and statutory compliance (required clearances have been identified and are achievable).
What government audit does not typically evaluate: revenue projections derived from market analysis, IRR or NPV calculations, debt service coverage ratios, or sensitivity analysis against commercial risk scenarios. These are financial analysis tools — not government audit tools.
What Banks Evaluate
A bank’s technical and credit assessment of an infrastructure project is an investment evaluation, not a compliance check. The bank is deciding whether to lend money to a project — and recovering that money requires the project to generate revenue, operate continuously, and service debt.
Bank technical assessment focuses on: construction risk (is the project buildable within the budget and timeline proposed?); revenue model (is the revenue projection credible, conservative, and based on documented market analysis?); operator risk (does the operator have demonstrated capacity to run this type of infrastructure?); and contract structure (does the concession agreement protect the lender’s security position adequately?).
The financial sections a bank requires — and that government DPR formats typically do not mandate: a 25-year financial projection with scenario analysis; a Debt Service Coverage Ratio (DSCR) analysis across base, conservative, and stress scenarios; an IRR calculation from the equity investor’s perspective; and a sensitivity table showing how financial viability changes under key assumption variations.
Where the Standards Conflict
The conflicts are specific and predictable. Cost estimation methodology is one: government audit requires DSR-based cost estimation (government rate schedules), while banks require market-rate or tender-based estimation. DSR rates are often below market — a cost estimate that passes government audit may look unrealistically low to a bank’s technical team.
Revenue projection is another: government scheme DPRs often state revenue projections as assumptions rather than supporting them with market studies. Banks require documented market analysis, comparable transaction data, and downside scenario modelling. A revenue projection without supporting data is a number to a bank — not a projection.
Risk allocation is a third: government DPR formats focus on statutory risks (land acquisition, environmental clearance, approval timelines). Bank assessment focuses on commercial risks (revenue shortfall, cost overrun, force majeure) and how the concession agreement allocates those risks between government and private parties.
DPACO’s Dual-Track Approach
DPACO structures every DPR with both audiences’ requirements as concurrent constraints, not sequential iterations. This is not a post-production adjustment process — it is a parallel design methodology applied from the first financial model iteration.
The financial model is built with dual outputs: a government-format cost summary and a bank-format financial analysis, derived from the same underlying data. Cost estimates use DSR-based pricing for the government audit summary and are reconciled to current market rates for the bank financial model — with the reconciliation documented and explained.
Revenue projections are supported by market studies and comparable transaction references — providing the evidentiary basis that satisfies bank review, while being presented in the government scheme format for the departmental submission.
Risk identification covers both statutory risks (in the government format) and commercial risks (in the bank analysis) — with the concession agreement structure designed to allocate commercial risks in a way that satisfies both government approval requirements and bank security requirements.
“The Shetkari Bhavan DPR was structured to satisfy APMC committee audit requirements and the APMC fund disbursement process simultaneously — because those were the two gates the project had to pass.”
Reference Case: Shetkari Bhavan DPR
The Shetkari Bhavan programme required DPRs that could pass APMC committee audit (for government scheme funding) and support the procurement process (for contractor selection and PMC appointment). DPACO structured each location’s DPR with dual compliance: government scheme format for the APMC committee submission, and a detailed cost and scope document for the procurement and PMC appointment process.
The per-unit cost structure (₹1.5 crore) was validated against both DSR-based cost estimation (for government audit) and current market construction rates (for procurement credibility). The two figures were reconciled and documented — allowing the DPR to pass the government audit process while also credibly supporting the subsequent tender process.