Project Budget Template
Projects don't overrun in total \u2014 they overrun one task at a time, quietly, in the lines that never had a number. This sheet gives every task its own row: labor as hours times rate (computed), materials and other costs beside it, and the task's budget one column over. The totals reconcile at the bottom, and REMAINING tells you the only running truth a project manager needs between status meetings.
One sheet, every format.
Estimate at the task level or not at all.
A project budgeted as one number is a wish with a deadline. The row-per-task structure is the discipline: forcing an hours estimate per task surfaces the vague ones immediately (the task you can’t estimate is the task you don’t understand yet), and when reality arrives, the variance points at a specific piece of work instead of the project in general. “We’re 20% over” starts an argument; “integration testing took 30 hours against 12” starts a fix.
Two habits from teams whose projects land on budget: estimate labor in hours even for fixed-fee work (the fee goes in Other, but the hours tell you whether the fee was sane), and add an explicit contingency task — 10-15% of the total, spent by name when surprises arrive. A project that ends with contingency unspent came in under budget honestly; one that never budgeted contingency just hid the same money inside padded tasks where no one can learn from it.

