Project resource planning software for teams that run many projects
Resource planning software answers the question project tools leave open: who is free to do this work, with the right skills, in the weeks it has to be done. Most project management software with resource planning added on still looks at one project at a time. We build project resource planning systems that look across every project, person and skill in the company, connected to the project management tools your teams already use, hosted in an EU region and with the code in your company's name.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Why project resource planning is its own problem
A project plan lists tasks, durations, dependencies and dates. It does not know that the one architect who can do the design review is already booked 80 percent on another client's project that month, on holiday for a week, and spending Fridays on internal work. Planned one project at a time, each plan looks fine. Added together, some people are booked at 140 percent and others at 30.
That is the situation in many consulting firms, engineering and design offices, IT and software teams, agencies, research groups and project-based contractors. The planning is done in spreadsheets kept by one or two people, or in a project tool whose resource view nobody trusts. The cost is familiar: late projects, overworked specialists, people sitting idle while new work is turned away, and sales saying yes to projects delivery cannot staff.
What the system does
- People and capacity. Each person's working hours, part-time rules, leave, public holidays by country and time set aside for internal work, so capacity is what is really available.
- Skills and roles. Skills, levels, certifications and languages per person, so a task asks for "senior structural engineer, German" rather than a name.
- Demand. Projects, phases and tasks with the roles and hours they need per week, imported from the project tools or entered by project managers.
- Bookings. People booked to projects by hours per day or percentage per week, tentative or confirmed, with the project manager and the line manager both seeing the result.
- Conflicts. Over-booking, bookings during leave and tasks with no one booked, shown at once and per week.
- Utilisation and forecasts. Planned and actual utilisation per person, team and office, and the capacity left over the coming months.
- Scenarios. What happens to the plan if a project starts a month later, or a proposal is won, before anyone is moved.
Capacity, demand and the gap between them
The heart of resource planning is a simple comparison: the hours each skill can give per week, against the hours the projects need. Shown per week for the next three to six months, it tells a manager three things at once. Where the company is short, so hiring or subcontracting can start early. Where people have time with nothing booked, so sales can be told what can be sold. And which projects compete for the same scarce people, so priorities are set by the people who own them and not by whoever books first.
| Question | Where the answer comes from |
|---|---|
| Can we take this project in March? | Free capacity per skill in March, including tentative bookings |
| Who can replace a person on leave? | People with the same skill and free time in those weeks |
| Are we over-promising? | Booked hours against capacity, per person and per team |
| Is this project on its staffing plan? | Booked and actual hours against the plan per phase |
| Do we need to hire? | The gap between demand and capacity for a skill over the next months |
Tentative bookings: the link between sales and delivery
A good share of resource conflicts start before a project is signed. Sales promises a start date, the client signs, and delivery finds the people are already booked. We build tentative bookings into the plan: a proposal holds the people it would need, with a probability and an expiry date, and is shown apart from confirmed work. When the proposal is won it becomes confirmed with one action; when it is lost the people are released. If your proposals are tracked in a CRM, the tentative bookings can follow its stages, as described on our CRM development page.
Connected to the project tools you keep
Resource planning should not become another place where project data is typed again. Project managers keep planning tasks in the tools they know, whether Jira, Azure DevOps, Asana, Microsoft Project or an industry tool, and the resource planning system reads projects, phases, tasks and estimates from them. Actual hours come from time tracking, and approved hours can go on to invoicing and payroll. We connect each system through its interface, as our API integration page describes.
One change many organisations face now: Microsoft retired Project Online on 30 September 2026. Its final reminder in the Microsoft 365 message centre (message MC1478955, read 11 November 2026) said customers would no longer be able to access their projects or associated data within the service after that date. Project desktop and Planner are separate products. If your resource planning lived in Project Online, the project data you exported can be the starting point for the new system.
Working time and fair loading
A resource plan is also a working time plan. In the EU, the Working Time Directive, Directive 2003/88/EC (read 11 November 2026), Article 6, limits average weekly working time, including overtime, to 48 hours over a reference period, and the Court of Justice held in case C-55/18 CCOO, decided on 14 May 2019, that employers must have a system that measures each worker's daily working time. National law and collective agreements set the details. The system flags people booked beyond their contract or the limits you set, keeps planned and actual hours side by side, and shows who has been loaded heavily for several weeks in a row, which is often the first sign of a resignation.
Booking and time data is personal data. Roles decide who sees what: a project manager sees bookings on their projects, a line manager sees their team, and only the people who need it see utilisation by name. Data is hosted in an EU region as standard.
Resource scheduling software: people, rooms and equipment
Resource scheduling software is a wider term than project resourcing, and it helps to know which kind you need. This page is about software resource scheduling for knowledge work: people booked onto projects by skill and by week. Shift-based work, where staff are rostered to opening hours or production lines, belongs to employee scheduling software. Booking things rather than people, such as rooms, vehicles, machines or equipment, follows the same logic of capacity and conflicts, and the system we build can hold them as resources too: a project that needs a test lab for two weeks or a specialist instrument on site is booked like a person, with the same tentative and confirmed states. One resource scheduling view across people and equipment avoids the common failure where the team is free but the machine is not.
Room scheduling software for offices is a separate, mostly ready-made category: meeting rooms and desks booked from the calendar people already use, panels outside the door, and bookings released automatically when nobody checks in. Microsoft 365 and Google Workspace both treat rooms as bookable calendar resources, and for most offices that plus a booking product is enough. Custom work fits when rooms are part of an operation rather than an office, such as training centres, clinics, studios, labs or sports halls (see sports scheduling software) where a room comes with equipment, staff and cleaning time; the massage scheduling page shows how one booking can hold a person, a room and equipment together. If occupancy sensors are added, the data shows where employees are, so it is planned as personal data under the GDPR from the start.
Ready-made tool or custom resource planning?
There are capable resource planning products, such as Float, Resource Guru and the resource modules in larger project and professional services suites, and for many teams one of them is the right choice. We say so when it is. Custom resource planning, or a custom layer around a product, fits when:
- the skills, roles or booking rules are specific to your field and do not fit the product's model;
- projects come from several tools, and no product reads them all;
- resource planning has to work with your own ERP, CRM, time tracking or invoicing in a way the product does not support;
- you need scenarios, forecasts or reports the product cannot give;
- you want the planning data and logic in your own hands, without per-user fees growing with the company.
For shift work at fixed sites, the better fit is our employee scheduling software or workforce management software; for construction crews, construction labor scheduling software.
How we build it
- Planning walk-through. Your resource managers, project managers and sales show us how a project is staffed today, from proposal to finish, and where it goes wrong.
- Scope and fixed price in writing. Capacity and skill model, booking rules, views, integrations and what the first phase leaves out.
- Data first. People, skills, current projects and bookings moved from the spreadsheets and tools, and checked with the people who know them.
- Planning views. The capacity board, conflicts and project staffing built in two-week rounds, with your planners using each version.
- Integrations and reports. Project tools, time tracking and the reports managers ask for each week.
- Parallel run and switch. The new plan runs next to the old spreadsheet for a few weeks, and then replaces it.
The code sits in your company's repository, and the database and hosting are in your name. Dashboards for leadership can be built on the same data, as our dashboard development page describes. See prices.
Questions we get
What is resource planning in project management software?
It is the part that answers who works on what, and when. Project management software plans tasks and dates; resource planning matches those tasks to people with the right skills and free time, across all projects at once, and shows where the company is short of people or has people with nothing booked.
Why is resource planning hard in normal project tools?
Most project tools look at one project at a time. A person who is half on one project and half on another looks free in both. Resource planning needs a company-wide view: each person's capacity after leave and internal work, every booking across every project, and the skills each task needs.
What is the difference between a tentative and a confirmed booking?
A tentative booking holds people for work that is likely but not signed, such as a proposal in progress. A confirmed booking is for agreed work. Keeping both in the plan shows sales and delivery whether the company can take on the next project before it says yes.
Can it connect to Jira, Microsoft Project or our time tracking?
Yes. We read projects, tasks and estimates from the tools your teams already use and actual hours from time tracking, so the resource plan and the projects stay in step. Planners book people in one place instead of typing data into several tools.
We used Project Online. What now?
Microsoft retired Project Online on 30 September 2026, and its notice says customers would no longer be able to access their projects or data in the service after that date. If your resource plans lived there, we can build resource planning around the project data you exported, or around the tool you moved to.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.