Capacity sits in one file and demand piles up in another. Completix puts them in the same view, so when a new idea arrives through intake you can model the work against the people you actually have, answer with evidence instead of a gut call, and defend the decision when it is challenged.
Most PMOs answer these from a spreadsheet, a few inbox threads, and memory. Here is what that looks like today, and where on this page Completix answers each one.
A sponsor wants a new initiative to start in March. The honest answer depends on the work the team already carries, and that lives in a different file from capacity.
See how it gets answeredAllocation questions get settled in inbox threads. By the time someone checks, the overloaded person has been overloaded for a month.
See both at onceHeadcount times forty ignores vacation, working patterns, and operational duties, so the plan starts short before any work is assigned.
See real availabilityStatus reports stay green while the people doing the work are stretched past what they can deliver. The slip shows up late, and all at once.
See it while it buildsScenario modelling lets you test a proposed initiative against actual resource capacity before committing to it. Give it its own demand, lay it onto a person or team, and Completix recalculates their allocation in real time. The weeks that tip into over-allocation show up at once, with modeled values hatched so they are never mistaken for committed work. This is scenario planning for capacity, and nothing changes in the live plan until someone applies the scenario.
Completix tracks utilization across every project a person is assigned to, so over-allocation and spare capacity sit side by side with the whole portfolio in view. Rebalancing becomes a decision made on evidence, before a missed date forces the conversation.
| Project | Role | Utilization | Actuals | Forecast |
|---|---|---|---|---|
| CRM Replacement | Developer | 60% | 212h | 184h |
| Mobile App v2 | Developer | 52% | 88h | 128h |
| Project | Role | Utilization | Actuals | Forecast |
|---|---|---|---|---|
| Data Migration | Analyst | 55% | 140h | 96h |
| ERP Modernization | Analyst | Model 2 · 40% | – | – |
Vacation, working patterns, days off, and operational duties all eat into the hours a plan assumes are there. Each person sets their availability in Completix, and it flows into the project schedule, the forecast, and the allocation, so the capacity you plan against is net of the time they are not working.
Because capacity and demand live in the same view, contention is visible as it forms. Where you have configured the triggers, the Warning Center surfaces resource over-allocation for review. Weighing what to do next is portfolio prioritization, tested against the capacity actually available.
Every view on this page draws on the same model, which keeps capacity and demand tied to the strategic initiatives the organization chose to pursue. It is the contention manufacturing PMOs face when plant engineers are shared across capital projects, and the one engineering programs face when specialists are stretched across several builds.
Net capacity against committed and modeled demand, by person or team, month by month.
What-if models with their own demand, shown in real time, then applied as a scenario or discarded.
Daily utilization per person, colored by severity, with modeled values hatched.
Every project a person is assigned to, with utilization, actuals, and forecast hours on one record.
Each person's commitments on a timeline, set against their availability, across every initiative they touch.
Working time and days off, set by each person and carried into schedule, forecast, and allocation.
One searchable view of who is off and when, so plans are built on the time people are actually present.
Forecast effort and cost against logged actuals by project and person, feeding financial management.
Time and cost views of effort, rolling up into portfolio reporting so the PMO sees where capacity is shaping delivery.
We will walk through your portfolio, your people, and their real availability, and show you where the contention is hiding.
A resource management plan defines what a project needs, when it needs it, and who decides where it goes. This guide covers the resource types, a build process, common pitfalls, and where software actually helps.
A practical guide to the five steps of project portfolio management, what each must produce, who owns it in the PMO, and the metrics leadership needs to see.
A repeatable project management process helps a PMO bring consistency to projects without imposing unnecessary bureaucracy. Learn how to standardize practices, improve adoption and build processes that scale across an organization.
