Field guide

Construction QA and QC: plan the standard, then check the work.

Quality assurance helps a project prepare a reliable way of meeting its requirements. Quality control checks the work being delivered. On a construction project, the useful question is who plans the check, who performs it and what happens to a finding afterwards.

Product and record-keeping guidance by SiteWarden. Read the linked source in its stated jurisdiction and project context, and use the project’s authorised people for contract, technical or compliance decisions. How these guides are reviewed.

The practical difference between QA and QC

ASQ describes quality assurance as providing confidence that quality requirements will be met, and quality control as fulfilling those requirements. Planning and inspection support each other, but they have different jobs.

A site quality plan explains the responsibilities and records for a package of work. An inspection can reveal an issue with the result. Connect the activities through named owners and clear follow-up.

A worked example: the kitchen cabinet doors

Consider an illustrative kitchen installation. Before the work starts, the team agrees which drawings and finish schedule apply, who checks the installation and when the check takes place. The supervisor knows which document to consult if the drawing changes.

During the walk, the supervisor observes that two adjacent cabinet doors sit at different heights. They record the kitchen location, a wide photo, a close photo and the observed gap. The record identifies the relevant trade and the person coordinating the follow-up.

After adjustment, the authorised reviewer checks the door alignment and operation against the applicable project requirement. The original finding and the review evidence remain connected. This is a fictional example of the record sequence, not a prescribed cabinet tolerance or repair method.

Make the handoff from inspection to follow-up explicit

Give the next person enough context to locate and understand the finding. “Kitchen unfinished” leaves several questions open. A specific location, item description and photo make those questions easier to resolve.

Keep the required decision visible too. Some findings need a trade visit; others need clarification from the designer or a qualified specialist. Record that next step before treating the item as ready for repair.

  • Identify the project, area and item being discussed.
  • Keep the observed issue and supporting evidence together.
  • Name the responsible follow-up and the authorised reviewer.
  • Record the review outcome after the work or clarification.

Record quality findings when the site is offline

A site walk may continue through areas with poor reception. SiteWarden supports offline capture in the mobile app, so the team can record a finding and its photos on site, then sync when a connection is available. Check the device and project setup before a walk where coverage is uncertain.

The offline record supports quality follow-up; it is not an approval of the work. Desktop access and online services need connectivity, and formal inspection and test plans, hold-point releases and quality approvals remain in the project’s designated system.

Keep the quality plan and the defect records connected

SiteWarden supports the field record and follow-up: photos, location, issue, trade, responsibility, priority and status. Project lists help the team organise findings from different walks. Professional and Business include the desktop workspace and internal team.

Formal inspection and test plans, hold-point releases, compliance testing and NCR dispositions belong in the project’s quality system. SiteWarden does not replace those documents or certify the work. Refer to the relevant requirement when a finding needs formal handling.

Review the record before reporting

Before a quality discussion, check that each selected item still describes the current situation. Resolve unclear locations and responsibility. Keep a contractor’s report of completion separate from your team’s acceptance.

The SiteWarden sample PDF shows the reporting format using 10 fictional outstanding items across three site lists. Its 16 pages include photos, location context and QR evidence links. Use it to inspect the output; it does not measure a customer’s quality improvement.

A few more details

Common questions.

Still weighing it up? Talk to our team.

What is the difference between QA and QC in construction?

QA provides confidence in how quality requirements will be met. QC checks and addresses the work delivered against those requirements. On site, connect the planned responsibility for a check with the finding, follow-up and review record.

Is a construction defect list a complete quality management system?

No. A defect list records findings and follow-up. The project may also require a quality plan, controlled documents, inspection and test plans, test results and formal non-conformance approvals. Those requirements remain in your project quality system.

Can construction quality findings be recorded offline?

SiteWarden supports offline capture in the mobile app and syncs records when a connection is available. Desktop and online services need connectivity. Keep formal quality approvals and inspection and test plans in the project’s designated system.

Which part of construction quality does SiteWarden support?

SiteWarden supports punch list and defect capture, responsibility, status tracking, evidence review and PDF reporting. AI-assisted fields help prepare records; the authorised project team remains responsible for inspection and acceptance.

See it on your next site walk

Bring your list.
We’ll walk you through it.

Unfinished work, defects and the details in between. See how the current app captures, organises and reports on them.

Book a Demo