When the budget and the narrative describe different projects

Reviewers rarely accuse applicants of bad faith when a budget and a narrative disagree. They simply conclude that the project is not yet designed. In audits, budget–narrative drift is one of the fastest ways to earn a clarification letter — or a quiet decline.

Where drift usually appears

The narrative promises field supervisors in each province; the budget funds one coordinator in the capital. The results framework counts four training cohorts; the budget lines only three. Letters of support name in-kind venue costs that never appear in the budget notes as leveraged contributions.

None of these errors require exotic forensics. They require someone to read the budget with the same attention given to the opening pages.

A practical reconciliation pass

Before you commission an outside audit, assign one person who did not write the narrative to complete a single table: each major activity in the narrative, the budget line that funds it, and the province or partner responsible. Empty cells are your drift map.

If an activity has no budget line, either cut the claim or fund it. If a budget line has no narrative home, either explain it in the notes or remove it. Half-measures — “capacity building” as a catch-all — are exactly what panel readers distrust.

What an auditor adds

An outside reader will also check whether unit costs, durations, and staffing percentages match the timeline in the work plan. Teams often fix province counts and still leave a six-month coordinator on a twelve-month project. That second-order drift survives internal reviews because everyone already “knows” what was meant.

Leave time for the awkward meeting where finance and programme staff disagree out loud. Better that meeting happen in your office than in a funder’s clarification round.