Snagging
Snagging keeps defects and handover items on the same job record as your site diary and timeline. Each snag has a status, assignee, priority, optional due date, location, and attachments.
Where to find snagging
| Entry point | Use when |
|---|---|
| Job → Construction → Snagging | Full register for one plot or job—filter, sort, group, and bulk actions |
| My Work → Snags | Personal queue: assigned to you or awaiting your review (tab appears when you have open snags) |
| My Work → Quick actions → Add snag | Capture a snag on site without opening the job first |
On a development, snags belong to plot jobs. When you add a snag from My Work with a development selected, pick the plot first.
Construction tab
The Construction tab on a job can include:
- Site diary — daily site logs (see Site diary)
- Snagging — the snag register for this job
- RFIs — requests for information (see RFIs)
Open Snagging to see all snags on the job. Use Add snag to create one with title, location, description, priority, due date, assignee, and optional photos or files.
External subcontractors (email + portal)
If a subcontractor does not use Sitehut, you can still assign work:
- Open a snag (or select several in the list) and choose Send to subcontractor or Email selected to… (requires snags:manage).
- Enter one or more email addresses and an optional message.
- They receive an email listing full details for each snag (reference number e.g. SNAG-001, title, location, priority, status, due date, and description). RFIs on the same share are listed with their reference number, subject, discipline, and description.
- If Include online portal link is enabled in Workspace settings → Subcontractors → Snag & RFI emails, the email also includes a button to open the public work portal where they can update status, upload photos, and leave comments—no login required.
- If the portal link is turned off, the email still contains all item details (so the trade is formally informed) but no online link is included.
- Links expire after 30 days; you can Revoke an active share from the snag detail sheet.
Comments and status updates from the portal appear on the snag's Activity & Comments tab.
Bulk email sends one email listing all selected snags for each recipient.
Status workflow
| Status | Typical meaning |
|---|---|
| Open | Logged, not yet started |
| In progress | Someone is working on it |
| Ready for inspection | Fix done; awaiting sign-off |
| Rejected | Failed inspection; needs rework |
| Closed | Accepted and complete |
Allowed next statuses depend on the current state—for example, In progress can move to Ready for inspection, Rejected, or Closed. Reopen a Closed snag if work needs to continue.
Location field
When creating or editing a snag, Location uses your workspace Library locations (Settings → Workspace settings → Library → Locations). Pick an existing room or area label, or add one inline. Keeping locations consistent helps reports and filters across jobs and snags.
My Work snags tab
When you have open snags, My Work shows a Snags tab with two sections:
- Assigned to me — snags where you are the assignee
- Awaiting my review — snags in Ready for inspection that need your sign-off
Update status inline from the list. If the tab is hidden, you have no open snags in either queue.
Permissions
Workspace and job roles control snagging through permission keys:
| Permission | Allows |
|---|---|
| snags:read | View the snag register |
| snags:write | Create and edit snags |
| snags:manage | Assign others and manage the register |
| snags:close | Close or reopen snags |
Built-in Editor roles typically include read and write; Admin and Owner include manage and close. Custom roles can mix these bundles—see Roles & Permissions.
Plot jobs and developments
Snags are stored on the plot or standalone job where the defect applies—not on the development (scheme) container. Scheme-level settings live on the development; day-to-day snagging happens on each plot.