Quality

End-to-end quality — material and work inspection requests, joint sign-off, NCRs, CQA Audit, and repeat-defect/vendor-quality analytics on one record.

What it is

One continuous quality record across the full inspection-to-analytics lifecycle. MAS raised - Approved, Material arrives — MIR raised — joint inspection against spec — pass or fail. Work starts — pre-WIR, during-WIR, post-WIR with photo, location, timestamp and joint CM-CQA-EHS-survey-MEP sign-off. Clean closure auto-triggers the bill workflow. Failures become NCRs; NCRs roll into CQA scores; pattern recognition surfaces repeat defects across vendor, project, package, employee. Field photos stay linked to drawing locations, not lost in WhatsApp.

Inputs

Triggers

·Vendor raises pre-WIR ready signal
·WIR scheduled date arrives
·MAS raised
·Method Statement Submittal (MSS)
·MIR scheduled against Client-supplied material handover
·Site Engineer + CQA joint inspection completes
·NCR raised during inspection or audit
·NCR closure submitted by vendor
·CQA audit scheduled (cadence or surveillance)
·Repeat-defect threshold breach detected
·Customer-facing defect pattern surfaced from M22 (Snagg) or M24 (Resident Services)

Data reads

·WO scope and schedule from M14 - Tendering
·Drawing version from M07 (Drawing)
·Spec from M09 (specs) with inspection acceptance criteria
·Vendor record from M13 (VMS) (history, NCR pattern, performance)
·Material handover record from M17 (Material)
·Previous WIRs against the same activity (for repeat-defect detection)
·Project segment from project record
·Past-project quality outcomes for comparable scope
·SOR (Site Observation Report) history

Artefacts consumed

·Pre-WIR submission with photo, location, scope
·Drawing reference and spec citation
·Test reports where applicable (cube strength, slump, etc.)
·Vendor declaration of compliance
·NCR raised by Site Engineer or CQA
·NCR closure evidence (photo, test result, rework proof)
·CQA audit reports
·Customer complaints from M24

Tools & Techniques

Methods

·Pre-WIR through joint inspection through closure workflow with hold-points
·MIR workflow for in-house supplied and vendor-supplied material handover
·Mobile-based inspection capture with photo, location, timestamp, signature
·NCR / SOR digital recording with category, severity, root cause
·Pattern recognition — repeat issues across vendor, project, package, material
·Customer-facing defect correlation back to source trade
·Auto-trigger bill workflow on clean WIR closure
·Auto-routing of repeat patterns to vendor performance review

Policies

·MAS/WIR/MIR workflow procedure
·quality objective
·NCR classification procedure with severity levels
·Bill auto-trigger procedure on clean WIR closure
·Inspection escalation procedure on repeat failures
·Repeat-defect threshold procedure per category
·Customer-defect correlation procedure

Decision rules

·Clean WIR closure auto-triggers bill workflow in M21 (billing)
·NCR open blocks downstream activity until closed
·Major NCR requires CQA Head sign-off on closure
·Three repeat NCRs of same type on same vendor auto-flags for CPT review
·Customer-facing defect correlates back to vendor on closure

Outputs

Artefacts produced

·WIR record per inspected activity (pre / during / post)
·MAS / MIR record per material handover
·NCR / SOR register with status, severity, root cause, closure evidence
·Inspection log per package per vendor
·CQA Audit Report
·Repeat-defect pattern reports per vendor and per package
·Customer-defect correlation reports

Data writes

·WIR/MIR status updated through lifecycle
·NCR status updated through closure (NCR open >30 days triggers billing to HOLD 30% of amount, variable per project)
·Vendor performance updated on every NCR event and closure
·Quality status updated per project, per package, per vendor
·CQA Audit Report

Downstream triggers

·Clean WIR closure auto-triggers bill workflow in M21 (billing)
·NCR and repeat-pattern flags trigger Vendor 360 review in M13 (Vendor Management)
·Repeat-pattern reports trigger tender exclusion in M14 (Tendering)
·Customer-correlated defects feed M22 (Snagg) snag prediction
·WIR closure rate feeds schedule velocity in M16 (Scheduling)
·Quality failure triggers root-cause workshop scheduling
·Quality alert mechanism — broadcast to design, CPT, CM

Stakeholders

Site EngineerRaises WIRs and MIRs against work and material handover
CMReadiness sign-off, continuous QC, post-WIR approval, rework follow-up
CQA EngineerJoint inspection, periodic audits, survelliance audits, NCR records
CQA LeadMajor-NCR sign-off, portfolio scoring, pattern reviews
CQA Headcontinous improvement, audit, monitoring, pattern reviews, SoPs
EHSSafety sign-off on joint post-WIR
VendorRaises pre-WIR, MAS, MIR, rectifies with evidence, closes NCRs
CommercialBill workflow triggered on clean WIR closure
Design (closing the loop)Pattern signals flow back to design choices

The flow

01MAS approval
02Material arrival at gate — MIR raised against in-house supplied or vendor-supplied material
03Joint MIR inspection (CM + CQA) against spec / FTP (field test plan) — pass or fail with reasoning
04Work execution with continuous CM-owned QC
05Pre-WIR raised by contractors before starting controlled activity (e.g. slab pour)
06Pre-WIR sign-off by CM (readiness, drawing version, spec citation confirmed)
07During-WIR spot checks by CM and CQA at planned hold-points
08Post-WIR raised on completion; joint sign-off by CM, CQA, EHS with photos
09Clean closure auto-triggers bill workflow in M21; failure raises an NCR
10NCR rectification by vendor with photo/test evidence, then CQA verification and closure
11Pattern recognition — repeat defects across vendor, project, package, employee — flags surface automatically
12Snag

State change

Before

MAS/MIR, WIR, MSS on paper or WhatsApp; sits in CQA queue till they are on site; bill blocked; photos lost. NCRs raised and closed in isolation; CQA scores computed manually and late; same vendor causes the same issue across three projects and nobody connects the dots.

After

Every MAS/MIR, WIR, MSS digital with photo, location, timestamp, drawing reference. Joint sign-off in hours not days. Bill auto-triggered on clean closure. Failures auto-feed the NCR register; CQA scores auto-computed; repeat-defect and vendor-quality patterns surface as alerts, not as discoveries during manual report review.

Real-world example

BA20 Eden D L12 — KCL raises pre-WIR for slab pour 14 May 9:38 AM. CM signs off at 9:51 AM. Concrete arrives 11:30 AM. During-WIR spot check at 12:05 PM. Post-WIR with 12 photos at 4:42 PM; joint sign-off by CM, CQA, EHS at 5:18 PM. Bill workflow auto-triggered. Meanwhile at Palava T4 — CQA audit raises NCR on flooring level T2 at 9:22 AM; pattern recognition identifies the third NCR this quarter for vendor Sterling, all flooring, two different sites. Sterling auto-flagged in Vendor 360; CPT alerted; Worli tender auto-excludes Sterling. 342 WIRs portfolio-wide, 4.2h average closure; CQA portfolio score 82.4; 3 vendors flagged repeat NCR.

Artefacts

·MIR record per material handover
·Pre-WIR / during-WIR / post-WIR record with photos
·Inspection checklist per activity type
·Joint sign-off log (CM · CQA · EHS)
·NCR / SOR register with status, severity, closure evidence
·Repeat-defect pattern report per vendor and per package
·Bill trigger record on clean WIR closure

Pain today

Inspections informal — WIR on paper, sits with CQA till they are on site, vendor billing waits, photos lost on WhatsApp. NCRs raised and closed in isolation; patterns across projects and vendors not connected; CQA score computed manually and late. Same root cause re-encountered every project; vendors flagged only when an incident is already systemic.

Integrations

No external system integrations — module operates on internal records.