What Is QA/QC in Construction? Complete Basics, Duties & Job Guide

Preparing for a QA/QC engineer interview, or starting your first job as a QA/QC or site engineer? This article is your complete preparation guide. It covers the concepts interviewers ask about, the documents you will handle on site, ready-to-use inspection checklists for daily work, and the most common QA/QC questions with proper answers — all in one place, in a field voice, the way these things actually happen on a construction site.

Read it fully once, and you will walk into the interview — and onto the site — knowing what quality work really means.

What Is QA/QC in Construction?

QA/QC stands for Quality Assurance and Quality Control. Together they are the system that makes sure the work built on site matches the drawings, the specifications and the contract — the first time, not after repair.

Every structure you see standing was checked hundreds of times before it was covered up: the steel before the pour, the soil before the foundation, the blocks before the plaster. Once concrete is cast or a wall is plastered, the inside can no longer be seen. That is why quality work is done before covering, not after handover. A QA/QC engineer is the person who makes sure nothing wrong gets buried inside the building.

QA vs QC — The Difference

This is the first question in almost every QA/QC interview, so learn it clearly.

Point	QA — Quality Assurance	QC — Quality Control
Meaning	The planned system that prevents defects	The inspection and testing that detects defects
Focus	Process — how the work is done	Product — the finished work itself
Nature	Proactive (before the mistake happens)	Reactive (finds the mistake after it happens)
Main tools	Quality plan, procedures, method statements, audits, training	Checklists, inspection requests, lab tests, measurements
Example	Writing the concreting procedure and training the crew before the first pour	Doing the slump test and cube test during the pour
Responsibility	Management and QA team	QC engineers and inspectors on site

Simple way to remember: QA builds the system right, QC checks the work right. A project needs both — a good system with no checking fails, and checking with no system means you are only catching mistakes instead of preventing them.

Why Quality Matters — The Cost of Poor Quality

Poor quality is not just an engineering problem, it is a money problem. Site people use a simple rule of thumb called the 1–10–100 rule: a mistake that costs 1 rupee to prevent at the planning stage costs about 10 rupees to fix during construction, and about 100 rupees after the structure is finished or has failed. A wrong bar diameter caught on paper costs nothing. Caught after the pour, it costs breaking, re-fixing and re-casting. Caught after handover, it can cost the whole element — plus the company’s name.

Beyond money, poor quality means rework and delays, disputes with the client, rejected work, and in the worst case, failure of the structure and loss of life. This is why clients and consultants take QA/QC seriously, and why a good QA/QC engineer is always in demand.

Documents a QA/QC Engineer Must Know

Half of quality work is paper — because the paper is the proof. These are the documents you will handle daily:

• Project Quality Plan (PQP): the master document that defines how quality will be managed on the project — responsibilities, procedures, inspections, tests and records.
• Specifications: the technical rules of the project. When in doubt, the specification wins.
• Approved / IFC Drawings: only the latest approved revision may be used on site. Working from an old drawing is one of the most common site mistakes.
• ITP (Inspection and Test Plan): a table for each activity listing what will be inspected or tested, against which standard, by whom, and at which type of point (hold, witness or review).
• Method Statement (MOS): the step-by-step description of how an activity will be carried out — sequence, manpower, equipment, materials and safety controls.
• Checklists: the point-by-point list used to inspect work before it is approved (ready checklists are given later on this page).
• Inspection Request (IR / WIR): the contractor’s formal request asking the consultant or client to inspect completed work before it is covered or the next activity starts.
• Material Submittal: documents and samples of a material submitted for approval before it is ordered or used.
• Material Inspection Request (MIR): the request to inspect material when it arrives on site, against the approved submittal.
• NCR (Non-Conformance Report): the formal report raised when work or material does not meet the specification or drawing.
• Daily Reports and Test Records: the daily record of work, inspections and lab results — the project’s memory.
• Calibration Certificates: proof that testing and surveying equipment (cube machine, total station, level, balances) has been checked against standards and reads correctly.
• As-Built Drawings: drawings updated to show what was actually constructed, submitted at handover.

Related reading: our guide on the RFI in construction explains another document you will meet in your first week on site.

What a QA/QC Engineer Does Every Day

1. Daily site walk — rounds of all active work fronts, watching workmanship while work is in progress, not after it is finished.
2. Material inspection — checking incoming material against the approved submittal, arranging sampling and lab tests, and rejecting what does not comply.
3. Inspection before covering — reinforcement, formwork, buried services and foundations are inspected and signed off before concrete or backfill hides them forever.
4. Witnessing tests — slump, cubes, field density, compaction and other tests are witnessed, recorded and followed up.
5. Raising and closing NCRs — recording non-conformances, following the corrective action, and re-inspecting the repair.
6. Coordination — with the site team (to prevent mistakes), the consultant (for inspections) and the lab (for results).
7. Documentation — checklists, inspection requests, test reports and registers kept complete and up to date, every day.

Inspection and Testing on Site

QC stands on tests. These are the tests you will witness most, and each one has a full guide on this site:

• Slump test — workability of fresh concrete, checked when concrete arrives: slump test on fresh concrete.
• Compressive strength (cube/cylinder) test — proof that hardened concrete reached its design strength: compressive strength of concrete.
• Field density test — proof that soil and layers are compacted to the specified percentage of MDD: field density test and report format.
• Subgrade preparation and compaction control — how a road layer is prepared and accepted: subgrade preparation for achieving compaction.
• Soil tests — the full family of lab and field tests on soil: soil tests used in civil engineering.
• Fresh and hardened concrete properties — what you are really controlling when you test concrete: properties of fresh and hardened concrete.

NCR and Defects — How Non-Conformance Is Handled

When work or material does not match the drawing or specification, it is recorded on an NCR (Non-Conformance Report). An NCR is not a punishment — it is a control tool that makes sure a defect is fixed properly and recorded, not quietly covered.

The NCR cycle runs like this:

1. Issue — the defect is described clearly, with location, drawing/specification reference and photos.
2. Root cause — why it happened (wrong material, untrained crew, old drawing, skipped inspection).
3. Disposition / corrective action — the decision: repair, rework, replace, or (rarely, with the designer’s written approval) accept as-is.
4. Corrective work — the repair is done by the approved method.
5. Re-inspection — the QA/QC engineer inspects the corrected work.
6. Close — only after re-inspection passes is the NCR signed off and closed in the register.

Common defects you will deal with: honeycombing in concrete, cracks, wrong cover, misalignment, low compaction and failed cube results. Each is covered in the questions section below.

Ready QA/QC Checklists for Site Work

Interviewers love checklists, and site engineers live by them. Below are ready inspection checklists for the most common activities. Learn what each point protects against — that understanding is what separates a tick-box inspector from a real QA/QC engineer.

Checklist 1 — Material Receiving Inspection

• ☐ Material matches the approved submittal and purchase order
• ☐ Delivery note, mill certificates and test certificates received and checked
• ☐ Quantity verified against the delivery note
• ☐ Visual inspection passed — no damage, heavy rust, contamination or expired shelf life
• ☐ Samples taken for lab testing where required (cement, steel, aggregates, blocks)
• ☐ Storage is correct — cement in a dry store on pallets, steel off the ground, aggregates on a clean hard surface
• ☐ Material Inspection Request (MIR) raised and signed
• ☐ Rejected material marked, segregated and removed from the work area

Checklist 2 — Reinforcement (Steel) Inspection

• ☐ Latest approved drawing revision is being used
• ☐ Bar diameter, grade and brand match the drawing and approved material
• ☐ Spacing of main and distribution bars is as per drawing
• ☐ Lap lengths and lap positions are correct and staggered
• ☐ Cover blocks of the specified size are provided and properly tied
• ☐ Chairs and supports keep the top steel at the correct level
• ☐ Steel is clean — no loose rust, oil, mud or concrete splashes
• ☐ Embedded items, sleeves and conduits are placed before the pour
• ☐ Inspection request signed before concreting is allowed

Checklist 3 — Formwork Inspection

• ☐ Dimensions, alignment and location match the drawing
• ☐ Level and plumb (verticality) are within tolerance
• ☐ Props and supports are firm, braced and on solid ground
• ☐ Joints are sealed so cement slurry cannot leak (leakage causes honeycombing)
• ☐ Release agent (shuttering oil) applied — without staining the reinforcement
• ☐ Inside of the formwork is clean — no timber offcuts, wire pieces or dust
• ☐ Openings, box-outs and cast-in items are fixed in position
• ☐ Camber is provided where the drawing specifies it

Checklist 4 — Concrete Pouring (Before, During, After)

Before the pour:

• ☐ Reinforcement and formwork checklists completed and IR signed
• ☐ Approved mix design available; plant and transit mixers arranged
• ☐ Vibrators ready — including a spare — and trained operators assigned
• ☐ Cube moulds, slump cone and thermometer on site
• ☐ Curing material (hessian, polythene, water arrangement) ready
• ☐ Weather checked; plan for rain or extreme heat in place

During the pour:

• ☐ Slump test done at the agreed frequency; out-of-range loads rejected
• ☐ No water added beyond the design water-cement ratio
• ☐ Concrete placed in layers and fully vibrated — not over-vibrated
• ☐ Cubes cast, labelled and stored correctly for curing
• ☐ Construction joints only at planned locations

After the pour:

• ☐ Curing started on time and continued for the specified period (normally at least 7 days)
• ☐ Formwork removed only after the specified time/strength
• ☐ Surface inspected; defects like honeycombing recorded for repair approval
• ☐ Cube results followed up at 7 and 28 days

Checklist 5 — Earthwork and Compaction

• ☐ Fill material is approved and free of organic matter and debris
• ☐ Layer thickness as specified (commonly 150–200 mm loose)
• ☐ Moisture content near the Optimum Moisture Content (within about ±2%)
• ☐ Compaction equipment suits the soil type (sheepsfoot for cohesive, smooth vibratory drum for granular)
• ☐ Field density tested at the specified frequency (sand cone or core cutter)
• ☐ Compaction achieved is at or above the specified percentage of MDD
• ☐ Proof rolling done; soft or pumping areas removed and redone
• ☐ Finished level and camber checked before the next layer is allowed

Checklist 6 — Blockwork and Plaster

• ☐ Blocks are approved, sound, and wetted/soaked as required before laying
• ☐ Mortar ratio as specified; mortar used within its working life
• ☐ Line, level and plumb checked continuously
• ☐ Joints are uniform, staggered, and not thicker than specified
• ☐ Lintels and sill bands provided over openings as per drawing
• ☐ Masonry cured for the specified period
• ☐ Before plaster: surface hacked/roughened, cleaned and wetted
• ☐ Plaster thickness controlled with dots/guides; finished surface true and cured

QA/QC Interview Questions and Answers

This is the preparation core of this page — the questions asked again and again in QA/QC engineer interviews, with the answers a working site engineer would give. Learn the reasoning, not just the lines.

1. What is QA/QC in construction?

QA/QC is the complete system for making sure construction work matches the drawings, specifications and contract. QA (Quality Assurance) is the planned, preventive side — procedures, plans and audits. QC (Quality Control) is the checking side — inspections and tests on materials and finished work. Together they prevent defects and catch the ones that still occur before the work is covered.

2. What is the difference between QA and QC?

QA is process-oriented and proactive: it builds the system that prevents mistakes, through the quality plan, method statements, training and audits. QC is product-oriented and reactive: it inspects and tests the actual work — slump tests, cube tests, density tests, measurements — to detect mistakes. QA asks “are we working the right way?”; QC asks “is this work right?”

3. What is a Project Quality Plan?

The Project Quality Plan (PQP) is the master quality document of a project. It defines responsibilities, procedures for inspection and testing, documentation, non-conformance handling and records, in line with the contract and usually with ISO 9001. Everything the QA/QC team does on site traces back to this plan.

4. What is an ITP?

ITP means Inspection and Test Plan. For each activity it lists the inspections and tests to be performed, the reference standard or specification clause, who performs them, who witnesses them, and the type of point involved — hold, witness, surveillance or review of records.

5. What is the difference between a hold point and a witness point?

At a hold point, work must stop and cannot proceed until the inspection is done and formally released by the client or consultant — for example, reinforcement inspection before a pour. At a witness point, the other party is invited to witness the work or test, but if they do not attend after proper notice, the work may proceed as planned.

6. What is a method statement?

A method statement is the step-by-step description of how a specific activity will be executed: the sequence of work, materials, manpower, equipment, quality checks and safety controls. It is submitted and approved before the activity starts, and the site team must follow it.

7. What is an Inspection Request (IR)?

An Inspection Request (also called WIR — Work Inspection Request) is the contractor’s formal request asking the consultant or client to inspect a completed stage of work. Only after the IR is approved may the work be covered or the next activity begin. Working ahead without an approved IR is a classic cause of disputes and NCRs.

8. What is a material submittal, and what is an MIR?

A material submittal is the set of documents — technical data, certificates, samples, test reports — submitted to the consultant for approval before a material is purchased or used. MIR is the Material Inspection Request raised when the material actually arrives on site, so it can be inspected against that approved submittal.

9. What is an NCR? When is it issued?

An NCR (Non-Conformance Report) is the formal report issued when work or material deviates from the specification, drawing or approved procedure — wrong cover, failed compaction, honeycombed concrete, unapproved material. It records the problem, its location and the reference it violates, and it stays open until the corrective action is completed and re-inspected.

10. How is an NCR closed?

First the root cause is identified, then a disposition is decided — repair, rework, replace, or accept-as-is only with the designer’s written approval. The corrective work is carried out by the approved method, the QA/QC engineer re-inspects it, and only when it passes is the NCR signed and closed in the register.

11. What is a snag list (punch list)?

A snag list, or punch list, is the list of defects and minor incomplete items found during inspection near completion — paint damage, misaligned fittings, small cracks, missing covers. Every item must be rectified and re-inspected before the section is handed over.

12. What is honeycombing in concrete, and why does it happen?

Honeycombing is the formation of voids and stone pockets in hardened concrete where the mortar failed to fill around the aggregate. Main causes: insufficient or improper vibration, congested reinforcement with harsh mix, leaking formwork joints losing cement slurry, and dropping concrete from a height causing segregation. Prevention is correct mix, tight formwork and proper layer-by-layer vibration.

13. What do you check before a concrete pour?

The completed reinforcement (diameter, spacing, laps, cover, cleanliness), the formwork (dimensions, level, supports, sealed joints, cleanliness), embedded items in position, and the signed inspection request. Plus readiness: approved mix design, vibrators with a spare, cube moulds and slump cone available, and curing arrangements ready. The full pour checklist is given above on this page.

14. Why are concrete cubes tested, and what happens if results fail?

Cubes (or cylinders) are cast from the fresh concrete and crushed at 7 and 28 days to prove the hardened concrete reached its design strength. Under ACI 318, strength is considered satisfactory when the average of three consecutive tests is at or above the specified strength f’c, and no single test falls more than 3.5 MPa below f’c (for f’c up to 35 MPa). If results fail, the investigation escalates: core tests from the actual structure, non-destructive tests like the rebound hammer, and finally the designer’s decision — accept, strengthen, or demolish and recast.

15. What slump is acceptable for concrete?

The acceptable slump is the one stated in the approved mix design and specification for that element — it is not one universal number. Slump is measured on arrival by the slump test; concrete outside the specified range is rejected, and water must never be added on site beyond the design water-cement ratio to “improve” it. Full procedure: slump test on fresh concrete.

16. What is concrete cover, and why is it checked so strictly?

Cover is the distance between the outer surface of the reinforcement and the nearest concrete face. It protects the steel from corrosion and fire and ensures bond. Too little cover rusts the steel and spalls the concrete; too much reduces the effective depth. It is provided with cover blocks of the specified size and verified during the reinforcement inspection — because after the pour, it can never be corrected.

17. Why is curing important, and for how long?

Curing keeps concrete moist while it gains strength; concrete that dries early stays weak and cracks. Moist curing is normally continued for at least 7 days for ordinary Portland cement concrete — longer in hot, dry or windy weather, or when the specification demands it. Common methods: ponding, wet hessian or jute, polythene covering and curing compounds.

18. What is calibration in QA/QC?

Calibration is the periodic checking of measuring and testing equipment — cube testing machines, total stations, levels, balances, sieves, slump cones — against known standards, so their readings can be trusted. Each instrument carries a calibration status and certificate; results from out-of-calibration equipment are not acceptable.

19. What is the cost of poor quality?

It is everything spent because work was not right the first time: rework, demolition, re-testing, delay, dispute and damage to reputation. The 1–10–100 rule of thumb expresses it: a defect costs about 1 unit to prevent, 10 units to correct during construction, and 100 units to correct after completion or failure. This is the economic argument for QA — prevention is the cheapest inspection.

20. What are as-built drawings?

As-built drawings are the final set of drawings revised to show exactly what was constructed — including every change, shift and additional work — prepared progressively during the project and submitted at handover. They are the record the owner will use for maintenance and future modification.

21. What documents are required at handover?

Typically: as-built drawings, all material certificates and test reports, inspection and test records, closed NCR and snag records, operation and maintenance manuals, warranties and guarantees, and calibration records. A project is not truly finished until this file is complete — final payment usually depends on it.

22. Which standards does a QA/QC engineer follow?

First, the project’s own specifications and contract documents — they rule over everything. Behind them, the common reference families are ASTM and ACI (American), BS (British), AASHTO (roads), and ISO 9001 for the quality management system itself. The ITP for each activity states which standard governs its inspections and tests.

QA/QC Topics We Will Cover in Detail

This article covers the basics completely. Each topic below will get its own detailed article in the QA/QC category on this site — written from site practice, not copied theory:

• NCR in Construction — issuing, disposition and closing, with format (detailed guide)
• ITP (Inspection and Test Plan) — how to read and prepare one
• Honeycombing in Concrete — causes, repair method and prevention
• Concrete Pour Checklist — the complete pre-pour, pouring and post-pour routine
• QA/QC Engineer Interview Preparation — extended question bank

Final Word

Every topic in this article reduces to one habit: check it before it is covered, and sign only what you have actually seen and verified. Learn the documents, learn the checklists, learn the reasoning behind the questions — and you are prepared, both for the interview and for the site.