What a Detailed Project Report should actually contain

Most Detailed Project Reports in Nepal are commissioned because a rule requires one. That is a poor reason to write a document, and it shows in the result: a survey done too quickly, quantities that do not reconcile with the drawings, and a rate analysis copied from a district norm that has not been revised in years.

A DPR that can actually be built has a few properties.

**The survey is real.** Contours come from a survey done on the ground with instruments that were calibrated, not from a freely available terrain model. Where a design decision depends on levels, those levels were measured.

**The quantities reconcile.** Every item in the Bill of Quantities traces to something drawn. If a quantity cannot be pointed at on a drawing, it is a guess, and guesses are where variation orders come from.

**The rates are current.** District rates move. A DPR priced on stale rates produces a tender that either attracts no bidders or attracts one who intends to claim the difference later.

**The risks are stated.** Every project has conditions that could change the cost — a river crossing, an unresolved land issue, a slope that needs investigation. Naming them in the report is not pessimism; it is the difference between a client who can plan and a client who is surprised.

None of this is expensive to do properly. It is mostly a matter of not skipping steps.