13.3 Supervisory Sign-Off Responsibilities

The last gate in QA/QC of Level I work is supervisory sign-off. A signature, digital approval, or “reviewed by Level II” block is a professional act. It tells the client, the maintenance planner, and—if something fails—the investigators that a qualified person stood behind the work product. This section clarifies what you are signing, why rubber stamps destroy trust and create liability, how to coach Level I, and what review documentation must capture.

What Level II Is Actually Signing

Unless your written procedure says otherwise, a Level II sign-off on a Level I package typically affirms that, to a reasonable professional standard:

Sign-off is not usually a claim that:

• You personally aimed the camera at every asset
• You guarantee no future failures (thermography is condition snapshot + judgment)
• You authorize electrical switching or mechanical isolation without operations authority
• You certify equipment “safe for all future loads” from a light-load survey

Write the limitation language your program requires: weather, load, access, windows, and measurement uncertainty. Sign-off includes those limitations as part of the truth package.

Minimum Review Actions Before Signing

A defensible Level II review is more than scrolling thumbnails. Use a consistent intensity scaled to risk and package size, but never skip the core:

1. Sample or full-check parameters on quantitative findings (ε, RAT, atmosphere, distance, τ)
2. Coverage reconciliation against scope and asset list
3. Identity spot-checks on high-severity and a random sample of mild findings
4. Severity math checks on all P1/P2 (and a sample of P3/P4)
5. Load and ambient presence for electrical/mechanical quantitative calls
6. Exception list complete and client-visible
7. Reclassification log complete when changes were made

If time pressure prevents adequate review, do not sign. Issue a delayed review, partial acceptance, or require the field team to complete missing evidence. A rushed signature is worse than a late report.

Liability and Ethics of the Rubber Stamp

Rubber-stamping means applying Level II approval without performing a meaningful review. It is attractive when schedules slip, clients push, or Level I “usually does fine.” It is still wrong.

Why it is an ethics failure

Why it is a liability risk

After a fire, injury, or unplanned outage, the signed IR report may be exhibits A–Z. Opposing experts will ask:

• Did you verify emissivity on the failed joint’s images?
• Why does metadata show τ = 1.0 through a window?
• Why does the report say “100% complete” with half the assets missing?
• Who signed, and what does your procedure say that signature means?

If the answer is “I trusted the tech,” your organization owns the gap between claimed and actual diligence. Level II individuals can face internal discipline, lost credentials in extreme cases, civil exposure depending on jurisdiction and contracts, and lasting reputational harm. You need not memorize legal codes for the exam—you must grasp that the signature allocates responsibility.

Feedback Loop to Level I

QA without feedback only catches errors once. A mature Level II program closes the loop:

1. Specific, timely notes — “ε = 0.95 on bare Cu lugs in images 14–22; use tape method next route.”
2. Pattern tracking — Count recurring defects (missing load, weak visuals, default RAT).
3. Positive reinforcement — Call out correct window τ use and excellent peer selection.
4. Field mentoring — Joint surveys when the same mistake repeats.
5. Procedure updates — If many Level I techs miss the same step, fix the checklist/template, not only the person.
6. Escalation path — Persistent refusal to follow quantitative rules → stop assigning solo routes.

Exam framing: Level II is a supervisor of quality, not only a second calculator. Teaching Level I is part of the job description in most industrial IR programs.

Documentation of the Review

What gets written down is what you can prove. Minimum review record (paper, CMMS, or PDF appendix):

Retain radiometric originals per client/program retention rules. Do not sign a package whose raw files are lost if quantitative claims remain.

Communicating Sign-Off Status to the Client

Clients need clear status language:

Never use “Approved” as a euphemism for “we ran out of time.” Exception lists protect both parties.

Integrating 12.1–12.3 as One Workflow

Skipping step 1 or 2 while completing step 3 is the definition of a rubber stamp.

Worked Sign-Off Scenarios

Scenario A — Clean package. Parameters sampled OK, full coverage evidence, one P3 with solid peer ΔT at 60% load, IDs match visuals. Level II signs Approved, notes sample plan, mild coaching optional.

Scenario B — Fixable errors. Three window images need τ; after correction one finding upgrades P4 → P2. Level II documents reclass, coaches Level I on τ field, signs Approved with documented corrections.

Scenario C — Rubber-stamp temptation. Client wants PDF tonight; half of HV yard missing; Level I swears “it was normal.” Level II refuses full approval, issues Approved with exceptions only for completed area or Rejected — re-inspect, and records the refusal reason.

Scenario D — Chronic Level I default ε. Fifth consecutive route with 0.95 on shiny bus. Level II rejects quantitative severity on those images, schedules joint mentoring, updates pre-job checklist, and escalates to program owner if needed.

Common Traps

Summary for Recall

Level II sign-off affirms scope honesty, radiometric adequacy, identity, severity logic, evidence, and open items—not omniscience or future failure-free operation. Rubber-stamping is an ethical and liability failure because it claims diligence that never happened. Run a specific feedback loop to Level I, keep a written review record, and use status labels (Approved / with exceptions / Rejected) that match reality. Chapters 14.1–12.3 form a single gate sequence: verify parameters and coverage, fix IDs and reclassify, then sign only what you actually reviewed.