Portfolio prioritization that scores every project the same way.
Set your prioritization criteria up as fields on the intake form and the project record. Every request and every project gets scored on the same terms, and the scores stay on the record for whoever has to make, or defend, the decision.
- Live in weeks, not quarters
- No system integrator required
Capital follows strategy, not whoever pushes hardest.
Every request competes for the same budget and the same people. Prioritization is the part of project portfolio management that decides what that competition rewards, and a shared scoring standard is what keeps it from rewarding volume.
The same fields on every request
Your criteria live as custom fields on the intake form and the project record, so a request from Finance is scored on exactly the same terms as one from IT.
Weights your leadership agreed
Derive the criteria and their weights from the objectives in your portfolio strategy. Put the weight in the field label and everyone scoring sees what each criterion is worth.
A decision someone can explain
Scores sit on the record next to the approval trail, so when leadership funds, defers, or declines, the basis for that call is still there months later.
A sponsor asks why their request lost out.
The Customer Portal Refresh was rejected and ERP Modernization went ahead. Without a shared standard, the honest answer is that someone argued better in the meeting.
With scoring fields on every request, you open both records and compare them on the same criteria, entered at the same point. Approvers come from your intake approval policy and every action is logged with who took it, so the score informs the decision and the trail shows who made it.
Scope grew. Is it still worth funding?
A project earns its place, it doesn't keep it by default. The same scoring fields sit on the project record, so when scope, risk, or cost moves, the PMO scores it again on the terms it was approved on. ERP Modernization went from 80 at intake to 61 after its scope expanded.
Rescore on the same terms
The criteria and weights don't change between intake and delivery, so the two scores are directly comparable.
Sunk cost stops being the argument
A lower score is a legitimate reason to take the budget back to the table in financial management. Whether to continue, rescope, or stop is still leadership's call.
The top of the list doesn't fit this year's capacity.
A score tells you what is worth doing. It doesn't tell you whether you can staff it. Before committing, load the work into a modeling project and see what it does to your people, in real time, on the same heatmap your resource management team already uses.
Modeled demand is hatched, so nobody mistakes it for committed work. When leadership decides, apply the scenario. Until then, nothing in live data moves. More on how this works in scenario planning.
Portfolio prioritization, common questions
What is portfolio prioritization?
Portfolio prioritization is the practice of scoring proposed and active work against agreed criteria, so limited budget and people go to the work that matters most. It is one of the core disciplines of project portfolio management.
How are requests and projects scored in Completix?
Scoring criteria are set up as custom fields on the intake form and on the project record. Scores are entered by hand, so each request and each project carries its own scores on its own record.
Can we use our own criteria and weights?
Yes. You define the fields, so the criteria reflect your strategy rather than a vendor's template. Putting the agreed weight in each field label keeps it in front of everyone who scores.
Does a high score approve or fund a project?
No. Scores inform decisions, they don't make them. Intake approvals follow your approval policy, every approval action is logged with who took it, and funding decisions stay with the people accountable for them.
How often should we rescore projects?
Whenever scope, risk, cost, or strategy shifts enough to change where a project stands, and at a regular portfolio review. Update the scoring fields on the project record using the same criteria it was approved on.
How does prioritization connect to scenario planning?
Once you know what is worth doing, load it into a modeling project to see what it does to capacity. Modeled demand shows in real time and nothing changes in live data until you apply the scenario.
See your own criteria on a real intake request.
We'll set up scoring fields that match how your leadership already makes the call, and show how they carry from intake through to the project record.