> 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-4.0-2026/snags-track-every-issue-from-checklist-to-resolution.md).

# Snags: Track Every Issue from Checklist to Resolution

An inspection that finds a problem has only done half its job. The other half is making sure the problem gets fixed, and until now a failed answer on a checklist was where the trail stopped. Release 4 adds snags to the Quality Module: raise one against any answer on a checklist, give it a severity, and track it until it's resolved, with the conversation about the defect kept on the defect itself.

#### Why This Matters

Issues found during inspections tend to scatter. The finding sits in the checklist, the follow-up happens over email or a phone call, and the evidence that it was fixed ends up somewhere else entirely. Without one place to see every open issue, it's hard to tell what's still outstanding, how serious it is, or who's dealing with it. Snags tie each issue to the answer that raised it and keep it visible until it's closed.

#### What's New?

* **Snags raised against any answer.** Raise a snag on any answer in a checklist, give it a severity, and track it until it's resolved.
* **A conversation on every snag.** Each snag has its own conversation. Reply on it and tag colleagues, who are notified, so the discussion about a defect stays with the defect.
* **A dedicated Snags screen.** Every snag is listed in one place, with filters and counts.

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

A Site Engineer inspecting blockwork notices a cracked lintel. They raise a snag against that answer on the checklist, set a high severity, and the issue is on record before they move to the next question.

The Quality Manager tags the trade supervisor in the snag's conversation. The supervisor is notified, replies on the snag to confirm when the repair will be made, and the whole exchange stays attached to the defect rather than scattered across emails.

A Project Manager opens the Snags screen ahead of a progress meeting, filters to the most severe open snags, and uses the counts to see how many issues remain open across the project.

{% hint style="info" %}

#### Key Considerations & Caution Points

**Raised from a checklist answer:** a snag is raised against a specific answer on a checklist, so each issue stays linked to the inspection that found it.

**Tagging notifies:** tagging a colleague in a snag's conversation sends them a notification.

**One list for everything:** use the Snags screen's filters and counts to see what's still open across the project.
{% endhint %}