Key takeaways
- Construction complaints lost in WhatsApp threads create retention disputes — the audit trail from a structured system is what protects the contractor when the dispute arrives
- Categories for construction feedback: Defect or Snag, Safety Observation, Design Discrepancy, Materials Quality, Workmanship Issue, Delay or Schedule
- Multi-trade routing: category-based auto-assignment sends each defect to the responsible subcontractor without the main contractor as manual switchboard
- Resolution rate by trade makes underperforming subcontractors visible before the final inspection, not at the retention review
- The defect liability period is where FeedSolve's timestamped audit trail delivers its highest value — exportable resolution history supports retention release and protects against DLP disputes
A construction client feedback system is a platform that gives project clients, site supervisors, and subcontractors a structured channel to submit snag lists, defect reports, safety observations, and complaints — via a QR code on site or a shared link. The main contractor manages submissions through a Kanban dashboard, assigns them to the relevant subcontractor or site supervisor, tracks resolution time, and closes each item with a documented outcome. For contractors managing active projects, this creates the audit trail that protects against disputes, delays, and retention withholds.
Construction Complaints Are Destroying Margins and Project Relationships
The WhatsApp defect report: a client site manager sends a WhatsApp message about a misaligned door frame. The message goes to the project manager's personal phone. It gets buried under 200 other messages. The door frame is still misaligned at the final inspection. The client withholds 3% retention as a penalty.
The no-audit-trail problem: in construction disputes, the question is almost always 'Was this complaint reported and when?' WhatsApp messages are not timestamped records in any legally useful way. An internal feedback board with timestamps and documented resolution history is.
The defect liability window: most construction contracts include a defect liability period of 6–12 months after handover. During this period, the contractor must respond to and resolve defect reports. Without a structured intake system, defect reports arrive informally, get missed, and become penalty clauses.
The subcontractor coordination gap: on multi-subcontractor projects, defect reports need to be routed to the right trade — M&E, civil, finishes, plumbing. Without a routing system, the main contractor becomes a manual switchboard for complaint forwarding.
A residential development project is three weeks from handover. The client's project manager has been sending WhatsApp messages about snag list items for two weeks. Some are resolved. Some are acknowledged but not resolved. Three are never seen because they landed in a message thread that was last checked six days ago. At the final inspection, the client's QS counts 23 outstanding defects and issues a retention notice for 5% of the contract value — £87,000 on a £1.74M contract. The main contractor disputes 11 of the 23. The dispute takes four months to resolve. The legal costs are £12,000.
The underlying cause of this dispute is not incompetence. The defects existed. Most were reported. Several were resolved. The problem is that none of this is documented in a way that creates a clear record of what was reported, when it was received, who was assigned to fix it, and when it was resolved. A structured site complaint system creates this record automatically. Every submission is timestamped. Every assignment is logged. Every resolution is documented with a public reply. The retention dispute becomes a 15-minute review of the resolution dashboard, not a four-month legal process.
What a Construction Site Complaint System Should Do
QR code placement on site: site office entrance, contractor notice board, material laydown area, individual floor or zone posters for multi-level projects.
Categories for a construction feedback form: Defect or Snag, Safety Observation, Design Discrepancy, Materials Quality, Workmanship Issue, Delay or Schedule, Documentation Error, Client Request.
Routing by trade: a plumbing defect routes to the plumbing subcontractor; an electrical issue routes to the M&E contractor; a finishes snag routes to the fit-out team. The main contractor sets routing rules once.
Tracking code for clients: the client's project manager submits a defect and receives #FSV-4981. They can check status at 4 PM without calling — 'In Progress: assigned to M&E team, target resolution Friday.' This replaces 15 WhatsApp follow-up messages.
Audit trail: every submission is timestamped with a full history of status changes, assignees, internal notes, and public replies. Exportable for retention disputes, defect liability reviews, and project post-mortems.
The construction complaint system must solve one problem above all others: making defects and complaints traceable from submission to resolution. Every item submitted must have a timestamp, a responsible party, a status, and a documented outcome. This is not bureaucracy — it is the evidence base that protects the contractor in every retention dispute, every defect liability claim, and every client relationship review.
The QR code model works in construction because project sites are physical environments where a printed poster or laminated card is more accessible than a web link sent by email. Placing a QR code on the site office door with the message 'Report defects and safety issues here — scan, submit, we respond within 24 hours' normalises the submission process. Subcontractors who find a defect at 6 AM scan the code, submit the issue, and get back to work. The main contractor's project manager sees the submission at 7:30 AM when they open the dashboard.
Managing Multi-Trade Projects — One Dashboard for All Complaints
Each trade or subcontractor can be a separate board, or a single board can use category-based routing to assign submissions to the correct trade.
Main contractor view: all defects across all trades in one Kanban board, filterable by trade, status, category, or submission date.
Resolution rate by trade: if the plumbing subcontractor has a 92% resolution rate and the electrical subcontractor has a 45% rate, the discrepancy is visible immediately — not at the final inspection.
Defect age report: submissions that have been in 'In Progress' for more than 7 days appear in a separate view. These are the items most likely to become retention disputes if unresolved at handover.
Weekly project meeting agenda: pull the dashboard summary — submissions this week, resolved this week, outstanding defects by trade, average resolution time. Replace 30 minutes of verbal status updates with a 5-minute dashboard review.
On a multi-trade residential project with 6 subcontractors, defect management without a structured system is a full-time job for the main contractor's site manager. They receive WhatsApp messages from 4 sources simultaneously, need to forward each one to the relevant trade, follow up when they do not hear back, and confirm resolution with the client. This coordination overhead alone costs 2–3 hours per day on an active project.
A single dashboard replaces this entirely. The client submits defects via QR code. They route automatically to the relevant trade based on category. The trade updates the status when the defect is rectified. The client sees the resolution on their tracking code. The main contractor's site manager sees the resolution rate across all trades in one view and spends 20 minutes per day managing the exceptions — items that are overdue or escalated — instead of manually coordinating every submission.
Building the Defect Liability Period Audit Trail
After practical completion, the defect liability period begins. Clients submit snag and defect reports throughout the period — typically 6–12 months.
A structured intake system during the DLP ensures every submission is timestamped and documented. If the client later claims a defect was reported and ignored, the contractor has a complete record proving it was received, assigned, and resolved — or documenting that it was never submitted.
Exportable resolution history: at the end of the DLP, export a full record of all submissions, their categories, assignment history, resolution dates, and public replies. This is the DLP completion document that supports full retention release.
Benchmarking performance: a contractor who can present a client with '97% of defect reports resolved within 14 days during the DLP' has a commercially differentiating claim — and the data to back it.
The defect liability period is where construction relationships are cemented or broken. A contractor who responds to DLP defects quickly, documents every resolution formally, and communicates status updates to the client without being chased builds a reputation that generates repeat business and referrals. A contractor who lets DLP submissions pile up in an email inbox, misses deadlines, and cannot produce a clear record of what was resolved is the contractor who loses the retention review.
The FeedSolve DLP setup is simple: create a 'Defect Liability — [Project Name]' board, share the link with the client's project manager, and include the QR code in the handover pack. Every DLP submission is logged automatically. Every resolution is documented. At the end of the period, export the full history, review any outstanding items, resolve them, and request retention release with a complete submission-to-resolution record attached.
FAQs
Do clients and subcontractors need to create accounts to submit defect reports?
No. They access the feedback board via a QR code on site or a shared link. No login, no account, no app download required. They submit in under 60 seconds and receive a unique tracking code. They can check the status of their submission at any time from any browser without logging in.
Can the system handle snag list items from multiple clients across multiple active projects simultaneously?
Yes. Create one board per project — 'Snag List: Riverside Phase 2,' 'Defects: Commercial Unit 5,' 'DLP: Marina Apartments.' Each board has its own QR code and can have project-specific category options. All boards are visible in one dashboard, filterable by project. The project manager can see resolution rates across all active projects in a single view.
Is this system suitable for the defect liability period, not just active construction?
Yes — and the defect liability period is where structured complaint management delivers its highest value. During DLP, every submission is automatically timestamped and stored. The contractor has a verifiable record of every defect reported, assigned, and resolved. This record directly supports retention release requests and protects against disputes about what was or was not reported during the liability window.
Ready to fix your feedback loop?
Set up your first complaint board in under 2 minutes. No credit card required.
Try FeedSolve Free