The rules
1
Scored per optionEach answer option carries its own points, set individually. Yes is not automatically three and No is not automatically zero.
2
Sections weight equallyThere is no per section weighting, so section design decides emphasis. A ten field section carries the same weight as a three field one.
3
No knockoutA single critical failure cannot force the whole submission to zero. Where that matters, the template asks the critical question explicitly and the answer is read on its own.
4
N/A leaves the denominatorMarking something not applicable removes it from the calculation rather than scoring it zero.
5
Scores freeze at submissionA score is stamped with the template version that produced it. Changing the scoring later does not rewrite history.
6
Normalised to 0 to 100So a twenty question inspection and a sixty question audit can be compared.
Direction is declared per template
Every template states whether high is good or high is bad, because both exist. A pass rate is high is good. A defect count is high is bad. Without the declaration a dashboard reads them the same way.
What gets scored
- Check items use a pass scale: Pass 2, Partial 1, Fail 0, and N/A excluded.
- Around 75 percent of fields are mandatory. The rest are context that helps but should not block a submission.
- Follow up fields are always optional, because they only appear in some circumstances.
- Info blocks are always optional, because they are content rather than a question.
Where a template scores something as zero it is usually deliberate. A control level of retraining only, a sample method of convenience, or a verification method of assumed all score zero because the library takes a position on what good looks like.