# Keep a snag list on a project

Source: https://help.mucka.ai/schedule/snag-list-on-a-project
Category: Schedule
Last updated: 2026-09-08

> Put snags down against the plot they're on as you walk round, tick them off in one tap, and see at a glance what's left and where.

When you're finishing a site for a housebuilder, the last few weeks are all snags. Someone walks round with a clipboard, writes down what needs putting right on each plot, and then the list lives in a photo of that clipboard until somebody types it up.

Every project in Mucka has a snag list, and it's kept by plot.

## Put one down

Open the project and scroll to **Snags**, then **Add a snag**. Two boxes:

- **Plot** — whatever you call it. `12`, `4a`, `the show home`. Leave it empty if the snag is about the site rather than a plot — a compound gate that won't lock, a skip that hasn't been collected.
- **What needs putting right** — in your own words. "Radiator leaking", "boxing in not finished", "no isolation valve under the sink".

Press Enter and it saves, ready for the next one. **The plot stays filled in**, because snags come in clumps — you walk plot 12 and find four things, and you shouldn't have to type "12" four times.

You can do it by asking too, which is easier stood in a hallway:

> put a snag on plot 12 at Ludlow, radiator leaking

## What you see

Snags group under the plot they're on, and the plot with the most left comes first. That's deliberate — the list is a work queue, and the plot you want next is the one with the most on it.

Under the Snags heading you get the one-line answer: **"8 left on 3 plots"**, or **"All clear — 22 sorted"** when the site's done.

Ask Mucka any time:

> what snags are left on Ludlow

## Tick one off

Press **Done** on the row. One tap, no confirmation.

It stays on the list, struck through, rather than disappearing. That's on purpose: if rows vanish as you work down the list you lose your place, and you're checking it against a clipboard that hasn't reordered itself. If you tick the wrong one, **Undo** puts it straight back.

## Things worth knowing

**Plot is just text, not an address.** Sites at snag stage usually don't have addresses yet — that's normal, and it's why Mucka doesn't ask for one. Write what the builder writes.

**"4", "Plot 4" and "plot 4" are the same plot.** Mucka groups them together so you don't end up with three headings for one plot and three different answers to "how many are left on 4". It shows them under whichever spelling you used first.

**Open or done, and nothing else.** No severity, no priority, nobody assigned. If a snag isn't being done, that's a conversation with the site manager rather than a status on a list.

**Anyone who can edit the project can add and tick off snags.** There's no separate permission — a snag is a fact about the job, and the person who found it should be able to write it down.