Why Resource Conflicts Keep Happening — and How to Fix Them
Resource conflicts are one of the most common problems in project environments.
The same people are wanted by several projects. Delivery dates overlap. Project managers assume resources will be available when they are not. Teams appear fully allocated on paper, while important work still slips.
The problem is usually not a lack of effort.
It is a lack of visibility and control over capacity, allocation and actual usage.
When organisations manage resources project by project instead of across the portfolio, conflicts are almost inevitable.
The first problem: projects plan in isolation
A project manager may build a perfectly reasonable plan based on the people they believe they need.
The problem is that several other project managers may be doing the same thing.
Each project looks achievable on its own.
The portfolio does not.
A resource conflict appears when the same person, role or specialist capability is expected to support more work than the organisation can realistically deliver.
That is why resource planning has to start above the individual project.
The organisation first needs to understand:
what capacity exists;
what work has priority;
what has already been committed; and
what capacity remains available.
Only then can projects be planned with confidence.
Capacity and allocation are not the same thing
These terms are often used interchangeably, but they describe different things.
Capacity is the amount of time or effort a resource has available.
Allocation is the portion of that available capacity that has been committed to particular work.
For example, someone may have 160 working hours available in a month.
That is capacity.
If 80 hours are committed to Project A and 40 hours to Project B, then 120 hours have been allocated.
The remaining 40 hours are still available for other work, assuming they are not reserved for BAU, leave or other commitments.
The distinction matters because a project should not assume that available capacity automatically belongs to it.
The second problem: allocation happens too late
In many organisations, projects are approved first and resource problems are dealt with afterwards.
The project gets a target date.
The budget gets approved.
The project manager creates the plan.
Only then does someone ask:
Who is actually available to do the work?
By that point, expectations have already been set.
A stronger process brings allocation forward.
The organisation should confirm resource availability before detailed delivery commitments are made.
That creates a much stronger sequence:
Capacity → Allocation → Project assignment → Forecast
This avoids building delivery plans around resources the organisation does not actually have.
The third problem: overcommitment is hidden
Resource overcommitment is often difficult to see when planning happens across spreadsheets, local project plans and separate systems.
One project may show someone at 50%.
Another may show the same person at 60%.
A third project may assume another 30%.
Individually, none of the plans looks unusual.
Together, the person is expected to deliver 140% of their available capacity.
The conflict only becomes visible when deadlines start slipping.
A portfolio-level allocation view should make that impossible to miss.
The organisation should be able to see, by month:
available capacity;
committed allocation;
remaining capacity;
conflicting project demands; and
future shortages.
That gives management time to act before the problem reaches delivery.
The fourth problem: planned utilisation is mistaken for actual utilisation
Another common source of confusion is treating allocation as proof that a resource is being used effectively.
It is not.
Allocation tells you what has been committed.
Utilisation tells you how much of that commitment is actually being used through planned assignments or recorded work.
For example, a resource may be allocated 80% to a project but only have enough project assignments to consume 40% of their capacity.
That gap matters.
It can mean:
the project plan is incomplete;
work has not yet been assigned;
the allocation is too high;
project timing has changed; or
capacity could be released elsewhere.
Strong resource governance therefore needs to compare allocation and utilisation, not simply display one number.
The fifth problem: organisations rely too heavily on named people
Projects often start by asking for specific individuals.
“We need Sarah.”
“We need James.”
“We need the senior architect.”
Sometimes that is appropriate.
But it can also make planning unnecessarily rigid.
What the project may really need is:
one business analyst;
two senior developers;
a procurement specialist;
an engineer with a particular capability.
This is where placeholder resources are useful.
A placeholder represents a resource requirement before a named person has been assigned.
It allows the organisation to plan demand honestly without pretending that the required person has already been secured.
That makes capability gaps visible much earlier.
Placeholders make shortages visible before they become crises
Imagine a portfolio needs five data engineers in January, but only three are available.
If every project simply puts a person's name into its plan, the shortage can remain hidden.
Using placeholders makes the gap explicit:
Demand: 5 data engineers
Available capacity: 3
Unfilled requirement: 2
Management can then decide whether to:
recruit;
use contractors;
delay lower-priority work;
move project dates;
change scope; or
redistribute capacity.
That is much better than discovering the shortage when projects are already late.
The sixth problem: priorities are not reflected in allocation
When capacity is limited, not every project can receive everything it requests.
Something has to decide who gets the resource.
Without clear portfolio priorities, allocation often becomes a negotiation between the loudest project managers.
That can result in strategically important work waiting while lower-value projects consume scarce capacity.
Resource allocation should therefore connect directly to portfolio prioritisation.
A higher-priority project may legitimately receive capacity before a lower-priority one.
That does not mean lower-priority work is unimportant.
It means the organisation is making an explicit trade-off instead of allowing resource conflicts to decide priorities by accident.
The seventh problem: BAU work is ignored
Projects are not the only demand on people.
Teams also have:
operational responsibilities;
support work;
management activity;
administration;
training;
leave; and
other non-project commitments.
If those demands are not represented, project capacity will always look larger than it really is.
A resource should not appear to have 100% project capacity simply because non-project work has been left out of the system.
A stronger model allocates capacity somewhere.
If a person is not available to projects, that capacity should be visibly committed to BAU or another category.
This prevents the portfolio from planning against imaginary availability.
The eighth problem: project timing changes without resource timing changing
Projects move.
A project planned for March may slip to May.
A programme may be accelerated.
A dependency may delay a workstream.
When project timing moves, resource allocation must move with it.
Otherwise the organisation ends up with a strange situation:
the project has changed, but its capacity commitment has not.
That can create two problems at once.
Resources appear unavailable in the old period and unplanned in the new one.
Resource governance should therefore make timing changes visible immediately across the allocation picture.
What good resource governance looks like
A reliable resource process has a simple logic.
Capacity → Prioritisation → Allocation → Assignment → Utilisation → Review
Each step answers a different question.
Capacity: What do we actually have available?
Prioritisation: Which work matters most?
Allocation: What capacity are we committing?
Assignment: What work will each resource perform?
Utilisation: Is the allocated capacity actually being used?
Review: Do we need to move, release or increase capacity?
When these stages are connected, resource planning becomes much more than a monthly spreadsheet exercise.
It becomes a portfolio control process.
A useful rule: no allocation before commitment
One of the strongest controls is simple:
No allocation → no project task assignment.
That means a project should not assign someone to planned work unless the organisation has already committed the required capacity.
The next control follows naturally:
No project task assignment → no forecast.
If the work has not been assigned, the financial forecast should not pretend that the corresponding resource cost is committed.
And finally:
No forecast → no timesheet.
This creates a controlled chain between capacity, delivery, cost and actual usage.
Resource conflicts are often a portfolio problem, not a people problem
When the same person is overcommitted across several projects, it is easy to blame poor planning at project level.
But often the deeper problem is portfolio governance.
Too much work has been approved.
Priorities are unclear.
Capacity is invisible.
Allocation decisions are informal.
Resource shortages are not surfaced early enough.
In those situations, asking project managers to “manage their resources better” will not solve the problem.
The portfolio needs stronger control over demand and commitment.
A simple test for your portfolio
Ask these questions:
Can you see resource capacity across the entire portfolio?
Can you see how much of that capacity has already been allocated?
Can you identify overcommitment before delivery is affected?
Can projects distinguish between named and placeholder resources?
Do project priorities influence allocation decisions?
Is BAU demand included in capacity planning?
Can you compare allocation with actual planned utilisation?
When project dates move, do resource commitments move with them?
If several answers are “no”, resource conflicts are likely being managed too late.
Better resource control creates better project control
Resource management is not separate from project financial control.
Resources drive work.
Work drives cost.
Cost drives the forecast.
If capacity and allocation are weak, the financial forecast will eventually become weak too.
That is why reliable portfolio management starts before the forecast.
It starts by understanding what capacity exists, deciding where it should be committed, and making sure project plans reflect those decisions.
When that happens, resource conflicts become easier to see, easier to explain and much easier to prevent.
Put stronger resource controls into practice
ProjectFiles connects capacity, allocation, project assignments, utilisation, financial forecasts and portfolio governance in one controlled environment.
Clarity. Control. Confidence.
Numbers that hold up when challenged.
