Use of third-party professionals for specialized reviews and inspections, contractor oversight, quality assurance, and liability implications. Covers qualification standards and peer review procedures.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
This course covers material relevant to the following ICC certification exams:
Use of third-party professionals for specialized reviews and inspections, contractor oversight, quality assurance, and liability implications. Covers qualification standards and peer review procedures.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamEstablish criteria for third-party reviewer and inspector qualifications
Building departments turn to third-party plan reviewers and inspectors for reasons that are almost always structural rather than a lack of confidence in staff. A sudden surge in permit volume — a commercial boom, a wave of rebuilding after a storm, or a single large project that dwarfs the department's normal caseload — can overwhelm in-house reviewers faster than a jurisdiction can hire and train new staff. Complex or unusual work, such as a high-rise structural system, an unfamiliar occupancy type, or a specialized fire-protection design, may call for expertise that simply is not on staff full time; it is rarely cost-effective to keep a structural engineer with high-rise experience on the payroll for the occasional project that needs one. Smaller and rural jurisdictions face a related problem: they may never have the budget or applicant volume to justify a full multi-discipline in-house staff, so contracting out certain disciplines is the only realistic way to offer complete service. Backlog and turnaround pressure is its own driver — applicants and elected officials both notice when review times stretch out, and a temporary third-party contract can restore acceptable turnaround without a permanent staffing commitment. Disaster and emergency surge is a sharper version of the same problem: after a major event, permit volume for repairs and reconstruction can spike well beyond anything the department normally handles, and jurisdictions that have already built an emergency-permitting response frequently work a pre-qualified roster of third-party providers into that plan so it can be activated quickly rather than assembled from scratch under pressure.
Third-party arrangements take several distinct forms, and part of establishing criteria is deciding which fits the situation at hand. Third-party plan review addresses the design — drawings, specifications, calculations — before construction begins; third-party or special inspection addresses the work in the field, verifying that construction matches the approved plans, even though the same firm sometimes performs both. Programs can be fully outsourced, where the third party becomes the review or inspection function for an entire category of work, or supplemental, covering only overflow or a narrow specialty while in-house staff handles everything else. A further distinction that matters for oversight is who selects and pays the provider: an owner-retained third party is hired directly by the project's owner or design team — the standard arrangement for special inspection, where the code places that engagement responsibility on the owner — while a jurisdiction-retained third party is selected and managed by the building department itself, usually from a pre-qualified roster. The two arrangements carry different conflict-of-interest exposures, discussed below.
Whatever form the arrangement takes, the criteria for who may serve as a third-party reviewer or inspector should mirror, not fall below, what the department expects of its own staff. Professional licensure demonstrates design competence, not necessarily code-compliance review competence, which is a distinct skill built through review experience and, ideally, relevant ICC certification. Accreditation of the firm itself matters as much as certification of the individual: agencies performing special inspection or fabrication inspection are increasingly expected to hold third-party accreditation confirming they operate under a documented quality-management system, not simply that their inspectors carry certifications — the same underlying "approved agency" concept the code uses for testing laboratories, inspection agencies, and product-evaluation bodies such as ICC Evaluation Service. Conflict-of-interest screening belongs at this same qualification stage: a firm should never be approved to review or inspect its own design work, and the department's written criteria should say so explicitly rather than leaving the problem to surface after the fact.
A fast-growing county building department watches its plan review backlog stretch from weeks to months as a residential boom follows a wave of commercial construction, and the budget will not support hiring enough reviewers to close the gap. Rather than simply approving more overtime, the building official proposes a structured peer-review program: qualified, licensed engineers and architects are trained and certified by the department in specific disciplines, then permitted to review and revise applicants' plans directly, with the department stepping back in to run an expedited final check. Documented programs built this way have cut effective review time by roughly half while allowing staffing to hold steady, because the trade-off shifts cost from the department's budget to the applicants who choose the faster path. Making it work took more than announcing it: the department built an explicit certification track for peer reviewers, published a current list of who was qualified, and kept monitoring their work on an ongoing basis rather than certifying reviewers once and walking away.
Common mistakes include assuming any state-licensed architect or engineer is automatically qualified for code-compliance plan review, when licensure and review competency are distinct skills; approving a firm without screening for conflicts of interest, only to discover later it designed the very project it was assigned to review; treating individual certification as sufficient without confirming firm-level accreditation; and setting up a program with no plan for ongoing monitoring, so qualifications approved at the outset are never reverified. The correction is to write qualification criteria down before the first provider is approved and apply that same standard to every applicant rather than negotiating case by case.
Code Reference: IBC 107 - The code establishes minimum requirements for establish criteria for third-party reviewer to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Manage quality assurance and liability in third-party programs
The single principle that governs everything else in a third-party program is that a building department can contract out the work of plan review or inspection, but it cannot contract away its responsibility for the outcome. The third party examines the drawings or fieldwork and makes a recommendation; the building official, or a designated plans examiner or inspector of record, makes the actual approval decision and remains accountable for it. This is not a formality: when a third-party reviewer misses a deficiency that later surfaces during construction or after occupancy, the department cannot point to the contract as a complete defense, because the authority to approve plans and issue permits was never the third party's to exercise — it was only ever delegated as a recommendation. Programs that treat a third-party stamp as automatically final, with no department-level check behind it, misunderstand this relationship and create real liability exposure for the jurisdiction.
Because the department's name is on the outcome either way, managing quality means holding third-party work to the same standard the department holds its own staff to — starting with which code actually governs. A third-party reviewer who works across multiple jurisdictions may default to whatever interpretation is standard practice at their own firm rather than the specific edition and locally adopted amendments in force where the project sits, a distinction covered in depth in the course on understanding adopted codes and amendments. Left unchecked, that habit produces reviews that are internally consistent but wrong for the jurisdiction doing the approving. The fix is procedural: give every provider the current adopted code and amendment package, then periodically audit a sample of their reviews against that standard — the same way a peer-review program keeps monitoring certified reviewers rather than certifying them once and stepping away.
Consistency also depends on how the arrangement is structured commercially. In most third-party plan review programs the applicant, not the jurisdiction, pays the provider's fee directly, in exchange for a faster review than the standard queue; the department's own fee schedule still applies for whatever oversight it performs. Fee structures are usually set by the market or the provider rather than the jurisdiction, part of the trade-off applicants accept for speed. Whatever the arrangement, the agreement should spell out service-level expectations — turnaround time, report format, and the standard the reviewer must apply — in writing. None of this is optional paperwork: an agreement without quality-assurance and audit provisions leaves the department no mechanism to catch substandard work until a problem surfaces in the field, by which point the cost has already shifted to the construction site.
A commercial applicant submits plans reviewed and stamped by a third-party firm the department has used successfully for two years. During a routine audit of a sample of that firm's recent reviews — a practice adopted specifically to catch drift before it becomes a pattern — a plans examiner notices the firm has been applying an interpretation of a fire-rated assembly requirement the department retired when it adopted its current amendment package, apparently because the reviewer also works in a neighboring jurisdiction that never made the change. Three recent reviews carried the same outdated interpretation. The building official flags the pattern with the firm, provides the current amendment package again in writing, and adds the firm's next several submittals to a closer review cycle rather than assuming a single conversation fixed the habit.
Common mistakes include treating a third-party stamp as the end of the department's involvement rather than a recommendation to be checked; allowing in-house and third-party reviewers to apply visibly different interpretations of the same code section, so applicants get different answers depending on who reviews their project; signing an agreement that never mentions quality assurance or audit rights; and assuming a fee arrangement that shifts cost to the applicant also shifts liability away from the department, which it does not. The correction is to build audit and consistency checks into the program from the start, comparing third-party interpretations against the department's own standard.
Code Reference: IBC 107 - The code establishes minimum requirements for manage quality assurance to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Maintain building department oversight and final approval authority
Every plan review comment, inspection report, and approval a third-party provider produces becomes part of the jurisdiction's own project file the moment it is submitted, not a separate record the provider keeps privately. That has two consequences. First, the department needs the same retention and retrieval discipline for third-party records that it applies to staff-produced work — the subject of the course on records management and document retention — because nobody pulling a project file for a later dispute will care whether a given inspection was performed by staff or a contracted provider. Second, because those records carry the department's name and support its approval, the department's liability exposure travels with them; a poorly documented third-party report is just as much a liability problem as a poorly documented staff report.
Independence is a recurring tension in third-party programs, showing up most sharply in special inspection, where the code places responsibility for engaging the special inspection agency on the project owner rather than the jurisdiction. That arrangement puts the inspector in an uncomfortable position: the entity paying the bill is also the entity whose work is being inspected, precisely the dynamic conflict-of-interest screening exists to manage. The mechanism the industry uses to handle this is the statement of special inspections, prepared before construction begins, spelling out exactly which special inspections and tests the project requires, who is qualified to perform them, and how findings get reported. Because that document is submitted to and accepted by the jurisdiction, the building official — not the owner or the inspection agency alone — retains final say over what gets inspected and to what standard, even though the owner pays the inspector's invoice.
Departments that lean heavily on third-party programs over a long period face a subtler risk than any single missed deficiency: the erosion of institutional knowledge. If enough work moves outside the department for long enough, in-house staff can lose the hands-on familiarity with complex projects needed to evaluate a third-party recommendation critically rather than simply accepting it. A department that can no longer independently judge whether a third-party review was sound has, in practice, given away authority it was never supposed to give away, even if the org chart says otherwise. Guarding against that means keeping enough in-house activity, on a rotating basis if necessary, that staff retain the judgment needed to catch what a third party gets wrong.
A hospital addition is one of the most complex projects the department has seen in years, and the building official contracts with a structural engineering firm to perform third-party plan review of the lateral force-resisting system, an area outside the in-house reviewers' depth. The firm's review comes back thorough and professionally prepared, and on a routine project the building official would likely be inclined to approve based on it directly. But because the department's practice is to have a senior plans examiner read every third-party review against the plans before signing off, rather than accepting the recommendation on its face, the examiner notices the firm applied wind-load provisions from an edition of the code it evidently used on a recent out-of-state project, one cycle behind what this jurisdiction adopted. The building official holds the approval, sends the discrepancy back to the firm with the correct adopted edition, and requires a revised review before the project moves forward. The episode does not reflect badly on bringing in a third-party reviewer for a project this complex; it reflects why the department kept its own final review step rather than treating the recommendation as the last word.
Common mistakes include losing track of which records — third-party or in-house — govern a project because retention practices were never made consistent; assuming that because a special inspector is paid by the owner, the department has no role in overseeing what gets inspected; leaning on third-party providers so heavily that in-house staff eventually cannot evaluate that work independently; and skipping the department's own final review step because a report looks complete. The correction is to fold third-party output into the department's normal records system, treat the statement of special inspections as a real checkpoint, rotate complex work through in-house staff, and require a department-level check on every recommendation before it becomes an approval — the habit that caught the wrong code edition above.
Code Reference: IBC 107 - The code establishes minimum requirements for maintain building department oversight to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
This course examines third-party plan review and inspection programs: why departments use them (workload surges, expertise gaps, small-jurisdiction staffing limits, backlog pressure, and disaster surge), the program models (plan review versus special inspection, fully outsourced versus supplemental, owner-retained versus jurisdiction-retained), and the qualification, quality-assurance, and oversight practices that make the arrangement work safely. The thread through all three modules is the same: a department can contract out the work, but authority and responsibility for the final approval stay with the building official. Sound programs screen providers for competency and conflicts of interest before approval, hold third-party work to the jurisdiction's own adopted code and amendments, audit consistency on an ongoing basis, treat third-party records as the department's own, and keep a genuine department-level check between a recommendation and a final approval.