How to prioritize projects with a weighted scoring model

What a weighted scoring model is

Most organizations have more project ideas than money, people or management attention. A weighted scoring model is a simple, transparent way to compare those ideas on the same terms. Instead of the loudest sponsor winning, every proposal is rated against the same short list of criteria, and the criteria themselves carry weights that reflect what the organization cares about most.

Three terms matter:

• Criterion: a question every project can be rated on, such as "How closely does this support our strategy?"
• Weight: the share of the total score a criterion controls. Weights add up to 100%.
• Weighted score: the sum of (rating × weight) across all criteria. With ratings from 1 to 5, the weighted score also falls between 1 and 5.

The model sits inside project portfolio management: it feeds the decision about which projects to start, pause or stop.

How to build the model in six steps

1. Pick four to six criteria. Fewer criteria make each one count. Typical choices: strategic fit, financial value, risk, urgency (regulatory or contractual deadlines) and resource feasibility.
2. Write a scoring guide for each criterion. Define what a 1, 3 and 5 look like. For financial value, 5 might mean "payback within one year" and 1 "no measurable financial benefit". Without this guide, two reviewers will score the same project differently.
3. Agree the weights with leadership before scoring. Setting weights after you see the scores invites people to tune them until their favorite project wins.
4. Score each project as a panel. Have two or three people score independently, then discuss large gaps. Record the reason behind each score.
5. Calculate and rank. Multiply each rating by its weight, add the products, and sort from highest to lowest.
6. Fund within capacity. Walk down the list and approve projects until the budget or key people are fully committed. A high score does not help if the organization cannot staff the work.

Score risk so that a higher number is always better (5 = low risk). Mixing "higher is better" and "higher is worse" in one table is the most common arithmetic error in these models.

Worked example: four projects, five criteria

A PMO compares four proposals. Weights: strategic fit 30%, financial value 25%, risk 20% (5 = low risk), urgency 15%, resource feasibility 10%. Ratings are 1 to 5.

Project	Strategic fit (30%)	Financial value (25%)	Risk (20%)	Urgency (15%)	Resources (10%)	Weighted score
A: Customer portal	5	3	4	2	3	3.65
B: Warehouse automation	3	5	2	4	4	3.55
C: New regional office	4	4	3	3	2	3.45
D: Compliance reporting	2	2	5	5	5	3.35

Check project A: (5 × 0.30) + (3 × 0.25) + (4 × 0.20) + (2 × 0.15) + (3 × 0.10) = 1.50 + 0.75 + 0.80 + 0.30 + 0.30 = 3.65. Project B: 0.90 + 1.25 + 0.40 + 0.60 + 0.40 = 3.55. Project C: 1.20 + 1.00 + 0.60 + 0.45 + 0.20 = 3.45. Project D: 0.60 + 0.50 + 1.00 + 0.75 + 0.50 = 3.35.

Now apply capacity. The budget is $1,000,000. Costs: A $400,000, B $350,000, C $300,000, D $200,000. Funding A and B uses $750,000. Adding C would bring the total to $1,050,000, which is over budget, so C waits. D fits: $750,000 + $200,000 = $950,000. The approved portfolio is A, B and D, with $50,000 unallocated.

Notice two things. The scores are close (3.35 to 3.65), so a one-point change on one criterion could reorder the list. And D, ranked last, is funded because it fits. That is normal: the ranking orders the queue, and capacity decides where the line falls.

Common mistakes

• Too many criteria. With twelve criteria at 5 to 10% each, no single factor moves the result, and every project drifts toward the middle.
• Double counting. "Revenue growth" and "financial return" measure the same thing. Merge overlapping criteria or one idea gets twice the weight.
• Treating the score as precise. A gap of 0.1 on a 1 to 5 scale is within the noise of human judgment. Treat close scores as a tie and decide on other grounds, such as dependencies between projects.
• Ignoring mandatory work. Legal or safety obligations are not optional. Put them in the portfolio first, then score the discretionary projects for the remaining capacity.
• Scoring once and never again. Rescore active projects at each review. A project that scored well a year ago may now have a weaker case, and stopping it frees capacity.
• Hiding the scores. Publish the criteria, weights and scores. Transparency is the main reason to use a model at all.

A scoring guide template you can copy

Criterion	1 (weak)	3 (moderate)	5 (strong)
Strategic fit	No link to a stated objective	Supports one objective indirectly	Directly delivers a top objective
Financial value	No measurable benefit	Payback in three to five years	Payback within one year
Risk (5 = low)	New technology, new team, fixed date	Some unknowns with clear owners	Familiar work, proven team
Urgency	Can wait a year without loss	Value falls if delayed six months	Hard external deadline
Resource feasibility	Needs people already fully booked	Needs some hiring or borrowing	Team available now

Adjust the wording to your organization, but keep three anchored levels. Reviewers can still use 2 and 4 for cases in between.

How to do this in Critova

Critova does not calculate a prioritization score for you; the scoring itself is best done in a shared spreadsheet or workshop where the reasoning is visible. Where Critova helps is before and after the decision. Add custom fields to projects to record each criterion score and the weighted total, then group projects into portfolios and compare them on the portfolio dashboards, which show cost, schedule and risk across every project. Once a project is approved, the risk register and expected monetary value feed the next scoring round with real data instead of opinion; the risk score calculator is a quick way to rate exposure consistently.