> For the complete documentation index, see [llms.txt](https://changelog.visilean.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.visilean.com/quality/quality-changelog/release-9.0-2026/rule-based-checklists-every-matching-task-gets-its-checklist.md).

# Rule-Based Checklists: Every Matching Task Gets Its Checklist

On a large programme, the right checklist needs to be on every task it applies to. Keeping it that way takes constant attention, and as tasks are added and plans change, it's easy for one to slip through without its checklist. Rule-Based Checklists remove that manual effort. Define rules on a checklist, and it attaches itself automatically to every task that matches. Quality gate sync then ties those checklists to progress, so a task's quality gate opens only when every required response on it has been approved.

#### Why This Matters

A task without its checklist is an inspection that never happens, and on a programme with thousands of tasks, nobody can spot the gaps by eye. Even when the checklist is there, progress and quality can drift apart if a task can move forward while its approvals are still outstanding. Rules make checklist coverage automatic, and quality gate sync makes approved quality work a condition of progress rather than something checked after the fact.

#### What's New?

* **Rules on a checklist.** Define rules on a checklist, and it attaches itself automatically to every task that matches.
* **Coverage without manual upkeep.** Set the rules once and each matching task carries its checklist, without anyone having to attach it by hand.
* **Quality gate sync.** Checklists are tied to progress. A task's quality gate opens only when every required response on it has been approved.
* **A clear signal on every task.** The quality gate shows whether a task's approvals are complete.

#### How It Helps: Three Example Use Case Scenarios

A Quality Manager sets up a waterproofing inspection checklist with rules matching the relevant tasks. From then on, every matching task carries the checklist automatically, including tasks added to the programme later.

A Planner reviewing the look-ahead sees that a task's quality gate is still closed because one required response hasn't been approved, and follows up with the approver before the task is due to move on.

A Project Manager uses the quality gates across a floor to confirm that every required approval is in place before the next trade starts, instead of cross-checking task lists against checklist responses by hand.

{% hint style="info" %}

#### Key Considerations & Caution Points

**Rules decide coverage:** a checklist attaches only to the tasks that match its rules, so check the rules cover every task you intend.

**Gates wait for every required approval:** a task's quality gate opens only when every required response on it has been approved, not just submitted.
{% endhint %}