Study guide

14.1 Quantitative Report Content Requirements

Certified Infrared Thermographer Level II Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 About the Level II Exam 1.2 Level I vs Level II Scope and Prerequisites

2 Chapter 2: Thermometry Fundamentals

2.1 Temperature Scales and Conversions 2.2 Contact vs Non-Contact Thermometers 2.3 Identifying and Reducing Measurement Errors

3 Chapter 3: Thermal Science and Heat Transfer

3.1 Thermal Science: Temperature, Energy Units, and Heat Capacity 3.2 Heat Transfer Modes and Conduction Variables

4 Chapter 4: Advanced Infrared Theory

4.1 Radiant Power and Stefan-Boltzmann Law 4.2 Planck's Curves and Wien's Displacement Law 4.3 Real Surfaces: Emissivity, Reflectivity, Transmissivity

5 Chapter 5: Emissivity Correction Methods

5.1 Why Emissivity Correction Matters at Level II 5.2 Reference Emitter, Tape, and Paint Methods 5.3 Reflected Apparent Temperature (RAT) Methods 5.4 Emissivity Tables: Metals and Non-Metals

6 Chapter 6: Camera Parameters and Measurement Setup

6.1 The Five Required Camera Parameters 6.2 Atmospheric Temperature, RH, and Distance 6.3 IR Window Transmittance Corrections 6.4 Target Size, IFOV, and Distance-to-Spot Ratio 6.5 Detectors, Optics, and Imager Specifications

7 Chapter 7: Calibration and Advanced Error Sources

7.1 Equipment Calibration and Accuracy Specs 7.2 Cross-Verification with Contact Thermometers 7.3 Filters, Windows, and Spectral Considerations

8 Chapter 8: Severity Classification Standards

8.1 NETA ATS Table 100.18 and Repair-Priority Conventions 8.2 Absolute Temperature Limits (ANSI/IEEE/NEMA) 8.3 ISO 18434 and Machinery Severity Criteria 8.4 Building Envelope Criteria (ASTM C1060 / ISO 6781) 8.5 Load and Ambient Correction of Absolute Limits

9 Chapter 9: Electrical Pattern Analysis

9.1 Three-Phase Electrical Fault Patterns 9.2 Transformer and Switchgear Thermography 9.3 Capacitor, Bus, and Connection Anomalies 9.4 High-Voltage Inspection Conditions and Load Requirements

10 Chapter 10: Mechanical and Steam System Analysis

10.1 Bearing and Rotating Equipment Signatures 10.2 Steam Trap and Steam System Inspection 10.3 Mechanical Drive and Alignment Indicators

11 Chapter 11: Building Envelope Analysis

11.1 Insulation Defects and Thermal Bridging 11.2 Air Infiltration and Blower-Door IR 11.3 Moisture Signatures and Flat Roof Protocols 11.4 Inspection Conditions: ΔT, Wind, and Timing

12 Chapter 12: Trending and Baseline Comparison

12.1 Establishing Baselines and Documentation 12.2 Rate-of-Change and Multi-Inspection Trending 12.3 Escalation Criteria from Trend Data

13 Chapter 13: QA/QC of Level I Work

13.1 Parameter Verification and Coverage Review 13.2 Equipment Identification and Finding Reclassification 13.3 Supervisory Sign-Off Responsibilities

14 Chapter 14: Reporting Standards and Professional Ethics

14.1 Quantitative Report Content Requirements 14.2 Paired Image Documentation and Presentation 14.3 Professional Ethics and Client Communication 14.4 Image Processing and Report Generation Software

14.1 Quantitative Report Content Requirements

Key Takeaways Explain This Topic AI

A Level II quantitative report must identify client/site, equipment IDs, date/time, load and environmental conditions, camera model/serial, and the full radiometric parameter set (ε, RAT, atmosphere, RH, distance, and window τ when used)

Measured temperatures, ΔT versus a defined reference, severity/priority, and actionable recommendations are required decision fields—not optional narrative color

Level II quantitative reports support temperature-based severity; Level I qualitative reports emphasize pattern recognition and may omit fully defended absolute temperatures

Missing load, wrong identity, or undocumented parameters make Priority numbers non-defensible even if the image looks dramatic

Report templates should force completeness: every finding row ties image evidence to parameters, conditions, and recommended action with owner and urgency

Last updated: August 2026

A thermogram without a complete report is only a picture. Level II certification expects you to produce quantitative reports : documents in which temperatures, deltas, priorities, and recommendations can be audited against known conditions and camera settings. This section lists the required content fields , explains why each field exists, and draws a bright line between Level II quantitative deliverables and Level I qualitative work.

Why Report Completeness Is a Safety Control

Severity systems in Chapter 8 (NETA-style ΔT bands, absolute OEM/ANSI limits, ISO machinery zones, ASHRAE envelope criteria) are only as good as the metadata that justifies them . A Priority 1 on a lug with no equipment ID, no load, and default emissivity cannot be executed safely by operations. Courts, insurers, and internal reliability reviews treat the signed report as the organization’s thermal condition statement—the same seriousness as Chapter 13 sign-off.

  • Incomplete field Typical failure mode
  • No equipment ID Crew opens wrong cubicle
  • No load / % rated Electrical ΔT mis-ranked
  • No ε / RAT Apparent T wrong by tens of °C
  • No date/time Cannot trend or prove conditions
  • No camera serial Calibration/traceability gap
  • No recommendation Finding becomes shelfware
  • Minimum Header Block: Who, Where, When, With What

Every quantitative report needs a stable header (cover or first page) that answers basic provenance questions before any finding table appears.

Field What to record Why Level II needs it

Client / site Legal entity, plant or building name, address or site code Ownership, confidentiality boundary, return access

Work order / scope PO, survey ID, promised route (e.g., “all 480 V MCCs Building B”) Completeness vs limited-scope honesty

  • Date and time Local date; start/end or per-image timestamps Load state, solar/ambient correlation, trending
  • Thermographer Name, cert level, company Accountability
  • Reviewer (if any) Level II QA signature when Level I collected Chapter 13 trail
  • Camera model and serial Exact instrument ID Calibration certificate linkage
  • Lens / FOV (when relevant) e.g., 24°, 45°, close-up Spot-size / IFOV defensibility
  • Software Analysis package and version Reproducibility of ΔT tools

Exam mindset: “FLIR camera” is not a model/serial. Quantitative reports name the specific instrument used for the numbers people will act on.

Conditions Block: Load, Process, and Environment

Quantitative severity is condition-dependent. Electrical contractor-convention priorities in this guide assume meaningful load (about ≥40% of rated where applicable). Mechanical and building surveys need analogous condition notes.

Domain Condition fields to capture

Electrical Amps or % rated per circuit or phase where findings exist; system voltage class; whether equipment was energized and normal process load

  • Mechanical Running vs idle; RPM/load if available; time since start for warm-up fairness
  • Steam Line pressure/status; trap duty; ambient

Building envelope Interior vs exterior air temperatures; wind; precipitation; solar exposure; time relative to sunset for roofs

General Indoor/outdoor ambient air temperature; notable weather; access limits

If conditions are inadequate for standard priorities (low electrical load, envelope ΔT too small, roof surveyed in wind > site limit), the report must qualify findings or schedule re-inspection—not invent a full Priority map.

Radiometric Parameter Block (Per Survey or Per Image)

Level II reports must state the five core camera parameters plus window transmittance when an IR window is in the optical path:

  • Parameter Symbol / note Report expectation
  • Emissivity ε Value used; surface basis (paint, oxide, tape)
  • Reflected apparent temperature RAT / T_refl Value and method (foil/reflector, assumed ambient)
  • Atmospheric temperature T_atm Path air temperature used in camera
  • Relative humidity RH % used in camera
  • Object distance d Camera-to-target distance
  • Window transmittance τ When viewing through IR window; model/age if known

Best practice is to record parameters in the radiometric file and echo them in the finding table or appendix so a PDF-only reader still sees them. Global defaults (“ε = 0.95 everywhere”) are acceptable only when surfaces truly match; mixed metal/paint routes need per-target or per-class documentation.

  • Surface class (teaching ranges) Typical ε handling in report
  • Paint, plastic, rubber, water Often 0.85–0.98; state value
  • Oxidized metals Mid-range; justify or use tape
  • Bright/polished metals Low ε; require tape/paint method notes
  • Finding-Level Quantitative Fields

For each anomaly (and, for high-value routes, for key normals used as baselines), capture:

  • Field Content
  • Equipment ID Tag matching nameplate / CMMS / one-line
  • Location description Building, lineup, elevation, phase
  • Image references IR file ID + paired visual ID
  • Measured temperature(s) Spot, area max/avg as used; units °C or °F consistently
  • Reference temperature Sister phase, similar component, baseline, ambient— define which
  • ΔT Measured − reference, with same units
  • Severity / priority e.g., P1–P4 per site map; or ISO zone; or absolute-limit flag
  • Confidence / limits Window, load, access, qualitative-only flags
  • Recommendation Action, urgency, owner suggestion
  • Follow-up Re-inspect date, outage need, trending link
  • Priority map (recall)

Experience-Based criteria, Infraspection Standard §10.1 — relative ΔT versus a similar component under similar load, P1 most severe:

  • Priority ΔT band Action gist
  • P4 1–10 °C Monitor / next inspection
  • P3 >10–20 °C Schedule repair at next outage
  • P2 >20–40 °C Repair soon
  • P1 >40 °C Immediate action / consider de-energize per procedures

Absolute OEM or code limits can override a mild relative band. Building and machinery findings use their own criteria (Chapters 8, 9, 10) but still need the same identity, condition, and parameter package.

Recommendations: Closing the Loop

A quantitative report that stops at “hot” fails the purpose of inspection. Recommendations should be specific, prioritized, and feasible :

What to do (torque, replace, clean, rebalance, reseal, re-insulate, re-inspect under load).

How urgent (aligned to Priority / absolute risk—not vague “ASAP” for everything).

What to verify after repair (post-repair IR, contact check, load test).

What remains open (locked rooms, low load, weather-limited envelope).

Weak recommendation Stronger Level II recommendation

“Check connection” “De-energize per LOTO; inspect and re-torque A-phase lug on MCC-3-B4; re-image at ≥40% load within 7 days”

  • “Monitor” “P4: include in next quarterly route; alarm if ΔT exceeds 10 °C vs sister phase”
  • “Fix insulation” “Seal air gap at north parapet flashing; re-survey after ≥10 °C indoor–outdoor ΔT”
  • Level II Quantitative vs Level I Qualitative Reports

Both levels produce valuable work, but the claim strength differs.

Aspect Level I (often qualitative / pattern-focused) Level II quantitative

Primary product Thermal patterns, comparative hot/cold, routing exceptions Defended temperatures, ΔT, priority numbers

Parameters May use defaults; less rigorous documentation ε, RAT, atm, RH, distance, τ documented and justified

Severity Qualitative language (“warmer than siblings”) or supervised Priority Priority/absolute calls tied to conditions and math

  • Load / conditions Sometimes omitted Required for electrical severity claims
  • Camera traceability Helpful Expected (model/serial)
  • Audience use Screening, training routes, flagging Work orders, outage planning, liability-grade records
  • Level II role Collect or draft under supervision Author quantitative package and/or QA Level I drafts

Honest hybrid: A Level I may capture excellent images that a Level II promotes to quantitative status only after parameters, load, identity, and severity are verified (Chapter 13). Conversely, Level II may intentionally issue a qualitative-only statement when geometry, windows, or access prevent trustworthy radiometry— label it qualitative rather than inventing fake precision.

Report Structure That Survives Audit

A practical Level II template order:

  • Cover / header — client, site, dates, personnel, camera serials, scope statement
  • Executive summary — count of findings by Priority; top P1/P2 actions; major limitations
  • Methodology — standards referenced (NETA-style bands, ISO, ASHRAE as used), load policy, parameter policy
  • Findings table — one row per anomaly with all quantitative fields
  • Image appendix — paired IR + visual (Section 14.2)
  • Open items / limited scope — incomplete coverage, low load, weather
  • Signatures — author and Level II reviewer when applicable
  • Worked Completeness Checks

Scenario A — Missing load. Finding table shows 28 °C ΔT, Priority 2, no amps. Level II either obtains load from operations logs for that timestamp or withdraws standard Priority language until re-inspected ≥40% load.

Scenario B — Full quantitative row. Client ACME Plant 3; MCC-2 Bucket 7 A-phase; 2026-08-12 14:22; 62% FLA; camera model X serial Y; ε = 0.95 on painted lug, RAT 24 °C foil method, T_atm 23 °C, RH 45%, d = 1.5 m; T_meas 71 °C, sister phase 48 °C, ΔT 23 °C → P2 ; recommend planned outage repair within 24–72 h per site policy; re-IR after torque.

Scenario C — Qualitative honesty. HV yard through unknown aged window, τ unknown, no safe tape access. Report: pattern shows A-phase bushing warmer than B/C; qualitative only ; schedule outage for contact/window-corrected quantitative pass.

Common Traps

  • Trap Correct practice
  • Pretty PDF with orphan images and no table Every finding has a data row
  • Priority without ΔT definition State reference (peer, baseline, ambient)
  • Mixing °C and °F in one table One unit system throughout
  • Claiming Level II quantitative with Level I defaults unreviewed Verify parameters first
  • “All equipment normal” with no conditions or coverage proof State scope, load, and evidence basis
  • Recommendations that ignore Priority Align urgency language to severity
  • Summary for Recall

Level II quantitative reports bind identity, time, conditions, camera, radiometric parameters, temperatures, ΔT, severity, and recommendations into one auditable package. Client and equipment IDs prevent wrong-target work; load and environment make electrical and envelope priorities valid; ε/RAT/atm/RH/distance/τ make numbers real; Priority and recommendations turn data into maintenance. Level I qualitative reports may flag patterns without full radiometric defense; Level II either completes that defense or explicitly limits the claim. Incomplete fields are not cosmetic gaps—they are reasons to qualify, re-inspect, or refuse a full clean bill of health.