Phase-only budgets stop telling you the truth at some point
Most architecture firms set fee budgets at the phase level: a number for SD, a number for DD, a number for CDs, and so on. That works fine until a phase starts running hot. Then the report says “DD is at 95% of budget and 70% complete,” and you know you have a problem without knowing where it actually is.
Task-level budgeting is the next layer down. Inside a phase, you split the fee across the work items that phase is actually made of: floor plans, sections, exterior detailing, code review, sub coordination, meetings, redline pickup. When the report flags a phase, you can drop a level and see which task ate the hours.
The case for going one level deeper
Phase-only budgets give you the headline. They don't give you the cause. A few things shift when you have task-level budgets in place:
- The signal arrives earlier. If sub coordination on DD has its own budget, the PM sees it cross 80% before the whole phase looks bad.
- Future fee proposals get sharper. Task-level history tells you what redline pickup actually costs, what code review costs, what RFI volume is on a project this size. The next proposal is built on numbers, not feel.
- Staffing decisions improve. If interior coordination consistently runs over on every project, that's a hire, not a PM problem.
- Accountability lands somewhere. A task with a budget and an owner is much easier to manage than “DD” with a team of seven on it.
- Client conversations get easier. When a client asks where the fee went, “exterior detailing burned through more hours than we'd budgeted” lands better than a hand-wave.
What “financial visibility” actually means at the task level
Most firms talk about financial visibility at the project level: is the project profitable, are we on budget. The problem is that by the time the project-level number is wrong, the moment to act has usually passed.
Task-level budgets connect daily work to the financial picture. When a designer logs three hours on exterior elevations, those hours land against a specific task budget. The PM checking the project on Friday afternoon doesn't see “DD is fine.” They see that elevations is at 110% with two weeks of work left, and they can do something about that on Monday.
Over a few projects, patterns emerge. The same tasks run hot across project types. The same tasks come in under. That's the data you can't get from phase-only budgeting, and it's the data your next fee proposal needs.
How task-level budgeting works in Archflow
Archflow's budget tools support phase budgets and task budgets in the same model. Set up a phase, drop a fee and hour budget on it, then break it into tasks if the phase warrants it. You don't have to use task budgets everywhere — some projects need it, some don't.
Hours logged on a timesheet roll up to the task, the phase, and the project automatically. The dashboard highlights tasks that are approaching or past their budget so the PM can adjust without scanning the whole portfolio. That same task data flows into invoices and reports, which means your firm-level numbers are sharper because the underlying data is sharper.
How to actually start using it
You don't have to retrofit task budgets onto every project to get value out of them. Most firms start by adding task budgets to one or two project types where overruns are most painful, get a feel for the cadence, and expand from there.
The lever that compounds is consistency. Use the same set of tasks across similar projects so historical data accumulates. After three or four similar jobs, you have something useful to point at when pricing the next one.
If you want to get a sense of how it feels in practice, book a demo. We'll set up a project you're running today with phase and task budgets and you can poke at it.