What does this calculator work out?
For each framework on your shortlist, the checker compares the rows you ticked against the matrix and counts how many are met and how many are not. A framework passes only when it meets every ticked requirement.
Frameworks that fail come with a list of their unmet rows. That list shows whether a single missing item or several rule a framework out. The checker reads matrix data already on the site and adds no new vendor fact. The arithmetic below models one framework at a time.
What do you enter?
- Ticked requirements (count)
The number of matrix rows you ticked, where each row is one capability in the matrix. Default 6, range 0 to 40. - Yes rows (count)
How many of your ticked rows the framework has marked Yes in the matrix. Default 4, allowed values 0 to 40. - Partial rows (count)
How many of your ticked rows the framework has marked Partial. Default 1, between 0 and 40. Yes plus Partial should not exceed the ticked count. - Partial counts (0 or 1)
Enter 1 to treat Partial as meeting a requirement, or 0 to count only Yes. Default 0, either 0 or 1.
How is the result calculated?
Start with the Yes rows, since they always count as met. If Partial counts, add the Partial rows to that total. The total is capped at the number of ticked requirements, so a mistyped count cannot exceed what you asked for.
Unmet requirements are the ticked rows minus the met rows. The framework passes when nothing is unmet. If you tick no requirements at all, the result is a pass with zero unmet, because there is nothing to fail.
met = min(ticked, yes + partialCounts * partial)
unmet = ticked - met
pass = 1 if unmet = 0, otherwise 0Worked example
With the defaults, you ticked 6 requirements, the framework has 4 Yes rows and 1 Partial row, and Partial does not count. Requirements met is min(6, 4 + 0 × 1) = 4. Requirements unmet is 6 - 4 = 2. Because unmet is not zero, pass is 0. If you switched Partial to count, met would become 5, unmet would be 1, and pass would still be 0.
What does the result not tell you?
The arithmetic is illustrative and uses your own inputs. It treats every ticked row as equally important, so a missing deal-breaker and a missing nice-to-have both count as one unmet requirement.
A Partial mark covers a range of situations. Counting it as met can hide a gap that matters for your project, so read the matrix note behind any Partial before relying on it.
Quality of fit is outside what the checker measures. A Yes says the matrix records the capability, and it says nothing about how that capability behaves under your workload. Read the relevant head-to-head comparison before you commit.