← Back to User Manual

Working with Snags

A snag is an individual defect or issue recorded against a specific location. Each snag can include a description, photos, notes, status and an assignee.

A good snag record is:

Creating a snag

  1. Open the relevant site
  2. Open the relevant unit
  3. Open the relevant location
  4. Add a new snag
  5. Enter the snag description
  6. Add photographs if required
  7. Add notes, assignee and status as needed
  8. Save the snag

Snags should normally be created in the exact location where the issue has been found. This keeps the inspection record accurate and makes reporting clearer.

Writing a good snag description

The description should explain the issue clearly and briefly. It should identify what is wrong and, where useful, where the issue is located.

Better example

Scratch to internal face of entrance door – redecorate complete panel.

Less useful example

Door damaged.

Keep the wording factual. Avoid vague wording where a more precise description is available.

Photos and supporting information

A snag can include one or more photographs. These help identify the issue clearly and improve the usefulness of the final report.

Where needed, you can also add notes to give further context or record supplementary information.

Status

Each snag has a status so that progress can be tracked clearly.

Keep the status up to date. This affects lists, filters, progress views and reports.

Assignees

A snag can be assigned to a person, trade or responsible party. This helps with filtering, follow-up and reporting.

Examples might include:

Editing an existing snag

You can return to an existing snag to update its details. This may include:

This is useful where work has progressed, additional evidence is needed, or the original wording needs refinement.

Bulk actions and list management

Snag lists may support bulk actions for faster management of multiple items. Depending on the screen and context, this may include changing status, assigning items, moving items or deleting items.

Use bulk actions carefully, particularly where several similar snag records exist in the same area.

Good practice