Inspector workflow
WDIIR photo documentation: a field-to-office checklist
A useful inspection photo needs context: which property, where it was taken, and what observation it supports. Keep that context with the original image through office handoff and inspector review.
A close-up can show a detail while losing the location that makes it useful. A wide shot can show the location while hiding the detail. For an Arizona WDIIR team, a practical photo workflow connects the two and keeps the inspector’s observation separate from an unconfirmed interpretation.
This checklist is an example of record organization, not an inspection method or a finding about any property. It is intended for discussions between the inspector, the qualifying party, and the office—not as a replacement for professional training.
Are photos required with an Arizona WDIIR?
PMD’s Guidance for Completing the WDIIR Form recommends photographs as useful supporting material but does not describe them as a PMD requirement. It also says additional pages attached to the report are addendums and must be noted in section 10 of page 1.
That distinction matters: taking an image for the company’s supporting records and attaching it to a delivered report are different actions. Decide which material belongs in the report during the inspector’s review, using current guidance and the business’s procedures. Do not assume a folder of photographs automatically constitutes a complete inspection report.
Start with the property and location
Before organizing images, decide how the team will refer to the job. Use a stable job reference already understood by the inspector and office. Keep it connected to the physical property address and inspection date.
Within that job, use location names that another person can follow. “Garage, west interior wall beside the pedestrian door” is easier to interpret than “back corner.” If the report diagram uses a reference label, include that label in the observation record too.
A location note should identify what the inspector actually knows. If a direction has not been confirmed, a stable landmark may be more useful than a guessed compass direction. The aim is consistent communication, not a more elaborate naming scheme.
Pair context with detail
Our suggested pattern is a context image and, when useful, a separate detail image:
| Image | Purpose | Caption prompt |
|---|---|---|
| Context | Locate the observation within the inspected area | Which wall, room, elevation, or feature is shown? |
| Detail | Show the visible feature more clearly | What visible detail is the inspector documenting? |
| Access condition, when relevant | Record the obstruction or limitation | What restricted the available view? |
These are documentation prompts, not instructions to enter an unsafe or inaccessible area. Work within the scope, access, and safety procedures of the inspection. A photograph of an obstruction does not reveal what is behind it.
Avoid replacing a missing context image with a confident guess later. If a location is unclear during review, mark it for the inspector to resolve while the visit is still fresh.
Keep observations distinct from conclusions
An observation note and a finding do different jobs. The first identifies what the image is meant to document. The inspector’s finding reflects their professional assessment in the report.
Illustrative documentation example:
Job AZ-1042 · Garage · West interior wall beside pedestrian door · Diagram reference A. Context image 004; detail image 005. Inspector to confirm final report wording during review.
This example intentionally does not diagnose an insect, prescribe treatment, or invent a finding. A team can add the inspector’s actual observation and reviewed wording within its own process.
If an office coordinator needs clarification, the question should travel back to the inspector. PMD’s WDIIR guidance assigns the report’s writing and notations to the person who completed the inspection. Improving file organization should not quietly turn into rewriting that person’s conclusions.
Preserve the original image
Retain an original copy when creating a crop, arrow, or annotated version for review. Use the derivative to help a reader find a detail, while keeping the unmarked image available for context.
This is our record-management recommendation, not a claim that Arizona prescribes a specific photo file format. A simple naming pattern can make the distinction clear:
AZ-1042_A_004_original.jpgAZ-1042_A_004_annotated.jpgAZ-1042_A_005_original.jpg
A filename alone cannot guarantee that an image belongs to the right job. Use the record’s location note, inspection date, and original image together. Avoid treating file order or a phone’s image number as the only connection to the report.
Do not add visual details that were not captured, remove evidence to make a picture cleaner, or use a generated illustration as inspection evidence. If an image needs explanation, make the explanation explicit in a caption or a separate marked copy.
Check the handoff before report review
The following list is intended to help a small team review its own workflow:
- Correct job: Do the folder and observation record identify the same property and inspection?
- Useful location: Can the inspector connect each selected image to a named place or diagram reference?
- Original retained: If an image is marked or cropped, is its original still available?
- Uncertainty visible: Are unresolved location or caption questions marked for the inspector?
- Attachment decision: Has the inspector decided which images, if any, belong in the report package?
- Consistent version: Does the package being prepared for delivery contain the reviewed material?
- Accessible office copy: Can the authorized office team locate the intended record without relying on someone’s personal phone?
Try the checklist on a synthetic training example before changing a production workflow. Ask a colleague who did not visit the property to explain which image belongs to which observation. Any hesitation can reveal a naming or handoff problem worth fixing.
Photos support the report; they do not expand its scope
A well-organized image set can still leave important limitations. It does not show concealed conditions, settle a structural question, or establish what happened after the inspection. Arizona’s WDIIR statute addresses visible and accessible conditions at the time of inspection; photo organization should not imply broader certainty.
For report readers, our Arizona WDIIR guide explains those boundaries. For teams arranging their administrative steps, WDIIR vs. TARF in Arizona separates the inspection record from state filing. Homeowners getting ready for a visit can use the inspection preparation guide.
Sources and editorial scope
Sources checked September 13, 2026:
- Arizona PMD: Guidance for Completing the WDIIR Form — guidance dated October 3, 2024; recommendations on photographs, attached material, and report authorship.
- Arizona Legislature: A.R.S. § 3-3633 — report scope and responsibilities.
The image pairs, filenames, captions, and handoff checklist are TermiteReport.io’s original educational examples. This article was prepared with AI-assisted research and drafting and has not been reviewed by a licensed pest professional. See our editorial approach. TermiteReport.io is developing reporting software; the workflow described here is not a claim of currently available product features.