What project resource planning means
A Gantt schedule tells you when each task should run. It says nothing about whether you have the welder, the crane and the machining centre free to run them. Resource planning fills that gap: it is the discipline of defining the machines, labour and tools your projects consume, planning them into each task, assigning people to own the work, and checking that you have not promised the same resource to two tasks in the same week.
It matters because resources are where projects actually get stuck. Material can usually be bought; a schedule can be redrawn; but a shop has one crane and a fixed number of skilled welders, and those constraints decide what can really happen when. Planning resources explicitly — rather than assuming they will be there — is what turns an optimistic Gantt into a plan the shop can keep.
The resource master — the priced pool
Resource planning starts from a single resource master: the pool of machines, labour categories and tools that every project draws on. Each resource is held once, with the attributes that let it be both scheduled and costed:
- Rate / price. The cost per unit — per hour, per day, per shift — that flows into every Bill of Resources line and, through it, into cost estimation and billing.
- Working hours per day. How much capacity the resource offers, so the schedule knows how long a given quantity of work will take.
- Efficiency. The factor that adjusts nominal capacity to realistic output, so plans are not built on textbook rates the shop never actually hits.
- Default holiday, unit and codes. A barcode, unit of measure and default non-working days, so availability and identity are unambiguous.
Holding all this once, in the master, is what keeps every project consistent. A crane-hour costs the same and offers the same capacity on project A as on project B, and when a rate or a shift pattern changes you update it in one place. That single source is the resource management module, and it is the reason estimates across a shop can be compared at all.
Classifying resources
A pool of a few hundred resources is only useful if it is organised, so resources are classified three ways — by group, category and type. Group might separate machines from labour from tools; category might split labour into skilled, semi-skilled and helper; type might distinguish a CNC machine from a manual one. The classification is not bureaucracy: it is what lets a Bill of Resources pick the right resource quickly, what lets a resource report roll consumption up by group, and what makes a large pool searchable rather than a flat list nobody can navigate.
Machines
Cranes, welding sets, machining centres, cutting machines — each with a machine-hour rate, working hours and efficiency, so plant time is planned and costed, not assumed free.
Machine-hour rateLabour
Trades and crews — welder, fitter, machinist, helper — by category, each priced as a man-hour or man-day, so effort is a costed line rather than a flat percentage.
Man-hour rateTools
Jigs, fixtures and consumable tooling committed to a task, held in the same pool so their cost and availability are planned alongside machines and labour.
ToolingAssigning resources and named users
Once the pool exists, planning a project means pulling resources into each task’s Bill of Resources — which machines, which trades, how many hours. But a resource line alone does not say who is responsible. That is where named-user assignment comes in: a specific person can be assigned to a task or to a BOR node, with their email, a priority, a planning date and a quantity, so the effort is owned by someone accountable rather than floating anonymously in the plan.
This is the difference between “welding needs 120 man-hours” and “these hours are owned by this team, starting this date.” The first is an estimate; the second is an assignment someone can be held to. It also makes alerts meaningful — task and milestone notifications can reach the named owner — and it feeds the audit trail, because dated task logs record who did what against the work they owned.
See your resource pool drive a plan
We can show you a resource master of machines, labour and tools feeding a task’s Bill of Resources and a resource-wise Gantt, with named owners, in a 30-minute demo.
Load-checking on the Gantt
The last step in resource planning is the one most shops skip: checking that the plan is physically possible. A project Gantt sequences the tasks of one job, but a resource-wise Gantt shows how each machine and crew is loaded across every job running at once. That view is where you catch the crane promised to two erection tasks in the same week, or the welding team booked at 150% of its capacity — before work starts, while you can still re-sequence or hire in, rather than on the day the conflict bites.
Because the resource master holds working hours and efficiency, the load view is realistic rather than nominal: it knows a resource’s true daily capacity, so an overload is a real overload, not an artefact of textbook rates. See Gantt scheduling for how the two views work together.
The bridge between scheduling and costing
Resource planning is the one discipline that touches both halves of a project business at once. The same priced resource, pulled into a task, does two jobs: its working hours and efficiency feed the schedule, and its rate feeds the cost estimate and, later, the bill. Plan resources well and scheduling and costing agree with each other, because they are reading the same numbers. Plan them in separate spreadsheets and the schedule and the cost drift apart until neither can be trusted.
How Fast Project Software plans resources
Fast Project Software centres resource planning on a shared resource master: machines, labour and tools, each with a rate, working hours, efficiency, default holiday and unit, classified by group, category and type. Those resources are pulled into each task’s Bill of Resources, named users are assigned to tasks and BOR nodes with a priority and planning date, and a resource-wise project Gantt shows how the pool is loaded across every job. The rate on each resource feeds cost estimation and project billing, so one pool serves scheduling, costing and billing together. It suits ETO manufacturers, fabrication shops and EPC firms; pricing is indicative and in INR — see pricing.
Frequently asked questions
What is project resource planning?
Project resource planning is the discipline of defining the machines, labour and tools your projects consume, planning them into each task's Bill of Resources, assigning people to own the work, and checking that the same resource has not been promised to two tasks at once. It starts from a resource master — the priced pool of resources — and bridges scheduling and costing, because the same resource's working hours feed the schedule while its rate feeds the cost estimate and the bill.
What is a resource master?
A resource master is the single pool of machines, labour categories and tools that every project draws on, with each resource held once. Each carries a rate or price, working hours per day, an efficiency factor, a default holiday, a unit and identifying codes, and is classified by group, category and type. Holding these attributes once keeps every project consistent — a crane-hour costs the same and offers the same capacity everywhere — and lets a rate change be made in one place and flow into every open plan and estimate.
How are named users assigned to project work?
A specific person can be assigned to a task or to a Bill-of-Resources node, with their email, a priority, a planning date and a quantity, so the effort is owned by someone accountable rather than floating anonymously. This turns 'welding needs 120 man-hours' into 'these hours are owned by this team, starting this date' — an assignment someone can be held to. It also lets task and milestone alerts reach the named owner and feeds the dated task logs that record who did what.
Why plan machines and tools, not just labour?
On many projects the plant — cranes, welding sets, machining centres — is the biggest constraint and a large share of the cost, yet materials-and-labour planning ignores it. A shop usually has one crane and a fixed number of skilled trades, and those limits decide what can really happen when. Holding machines and tools in the same priced resource pool as labour means their cost and availability are planned and costed alongside everything else, so the schedule is achievable and the estimate is complete.
How does resource planning connect scheduling and costing?
The same priced resource does two jobs at once. Its working hours and efficiency feed the Gantt schedule, determining how long a quantity of work takes and how heavily a resource is loaded across all projects. Its rate feeds the cost estimate and, later, the project bill. Because scheduling and costing read the same resource numbers, they agree with each other; when resources are planned in separate spreadsheets, the schedule and the cost drift apart until neither can be trusted.