Software Project Risk Assessment Tool (Free Scorecard)

Before you sign off on a custom software build, pressure-test it. This software project risk assessment scores six factors that make or break delivery, requirements, budget, stakeholders, timeline, complexity and team experience, into a single risk percentage and tells you which weak spot to fix first.

§ · written guide

How to use the Software Project Risk Assessment Tool

This scorecard turns six judgment calls about a planned software build into one risk percentage. Each answer scores 1, 2 or 3 points for low, medium or high risk, and the total is rescaled to 0 to 100 percent with the single riskiest factor named as your top risk driver. Use it before you sign off on a custom build, with a vendor or your own team.

Step by step

Rate the requirements
Under How clear are the requirements?, pick Very clear if the scope is documented and signed off, Roughly known if gaps remain, or Still vague if the plan is to work it out later. Every question starts on the middle answer.
Rate budget and people
Under How certain is the budget?, choose Fixed & funded, Ballpark or Not set. Under Are stakeholders aligned?, choose One clear owner, Mostly aligned or Competing agendas.
Rate the timeline
Under How realistic is the timeline?, pick Comfortable if there is room to breathe, Tight if there is little slack, or Fixed & aggressive if the date cannot move.
Rate complexity and experience
Under How technically complex is it?, choose Standard for proven patterns, Some unknowns for a few integrations, or the third option for novel or heavy integration work. Under Team / vendor experience with this?, choose Done it before, Adjacent work or First time.
Read the score and fix the top driver
The result panel updates on every click. Check the risk percentage and its band, then read the Top risk driver card. That is the factor to fix before you start building.

Reading the result

Risk % is (sum of the six scores minus 6) divided by 12, times 100. With every question on the middle answer the sum is 12 of 18, so the risk is 50%.
Under 35% reads Low risk, 35% up to 60% reads Moderate risk, and 60% or more reads High risk. From the default 50%, moving two answers to the high risk option takes the score to 67%, which is High risk.
The line under the percentage shows the band and your raw score out of 18, and the formula line shows the sum it used.
The Top risk driver card names the highest scoring factor. When several are tied, the first one in the list wins, so with all six on the middle answer it shows Requirements clarity at Medium risk.
The bars show each of the six factors as Low risk, Medium risk or High risk.

Tips and common mistakes

Answer for the project as it stands today. If the budget is only a ballpark, choosing Fixed & funded hides the very risk the tool is there to show.
All six factors weigh the same, so moving any one answer a single step toward high risk, from low to medium or from medium to high, adds about 8 points to the percentage.
Re-run the scorecard after each fix, such as signing off requirements or naming one decision maker, to see whether the project drops into a lower band.
Fill it in with the other people involved. If you and a stakeholder pick different answers on the same question, that disagreement is itself a risk.

Privacy and limits

The score is calculated in your browser from the answers you click. Nothing is sent anywhere and nothing is saved, so reloading the page puts every question back on the middle answer. It is a structured gut check, not a measured prediction.

Back to the tool

How it works

A software project risk assessment turns a gut feeling into a number you can act on. This scorecard rates the six factors that most reliably predict whether a custom build ships on time and on budget: how clear the requirements are, how certain the budget is, whether stakeholders agree, how realistic the timeline is, how much technical complexity is involved, and how much relevant experience the team or vendor brings.

Each factor is scored as low, medium or high risk, 1, 2 or 3 points. Add the six scores (a range of 6 to 18) and normalise to a 0-100% scale. Below 35% is low risk, 35-60% is moderate, and 60% or above is high risk. The tool also flags your single highest-scoring factor as the top risk driver: the one thing to fix before anything else.

Risk % = (sum of 6 risk scores − 6) ÷ 12 × 100

Use it as a gate, not a verdict. A high score doesn't mean don't build, it means invest in de-risking first: a discovery phase to clarify scope, a budget contingency, a named decision-maker, or a proof-of-concept on the hardest part. Once you know the shape of the work, price it with the software development cost calculator, or if you're still weighing custom against off-the-shelf, run the build vs buy calculator.

FAQs

What is a software project risk assessment?

It's a structured way to gauge how likely a software project is to overrun on time, budget or scope before you commit to it. You rate each major risk factor, requirements, budget, stakeholders, timeline, complexity and team experience, and combine them into an overall risk score, so you can decide whether to proceed, renegotiate, or de-risk first.

How is the risk score calculated?

Each of the six factors is scored 1 (low), 2 (medium) or 3 (high) risk. The scores are summed (6 to 18) and rescaled to 0-100% with the formula (sum − 6) ÷ 12 × 100. Under 35% is low risk, 35-60% is moderate, and 60%+ is high. The highest-scoring factor is surfaced as your top risk driver.

What should I do if the project scores high risk?

A high score is a signal to de-risk, not to abandon. Attack the top driver first: lock and document the requirements, add a budget contingency, name a single decision-maker, or build a proof-of-concept on the most complex piece. Re-run the assessment after each fix, most projects drop into the moderate or low band once the weakest factor is addressed.