RFI - Request for Inspection in Construction: A Practical Guide for Site Engineers and Quality Managers

Premium Pet Products
Quality Delivered Worldwide

🐾 🐾 🐾

Everything Your Dog and Cat Needs — In One Place

Toys beds grooming harnesses water fountains and more. Premium quality products shipped directly to your door.

Free Shipping in the US Premium Quality Secure Checkout

Shop Now at Yozafy.com

yozafy.com

The site engineer had been on the project for three months. It was his first posting on a large reinforced concrete structure — eight storeys, commercial use, the client a government authority with a detailed quality specification that filled two volumes. He had read the specification. He had read the Inspection and Test Plan. He understood, in general terms, that certain activities required inspection before proceeding.

What nobody had explained clearly was the difference between a hold point and a witness point — and specifically, what each one required him to do before work could continue.

His approach, based on his reading of the documents, was consistent: when an activity reached an inspection point in the ITP, he submitted a Request for Inspection to the client's quality team, waited until the next morning, and if no inspector had arrived by the time the crew was ready to proceed, he allowed the work to continue. This seemed reasonable. The notification had been sent. The inspector had chosen not to attend. The work was ready. The programme was pressing. He proceeded.

Three months in, the client's quality manager sat down with the inspection register and the ITP and worked through every activity completed to date. She found six instances where hold point activities had proceeded without a signed release from the client's inspector. In each case, the site engineer had submitted a proper Request for Inspection. In each case, no inspector had attended. In each case, the work had proceeded.

The quality manager explained the problem calmly but clearly. A witness point allows the contractor to proceed if the inspector does not attend after proper notification. A hold point does not. A hold point is a mandatory gate — work physically cannot proceed until the inspector has attended and signed the release, regardless of whether the inspector responds or not. If the inspector fails to attend a hold point within the notification period, the contractor's correct action is to escalate — not to proceed.

The engineer had read the ITP correctly. He had submitted his inspection requests correctly. The single gap in his understanding — the distinction between H and W in the inspection category column — had created six non-conformances, required re-inspection of six completed activities, and generated a formal quality audit that occupied the project team for two weeks. The work was accepted. But the quality record carried the NCRs permanently, and the contractor's quality standing with the client was affected for the remainder of the project.

What the Request for Inspection Actually Controls

In construction, the Request for Inspection — also called a Work Inspection Request or WIR, particularly on projects operating under Middle East quality frameworks including Saudi Aramco, NEOM, ADNOC, and similar specifications — is the formal document that activates the quality control gates defined in the Inspection and Test Plan.

The ITP is a structured plan that maps every significant activity in the construction sequence against a set of quality requirements — what needs to be checked, what standard it must meet, which parties need to be involved, and at what level of scrutiny. The Request for Inspection is the trigger that brings the relevant party to site at the moment the activity is ready for assessment. Without it, the inspection gate is bypassed — the activity proceeds without the formal verification the contract requires, the quality record is incomplete, and the contractor's ability to certify the work at handover is compromised.

Understanding the Request for Inspection is not just about quality compliance. It is about protecting the contractor's commercial position. An incomplete inspection record is not just an internal quality failure — it is a contractual deficiency that the client can use to withhold payment, delay handover acceptance, or require expensive remediation of work that may have been perfectly executed but cannot be certified without the inspection record to support it.

The Three Inspection Categories — Hold Point, Witness Point, and Surveillance

The single most important concept in managing inspection requests on a construction project is understanding what each inspection category in the ITP requires. The three categories — Hold Point, Witness Point, and Surveillance — look similar in the ITP table but carry completely different obligations. Treating them identically, as the site engineer in the opening story did, produces exactly the kind of quality record failure that is difficult and expensive to resolve. This is also a Site Engineer responsibilities see the full details here:  Site Engineer Role in Construction: Full Guide

Why Hold Points Cannot Be Bypassed

A hold point exists for activities where the consequence of proceeding without inspection is irreversible and potentially significant. Reinforcement in a column before the concrete is poured. Waterproofing membrane before the screed covers it. Pipe work before the trench is backfilled. Foundation bearing level before the blinding concrete is placed. Once the next stage has proceeded, the inspectable element is gone. It cannot be verified without destructive investigation.

The hold point is the contract's recognition of this irreversibility. It places a mandatory gate at the last moment when verification is still possible. The obligation on the contractor is not just to notify — it is to wait for the release. If the inspector does not attend within the notification period, the correct action is to contact the client's quality manager directly and request confirmation of when the inspector will attend. If the inspector's non-attendance is itself a failure on the client's side — a failure to resource the inspection function adequately — that becomes a formal issue between the parties. But proceeding past a hold point without a release is never the contractor's unilateral decision to make.

Witness Points — When the Contractor Can Proceed

A witness point gives the client the opportunity to attend without making their attendance mandatory. The contractor notifies the client's inspector within the required period. If the inspector attends, they witness the activity, sign the record, and the inspection is complete. If the inspector does not attend by the scheduled time and the contractor can demonstrate that proper notification was given — with a timestamped copy of the submission and evidence of receipt — the work may proceed. The contractor's own internal inspection record, completed and signed, documents the activity in the absence of the client's witness.

The witness point is designed for activities that are significant enough to warrant the client's involvement but not so irreversible that a missed attendance creates an unacceptable risk. The client has the right to attend. The contractor has the obligation to notify. The work does not stop indefinitely if the inspector fails to appear.

How to Raise a Request for Inspection — What Every WIR Must Include

A Request for Inspection that contains insufficient information creates friction at every stage — the inspector arrives without knowing what to look for, the record is incomplete, and the ITP audit trail is weakened. A well-prepared WIR gives the inspector everything they need to conduct a productive inspection without a preliminary phone call and without having to search through drawings to find the activity being inspected.

The checklist field in that table deserves specific attention. On well-managed projects, the site engineer completes a pre-inspection checklist — sometimes called a contractor's internal inspection report — before submitting the WIR. This checklist confirms that the site team has reviewed the work against the specification requirements before asking the client's inspector to attend. It demonstrates quality discipline, reduces the number of inspections that identify avoidable deficiencies, and builds the inspector's confidence that the contractor's internal quality processes are functioning. Over the course of a long project, that confidence translates into a more collaborative relationship with the inspection team and faster turnaround on inspection requests.

The Notification Period — Why Timing Is a Contract Obligation

The notification period for inspection requests is not a courtesy. It is a contract requirement — typically specified in the project's quality specification or Schedule Q, and typically set at 24 hours for standard site activities and 48 hours for activities scheduled on weekends, public holidays, or at locations that require the inspector to travel.

Submitting a WIR at 4pm for an inspection required at 8am the following morning does not satisfy a 24-hour notification requirement — it gives the inspector 16 hours, not 24. An inspector who arrives at an activity and finds it has already proceeded, with a WIR submitted less than 24 hours before the planned start, has grounds to raise a non-conformance regardless of the quality of the work itself. The process failure is independent of the workmanship quality.

The practical discipline is to submit every WIR at least one full working day before the inspection is required — and for hold points, to plan the construction sequence so that the hold point inspection is built into the programme as a defined activity with its own duration, not squeezed into the gap between one trade completing and the next trade mobilising.

What Happens After the Inspector Attends

A Request for Inspection that results in a clean inspection sign-off closes the loop in three steps: the inspector signs the WIR or the associated inspection checklist, the signed record is filed in the inspection register against the relevant ITP line item, and the activity is updated in the ITP tracking document to show it has been released. The contractor can then proceed with the next stage.

When the inspector identifies a deficiency — a dimension outside tolerance, reinforcement cover insufficient, a weld that does not meet the specification, waterproofing with a missed area — the outcome is a Non-Conformance Report, commonly called an NCR. The NCR documents the deficiency, the corrective action required, and the timeline for re-inspection. The work cannot proceed past the hold or witness point until the NCR is formally closed — which requires the corrective action to be completed and verified by a further inspection.

A well-managed NCR process is not a sign of poor quality — it is a sign of an effective quality system. Projects that never generate NCRs are usually projects where the inspection process is not functioning correctly, not projects where the work is always perfect. The NCR register, maintained transparently and closed promptly, demonstrates to the client that the contractor takes quality management seriously and responds to findings constructively rather than defensively.

The Inspection Record at Handover

At practical completion, the contractor assembles the handover documentation package. On most contracts, this package must include a complete set of signed inspection records for all ITP hold and witness point activities, alongside as-built drawings, operation and maintenance manuals, test certificates, and warranties. The inspection register — maintained throughout the project from the first WIR submitted to the last hold point released — is what makes this package complete.

A handover package with missing inspection records is an incomplete handover package. The client's representative is entitled to withhold the practical completion certificate — and the payment release associated with it — until the gaps are resolved. On a large project, resolving inspection record gaps at handover can mean re-inspecting completed work that has been buried or enclosed, producing retrospective concession documentation, or in the worst cases opening up finished work to allow the verification that should have been done during construction.

The engineer in the opening story was fortunate. His six hold point non-conformances were identified three months into construction, when the work was still accessible and the investigation cost, though significant, was manageable. Had those gaps been discovered at handover, eighteen months into the project with multiple subsequent layers of finishes applied, the consequences would have been considerably more serious.

The Request for Inspection sits within the broader quality and document management framework that every construction project needs from day one. For a practical guide to the document control disciplines that keep inspection records, RFI logs, and the full commercial correspondence organised throughout a project's life, see our article on Construction Document Control: The Basics Every QS Should Know.