Bill of Resources & project costing

On a repeating product you can lean on a standard recipe: the same Bill of Materials, the same routing, the same cost. A project has no such luxury. Every one-off deliverable has to be costed from scratch — and the businesses that stay profitable are the ones that cost each task deliberately, with the people and machines it needs priced alongside the material, before the work starts. The tool for that is the Bill of Resources, and the discipline it enables is the difference between a quote that holds and a project that quietly eats its own margin.

This article is for the person who quotes and controls project cost — an estimator, project manager or business owner in an engineer-to-order, fabrication, EPC or construction business. It explains what a Bill of Resources is, how it differs from a Bill of Materials, how its priced lines roll up into a project cost estimate, and how estimated cost is compared against budget and against actual. If you have not yet broken your project into tasks, start with What is a Work Breakdown Structure? — a BOR is built per task. For the wider picture, see the pillar guide, What is project management software?

1. What a Bill of Resources actually is

A Bill of Resources (BOR) is the plan of everything a task will consume to be completed — its material, labour, machine and tool lines, each with a quantity and a rate. It is authored per task within a project, and because every line is priced, it does two jobs at once: it tells you what the task needs, and it tells you what that will cost.

The word "resources" is deliberate and broad. A task on a fabrication or EPC project does not just consume steel — it consumes a welder's hours, a machine's running time, a crane's day. A BOR captures all of it in one structure, so the cost of a task reflects the reality of doing the work, not just the reality of buying the material. That breadth is what makes the BOR the natural costing unit on a project, where labour and equipment are often a larger share of the cost than the material itself.

Three things make a BOR a working document rather than a rough estimate:

• It is per task. Each WBS task carries its own BOR, so cost is built bottom-up from real work, not guessed top-down from a lump sum.
• Every line is priced. Quantity × rate on every material, labour and machine line means the BOR is a cost the moment it is complete.
• The rates are shared. Prices come from a resource master, so the same crew or machine costs the same on every project, and a rate change flows everywhere at once.

2. BOR vs BOM — takes-to-make vs made-of

The Bill of Resources is easy to confuse with the Bill of Materials, and the distinction is worth getting exactly right because they answer different questions.

A neat way to hold the difference: a BOM is made-of, a BOR is takes-to-make. On a repeating product, a BOM plus a routing is enough. On a project, the BOR is the broader and more useful structure, because it prices the whole effort — material and the hands and machines that turn it into the deliverable. A project can still draw material from the shared item master; the BOR simply wraps that material together with the labour and machine lines the task also needs.

3. The three-level BOR structure

A task's Bill of Resources is not a flat list — it is a small three-level structure that mirrors how the work is actually organised. Understanding the levels makes the cost roll-up obvious.

The resource lines are the heart of it. Each is a real, priced item: a resource group (material, labour or machine), a resource code drawn from the master, a quantity per parent, a unit and a rate. Because the lines sit in a hierarchy under the process and header, a task's cost is a clean roll-up — sum the resource lines, and you have the task cost; there is no separate cost sheet to reconcile.

4. Rates and the resource master

A BOR is only as trustworthy as the rates on its lines, and the discipline that keeps rates trustworthy is holding them in one place — a resource master. Every machine, labour category and tool is defined once, with its rate, working hours per day, efficiency and unit, and every BOR line draws its rate from there rather than having a number typed in by hand.

Holding rates in a master rather than in each estimate is what keeps project costs comparable. When the same welding crew is priced three different ways on three different jobs, the numbers stop meaning anything; when it is priced once from the master, every estimate is built on the same foundation and a rate revision updates every project that uses it. See Resource Management.

5. Cost estimation — roll-up vs budget

With priced resource lines in place, cost estimation is arithmetic the software does for you. Each line's quantity is multiplied by its rate to give a line cost; the lines sum to an estimated task cost; and the tasks sum to an estimated project cost. That single number — built bottom-up from real resources — is then set against the project budget.

The value is in the timing. Because the estimate exists before work starts, an over-budget project is visible at the planning stage, when you can still re-scope, re-negotiate or re-plan — not at hand-over, when the loss is already booked. And because the whole roll-up reads from the resource master, changing a rate or a quantity re-flows the entire estimate instantly, so "what if the plate price rises" is a question you can answer on screen rather than by rebuilding a spreadsheet.

Cost estimation is a roll-up: priced resource lines sum to task costs, task costs sum to the project estimate, and the estimate is checked against budget before work starts.

6. Estimated vs actual

The estimate is what the BOR planned. The actual is what the project really consumed — and the two only agree if you capture the actual as it happens. As material is issued from the store against a task, and labour and machine time are booked, the actual cost builds up alongside the estimate on the same tasks.

Estimated-versus-actual is the comparison that turns costing from a one-time quote into live control. Because the project header holds both a budget and an actual budget — and both a planned finish and an actual finish — a project business can see cost variance and schedule variance against plan on one record. An overrun on a task shows up while the project is still running, when something can be done, instead of surfacing in a post-mortem after the money is gone.

7. A worked example — costing one task

To make the roll-up concrete, here is a single task — "weld and assemble a frame" — costed as a small Bill of Resources. All numbers below are illustrative, chosen only to show how quantity, rate and roll-up work — not drawn from any real project or price list.

Two things are worth noticing. First, labour and machine together (₹17,200 illustrative) rival the material (₹19,000 illustrative) — which is exactly why a material-only BOM would understate this task's cost badly. Second, the total is a clean roll-up: raise the plate rate, or add welder hours, and the task cost updates without touching a separate sheet. Roll several such tasks together and you have the project estimate that gets checked against budget.

8. How Fast Project Management implements BOR and costing

Fast Project Management Software is the project and ETO-execution product of the Fast Suite, built in Pune by Improsys under the Fast Technology brand and available cloud or on-premise. It implements the Bill of Resources and costing with real, named screens:

9. Frequently asked questions