Skip to content

docs: explain percentage and points score types for checklists #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mrprkr merged 1 commit into from
Nov 2, 2026
Merged

docs: explain percentage and points score types for checklists #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 19 additions & 7 deletions content/docs/tutorials/effective-checklists/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,8 @@ create dialog or the flow editor's inspector:
how drift in prices, copy or plan names gets caught between runs.

A checklist's **Passing score** decides the verdict for its weighted checks. It
defaults to 100, which reproduces the old all or nothing rule, so a checklist
you already have behaves exactly as it did until you lower it.
defaults to every point (100%), which reproduces the old all or nothing rule,
so a checklist you already have behaves exactly as it did until you lower it.

The two hurdles are independent on purpose: no blocking check may fail, **and**
the weighted score must reach the threshold. Folding pass/fail checks into the
Expand All @@ -93,11 +93,23 @@ of 100" is five weighted checks: four with those weights and one with a weight
of -20. The maximum is the positive weights only, so the run really is out of 100. Partial credit ("15 if the messaging is only partly clear") is two checks
of 15 rather than one of 30, since a check has one verdict.

The passing score is a percentage, and the editor shows the points it works out
to at the current weights (75% of 100 is 75 points). Under **Grades**, name the
ranges a score can land in, best first: Optimal from 75%, Partial adoption from
37.5%, Pushed back below that. A run then reports its grade next to its score.
Grades only label the score; the passing score still decides whether it passed.
Choose the **Score type** that matches how the rubric is written:

- **Percentage** (the default) scores the share of the available points a run
earns, so "pass at 75%" keeps its meaning when you change the weights. The
editor shows the points it works out to at the current weights (75% of 100 is
75 points).
- **Points** scores the points a run earns, as they are, so "pass at 60" stays
60 however the weights move. Name what the points count, such as "marks" or
"stars", and runs report "62 marks" rather than a percentage. A penalty can
take a points score below zero.

The passing score and grades are in the score type you choose, and switching
type converts them at the current weights so the bar stays where it was. Under
**Grades**, name the ranges a score can land in, best first: Optimal from 75%,
Partial adoption from 37.5%, Pushed back below that. A run then reports its
grade next to its score. Grades only label the score; the passing score still
decides whether it passed.

## Order the checks, and let one depend on the last

Expand Down
Loading