Every decision, weighed against the whole portfolio.
Simulate funding shifts, team moves, and timeline changes across the portfolio. Build a what-if scenario, load the resources, budget, and schedule you are considering, and preview the impact. Nothing touches the real portfolio until you apply it.
Spreadsheets guess. A modeling project shows you.
Most portfolios still test a big change the same way: a spreadsheet, one variable at a time, built by whoever has the time to build it.
Testing a change today
- Budget, resourcing, and schedule get modeled in separate files, if they get modeled at all.
- The numbers are pulled by hand and go stale the moment the real portfolio moves.
- Comparing two options means keeping two files straight and hoping the assumptions match.
- Nobody outside the file can tell what was modeled and what is actually committed.
Testing a change in Completix
- Budget, resourcing, and schedule are loaded into one modeling project, together.
- It draws from the live portfolio, so the starting point is current, not remembered.
- Build a second modeling project and set them side by side under the same assumptions.
- Modeled data is marked as modeled, so what is real and what is a draft is never in question.
| Wk 1 | Wk 2 | Wk 3 | Wk 4 | |
|---|---|---|---|---|
| M. Reyes | 80% | 80% | 100% | 100% |
| S. Whitfield | 60% | 90% | 90% | 90% |
| J. Okoro | 40% | 40% | 40% | 70% |
Modeled data is marked. Committed data is not touched.
A modeling project sits on top of live allocations, budget, and schedule without changing any of them. The hatched cells above are what the scenario proposes, the solid cells are what is already committed. Nothing in the real portfolio moves until the scenario is applied.
Modeled versus committed, at a glance
The same diagonal marking used everywhere in Completix for a proposed, not-yet-real change.
Built from live data
The starting point is the actual portfolio, not a stale export someone made three weeks ago.
A what-if scenario stays a scenario until someone applies it.
Modeling is meant to be explored freely. Nothing calculates its way into the real portfolio on its own, and applying a scenario does not skip the reviews your organization already relies on to fund and commit work.
Applying is explicit
You choose the moment a modeled change is written into the live portfolio. There is no automatic promotion.
Gates still apply
A funding or scope change still runs through whatever review your organization requires. A scenario informs that decision, it is not a substitute for it.
Discard freely
Most scenarios are meant to be tested and set aside. Discarding one leaves the real portfolio exactly as it was.
Weigh two options with the same assumptions behind both.
A single scenario tells you what one change does. Building a second modeling project against the same starting point tells you which of two paths is the better call, before either one is real.
Same starting point, two directions
Both scenarios draw from the same live portfolio, so the comparison is fair.
Only one gets applied
Review both, then apply the one you choose. The other can sit as a record of the option not taken.
Phased rollout
Fast-track rollout
Everything that a real commitment touches.
A scenario is not a single-variable calculator. It carries the same categories a live decision would.
Funding shifts
Move budget between initiatives and see the effect on the wider portfolio total.
Team moves
Reassign people across projects in the model and see who ends up over-allocated.
Timeline changes
Push a date and see which linked projects and milestones move with it.
Utilization impact
See how a change lands on individual capacity, not just a portfolio-wide average.
Multiple scenarios
Keep more than one modeling project open at a time to weigh different paths.
Apply when ready
Write a scenario into the live portfolio in one action, on your timing, not before.
See a scenario built and applied, live.
Book a demo and we will load a real change into a modeling project, and show you the impact before anything is committed.
Book a demo