A resource-loading scenario is a costed version of a proposed delivery team. It records roles, skill or location, allocation by period, duration, deal budget, and governed cost assumptions, then calculates an option margin on one consistent basis. Comparing scenarios reveals trade-offs; it does not automatically select the team most likely to deliver.
In plain words
A resource-loading scenario is one possible way to staff a project: which roles, how much of their time, for how long. Comparing two or three scenarios on cost and margin shows how much the choice of team changes the result.
Who this helps: Presales consultants, delivery leads and finance staff who compare staffing choices.
Questions this guide answers:
- What is a resource-loading scenario?
- How do you compare staffing scenarios for a proposal?
- How does team mix change project margin?
What is a resource loading scenario?
A scenario should express a delivery hypothesis in units that finance, presales, and delivery can inspect. At minimum, that means a named role or role profile, a time period, an allocation, a cost-rate basis, and the commercial amount against which cost will be compared. Skill, seniority, and delivery location may matter when they change capability or cost.
PMI's estimating guidance describes planned cost as a combination of the resources required, how long or how intensively they are applied, and their cost rates. That relationship makes a resource plan more useful than a single margin percentage: reviewers can see which assumption produced the result.
Option margin = deal budget − commission − labor cost − overhead
Use the firm's documented cost boundary. If overhead is already embedded in the cost rate, do not add the same cost again.
The scenario should remain a comparison model, not a staffing promise. A role may be a placeholder rather than a named person, and a financially attractive mix may still be unsuitable because of availability, skills, continuity, client commitments, or delivery risk.
Example: three ways to staff one IT deal
Assume a USD 120,000 fixed fee and a ten-week plan using a 40-hour week. Senior planning cost is USD 100 per hour and delivery-role cost USD 50. Quantity is one per role. The following alternatives assume the same scope, but delivery must validate whether the different supervision levels are feasible.
| Option | Senior loading and cost | Delivery loading and cost | Labor total |
|---|---|---|---|
| A: senior-heavy | 100% × 400 h × USD 100 = USD 40,000 | 100% × 400 h × USD 50 = USD 20,000 | USD 60,000 |
| B: balanced | 75% × 400 h × USD 100 = USD 30,000 | 100% × 400 h × USD 50 = USD 20,000 | USD 50,000 |
| C: lean | 62.5% × 400 h × USD 100 = USD 25,000 | 100% × 400 h × USD 50 = USD 20,000 | USD 45,000 |
Commission is 5% of fee, or USD 6,000 for each option. Labor overhead is 10%, giving USD 6,000, USD 5,000 and USD 4,500. Margin amount = fee − labor − commission − overhead. A leaves USD 48,000 / 40%; B leaves USD 59,000 / 49.17%; C leaves USD 64,500 / 53.75%.
C assumes 150 fewer senior hours than A. It is cheaper only if the work can be delegated or simplified without losing required quality. Add review, onboarding and likely rework to the applicable role before deciding. Loading shows assumed time; it does not confirm a named person is available. In Managed Margin, create one strategy per option, enter these rates and allocations, add the common cost rules, and compare the results before finalizing the approved plan.
Scenario: which of the three options goes to the approver?
Take the three options above (A senior-heavy, B balanced, C lean) on the USD 120,000 fixed fee. The margin alone would pick C at 53.75%. Here is how the three reviewers actually decide.
| Reviewer | What they check | What they say about this deal |
|---|---|---|
| Presales lead | Commercial context | The client is price-sensitive but the scope is clear. The fee is USD 120,000 under every option, so the choice changes our margin, not the client’s price; A leaves the thinnest margin (40%) |
| Delivery lead | Can the roles do the work? | C relies on 150 fewer senior hours. The integration needs senior judgment, so C is only safe if we add review time |
| Finance | Rates and cost rules | Same 5% commission and 10% overhead applied to every option; the arithmetic is right |
- The delivery lead adds 60 senior review hours to C: 60 × USD 100 = USD 6,000, so C's labor rises from USD 45,000 to USD 51,000.
- C's overhead becomes USD 5,100, and margin = 120,000 − 51,000 − 6,000 − 5,100 = USD 57,900, or 48.25%.
- B (49.17%) now beats the adjusted C and needs no extra assumption, so the approver chooses B and records why.
The highest calculated margin is not automatically the best option. The goal is a plan that is commercially acceptable and operationally credible. The worked mechanics of loading roles by week are in the resource loading pricing example.
What should you check when comparing scenarios?
- Hold the commercial basis constant. Compare options against the same deal budget, scope version, commission rule, and overhead rule.
- Check the time shape. Confirm that allocation by period matches the actual sequence of work, including mobilisation and closeout.
- Challenge role feasibility. Ask whether each role has the required skill and whether the planned work can be performed at that seniority.
- Trace every rate. Record the effective cost assumption and flag project-specific overrides.
- Test sensitive inputs. Examine how a longer duration, higher allocation, or changed role mix affects cost and margin.
- Document the selection. Record why the chosen option is commercially acceptable and operationally credible.
The UK Infrastructure and Projects Authority's cost-estimating guidance recommends documenting assumptions and exclusions, using consistent units and baselines, reviewing evidence, and applying sensitivity analysis. A lightweight services-pricing review can use the same disciplines without pretending the comparison predicts an outcome.
What does a Managed Margin pricing strategy calculate?
Each project pricing scenario is saved as a pricing strategy on its service order. You plan roles from your resource profiles on a weekly or monthly grid for the engagement length; hours come from each location’s working week. The strategy calculates hours, labor cost, revenue (the quoted price for fixed price, or billable hours at client billing rates for time and materials), your cost rules, three margin layers and markup. Compare strategies side by side, revise or duplicate them, and finalize one as the approved pricing baseline.
The calculation is only as current as its inputs. It does not confirm who is available or guarantee that the team can deliver the scope; delivery names people against the finalized seats after handover. Read the sales-to-delivery handoff guide, or see project pricing software.
Real example: a presales consultant builds three scenarios
An illustrative story with invented figures, to show how the idea works in a real office.
Pedro, a presales consultant, builds three scenarios for one USD 120,000 proposal: a fast one with a larger team for 8 weeks, a standard team for 12 weeks and a lean team for 16 weeks. (Direct labor only, to keep the example simple.)
He keeps the scope, the quality bar and the fee the same, so the only thing changing is staffing. The fast scenario costs USD 96,000 (20% margin), the standard USD 84,000 (30%) and the lean USD 78,000 (35%).
The client wants speed, so Pedro explains what it costs: ten margin points compared with the standard plan. Sales decides whether to accept that.
When do you compare scenarios, and what comes before and after?
| Stage | Owner | Checkpoint |
|---|---|---|
| Frame the options | Presales consultant | Same scope version, fee and cost rules for every option |
| Cost each option | Presales consultant | Role, allocation, duration and approved rate are traceable |
| Challenge | Delivery lead and finance | Roles are feasible; policies applied identically |
| Choose | Final approver | The reason for the choice is recorded, with the options rejected |
| Hand over | Project manager | The chosen option becomes the delivery baseline |
Resource loading scenarios: frequently asked questions
How many scenarios should I build?
Start with a small set of materially different, feasible alternatives. Add another only when it tests a decision not represented by the existing options. There is no universal optimal number.
How do scenarios connect to the baseline?
The chosen one becomes the baseline, as in the sales-to-delivery handoff guide.
Continue the sequence: guides to read next
- Resource Loading Pricing Example for an IT Project: a worked scenario from cost to margin
- How to Price an IT or Professional Services Project: where scenarios fit in pricing
- Project Baseline Handoff: From Sales to Delivery: what happens after you choose
Sources and methodology
- Project Management Institute, Project Management 101: Estimating. Used for the relationship among resources, duration or application, rates, and planned cost.
- UK Infrastructure and Projects Authority, Cost Estimating Guidance. Used for assumptions, evidence, consistent baselines, review, and sensitivity principles.
- The worked comparison is original. Product claims were reviewed against the current Managed Margin application on 26 September 2026.