Snagging Software & Snag List Format in Excel: A 2026 Guide for Indian Construction Sites

Site engineers in India know the feeling. You finish a stage of work, the client or PMC walk-through starts, and the same issues keep surfacing: hollow tiles, seepage marks, uneven switch plates, missing silicone, loose handrails. Photos fly on WhatsApp, someone updates an Excel sheet at night, and by next morning nobody can say which flat was fixed, which was rechecked, and which is still open.

A snag list app is a simple digital system that captures each defect with a photo and a precise location, assigns it to the right trade, sets a due date, and closes it only after somebody verifies the fix on site. For Indian contractors and builders it is the cheapest way to tighten quality control without adding paperwork, and in 2026 it has become something more: the evidence trail you need when a defect resurfaces two years after possession.

This guide covers the whole snagging stack for Indian sites: what a snag list is, a free snag list format in Excel you can download and use today, and what dedicated snagging software adds once the register outgrows a spreadsheet.

What a snag list is, and how it differs from a punch list#

A snag list is a record of work that is incomplete, incorrect, damaged, or not as per drawings and specifications, captured during inspection so it can be corrected before handover.

Snag list and punch list describe the same document. Snag list is the term used in the UK, Ireland, the Gulf and most Indian sites that inherited British contract vocabulary. Punch list is the North American term, and it shows up on Indian projects with US-based clients, MNC fit-outs and data centre work. There is no standards body that separates them, so the safest approach is to define the word once in your project quality plan and use it consistently everywhere, including in your punch list management software and in your contract correspondence.

Where teams do draw a line, the convention is usually about who raised the item: the contractor's own internal sweep is the punch list, and the consultant's or client's findings are the snag list. That is an internal convention, not an industry definition, so write it into the project procedure rather than assuming everyone shares it.

On Indian projects, snagging runs in rounds:

• Rolling snagging after each stage: RCC, masonry, plaster, waterproofing, tiling, painting.
• Pre-handover snagging, flat by flat or floor by floor, before possession.
• Post-handover snagging during the defect liability period.

Snag versus NCR#

A snag can be minor (a paint touch-up) or major (a leak). A Non-Conformance Report is the formal route, used when the deviation is repeated, safety-critical, structural, or needs documented corrective and preventive action.

The practical rule most Indian SMB teams settle on:

• Snag list for everyday defects and finishing issues, closed by the trade within days.
• NCR for repeated or high-impact issues such as recurring seepage, repeated honeycombing, wrong slope, or missing firestopping. If your team is formalising this route, see how NCR management works alongside snagging.

The trigger between the two should be numeric, not a matter of judgement. A workable threshold: if the same defect type appears more than five times in one tower, or more than twice in the same flat, it stops being a snag and becomes an NCR with a root-cause note.

Why snagging matters more in 2026 than it did five years ago#

The rework number is smaller than the slogans, and still worth chasing#

Industry writing has long quoted rework at 5 to 10 per cent of project cost. That range comes largely from estimates and self-reported survey data. A 2026 study by Peter E. D. Love published in the Journal of Construction Engineering and Management measured actual rework spend on a contractor's projects instead of asking people to estimate it, and found pre-completion field rework averaged 0.38 per cent of contract value, rising to about 0.76 per cent once post-completion corrections were counted. The same study found rework costs were underreported by roughly 300 per cent, so the measured figure is a floor rather than a ceiling. You can read the ASCE write-up of that study for the full method.

The honest takeaway for an Indian contractor: rework probably is not eating 10 per cent of your turnover, but on a 3 to 6 per cent net margin, even 0.8 per cent of contract value is a meaningful slice of profit, and it is the slice you are least likely to be tracking.

RERA makes the snag record an asset, not just admin#

This is the part Indian builders underrate. Under Section 14(3) of the Real Estate (Regulation and Development) Act, 2016, if a structural defect or a defect in workmanship, quality or provision of services is brought to the promoter's notice within five years of handing over possession, the promoter must rectify it at no further cost within thirty days. Fail, and the allottee is entitled to compensation decided by the state authority. The Act does not define structural defect, which is exactly why disputes turn into arguments about whether an item is a construction failure or a maintenance issue.

A clean, timestamped snag record is what settles that argument. If you can show that Flat 902 Toilet 2 was ponded for 48 hours, passed, was photographed dry from the same angle, and was verified by a named engineer on a specific date, you are in a very different position from a promoter with a WhatsApp thread. Teams already running RERA-aligned project documentation usually find snag records are the easiest part of the file to strengthen.

Regulators are now asking for quality records directly#

Maharashtra has gone furthest. MahaRERA's Quality Assurance Certificate in Form 2A, originally introduced under MahaRERA Order No. 5 of 2018 and revised through the MahaRERA General (Amendment) Regulations, 2024, requires the site engineer and promoter to jointly certify structural stability, input material standards, workmanship quality and safety measures at the end of each financial year, and to publish it. Among the items it expects promoters to maintain are inspection registers, site order books and quality control test registers. If those registers exist only as paper and photos on someone's phone, the annual certification becomes a fire drill. Check MahaRERA's circulars and orders page for the current filing position, and your own state authority's equivalent, since requirements vary considerably outside Maharashtra as of mid-2026.

How a snag list app works on a live site#

The workflow replaces scattered photos and versioned Excel files with one loop:

1. Capture the snag with a photo or short video and a measurable description.
2. Tag the location precisely: Tower B, Floor 8, Flat 804, Toilet 2.
3. Assign it to a trade or vendor with a due date.
4. The trade fixes it and uploads closure evidence.
5. An engineer verifies on site, then closes it.

Step 5 is the one teams skip, and it is the one that makes the record worth anything. A snag closed by the person who caused it is not evidence.

Minimum fields every snag should carry#

Severity and SLA, decided once#

Set the clock by severity, not by who shouts loudest. A workable default for Indian residential work:

Worked example: seepage in a toilet#

• Snag: Toilet 2, damp patch at skirting near door jamb, approximately 300 mm wide.
• Category: Waterproofing. Severity: Critical.
• Location: Tower A, 9th Floor, Flat 902, Toilet 2.
• Assignee: waterproofing subcontractor plus plumber.
• Due: 48 hours.
• Closure rule: ponding test at the commonly specified 50 mm depth held for 48 hours with no leakage or damp patch on the floor or the soffit below, plus a dry photo from the same angle as the original.

That closure rule is the whole point. If your specification for waterproofing works already defines the test, the snag app should refuse to accept closure without the test evidence attached. Run this consistently across 60 to 200 flats and the "which flat?" and "who owns it?" conversations disappear.

Snag list format in Excel (free download)#

Plenty of sites are not ready for an app on day one, and that is fine — a disciplined Excel register beats an undisciplined app every time. The problem with most snag list templates in circulation is that they are either gated behind a lead form or written for UK house-buyers rather than an Indian tower handover. So we built one around the field list above and put it behind a plain link: download the snag list format in Excel — no form, no email. It is one of the free construction templates we maintain alongside the NCR and inspection formats.

The format is one row per snag, with twelve columns:

A second sheet carries the severity and SLA table from earlier in this guide, the snag-versus-NCR threshold and the retention rule, so the register and the procedure travel in the same file. The same workbook doubles as a handover snagging sheet: filter by flat, print to PDF, and attach it to the possession letter.

Three habits keep the Excel version alive on a real site. Keep one file per project with one named owner, because a folder full of files named Final v7 Tower B updated is exactly how photo evidence gets orphaned. Paste photo file names into the register rather than embedding photos, and keep the images in a folder-per-flat structure that mirrors the location column. And pull the weekly numbers — open count, aging, reopens — from filters on this one sheet, in the same 15-minute triage described later in this guide.

Photo evidence that actually holds up#

Most snag photos are useless three months later. Five rules fix that:

• Shoot the same frame twice. Mark a reference point (door frame, socket, corner) and take the after photo from the same position. Reviewers can compare in two seconds instead of arguing.
• Keep the timestamp and location metadata intact. Photos forwarded through WhatsApp lose EXIF data and get recompressed, which is precisely why the WhatsApp thread is weak evidence under Section 14(3).
• Include a scale or identifier in the frame. A tape, a marker pen line, or a small board with the flat number.
• Capture the test, not just the result. A ten-second video of a running tap, a ponded floor, or a door operating is worth more than a still.
• Retain for the full liability window. Section 14(3) runs five years from possession, so plan storage for at least six years from handover, per unit, retrievable by flat number.

Sites in basements, lift shafts and lower floors routinely have no mobile signal, so the capture tool has to write locally and sync later. Anything that needs a live connection at the moment of capture will simply not get used, which is why offline-capable site software is a hard requirement rather than a nice-to-have.

Snag examples by trade, with the evidence that closes them#

Wet areas and waterproofing#

Typical snags: water stagnation from improper slope to the drain, seepage at wall-floor junctions, door thresholds or pipe penetrations, poor sealing around the floor trap, broken screed at corners, missing upturn or kerb detailing.

Closure evidence: ponding test photo or video with start and end times, plus a dry-condition photo from the original angle after rectification.

Finishes: tiling, paint, doors and windows#

Typical snags: hollow tiles or lippage between tiles, chipped edges, poor grout cleanup, uneven skirting line, gaps at the tile and skirting junction, missing silicone in wet areas, roller marks, cracks at the wall-ceiling junction, door shutters rubbing, loose hardware, unsealed gaps between frame and wall, window shutters not locking smoothly.

Closure evidence: after-photo from the same viewpoint, plus a short operation-check video for every door and window. Hollow tiles need a tapping-survey note recording how many tiles were replaced, not just a photo of the finished floor.

MEP#

Typical snags: switch plates uneven or at the wrong height, loose modular fittings, missing DB labels, non-functional points such as two-way switches, exhaust fans and bells, earthing or polarity issues, leaks at angle valves and joints, low flow, choked traps, drainage slope causing backflow.

Closure evidence: photo of the corrected point and the updated DB labelling, plus a short video for leak and flow tests. Record the instrument reading, not just the plate.

Common areas and safety#

Typical snags: loose handrails, uneven stair nosing, broken tactile tiles, sharp edges, incomplete firestopping around shafts and penetrations, damaged lobby flooring, missing signage.

Closure evidence: after-photo plus a signed verification note from the engineer. Safety-critical items should never close on photo review alone.

When Excel breaks: what a snag management system adds#

The register above holds up to roughly 30 units of handover or a few hundred open snags. Past that point the failure is never the columns — it is the workflow around them. Photos live outside the sheet, two engineers keep two copies, trades report done on WhatsApp, and the verification column quietly starts filling itself.

Snagging software — a snag management system, if your tender prefers that phrasing — is the same register with the workflow enforced:

• Capture happens at the defect, offline, in seconds: photo, location picked from the project's own tower-floor-flat hierarchy, severity, trade. No evening data entry, and no EXIF data stripped by WhatsApp forwarding.
• The SLA clock starts itself. Severity sets the due date, reminders chase the assignee, and overdue items escalate without anyone having to play bad cop.
• The Ready for Review gate becomes mandatory. A trade can mark a fix done, but only a named engineer can close the snag — the register's most important rule stops being optional.
• Each subcontractor sees their own filtered list with photos, locations and due dates, which ends the nobody-told-me conversation.
• Handover packs assemble themselves: every snag for Flat 902 with before-and-after evidence and verification signatures, exported per flat for the possession file and the closeout documentation.
• The weekly numbers described later arrive as standing reports across projects, instead of being rebuilt from spreadsheet filters every Monday morning.

None of this requires an enterprise platform. For an Indian SMB builder the jump is from a shared spreadsheet to a mobile-first tool that a thekedar's supervisor can operate one-handed — and the evaluation list below is written for exactly that decision.

Choosing snagging software teams will actually use#

For Indian SMB teams, adoption beats feature count. Judge candidates on this list:

• Offline-first mobile capture with reliable sync, and photo capture in under ten seconds with simple markup.
• A location hierarchy that matches how your project is actually numbered, whether that is tower and flat or chainage and workfront.
• Assignment, due dates and reminders, plus a mandatory Ready for Review state so nobody self-closes.
• Reports that survive a Monday review: open snags by subcontractor, aging buckets of 0 to 2, 3 to 7 and 8 or more days, and repeat snags by defect type.
• PDF and Excel export for consultant updates and the handover pack.
• Reusable inspection checklists for stage-wise activities so snagging is not purely reactive.
• Language and literacy fit. If your thekedar's supervisor cannot operate it one-handed on a 4-inch screen, it will not be used.

Run a two-week pilot on one tower before rolling out. Give the app to two site engineers and one finishing subcontractor, log every snag on that tower only, and at the end count three things: how many snags were logged, how many closed within SLA, and how many the engineers logged on paper anyway. The third number tells you the truth.

What to measure weekly#

Keep it to five numbers and hold a 15-minute triage with zone engineers and key thekedars:

A rising reopen rate is the most useful early warning on any finishing site. It means trades are closing items to clear their list, not to fix the defect. Track your own baseline for a month before setting targets, because these numbers vary enormously by project type and there is no credible published Indian benchmark.

Best practices for faster closeout#

• Start rolling snagging early, and standardise location naming before the first snag is logged. A defect caught at plaster stage costs a fraction of the same defect caught after painting, and retrofitting a location hierarchy across 400 open snags is miserable.
• Treat repeat snags as method failures. If the same defect appears across a floor, fix the method, material or supervision, not the twenty symptoms.
• Fold the final snag list into the handover pack rather than treating it as a separate exercise, so the closure evidence sits alongside the project closeout and handover documentation the buyer and the authority will eventually ask for.

Where SiteSetu fits#

If you would rather not add a standalone tool, SiteSetu's quality module runs snagging as part of routine inspections: digital checklists for activities like RCC, plastering, waterproofing, flooring, MEP rough-in and handover, photo documentation attached to each checklist item, snag items assigned to contractors with deadlines, approval workflows with an audit trail, non-conformance tracking, and PDF inspection reports for the client or consultant. Because it sits in the same system as tasks, drawings and inventory, a snag against Flat 902 stays connected to the work item and the drawing revision it came from.

Final takeaway#

A snag list app is not about adding technology. It is about removing ambiguity on four questions: where is the defect, who owns it, when is it due, and what proof closes it. Answer those consistently, start rolling snagging early, and two things happen. Handovers get smoother, and five years later, when someone reports a damp patch, you have the record instead of the argument.

FAQs#

Is a snag list the same as a punch list?#

In practice, yes. Snag list is the British and Indian term, punch list is the North American one, and both describe a list of defective or incomplete work to be corrected before handover. Some organisations use punch list for the contractor's internal sweep and snag list for the consultant's findings, but that is a local convention rather than a standard, so define it once in your project quality plan.

How long should we keep snag photos and closure records?#

At minimum, through the full defect liability window. RERA Section 14(3) gives the allottee five years from possession to raise a structural, workmanship, quality or service defect, so plan retention for at least six years from handover, indexed by unit number so you can pull one flat's file quickly. Records that live only in WhatsApp threads lose their timestamps and are hard to produce when a dispute reaches the state authority.

How many snag rounds should we plan on a residential tower?#

At least one per major finishing stage, so after waterproofing, after tiling, after painting and after fixture installation, plus a final pre-handover walk per flat. Rolling snagging at each stage keeps the final list short, which matters because the final list is the one that delays possession. Teams that only snag at the end typically discover items that need the floor or ceiling opened again.

Is a snag list app only worth it for large builders?#

No, and SMB contractors often see the benefit faster. With a small team there is nobody spare to chase status, so making ownership and due dates visible removes more waste proportionally than it does in a large PMC-run setup. The practical test is unit count: once you are handing over more than about 30 units, an Excel sheet stops holding the photo evidence reliably.

What is the fastest way to make subcontractors accountable without constant conflict?#

Give them the same list you are working from, with photos, exact locations, realistic due dates and a stated SLA by severity. Review weekly rather than daily so the list does not feel like harassment, and escalate only items that are overdue or repeated, following whatever your contract actually says about rectification. Most disputes on Indian sites come from vague descriptions, not from unwillingness to fix.

Should snags be linked to retention or final payment?#

Commonly yes, and that is exactly why the record needs to be defensible. If retention release depends on snag closure, both sides will scrutinise the evidence, so a closure that consists only of a photo with no verification signature will be challenged. Agree the closure criteria per category at the start of the finishing phase rather than negotiating them item by item at the end.

What is the standard snag list format in Excel?#

There is no IS code or contractual standard for the format; what matters is that one row captures location, description, severity, ownership, dates, evidence and verification for each snag. A workable version has twelve columns — snag ID, date raised, location path, trade, description, severity, assignee, target date, status, closure evidence, verified by, and a reopened flag. You can download our free snag list format, which ships those columns plus a severity and SLA reference sheet.

What does snagging software do that an Excel snag list cannot?#

It enforces the workflow the spreadsheet only describes: photos are captured at the defect with timestamp and location intact, severity starts an SLA clock with automatic reminders, trades cannot close their own items because verification is a separate mandatory step, and per-flat handover packs export themselves. Excel remains a fair choice below roughly 30 handover units; past that, the register keeps working but the evidence around it falls apart.