Issue Tracking in Construction: A Builder's Guide
A practical guide for UK builders on recording, prioritising, and closing out site issues without the administrative burden of traditional spreadsheets.
By James Shorter ·
Issue Tracking in Construction: A Builder’s Guide

Issue tracking in construction means every problem on a job gets recorded once, given one owner and one deadline, and stays on a list until someone checks it is fixed. On most small and mid-size UK jobs, that record lives in a WhatsApp group, and that is where issues go missing. BRCKS is built for this: a site team keeps chatting as usual, and one tap turns a message into a snag, an order, a site visit or a checklist item on a single list per job.
This guide covers what counts as an issue, what to write down, how to assign and prioritise, and how to get subbies and clients reporting without forcing them onto new software.
TL;DR
- An issue is anything that stops or threatens the work: a defect, a clash, a missing decision, a late delivery, an access problem. Snags are one type.
- Record each issue once, with a number, location, photo, owner and date. Agree location names before you start.
- One owner per issue. Three priority levels are enough on most residential jobs.
- Issues stay in group chats because chat is quick. The fix is a list that fills from the chat, not a new habit for everyone.
- BRCKS files issues from site messages into one list per job. Subcontractors and clients use it free through WhatsApp. Teams is £40 per seat per month billed annually.
Table of Contents
- What issue tracking means on a UK site
- Why issues get lost in a group chat
- What to record when an issue is raised
- Assigning and prioritising issues
- Turning an issue into action
- Preventing issues, not only logging them
- Getting subbies and clients to report
- What to look for in a digital issue tracker
- How BRCKS handles issue tracking
- Our view on issue tracking
- FAQ
- Sources
What issue tracking means on a UK site
An issue is a problem that needs a decision or an action from someone. A tracker is the list that stops it being forgotten.
The terms overlap, so it helps to separate them:
- Snag or defect: work that is incomplete or not up to standard, usually found near handover. It is also called a punch list in some places.
- RFI (request for information): a question that needs an answer from the designer or engineer before work can go on. Guidance on commissioning logs draws this same line: punch list items are work to finish by a deadline, while RFIs need clarification before work can proceed.
- Variation: a change to the agreed scope or price. Some issues end here, when the fix is extra work. Some contracts call it a change order.
- Risk: something that has not happened yet. Once it happens, it becomes an issue.
The UK Government’s project delivery guidance treats an issue as something already affecting the project, and says the response should be noted in an issues register. That response can range from accepting the impact, to corrective action within tolerances, to a formal change request. That range is useful on any job. Not every issue needs a variation. Every issue needs a recorded decision.
Why issues get lost in a group chat
A WhatsApp group is fast. A sparky posts a photo of a clashing duct, the plumber replies with a thumbs-up, and by the next morning it is 80 messages down. Nobody has been told it is theirs. Nobody has said when it needs sorting.
Three things go wrong:
- No owner. Everyone saw it, so everyone assumes someone else has it.
- No status. You cannot tell open from closed without scrolling.
- No record. When a variation or a dispute comes up months later, the evidence is a photo buried in a thread.
The usual answer is a spreadsheet or a heavyweight system that the whole team has to adopt. Both fail for the same reason: they rely on someone writing it up at night. Our guide to reducing miscommunication on site goes into the habits behind this.
What to record when an issue is raised
Keep the record short enough that people fill it in on site, with a phone in one hand. A commissioning standard sets out a thorough log: project and location, issue number, description, pictures, date found, who found it, effects, possible cause, recommended resolution, who is assigned, actions taken and approvals. That suits a large commissioning team. For a house extension or a fit-out, the core is:
| Field | Why it matters |
|---|---|
| Issue number | One reference everyone can quote on the phone |
| Location | Room, floor or elevation, named the same way every time |
| Description | One or two plain sentences |
| Photo | Proof of the state on the day |
| Date raised and by whom | Starts the clock and shows who saw it |
| Owner | One named person or firm |
| Priority and due date | Decides what is dealt with first |
| Status and sign-off | Open, in progress, fixed, checked |
Add cost or programme impact when the issue might become a variation. Professional guidance from the American Society of Civil Engineers says that when a problem arises, stakeholders should be told what it is, when it was found and whether it could affect budget or schedule. The same article advises keeping an issue file with the supporting paperwork: daily reports, correspondence, RFIs, photographs and inspection reports. On a UK contract, that means your diary entries, instructions and drawings.
Agree location names first
This is the detail that saves the most grief later. The same commissioning guidance says location tags should be agreed before issues are tracked, because it is too late to reorganise once hundreds of issues exist. On a house, that means deciding whether it is “Bed 2” or “Back bedroom” and sticking to it. Put the names on the first drawing issue and on the job’s checklist.
Assigning and prioritising issues
One owner per issue
An issue with two owners has none. Name one firm or person for each item. If the cause is disputed, the main contractor or site manager should decide who takes it, so the item does not sit unowned while people argue by email. The Government’s guidance says the same in its own terms: the issue owner assigns actions to named action owners.
Three priority levels
On residential and small commercial work, three levels are enough. This is a practical scheme, not a standard:
- Critical: safety, structure, fire protection, water ingress or anything that stops the next trade. Same day or next day.
- Major: affects how something works or lasts, or would hold up handover. Fixed before the trade leaves site.
- Minor: appearance and finishing. Cleared at the snagging stage.
Priorities move. Commissioning guidance notes that a prioritisation mechanism in the log lets the most important issues be discussed first in time-limited meetings, and thatpriorities keep changing as issues appear and close. Review the list weekly and re-rank it.
Close with a check, not a message
“Done” in a chat is a claim. Closure is when someone other than the person who did the work looks at it and signs it off, ideally with a photo. Build that into the status: fixed, then checked. For the end-of-job version of this list, see our snagging list template.

Turning an issue into action
An issue is closed one of three ways, and your tracker should show which:
- Fix it within the existing scope. Rework by the responsible trade at their cost, or a minor adjustment.
- Ask a question. If the answer sits with the designer or engineer, raise an RFI and link it to the issue so the work is not left waiting without a reason on record.
- Change the scope. If the fix means extra work or a different spec, it becomes a variation. Record the instruction, the cost and the programme effect before the work starts. A change that is only agreed on site by word of mouth is the one that ends in a dispute.
The Government’s guidance asks that responses be proportionate to the impact, and that the effect on the plan and the documentation is considered, which may need a formal change request. In builder’s terms: do not let a small fix become an unrecorded change to the job.
Preventing issues, not only logging them
A tracker that only counts problems is half a tool. The construction quality body CQIC advises preparing a project quality plan before works start, with the focus on getting the work right first time, not just snagging afterwards. It also recommends regular quality meetings that look ahead at upcoming work and, for recorded snags, ask why the issue happened and what stops it recurring.
A simple way to do that from your list:
- Group the month’s issues by cause: drawings out of date, trades clashing, late materials, unclear instructions, workmanship.
- Look at the biggest group. If it is drawings, tighten version control (see our note on drawing version control). If it is trades clashing, put the sequence on the shared calendar.
- Raise it at the next site meeting, and keep it short. Our checklist for construction meetings helps.
Getting subbies and clients to report
Subcontractors report issues when it costs them nothing. Ask a plumber to log into another system and the issue goes back to a phone call. The HSE’s guidance on the construction phase plan says the principal contractor should explain how they will communicate with others on the job, for example through a daily update, including what happens when plans or materials change or there are delays. A communication routine is part of running a safe, organised site, not an extra.
What works in practice:
- Let subbies report in the channel they already use. For most UK trades, that is WhatsApp.
- Tell them what happens next: who owns it and by when.
- Reply on the same day, so reporting is seen to work.
- Keep the list visible to the client, so they raise issues in one place and not by phoning the site manager.
Our pieces on site communication workflow and task tracking for UK project managers set out the routine in more detail.
What to look for in a digital issue tracker
Whether you use a spreadsheet or software, test it against these points:
- Can you raise an issue from your phone in under 30 seconds, with a photo, on site?
- Does it work with how the team already talks? If it needs everyone to change habits, adoption will stall.
- One list per job, not one per trade or one per person.
- Named owner, priority, due date and status on every item.
- An audit trail, so you can show who said what and when if a variation is questioned.
- Free access for subcontractors and clients, so the cost does not rise with every person you invite.
- Links to the rest of the job: diary, drawings, variations and RFIs.
The commissioning guidance is blunt on discipline: if people do not follow the agreed way of entering issues, others cannot report reliably on status or reach completion. The easier the entry, the better the discipline. Our comparison of UK construction reporting tools sets out the options by type.
How BRCKS handles issue tracking
BRCKS is the chat app for building sites. Your core team uses it on iPhone or Android and works the way they do in WhatsApp. When someone posts an issue, one tap turns the message into a snag, a materials order, a booked site visit or a checklist item. It lands on a single list for that job, with the photo attached. Nobody writes it up at night, and we aim to save site teams 30+ minutes a day on admin.
Subcontractors and clients join through BRCKS on WhatsApp. They install nothing and pay nothing. The same job, the same record, whichever way the update comes in. The office sees it on BRCKS Web on a bigger screen.
For the follow-through, the job also holds snagging and checklists, a shared team calendar, site diaries, variations and RFIs with audit trails, and versioned project files for drawings, RAMS and quotes.
Solo is £20 per month. Teams is £40 per seat per month billed annually, or £50 billed monthly. Every plan starts with a 14-day free trial. See BRCKS pricing for the full detail, or look at our construction communication software for how the chat side works.

If you would like to see an issue go from a site message to a closed item, book a BRCKS demo. If you are weighing it against your current group chat, the WhatsApp vs BRCKS comparison lays it out.
Our view on issue tracking
We started BRCKS because a builder with 20 years on site was tired of finding out about problems three days late.
The issue is rarely that nobody noticed. Somebody always noticed. They posted it in the group, and it scrolled away. So we do not ask the team to adopt a new routine. We take the one they already have, the site chat, and make a tap on a message do the filing: a snag, an order, a site visit, a checklist item, all on one list per job.
Subbies and clients stay in WhatsApp, free, and install nothing. That matters more than any feature. A tracker only works if the plumber and the client use it, and they will only use something that costs them no effort.
Our advice: pick one place for every issue on every job, give each one an owner, and close it with a photo. Whatever you use, do that. If you want the list to build itself from the chat, that is what we made.
James
FAQ
What is the difference between issue tracking and snagging?
Snagging is a form of issue tracking focused on defects and incomplete work, usually found near handover. Issue tracking covers everything that affects the job along the way, including clashes, missing information, late deliveries and access problems. A good list holds both, so snags are not a separate system.
Do I need software, or is a spreadsheet enough?
A spreadsheet works for one small job and one person updating it. It struggles once several trades report from site, because entries depend on someone typing them up. Software that files issues straight from the site chat keeps the list current without extra admin, and BRCKS has a 14-day free trial to try this on a live job.
How many priority levels should I use?
Three is enough on most residential and small commercial jobs: critical, major and minor. More levels slow people down at the point of raising an issue. Review priorities weekly, as they change when new issues appear and others close.
Who should own an issue when responsibility is disputed?
The main contractor or site manager should assign it and settle the argument afterwards. Leaving it unowned while trades debate it by message is how items sit open for weeks. Record the decision and the reason on the item.
How do I get subcontractors to report issues?
Let them use WhatsApp, which they already have, and make sure every report gets a named owner and a reply the same day. With BRCKS on WhatsApp, subcontractors and clients join free and install nothing. The report lands on the job’s list, with their photo.
Sources
- ASHRAE SSPC 300 Informative Annex 11: Issues and Resolution Log
- Government Project Delivery, Teal Book Chapter 21: Issue management
- ASCE Civil Engineering Source: What to do when things go wrong on a construction project
- CQIC: Construction Quality Guidance for Contractors
- HSE: CDM 2015 Construction Phase Plan (CIS 80)
Recommended
- Construction Task Tracking: A UK Project Manager’s Guide
- Construction Progress Tracking: A Guide for UK Builders
- Design Change Tracking in Construction: UK Guide
- Drawing Version Control for UK Builders
How BRCKS Can Help
Effective issue tracking is the cornerstone of a project delivered on time and within budget, ensuring that minor snags do not escalate into costly delays. By centralising communication and providing real-time visibility, BRCKS simplifies this process, allowing your team to resolve site discrepancies with total precision. Embracing a digital approach ensures that nothing falls through the cracks, giving you the confidence to focus on quality craftsmanship. We invite you to discover how BRCKS can transform your site management by exploring our platform today. Learn more at BRCKS and explore our full feature set.
