The Concrete QA/QC Plan for a Hydropower Dam: 15 Sections Every Plan Must Include

Every hydropower dam contract requires the contractor to submit a Concrete QA/QC Plan before placing a single cubic metre. The plan is the contractual operating manual for quality. It defines who does what, against which standard, with what frequency, and how non-conformance is closed out. The owner’s engineer reviews it, the project owner approves it, and from that point forward it becomes the document everyone is audited against.

Most QA/QC plans submitted to PSU and EPC clients are not bad. They are generic. The contractor adapts a template from a previous project, swaps the project name, and submits it. The owner’s engineer rejects it on first read because the template was written for a different concrete grade, a different dam type, and a different code regime. The cycle costs both sides two to three weeks, sometimes longer, with no concrete placed.

This is the section-by-section reference for a Concrete QA/QC Plan that will survive owner’s engineer review on the first pass. Each section explains why it matters, what must be in it, the common errors that fail review, and what the owner’s engineer is checking for when approving it. The framework draws on ACI 121R-08, Guide for Concrete Construction Quality Systems in Conformance with ISO 9001, ICOLD Bulletin 136, Specification and Quality Control of Concrete for Dams, USACE EM 1110-2-2000, Standard Practice for Concrete for Civil Works Structures, and Indian Standards including IS 456, IS 457, IS 4926, IS 1199, IS 516, IS 10262, and IS 14591. Where the plan addresses a specific dam programme, it must also reflect the contract specification clause by clause.

1. Scope, Applicability, and Project Parameters

Why it matters. The scope section is the contract handshake. It establishes which concrete work the plan covers, which contract clauses it implements, and which exclusions are claimed. Disputes 18 months into a project frequently trace back to a scope section that was vague at submission.

What must be in it.

• Project identification: name, location, owner, contractor, EPC contract reference number, key milestones
• Concrete scope covered: dam body mass concrete, foundation concrete, RCC, shotcrete, tunnel lining, grouting, repair materials, secondary works
• Concrete grades within scope: M15 through M50 typically, with the specific grades and exposure classes per the contract
• Approximate concrete volumes by grade and structural element
• Applicable codes and standards with version dates, including IS, ACI, ASTM, ICOLD, BIS, and project-specific specifications
• Definitions of acronyms used throughout the plan
• Exclusions: what concrete work is explicitly outside scope, with reference to which contractor handles it

Common errors. Scope written as a paragraph instead of a structured list. Volumes given as a single total without breakdown by element. Standards listed without version dates, leaving open which revision applies. Exclusions absent, creating ambiguity on the interface between contractors.

How the owner’s engineer reviews. Cross-checks the listed concrete grades against the contract specification’s technical schedule. Verifies that every grade in the specification appears in the QA/QC plan’s scope. Confirms standards versions are current and consistent with the contract.

2. Organisational Structure, Roles, Responsibilities, and Accountability Matrix

Why it matters. The plan must show who is accountable for every quality decision. On a dam project, accountability gaps at the QC engineer to quality manager interface are where defects slip through. This section is also the first signal of whether the contractor is mobilising the right resources.

What must be in it.

• Project organisation chart showing reporting lines from the contractor’s project director down to the QC engineers at the batching plant, lab, and placement face
• Named individuals for every QA/QC role, not just position titles
• Qualifications and experience required for each role, with verification that the named individual meets them
• Responsibility, Accountability, Consulted, Informed (RACI) matrix for the 20-30 key quality decisions: mix design approval, batch plant calibration sign-off, hold point release, NCR raise, NCR closeout, acceptance test review, lift release, formwork stripping authorisation, curing termination, final acceptance
• Interface with owner’s engineer team and project owner: communication protocol, reporting cadence, escalation path
• Backup arrangements: who covers each role during leave, illness, or attrition

Common errors. Roles assigned to “TBA” individuals who never get mobilised. RACI matrix copied from a template with the same person accountable for raising and closing out NCRs (a structural conflict of interest). Quality manager reporting to the project manager rather than to the corporate quality function, undermining independence. No backup arrangement for the QC engineer position, leaving the lab unmanned during peak placement.

How the owner’s engineer reviews. Cross-checks named individuals against the contractor’s mobilisation schedule and CVs. Confirms the quality manager has a dotted line to a corporate quality function outside the project’s commercial chain. Verifies the RACI matrix does not place accountability for raising and closing the same NCR in the same person.

3. Document Control, Version Management, and Traceability

Why it matters. A QA/QC plan that cannot be traced is not a quality system, it is a folder of paper. The document control section establishes how every test result, mix design, NCR, and approval is identified, retrieved, and audited.

What must be in it.

• Document numbering scheme for every document type: drawings, specifications, mix designs, test reports, NCRs, lift release certificates, calibration certificates, training records
• Version control: how revisions are tracked, how the current version is identified, how superseded versions are archived
• Distribution control: who receives each document, how acknowledgement of receipt is captured
• Document approval workflow: who reviews, who signs, what the turnaround commitment is
• Retention schedule: how long each document type is held, in what format (physical, electronic, both), in what location
• Audit trail requirements: every test result must trace back through sample identification, batching record, mix design, material lot, and supplier source
• Software systems used (if any) for electronic document management, with backup and recovery procedures

Common errors. Document numbering scheme not actually applied; existing documents on site already deviate from it. Version control limited to “Rev A, Rev B” markers without log of what changed. Retention schedule shorter than the regulatory requirement (Indian dam safety regulations require concrete construction records for the life of the structure). No audit trail from cube test result back to placement.

How the owner’s engineer reviews. Picks one cube test result at random and traces it back through sample ID, batching record, mix design ID, material lot, and supplier source. If the trace breaks anywhere, the document control system is failed.

4. Material Qualification and Source Approval

Why it matters. Concrete quality on a dam is bounded by material quality. Material qualification is the gate that decides what enters the project. A weak gate produces a project with embedded material variability that no downstream QC can correct.

What must be in it.

• Approved supplier list for cement, aggregates, supplementary cementitious materials (fly ash, GGBS, silica fume), chemical admixtures, water, and reinforcement
• Source qualification testing for each material: required tests, frequency, acceptance criteria
• Cement source: certification per IS 12269 (53-grade OPC), IS 8112 (43-grade OPC), IS 1489 (PPC), IS 455 (PSC), or IS 12330 (sulphate-resisting cement), with manufacturer’s test certificates required at minimum monthly intervals
• Aggregate source: petrographic examination, alkali-silica reactivity (ASR) testing per IS 2386 Part VII or ASTM C1293, gradation per IS 383, deleterious materials, soundness, abrasion
• Fly ash source: testing per ASTM C311 sampling and testing methods, ASTM C618 or IS 3812 acceptance, with chemical analysis (SiO₂, CaO, LOI, alkali content) every 30 days
• Admixture qualification per IS 9103 or ASTM C494
• Mixing water source: testing per IS 456 clause 5.4 or ASTM C1602/C1602M-22, including chloride, sulphate, alkalies, total dissolved solids, and pH
• Material acceptance log: every lot received, source, date, test result, accept or reject decision
• Re-qualification triggers: change of supplier, change of source, test failures, extended storage, monsoon contamination

Common errors. Approved supplier list with no qualification test data attached. Aggregate ASR testing planned at a frequency too low to detect source variability (one test per quarter on a project consuming 50,000 tonnes per quarter is meaningless). Fly ash acceptance based only on supplier certificate, with no independent calorimetry or chemical verification. No re-qualification trigger when the cement supplier changes coal source for clinker production.

How the owner’s engineer reviews. Selects three materials at random from the approved supplier list. For each, requests the qualification test data and verifies it is current, complete, and from a NABL-accredited or equivalent laboratory. If any material lacks current qualification data, the source is removed from the approved list until requalified.

5. Mix Design Submission, Approval Workflow, and Trial Mix Qualification

Why it matters. Mix design is where the contract specification meets the contractor’s intent. The approval workflow is the gate that ensures the mix the contractor will batch is the mix the owner agreed to pay for.

What must be in it.

• Mix design procedure followed: ACI 211.1, IS 10262:2019, or other applicable
• Submission package contents: design calculations, material specifications, supplier certificates, target proportions, trial batch results, statistical analysis of trial cubes, recommended w/cm, expected fresh and hardened properties, exposure-class durability provisions
• Trial mix programme: number of trials, age-strength relationship, durability testing (rapid chloride penetration per ASTM C1202, water permeability, AAR if reactive aggregates suspected)
• Approval workflow: contractor submission, owner’s engineer review with stated turnaround commitment (typically 10-14 working days), revisions and resubmission, final approval signature, mix design identification number
• Production sample verification: minimum 28-day cubes from first production batch confirming trial mix performance
• Mix design control during production: when a mix design must be revised (change of source, change of grade, change of exposure class), and how that revision is approved
• Library of approved mix designs maintained as a controlled document

Common errors. Mix design submitted without trial batch results, relying on a similar mix from a previous project. Approval signed off by the contractor’s QC engineer rather than by the owner’s engineer. Mix design identification number reused for two different mixes, breaking traceability. Production sample verification skipped because of schedule pressure. Mix designs revised on the batching plant control screen without going through formal revision approval.

How the owner’s engineer reviews. Verifies every approved mix design has a trial batch result, owner’s engineer signature, and a unique identification number traceable to placement records. Confirms the production sample verification was performed and the result is in the file. Spot-checks that the mix design on the batching plant control screen matches the approved version, not a hand-edited variant.

6. Batching Plant Controls, Calibration, and Material Handling

Why it matters. The batching plant is the production engine. Its accuracy and consistency determine whether the batched concrete matches the approved mix design. Calibration drift, scale wear, and moisture-compensation failure are silent producers of out-of-spec concrete.

What must be in it.

• Batching plant specifications: capacity, type (wet-batch / dry-batch / RCC paver-feed), mixer type and capacity, control system
• IS 4926:2003 ready-mixed concrete batching tolerances: cement and mineral admixtures ±2 percent, aggregates and chemical admixtures and water ±3 percent
• Scale calibration: installation accuracy ±0.25 percent of full scale, operational accuracy ±0.50 percent, recalibration interval every 2 months for mechanical and every 3 months for electrical load-cell scales per IS 4926
• Aggregate moisture compensation: how moisture is measured (probe type, calibration), how often, how the batch is adjusted, what happens at shift change
• Material storage and handling: stockpile management (segregation prevention, contamination protection, monsoon cover), cement silo aeration and discharge controls, fly-ash silo, admixture tank temperature control
• Ready-mix discharge timing: per IS 4926, concrete must be discharged within 90 minutes from water addition OR within 300 mixer revolutions, whichever comes first
• Plant operator training: certification, refresher schedule, supervision arrangement
• Plant log: every batch’s mix ID, weights, moisture, target slump, mixing time, discharge time, destination location

Common errors. Calibration interval stated as “monthly” without specifying installation or operational accuracy. Aggregate moisture compensation defaulted to a fixed value rather than measured per batch. No discharge time recorded; ready-mix arriving at the dam face well past the IS 4926 90-minute window. Plant operators rotated without retraining records. Plant log gaps during peak placement.

How the owner’s engineer reviews. Walks the batching plant during a production shift. Verifies scale calibration certificate is current and from an accredited calibration agency. Picks one batch at random and verifies the plant log against the actual delivery ticket and the cube sample. Confirms the moisture compensation reading is updated each shift.

7. Transport, Placement, and Consolidation Protocols

Why it matters. Concrete that leaves the plant in spec can arrive at the placement face out of spec because of transport-induced segregation, temperature gain, or workability loss. The placement protocols then decide whether the concrete behaves as designed.

What must be in it.

• Transport methods: transit mixer, dumper, conveyor, pump, crane bucket
• Transport time limits: per IS 4926 and the project-specific specification, considering ambient temperature and travel distance
• Concrete temperature management during transport: insulated tarpaulin, chilled water flushing of transit mixer drums, route selection
• Placement methods by structural element: chute, pump line, crane bucket, RCC paver, shotcrete gun, tremie for underwater concrete
• Lift height and rate: per ACI 207.1R for mass concrete, typically 1.5 to 3.0 metres per lift in dam body construction
• Vibration protocol: vibrator type, immersion spacing (typically 4 to 6 times vibrator diameter), immersion time (5 to 15 seconds per insertion), withdrawal speed, layer reach (vibrator must penetrate 100 mm into previous lift to consolidate the interface)
• Cold weather and hot weather placement triggers: ambient temperature thresholds, additional cooling or heating measures
• Stopping criteria: when placement must halt because of weather, plant breakdown, materials shortage, or shift change, and what becomes a construction joint
• Construction joint preparation: green cutting, scrubbing, bedding mortar application

Common errors. Transport time limit stated only as “as soon as possible” without numerical bound. Lift height set at the maximum allowed for every pour regardless of thermal control plan constraints. Vibration immersion time prescribed but no enforcement mechanism; vibration operators not trained. Cold weather and hot weather triggers absent or set so high they are never triggered. Construction joint criteria left to placement engineer’s field judgment.

How the owner’s engineer reviews. Verifies transport time limits against the project’s ambient conditions. Checks that lift height in the QA/QC plan matches the lift height in the thermal control plan. Watches a placement and confirms vibration protocol is being followed by the actual crew, not just written in the plan.

8. Thermal Control Monitoring and Compliance

Why it matters. Mass concrete in a hydropower dam is one of the most thermally sensitive structures built by civil engineering. The QA/QC plan must show how the thermal control plan is monitored, how data is reviewed, and how thermal non-conformance is closed out before it propagates into permanent cracks.

What must be in it.

• Reference to the project’s thermal control plan, which is typically a separate document but must be cross-linked from the QA/QC plan
• Standards: IS 14591, Temperature Control of Mass Concrete for Dams - Guidelines, authored by PCCI’s Managing Director, and ACI 207.1R, 207.2R, 207.4R series
• Placement temperature limits: maximum at the dam face, with field-verification protocol
• Peak temperature limits: per ACI 301, maximum internal mass concrete temperature 70°C (158°F) to avoid delayed ettringite formation
• Core-surface temperature differential limits: per ACI 207.2R, typically 19.4°C (35°F), with newer Performance-Based Temperature Difference Limit (PBTDL) approach where qualified by analysis
• Cooling rate limit: typically not more than 11°C (20°F) per 12 hours per ACI 207 guidance
• Embedded thermocouple instrumentation: layout, calibration, data logging frequency, redundancy
• Cooling pipe system (where used): layout, flow rate, water temperature, cooling cycle duration, post-cooling termination criteria
• Daily thermal report contents: maximum temperature, maximum differential, cooling rate, comparison with limits, NCR triggers
• Curing temperature monitoring: surface insulation, cover thickness, exposure protection

Common errors. Reference to thermal control plan made but the plan itself is not attached or cross-referenced by document number. Placement temperature limit stated but no verification protocol at the dam face. Thermocouple layout described but no redundancy; single thermocouple failure produces gap in monitoring. Daily thermal report not actually compiled because no responsible engineer is named.

How the owner’s engineer reviews. Confirms the thermal control plan and the QA/QC plan use the same numerical limits. Spot-checks one lift’s thermal record from placement to peak to cooling termination, verifying the data was logged at the specified frequency and reviewed against limits. Verifies cooling pipe flow rates and water temperatures were within plan.

9. Curing Protocols, Duration, and Temperature Management

Why it matters. Curing is the cheapest concrete quality investment and the most commonly compromised. A QA/QC plan that does not explicitly define curing protocols, by structural element and by ambient condition, will see curing reduced to “spraying water sometimes” within months of starting.

What must be in it.

• Curing method by structural element: water curing (ponding, sprinkling, wet hessian), membrane curing, steam curing, insulation
• Curing duration: per ACI 308R, Guide to External Curing of Concrete, minimum 7 days when daily mean ambient temperature is above 5°C, or until 70 percent of specified compressive strength is reached, whichever is later. For mass concrete with extended hydration cycles, longer curing periods are typically specified.
• Curing temperature management: how surface temperature is monitored during curing, how thermal shock is prevented at formwork stripping, how cooling rate is controlled
• Curing water quality: meeting IS 456 clause 5.4 or ASTM C1602/C1602M-22 limits for chloride, sulphate, alkalies, and total solids
• Cold weather curing: protection against freezing, insulating blanket use, ambient threshold triggers
• Hot weather curing: continuous wet curing requirement, evaporation rate calculation per ACI 305, drying-shrinkage prevention
• Curing supervisor: named individual responsible for daily curing inspection
• Curing log: every day’s curing water application, surface condition, temperature, notes

Common errors. Curing duration stated as “as per IS 456” without numerical days. Curing supervisor role assigned to “site engineer” without naming a specific individual. Curing log absent or filled in retroactively. Hot weather curing not scaled up during the Indian summer when evaporation rates exceed 1 kg/m²/hr. Curing water source not specified, allowing the use of poor-quality water from convenience sources.

How the owner’s engineer reviews. Inspects 10 curing locations at random and asks the named supervisor to produce the curing log entry for each. Verifies curing water source meets the specified quality. Compares the curing protocol for hot weather days against the day’s evaporation rate; if evaporation exceeds 1 kg/m²/hr, additional protection should be in place.

10. Sampling and Testing Schedule for Fresh and Hardened Concrete

Why it matters. Sampling and testing produce the evidence on which acceptance decisions are made. A schedule that under-samples generates false confidence; one that over-samples drowns the laboratory and reduces test quality.

What must be in it.

• Fresh concrete sampling per IS 1199 Part 2:2018 and ASTM C172: location of sample collection, sample size, frequency
• Fresh concrete tests: slump (IS 1199 / ASTM C143), temperature, density, air content if entrained, workability retention
• Hardened concrete sampling per IS 456 clause 15: minimum 1 sample per 30 m³ per grade per day, or per the project specification (more demanding limits commonly apply on dam projects). Each sample = 3 cubes per IS 516 / ASTM C39 for 28-day acceptance, plus additional cubes for 7-day, 56-day, 90-day, and 365-day testing on mass concrete
• Specimen making per ASTM C31 for field-cured and standard-cured specimens
• Cube curing per IS 516 at 27°C ± 2°C, or ASTM C31 / C511 at 23 ± 2°C
• Accelerated testing: optional per IS 9013, Accelerated Curing of Concrete, to predict 28-day strength from early-age tests
• Additional hardened concrete tests: rapid chloride permeability (ASTM C1202), water permeability (ISAT or DIN 1048), modulus of elasticity, splitting tensile strength, durability tests as specified
• Aggregate testing during production: gradation, moisture, deleterious materials, weekly or monthly per spec
• Cement testing during production: monthly compressive strength, fineness, soundness, setting time
• Laboratory accreditation: NABL accreditation required for the on-site lab, or third-party NABL lab for tests the site lab cannot perform
• Cross-check testing: percentage of acceptance samples cross-tested at an independent NABL lab

Common errors. Sampling frequency lower than the contract specification, citing IS 456 minimum as the project standard. Cube cure tank temperature not monitored or not calibrated, biasing all acceptance results. No cross-check testing, leaving the contractor’s lab as the sole source of truth. Aggregate and cement production testing skipped because of schedule pressure.

How the owner’s engineer reviews. Audits one month’s sampling records and verifies the actual sampling frequency matches the plan. Witnesses cube preparation at the lab and confirms specimens are made per IS 516 or ASTM C31. Pulls a cube from the cure tank and confirms it is fully submerged, the tank is at 27°C ± 2°C, and the curing date matches the lab log.

11. Acceptance Criteria and Statistical Quality Control

Why it matters. Acceptance is the decision that admits concrete into the structure. The criteria must be unambiguous, code-aligned, and statistically defensible.

What must be in it.

• Acceptance criteria for 28-day compressive strength per IS 456:2000 clause 16 (with Amendment No. 3, August 2007):
  • Criterion 1: Mean of group of 4 consecutive test results greater than or equal to f_ck + 0.825σ (when σ is established from at least 30 results), or f_ck + 3 N/mm² (M15) / f_ck + 4 N/mm² (M20 and above) when σ is not established, per Table 11
  • Criterion 2: Each individual test result greater than or equal to f_ck − 3 N/mm² for M15 and above (per Amendment No. 3, 2007, which strengthened the limit from f_ck − 4 N/mm²)
  • Individual cubes within a sample within ±15 percent of the sample average per IS 516, or the sample is invalid
• Acceptance criteria per ACI 318 clause 26.12 where the project specification calls for ACI rules: mean of 3 consecutive strength tests greater than or equal to f’_c, and no individual test more than 3.5 MPa below f’_c (for f’_c ≤ 35 MPa)
• Standard deviation establishment: minimum 30 consecutive test results before σ is considered established
• Acceptance criteria for fresh concrete: slump within target band, temperature within limit, density within range
• Acceptance criteria for hardened durability: chloride permeability, water permeability, AAR expansion, modulus, sorptivity per specification
• Non-conforming concrete disposition: investigation, core extraction, structural assessment, accept-as-is, repair, or replace
• Acceptance certificate format: lift release certificate, structural element release certificate, mass concrete pour completion record

Common errors. IS 456 and ACI 318 criteria both listed without resolving which applies for which structural element on a multi-code project. Standard deviation taken from the first 4 cubes rather than 30. No defined disposition workflow for non-conforming concrete. Acceptance certificate signed by the contractor without owner’s engineer countersignature.

How the owner’s engineer reviews. Selects one acceptance certificate from a recent pour and verifies the acceptance calculation against the relevant code. Confirms standard deviation used in the calculation is from at least 30 results. Verifies non-conforming concrete from the past three months has documented disposition.

12. Non-Conformance Reporting (NCR) Workflow, Root Cause, and Corrective Action

Why it matters. NCRs are the immune system of the QA/QC plan. A weak NCR workflow leaves defects undocumented and recurrent. A strong one converts every defect into an institutional learning event.

What must be in it.

• NCR triggers: out-of-spec materials, test failures, placement defects, procedure deviations, missed hold points, equipment failures, environmental non-compliance
• NCR raising authority: any engineer on site can raise; QC engineer must raise if not raised by others
• NCR severity classification: minor (correctable on-site within shift), major (requires investigation and CAPA), critical (work halt until resolved)
• NCR workflow: raise → notify (within 4-8 hours) → investigate → root cause → corrective action → preventive action → closeout sign-off
• Root cause analysis methods: 5-Whys, fishbone diagram, fault-tree analysis, depending on severity
• Corrective and Preventive Action (CAPA): time-bound, with named owner, completion verification, effectiveness check at 30 / 60 / 90 days
• NCR register: every NCR logged with reference number, date, location, description, severity, status, closeout date
• NCR trend analysis: monthly review of NCR categories to identify recurring patterns and systemic issues
• Escalation: NCRs not closed within target timeframe escalate to project director and owner’s engineer

Common errors. NCR raising treated as an admission of fault and discouraged by site management. NCRs filed without root cause. CAPA listed but no completion verification or effectiveness check. NCR register incomplete; verbal closeouts substituted for documented ones. No trend analysis, so the same defect category recurs across multiple lifts.

How the owner’s engineer reviews. Selects 10 NCRs from the register at random and verifies each has root cause, CAPA, and closeout signature. Selects 3 closed NCRs that are at least 90 days old and checks the effectiveness verification. Reviews monthly trend analysis for patterns the contractor has not yet acted on.

13. Hold Points, Witness Points, and the Inspection and Test Plan (ITP)

Why it matters. Hold and witness points are the gates that prevent defective work from being concealed by subsequent work. A weak ITP turns the QA/QC plan into a paper exercise.

What must be in it.

• Inspection and Test Plan as a structured document, typically a spreadsheet, listing every activity requiring verification
• For each activity: activity name, applicable specification clause, inspection method, acceptance criteria, responsible party, Hold (H) / Witness (W) / Review (R) classification, sign-off requirement
• Hold Points: work cannot proceed without owner’s engineer sign-off. Typical examples on a dam project: foundation acceptance before first concrete, reinforcement acceptance before pour, mix design approval before batching, lift release before next lift, post-cooling termination, final acceptance.
• Witness Points: owner’s engineer may attend the inspection but work may proceed if absent. Typical examples: routine sampling, fresh-concrete testing, curing inspection, formwork inspection for non-critical elements.
• Review Points: post-completion review with no work-stoppage authority. Typical examples: cube test results, calibration certificates, training records.
• Typical ITP for a major dam programme: 200-500 line items, 15-25 hold points, 50-100 witness points, the remainder review points
• Notification requirements: hold and witness points require 24-72 hours advance notice to the owner’s engineer
• Missed hold point protocol: what happens when work proceeds without the required sign-off

Common errors. Hold and witness points classified the same as the previous project without re-mapping to current contract specification. Notification window not enforced; contractor calls owner’s engineer 30 minutes before a hold-point inspection. Missed hold point protocol absent, leaving non-compliant work in the structure.

How the owner’s engineer reviews. Verifies the ITP lists every contract-specified mandatory inspection as a hold point. Confirms the notification window is realistic for the owner’s engineer team’s site presence. Spot-checks 5 hold points from the past month and verifies each has documented sign-off before work continued.

14. Audit and Review Cadence

Why it matters. A QA/QC plan that is not periodically audited becomes a static document while the project evolves. The audit cadence is what keeps the plan operational.

What must be in it.

• Internal quality audits by the contractor’s corporate quality function: minimum quarterly, with audit scope, audit team, audit report distribution
• Owner’s engineer audits: monthly site audit, quarterly system audit, with written report to project owner
• Third-party audits: triggered by contract or by NCR escalation
• Lab audits: NABL re-accreditation audits, internal lab audits monthly, owner’s engineer lab audits quarterly
• Management review: contractor’s senior management review of quality system performance, minimum half-yearly, with documented inputs (KPIs, NCR trends, audit findings) and outputs (action items, resource decisions)
• Audit findings closeout: each finding has time-bound corrective action and verification
• Audit trend review: comparison of findings over time to identify systemic improvement or deterioration

Common errors. Audits scheduled but not performed, with audit reports backdated. Findings logged but never closed. Management review reduced to a quarterly meeting with no documented inputs or outputs. Lab audits skipped because of placement schedule.

How the owner’s engineer reviews. Requests the past 12 months of internal audit reports and verifies each was performed on schedule. Cross-checks one audit’s findings against the closeout actions. Attends the contractor’s management review.

15. Final Acceptance, Documentation Handover, and As-Built Records

Why it matters. Final acceptance is when the contractor’s responsibility for the concrete ends and the owner’s responsibility begins. The documentation handover defines what evidence the owner has, for the next 100 years, that the concrete was built as specified.

What must be in it.

• Final acceptance criteria: completion of all hold points, closeout of all NCRs, structural completion, performance testing, defect liability period
• Documentation handover package: every approved mix design, every test result, every NCR with closeout, every audit report, every calibration certificate, every training record, every lift release certificate
• As-built records: structural drawings updated for actual construction, embedded item locations, cooling pipe layouts, thermocouple positions, contraction joint locations and treatments
• Performance test results: long-age strength (90-day, 180-day, 365-day cores where specified), durability test results, in-situ NDT data
• Operations and maintenance manual handover: any concrete-specific provisions for future inspection, repair, or rehabilitation
• Handover format: electronic database with searchable index, plus physical archive copies, with retention duration matching dam safety regulatory requirements
• Final acceptance certificate: signed by contractor’s senior management, owner’s engineer, and project owner

Common errors. Documentation handover deferred to end of project, by which time critical records (early-age test reports, calibration certificates) have been misplaced. As-built drawings prepared from contract drawings without updating for construction-phase variations. Final acceptance signed before NCR closeout is complete.

How the owner’s engineer reviews. Audits the documentation handover package for completeness against the contract specification. Verifies as-built drawings against site surveys at 10 random locations. Confirms all NCRs are closed before signing the final acceptance certificate.

What an owner’s engineer looks for in the first 5 minutes of plan review

Across 40+ years of leadership experience spanning more than 4,000 MW of hydroelectric concrete programmes including Tala HEP (1,020 MW), Mangdechhu HEP (720 MW), and Punatsangchhu-1 HEP (1,200 MW), where PCCI leadership authored the Concrete Quality Control Manual, the first five minutes of QA/QC plan review tell you whether the plan is operational or theatrical. Five quick checks:

1. Open to the organisation chart. If the names are filled in and align with the mobilisation schedule, the plan is taking responsibility seriously. If the chart has “TBA” markers or shows the same person accountable for two conflicting decisions, the plan is theatrical.

2. Open to the ITP. Count the hold points. For a major dam project, 15 to 25 hold points is typical. If the ITP shows 5 hold points, the contractor is reserving discretion to themselves. If it shows 100 hold points, the contractor is going to drown the owner’s engineer in inspections, which will result in waivers, which defeats the purpose.

3. Open to the NCR workflow. Is there a defined CAPA closeout step with effectiveness verification at 30 / 60 / 90 days? If yes, NCRs will close properly. If no, NCRs will be raised and forgotten.

4. Open to the acceptance criteria section. Are IS 456 and ACI 318 criteria both listed without specifying which applies to which element? That is a contract management problem waiting to surface during the first dispute.

5. Open to the document control section. Pick one document type, say “cube test reports.” Trace the numbering scheme from issue through filing to retention. If the trace breaks, the entire audit trail is compromised.

These five checks take five minutes and reveal more than reading the plan cover to cover. A plan that passes all five gets a deep review. A plan that fails any of them goes back to the contractor for revision before the deep review starts.

Closing

A Concrete QA/QC Plan that survives owner’s engineer review on the first pass shares three properties. It is specific to the project (not a template). It assigns accountability by name (not by position). And it builds in feedback loops (audits, NCR trend analysis, management review) that keep it operational long after submission.

The 15 sections above are the architecture. The technical content within each section is what the contractor’s quality manager fills in against the contract specification and the applicable codes. The owner’s engineer’s job is to verify that the architecture is sound and the technical content is right, and then to hold the system to its own discipline through the construction window.

PCCI’s QA/QC consulting draws on leadership experience across the six landmark hydropower programmes that make up the company’s portfolio, including the authoring of the Punatsangchhu-1 Quality Control Manual referenced in this article. If your hydropower project is moving toward concrete placement, the cheapest insurance for the next 100 years of dam life is to bring an independent reviewer in before the QA/QC plan is signed off. The conversation begins with the contract specification, the contractor’s draft plan, and a walk through the batching plant.