Checklists 2.0: sections, scoring, and asset references

Every checklist in fam. now runs on a new engine. Sections replace the flat list, questions branch on earlier answers, scores add up to a verdict, and a step can point at the exact asset it describes. It is rolling out to every workspace this week, and your existing checklists carry over automatically.

Here is the technology it retires:

Sections that branch

A checklist is now a set of sections, and a section can wait its turn: it appears only when the answers before it say it should. Mark a measurement out of its acceptable range and the corrective section unfolds. Answer "not in use" and three sections you did not need never load. Sections can also repeat per unit, so one template covers a corridor of identical rooms without copy-paste.

Under the hood are twenty-one answer types: the field vocabulary of yes/no and pass/flag/fail, measurements with acceptable ranges and units, ratings, scales, Likert rows, currency, dates and times, photos, file attachments, and a signature, which is now a step like any other instead of a checkbox bolted to the end.

A verdict, not a pile of answers

Turn on scoring and every question carries a weight, every option a score, and the checklist a pass threshold. A completed checklist stops being a stack of answers and becomes a result: points earned against points possible, passed or failed, with a gauge on top and every flagged or failed step one filter away.

And because a completed checklist stays pinned to the exact version it was filled against, the score you audit in December is the score that was true in July. Templates evolve; records do not.

Steps that know their asset

An Asset step lets the person filling pick the exact unit from your register, filtered to the right category if you want. The answer keeps the link alive: tap it later and the asset's full card opens, current location and all. "Fridge 2" stops being a guess and becomes a record.

Rolling out now

Checklists 2.0 reaches every workspace this week. Existing checklists migrate automatically, attach to tickets exactly as before, and completed ones keep rendering exactly as they were filled. Build one, hang it on a recurring ticket, and let Friday check itself.