Skip to main content

Snags

Walk the site and raise snags in seconds, assign them to a subcontractor or team member in bulk, and take each one through fix, independent verification and close.

Where
  1. Projects
  2. open a project
  3. Snags
Who
  • Company Admin
  • Project Manager
  • Site Engineer
  • QA/QC Engineer

The Snags tab is the punch list a handover runs on. A snag is a defect in finished or nearly finished work β€” a hollow tile, a door that will not close, a leaking tap β€” filed against a location so someone can go and find it.

πŸ“· Screenshot spot β€” the Raise snag form on a phone with a location selected and the category chips showing, above the punch list

Save as static/img/screenshots/site-snags.png and replace this box with ![Snag list](/img/screenshots/site-snags.png)

Raise snags on a walk​

  1. Open the project and go to the Snags tab.
  2. Click Raise snag.
  3. Pick the Location β€” flat, floor, room. It stays selected between snags, so you can walk a whole flat without picking it again.
  4. Pick the Category. Common titles for that category appear as one-tap buttons ("Hollow tile", "Paint patchy", "Leaking tap"). Tap one or type your own Title.
  5. Set the Priority: low, medium, high or critical.
  6. Optionally add the Trade ("Tiling", "Plumbing"), a Description, and the Photo URL (before).
  7. Tick Raised by the client if the client or their consultant pointed it out.
  8. Click Add snag. The form clears for the next one and counts N raised this walk.
  9. Click Done raising when you finish.

Categories: workmanship, material defect, damage, incomplete work, cleaning, snag from client, safety, services, finishing.

Photos are added as a web link (https://…), not as a file upload. A snag raised with a before photo must be resolved with an after photo.

Snag locations come from the project's location tree on the Site tab under Locations. If the flat you need is missing, ask your Project Manager to add it.

Assign snags​

Assign one at a time from the snag's panel, or many at once from the list.

In bulk:

  1. Tick the snags in the list. Only snags that are open, assigned or reopened can be ticked.
  2. In the bar that appears, choose who from Assign to… β€” a subcontractor (from your vendors) or a team member.
  3. Set a due date. The snag form has no due date, so this is where it is set.
  4. Click Assign all.

Bulk assignment is all or nothing. If any ticked snag is already under way or finished, nothing is assigned and the message names the ones in the way.

One snag: click Open on its row, choose the assignee and due date in the panel, and click Assign (or Reassign before work starts).

A person can only be given a snag if they are on the project team β€” otherwise the message says to add them to the team first. Blacklisted or inactive vendors are not offered.

How a snag moves​

OpenAssignedIn progressResolvedVerifiedClosed
ResolvedReopenedAssigned
OpenRejected
StepButtonWho
Open β†’ AssignedAssignSite Engineer, QA/QC Engineer, Project Manager
Assigned β†’ In progressStart workSite Engineer, Project Manager
In progress β†’ ResolvedResolveSite Engineer, Project Manager
Resolved β†’ VerifiedVerifyQA/QC Engineer, Project Manager β€” not the person who resolved it
Resolved β†’ ReopenedReject fix (needs a reason)QA/QC Engineer, Project Manager
Verified β†’ ClosedCloseQA/QC Engineer, Project Manager
Open or Assigned β†’ RejectedNot a snag (needs a reason)QA/QC Engineer, Project Manager

Company Admins can do every step. Store Keepers and Safety Officers can raise snags but not move them. A subcontractor does not sign in; the Site Engineer starts and resolves the snag for them.

Type a Note / reason in the panel before you press a button β€” it goes into the snag's Activity trail, and it is required for Reject fix and Not a snag.

Resolve and verify​

  1. When the work is fixed, open the snag. If it has a before photo, paste the After photo URL.
  2. Click Resolve.
  3. A different person checks the fix on site, then clicks Verify β€” or Reject fix with what is still wrong.
  4. Once verified, click Close.
The resolver cannot verify

The person who resolved a snag cannot verify it β€” the Verify button is greyed out for them and the panel says You resolved this snag, so someone else has to verify it. A fix is not a fix until someone else has looked at it.

A rejected fix goes to Reopened and must be assigned again. The third time a fix is rejected, the snag is marked escalated and counts in the Escalated tile ("reopened 3+ times") for the Project Manager to deal with.

Closed and rejected snags are history: they cannot be edited and take no more photos.

Photos and activity​

The snag's panel shows its Photos (before, after, reference) and its Activity β€” every status change with who, when and the note. Anyone who can raise or resolve snags can add a photo link with Add, choosing Before, After or Reference.

Filters and the numbers at the top​

Filter the list by All statuses, All priorities and All locations. Overdue due dates show in red.

The tiles show Open (with how many are awaiting verification), Overdue, Critical open, Closed as a percentage of valid snags, and β€” when there are any β€” Escalated and Client-raised open.

Clear critical snags before handover

The Critical open tile reads blocks retention release: treat any open critical snag as a reason not to hand over or ask for retention. The app does not itself stop a bill or a retention release, so the check is yours.

Cost impact (optional) appears on the form and the list only for roles that see costs, or team members marked Sees financials on the project team.