Project Fit Scoring Framework
Last reviewed: April 2026
A disciplined fit score helps teams avoid emotional or opportunistic applications. The purpose is not to create fake precision. It is to make decision-making explicit and comparable across projects.
Scoring dimensions
Use a 1 to 5 score for each category:
| Stage | Description |
|---|---|
| Strategic fit | Does the project support a real company objective? |
| Readiness | Are the owner, data, timeline, vendor inputs, and decision-makers in place? |
| Feasibility | Is the implementation plan believable for this team, within this budget, in this time frame? |
| Return logic | Can the business explain what improvement it expects and why the spend is proportionate? |
Interpretation bands
- 16 to 20: proceed
- 12 to 15: improve before submission
- below 12: pause and redesign
You can also apply a mandatory override. If project timing has already compromised supportability, the score should not be used to justify submission.
Example
A company wants a regional ERP rollout.
Strategic fit: 5
Readiness: 2
Feasibility: 2
Return logic: 4
Total: 13
Decision: improve before submission. The business case is strong, but readiness and feasibility are weak.
Important note
Warning
A strong commercial idea can still be a poor grant application if the company is not ready to implement, measure, and evidence it.
Next step
Continue to PSG Playbook.