Completix

Portfolio prioritization that scores every project the same way.

Set your criteria up as fields on the intake form and the project record, each with its own weight. People enter the ratings, the total is calculated, and the score stays on the record for whoever has to make, or defend, the decision.

  • Live in weeks, not quarters
  • No system integrator required
Intake requestREQ-0248
ERP Modernization
Submitted byR. Fontana
Budget request$1.2M
StatusSubmitted
Prioritization scorecardExample, drag to adjust
80Priority score
Strategic fit35%8 / 10
Risk-adjusted value25%8 / 10
Cost efficiency20%9 / 10
Resource fit20%7 / 10
Weighted total28 + 20 + 18 + 14 = 80
Approval policy
Budget request over $500K
MLM. Laurent KSK. Singh
Parallel approval, all must approve
Why score at all

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. Each criterion carries its weight, so everyone scoring sees what it 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.

Change the weights and watch the priorities change.

Weights are a leadership decision, because they decide what wins. Try it, the same three requests can each come out on top.

Criterion weightsExample, drag to adjust
Balanced
Strategy first
Value first
Strategic fit35%
Risk-adjusted value25%
Cost efficiency20%
Resource fit20%
Three requests, same ratingsPoints from each criterion
ERP ModernizationREQ-0248
Highest score80
Customer Portal RefreshREQ-0261
Highest score70
Warehouse AutomationREQ-0274
Highest score65

The score informs the decision. People make it.

A high score doesn't approve anything. Who approves each request comes from your intake approval policy, which can name several approvers who all have to agree.

Every action is logged on the request with who took it. When a sponsor asks why their request lost out, you can open the record and show the score, the ratings behind it, and who decided.

A project earns its place. It doesn't keep it by default.

The same scorecard sits on the project record, so priorities can be tested again once the work is underway, and checked against the people who have to deliver it.

Rescore when the ground moves

When scope, risk, or cost shifts, score it again on the terms it was approved on. A lower score is a fair reason to take the budget back to the table in financial management. Whether to continue is still leadership's call.

Check capacity before you commit

A score tells you what is worth doing, not whether you can staff it. Load the work into a modeling project and see it on the resource heatmap, hatched as modeled. Nothing live moves until you apply the scenario.

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.

Scoring criteria are set up as custom fields on the intake form and on the project record, each with its own weight. People enter the ratings by hand and the total is calculated, so each request and each project carries its own score on its own record.

Yes. You define the criteria and the weight each one carries, so the scoring reflects your strategy rather than a vendor's template.

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.

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.

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 scoring on a real intake request.

We'll show how criteria and weights are set up, and how scores carry from intake through to the project record.