Reinforcement is fixed, formwork is ready, embedded items have been checked, and the concrete pour is next on the programme. Before the work becomes concealed, however, the project may require an authorised inspection to confirm that the completed stage meets the applicable drawings, specifications and quality requirements.
That is where a Work Inspection Request, or WIR, comes in. A typical process moves from completed work and contractor checks to a formal inspection request, followed by inspection, comments and either release to proceed or corrective action. The exact terminology, notice periods and approval statuses depend on the project's contract and quality procedures.
A Work Inspection Request (WIR) is a formal construction-quality document used to notify the consultant, engineer, client representative or other authorised inspector that a specific item of work is ready for inspection.
A WIR may be used for activities such as reinforcement before concrete placement, waterproofing before covering, underground services before backfilling, blockwork, finishes, MEP installations or other work that must be inspected at a defined stage.
Timing is particularly important where later activities would make the work difficult or impossible to inspect. Reinforcement, for example, cannot be properly inspected after it has been covered by concrete. The same principle applies to waterproofing beneath finishes and services concealed above ceilings or inside walls.
HAL's guide to Quality Assurance vs Quality Control in Construction explains the wider relationship between quality planning and the inspection of actual work. A WIR sits within that broader quality-control process rather than replacing it.
The WIR is only one step in a wider construction quality process.
A simplified sequence is:
Requirements → Method Statement → ITP → Execute work → Internal inspection → WIR → External/authorised inspection → Release or correction
The documents within that sequence serve different purposes.
A Method Statement explains how the activity is intended to be carried out. An Inspection and Test Plan (ITP) identifies where inspections and tests are required, the applicable acceptance criteria and often the parties involved. The WIR is then raised when the actual work reaches the specified inspection stage.
This distinction is important because a WIR does not create the quality requirement. It points the inspector back to requirements that already exist in approved drawings, specifications, ITPs and other project documents.
The current ISO 9001:2026 quality-management standard similarly emphasises controlled operational processes, documented information, monitoring and evaluation. ISO 9001 provides the wider quality-management framework, but it does not prescribe a universal construction WIR form.
Construction projects use several documents that can look similar to people who are new to site QA/QC.
Terminology is not completely universal. On some projects, RFI can also be used to mean Request for Inspection rather than Request for Information.
Project procedures should therefore be checked before assuming that an abbreviation has exactly the same meaning on every construction project.
A WIR should be submitted when the relevant work has reached the required inspection stage and is genuinely ready for the authorised inspection.
Common inspection points include:
Readiness is more important than the programme date. A WIR should not be submitted simply because an activity was expected to finish that day.
Before submission, the contractor should confirm that the work is complete to the appropriate stage, internal inspections have been carried out, current approved drawings are available and relevant materials and supporting records are in place.
Any necessary test results, checklists or previous inspection comments should also be reviewed.
A useful principle is:
The WIR should confirm readiness for inspection, not ask the consultant to perform the contractor's internal quality control.
WIR formats vary, but a useful inspection request should give the inspector enough information to identify exactly what is being inspected and against which requirements.
Not every project requires every field. The contract, project quality plan and approved inspection procedure determine the actual submission format.
The most important qualities are specificity and traceability. “Inspect wall” is a poor description. “Blockwork inspection, Level 3, Grid B4-B8, Rooms 305-312” gives the inspection team a much clearer scope.
The activity does not always need to be fully finished. It needs to have reached the point defined by the ITP or project procedure.
For example, a reinforcement WIR is raised once the reinforcement and relevant embedded items are ready for inspection but before concrete is placed.
The site engineer, supervisor and QA/QC personnel should check the work as required before involving the consultant or client inspector.
Depending on the activity, this may include dimensions, levels, workmanship, approved materials, interfaces with other trades and the status of earlier comments.
The contractor should also confirm that the area is clean and accessible enough to inspect properly.
Before preparing the request, confirm which inspection point applies and what evidence must accompany it.
The ITP may identify a hold point, witness point or another project-defined control point. It may also specify required checklists, test reports, inspection responsibilities and notification requirements.
There is no universal rule that every WIR must be submitted 24 hours in advance. Notice periods should come from the actual contract or project procedure.
Complete the approved WIR form or digital submission using precise information.
Supporting information may include the current drawing, relevant specification or ITP reference, method statement, inspection checklist, test results, approved material information and photographs where required.
The exact location should be unmistakable. Inspection delays frequently occur simply because inspectors cannot determine which area or section a submission refers to.
The WIR should then move through the project's approved submission process.
Depending on the project, that might involve an electronic document-management system, common data environment, QA/QC platform, document-control process or another project-management workflow.
HAL's guide to Document Controller Responsibilities explains the document-registration, routing and revision-control role in more detail. Document control may register and distribute a WIR, but the technical responsibility for confirming that the work is ready normally sits with the appropriate construction and QA/QC personnel.
The authorised inspector assesses the work against the applicable requirements.
Inspection may include visual examination, dimensional measurement, survey information, physical testing, document review or review of associated test results, depending on the activity.
The current ISO/IEC 17020:2026 defines inspection broadly as examination of items such as materials, products, installations, processes, work procedures or services and determination of their conformity with applicable requirements.
Those requirements may come from contracts, standards, regulations or project specifications.
After the inspection, the outcome should be recorded according to the project's approved status system.
Possible outcomes may include acceptance, acceptance subject to comments, rejection or a requirement to revise and resubmit. The terminology and contractual effect of each status vary between projects.
The article should therefore not assume that an “A,” “B,” “C” or “D” status means the same thing everywhere.
If the inspector identifies issues that prevent release, the contractor should correct them and conduct another internal check before resubmission.
The updated request should preserve appropriate reference to the earlier inspection so that the history remains traceable.
The sequence becomes:
Inspection comments → Correction → Internal reinspection → Resubmission → Reinspection → Closure
Inspection and Test Plans often identify different levels of inspection involvement.
A Hold Point is a defined stage where the project procedure requires release before subsequent work can proceed. This is commonly used where continuing the work would conceal something important or make correction significantly more difficult.
A Witness Point provides the identified party with an opportunity to witness an inspection or test.
The practical consequences of a witness point depend on the project requirements. Some procedures may allow work to proceed after the required notification period if the invited party does not attend, while others may impose different conditions.
That is why WIR procedures should always be read together with the project's ITP, quality plan and contract.
Neither “hold point” nor “witness point” should be interpreted solely from generic online definitions when the contract establishes specific obligations.
Consider a contractor preparing to pour a reinforced concrete slab.
The activity could be described as:
Reinforcement and embedded-item inspection — Ground Floor Slab, Zone A
The WIR might reference the current approved structural drawing, relevant Method Statement, applicable ITP, material approvals and reinforcement checklist.
Before submitting the inspection request, the contractor's team may check items such as bar size, spacing, cover, laps or anchorage where applicable, openings, embedded items, MEP sleeves, levels, cleanliness and interfaces with other work.
The actual acceptance criteria should come from the approved drawings, specifications and relevant technical requirements. Generic values for reinforcement cover, spacing or lap lengths should not be copied from another project.
Once the internal check is complete:
WIR submitted → Authorised inspection completed → Comments/status recorded → Concrete released if project requirements are satisfied
If the inspection identifies unacceptable work, the issue is corrected and the activity is reinspected according to the approved project procedure.
A rejected WIR can result from technical non-conformance, poor preparation or incomplete documentation.
Common reasons include:
A rejected WIR does not necessarily mean that the entire construction activity is defective.
For example, an inspection request may be rejected because supporting documentation is incomplete even though the physical installation itself is acceptable. Conversely, the documentation may be complete while the workmanship fails to meet the specified requirement.
The reason for rejection should therefore be clearly recorded.
Many contractors use status codes to make WIR tracking easier, but there is no universal coding system.
These descriptions are illustrative only.
The project's contract, quality plan and document-control procedures determine what each status actually allows the contractor to do. Teams should never proceed with dependent work simply because a generic online template labels a particular status as “approved.”
Projects with frequent inspections should maintain a reliable WIR register rather than relying on individual emails or forms.
A register may contain:
A structured register helps project teams see which inspection requests are still open, which areas require reinspection and whether rejected submissions are accumulating.
It also supports traceability during handover because project teams can locate historical inspections alongside the relevant activity, drawings and supporting evidence.
Document control should support this traceability without replacing the technical inspection process itself.
A rejected WIR and a Non-Conformance Report are related, but they are not automatically the same record.
A WIR can be rejected because the submission is incomplete, the work is not ready, required references are missing or the inspection was requested against the wrong area.
Those issues may not necessarily establish that the construction work itself fails a technical requirement.
An NCR generally addresses work, material or another output that does not conform to an applicable requirement and needs to be controlled through the project's non-conformance procedure.
If an inspection identifies actual non-conforming work, the project procedure may require an NCR in addition to the rejected WIR.
HAL's Quality Assurance vs Quality Control in Construction guide covers the wider role of inspection, verification and non-conformance control within construction quality management.
✓ Work is complete to the required inspection stage
✓ Site/internal inspection has been completed
✓ QA/QC check has been completed where required
✓ Current approved drawing has been verified
✓ Relevant specification reference has been checked
✓ Approved Method Statement is referenced
✓ Correct ITP inspection point has been identified
✓ Required inspection checklist is complete
✓ Relevant material approvals are available
✓ Required tests or certificates are available
✓ Inspection location is described precisely
✓ Interfaces with other trades have been checked
✓ Area is accessible for inspection
✓ Previous inspection comments have been closed where required
✓ Supporting photographs are included where required
✓ Inspection date and time are clearly stated
✓ Internal signatures or approvals are complete
The checklist should reflect the project's approved quality process. Not every inspection requires the same attachments or internal sign-offs.
WIR processes can become difficult to manage when forms, drawings, comments, photographs and status updates are spread across email, spreadsheets and separate project folders.
A digital workflow can help teams keep the inspection request closer to its project, location, drawing references, supporting files and inspection history. The benefit is primarily better organisation and traceability rather than automatic quality control.
HAL Construction currently centralises construction information across project timelines, progress, budgets, resources, materials, blueprints and project documents.
HAL Document Manager also provides central document storage, module-based organisation, search, document history and user attribution. These capabilities can support the wider information environment around inspection documentation.
They should not be interpreted as automated WIR approval or inspection functionality. The project still requires competent inspectors, applicable acceptance criteria, appropriate QA/QC procedures and contractual approvals.
A Work Inspection Request creates a formal quality-control step between completing a defined stage of construction and moving on to work that depends on it.
The practical sequence is:
Complete → Internally check → Request inspection → Inspect → Record outcome → Release or correct
When WIRs contain precise locations, current technical references and appropriate supporting evidence, they make inspection easier to manage and leave a clearer quality record for the project.
HAL Construction can help contractors centralise project information, documents, progress and wider operational workflows. To explore how HAL could fit into your construction-management environment, book a demo.
WIR commonly means Work Inspection Request. It is used to notify the authorised inspector that a defined construction activity has reached the stage at which the required inspection can take place.
The contractor normally raises the WIR through the person or function defined in the project procedure. This may involve the site engineer, QA/QC engineer, document-control team or another authorised representative.
The inspection decision may be made by the consultant, engineer, client representative or another authorised inspector. The contract and project quality procedure determine who has approval authority.
Typical supporting documents can include the relevant drawing, ITP, Method Statement, inspection checklist, material approvals, test results and photographs. Requirements vary according to the activity and project.
The ITP establishes what needs to be inspected or tested and at which stage. The WIR is raised when the specific work reaches one of those required inspection points.
A WIR normally requests inspection of construction work. A Material Inspection Request, or MIR, normally relates to verifying materials intended for use on the project.
Not automatically. Whether the contractor may proceed depends on the inspection point, reason for rejection, ITP, contract and approved project procedures. Work at a hold point, for example, may require formal release before the next activity begins.
