--- title: "Budget-Constrained Project Planning | Orangescrum" description: "How to plan a project when the money is fixed and the scope has to flex: set the ceiling, price the work, and watch the variance." canonical: https://www.orangescrum.com/optimization/budget-constrained-project-planning --- # Budget-Constrained Project Planning | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Planning techniques](/optimization) / Budget-constrained project planning Planning technique # Budget-Constrained Project Planning, _Explained Properly_ When the budget is fixed, the plan has to be built backwards from the money. Here is how to do that, and what Orangescrum gives you to keep it honest. [Start free trial](/sign-up?utm_source=site&utm_medium=technique&utm_campaign=optimization_budget-constrained-project-planning) [See all features](/features) ## What is budget-constrained project planning? Budget-constrained project planning means deciding what a project will contain, and in what order, when the money available is fixed and the scope is the thing that has to flex. Instead of estimating a plan and then asking for funding, you start from the ceiling and work backwards: what can genuinely be delivered for this amount, at these rates, with these people. The technique depends on knowing three numbers well, the budget, the cost of the work already done, and the cost of the work still committed. When the forecast crosses the ceiling you have only three real levers, cut scope, change who does the work, or go back and ask for more money. Planning this way makes that conversation happen early, while the options are still cheap. ## Where budgets _quietly break_ - **The budget is a number nobody sees**It lives in a finance spreadsheet the delivery team never opens, so the first anyone hears about an overrun is at month end, when the money is already gone. - **Cost is estimated, never measured**Hours are guessed after the fact rather than logged as they happen, so the real cost of a task is unknown and every forecast is just a repeat of the original guess. - **Scope grows one small piece at a time**Each addition is too small to argue about on its own. Nobody tracks the running total, and together those small additions are the overrun. - **Rate differences are invisible on the plan**A timeline counts days, not money. Moving a task from a junior to a senior looks free on a Gantt chart and can change the cost of the project by a third. ## What Orangescrum _actually gives you_ Real features, named. Nothing here is an algorithm that decides for you. [**Put the ceiling next to the work**Record the project budget alongside the tasks, so the number the delivery team plans against is the same number finance is holding you to._Budget and cost_](/budget-and-cost-management)[**Turn hours into money**Logged time becomes actual cost at your rates, so the spend figure updates from real work instead of from a monthly estimate._Time tracking_](/time-tracking)[**Check the hours before they become cost**Weekly timesheets go through an approval step, so the time that turns into spend has been looked at by someone rather than accepted blind._Timesheets_](/timesheet)[**See what the plan is made of**Allocation shows who is booked on the project and for how long. That is what the cost is built from, so an unaffordable plan is visible before it starts._Resource management_](/resource-management)[**Compare planned with actual**Planned against actual cost, per project and per task, shows where the estimate was wrong. That is the only way the next estimate gets better._Reporting_](/project-reports-analytics)[**Keep the funding detail on the work**Add fields for cost centre, purchase order, or funding source, then filter and report on them when finance asks where the money went._Custom fields_](/custom-fields) ## How to _plan against a fixed budget_ 1. **Fix the ceiling and write it down where the team can see it**A budget that only finance can see is not a constraint, it is a surprise. Put the number on the project so every planning conversation starts from it. 2. **Price the work, not the days**Convert the estimate into money using real rates. Two plans with the same duration can differ enormously in cost depending on who is on them. 3. **Rank the scope before you need to cut it**Agree with your sponsor, in advance, what comes out first if the money runs short. Deciding that calmly in week one is far better than deciding it in week nine. 4. **Log time from the first day**Actual cost only exists if hours are recorded. A team that starts logging in month three has no baseline and no way to forecast the rest. 5. **Review forecast against ceiling every week**Look at spend so far plus committed work still to come. If that total is drifting towards the ceiling, act while cutting scope is still an option. ## What Orangescrum does not do here Orangescrum tracks budget and cost. It does not solve for the best plan within a budget ceiling. There is no optimiser that takes your ceiling, your rates, and your backlog and returns the most valuable scope you can afford. What you get is the ceiling, the actual spend, the variance, and the allocation driving it, updated as work is logged. Deciding what to cut when the forecast crosses the line is a judgement for you and your sponsor. Budget and cost tracking is on Cloud Pro and above, and included in Self-Hosted. ## Budget-constrained planning FAQ Does Orangescrum automatically build a plan that fits my budget? No. There is no solver that takes a budget ceiling and returns an affordable plan. Orangescrum records the budget, turns logged time into actual cost, and shows the variance as it moves. Choosing what scope to keep and what to drop is a human decision, made with those numbers in front of you rather than made for you. How is actual cost calculated? From logged time against your rates. Someone records the hours they spent on a task, and those hours become cost. This is why teams that log time properly get a forecast worth reading and teams that log time at the end of the month do not. How do I see cost broken down below project level? Time is logged against individual tasks, so you can see which work absorbed the hours. For grouping beyond that, such as cost centre, work package, or funding source, add a custom field and report by it. What do I do when the forecast crosses the ceiling? There are only three honest answers: reduce the scope, change who does the remaining work so it costs less, or ask for more money. Delivering the same scope with the same people for less is not a fourth option, however often it is requested. Which plan or edition do I need for this? Time logging is in all three editions. Timesheets and budget and cost tracking are on Cloud Pro and above, and included in Self-Hosted. Resource management is on Cloud Premium and included in Self-Hosted. Does Orangescrum stop work when the budget is spent? No. It does not block time logging or close tasks when spend passes the ceiling. It shows you the overrun. A hard stop would hide the real cost rather than reveal it, and you would find out later and worse. Is this the same as fixed-price delivery? They are related but not the same. Fixed price is a commercial arrangement with your customer. Budget-constrained planning is how you plan the work inside any funding limit, whether the contract is fixed price, time and materials, or an internal cost centre. ## Plan against the real number Free 14 day trial, no credit card. Every plan includes unlimited users. [Start free trial](/sign-up?utm_source=site&utm_medium=technique_cta&utm_campaign=optimization_budget-constrained-project-planning) ## Related [**Budget and cost**Track spend against the ceiling](/budget-and-cost-management)[**Time tracking**Where the money actually goes](/time-tracking)[**Cost-efficient task sequencing**Order work so it costs less](/optimization/cost-efficient-task-sequencing)[**Resource-constrained scheduling**Planning around limited people](/optimization/resource-constrained-scheduling)