Test Square Hail Inspection Checklist For Roofing Crews

A test square is a way to make hail inspection documentation more consistent. It is not an automatic roof replacement decision, an insurance approval, or proof that every mark on a roof came from hail. A good crew workflow is: confirm safety, capture weather context, choose representative test areas, photograph the roof and square boundaries, separate possible hail impact indicators from other conditions, get supervisor review, and keep homeowner language factual.

Haag's hail inspection protocol article describes test squares as 100-square-foot roof areas, commonly 10 feet by 10 feet, and discusses representative placement by roof direction. That makes test squares useful for organized documentation. It does not turn a checklist into a legal standard, a policy interpretation, or a coverage promise.

The Nebraska Department of Insurance hail damage page cautions that an inspection can reveal other causes before assuming hail damage and notes that granule loss does not prove damage. OSHA's roof inspection, tarping, and repair guidance describes hazards tied to ladders, raised work surfaces, steep or slippery roofs, damaged roofs, tools, power lines, slips, trips, and falls. Those two boundaries should sit at the top of every test-square workflow: do not overclaim the marks, and do not put a crew on an unsafe roof.

RoofPredict can organize the workflow around those boundaries: source context, inspection assignment, safety status, test-square photo packet, condition notes, supervisor review, homeowner follow-up, and next action. RoofPredict should not be treated as an inspector, engineer, adjuster, insurer, attorney, safety authority, or compliance authority.

Pre-Access Safety Checklist

No test square matters if the roof access decision is wrong. The first checklist is not about chalk lines or photos. It is about whether the crew should access the roof at all.

Check	Record	Hold trigger
Weather status	Active warnings, lightning, wind, rain, heat, ice, or low visibility	Active dangerous conditions
Ladder setup	Access point, ground condition, ladder condition, power-line proximity	Unsafe setup or unclear approach
Roof condition	Slope, surface moisture, loose material, damaged decking, debris	Steep, wet, unstable, or damaged surface
Edge exposure	Eaves, drops, openings, transitions, and work near edges	Fall exposure without approved controls
Crew readiness	Training, equipment, communication, and site lead	Missing qualified lead or equipment
Homeowner status	Permission, appointment, pets, gates, access limits	No permission or unclear access
Stop authority	Named person who can pause the inspection	No one owns safety stop

OSHA's fall protection construction resources highlight construction fall-protection standards and training resources. For a roofing company, that means the test-square checklist should never be used as a shortcut around a job-specific safety plan. If a roof is wet, steep, damaged, unstable, near power lines, or affected by active weather, the correct answer may be no roof access.

The safety note should be stored with the inspection file. If the crew documents from the ground, drone, attic, or exterior only because the roof is unsafe, that is not a failed inspection. It is a documented safety decision. A supervisor can reschedule, send a better-equipped crew, or request a different inspection method.

Weather And Source Context

Weather context helps explain why the inspection is happening. It does not decide what the roof condition is. NOAA's NSSL hail basics page explains that hail forms inside thunderstorm updrafts and can damage homes and cars. The NWS severe thunderstorm education page explains hail and wind criteria, including hail of one inch or greater and wind of 58 mph or greater.

Record the source context in a short, neutral way:

• Storm date.
• Source type.
• Source link or saved report.
• Reported hail size or severe-weather context, if available.
• Property address.
• Inspection date.
• Inspection owner.
• Homeowner request status.

Do not write "hail proved roof damage" in the weather field. Better language is: "Hail reports and homeowner request support inspection scheduling." The weather note explains why the crew is looking. The inspection record documents what the crew actually sees.

Test Square Placement Checklist

A test square should be representative, visible, and tied to a roof direction or roof area. Haag's article describes 100-square-foot test areas and discusses direction-by-direction inspection and representative placement. Use that concept carefully: the goal is consistent documentation, not a forced result.

Placement check	What to do	Why it matters
Size	Mark a 100-square-foot area when the roof geometry allows it	Keeps the sample area consistent
Direction	Record the roof direction or slope area	Supports review by slope or exposure
Representative area	Avoid unusual obstructions when possible	Reduces distorted sample conditions
Separate conditions	Do not mix newer addition, older main roof, and unusual repairs into one sample	Different areas may have different histories
Edge and valley caution	Evaluate poorly supported or edge-adjacent materials separately	Avoids treating vulnerable areas as representative field shingles
Photo visibility	Make the square boundaries visible in photos	Helps reviewer understand location and scope
Location map	Record where the square sits on the roof diagram or photo	Makes the packet auditable

A crew should usually avoid placing the test square only where the marks are most dramatic. That can create a misleading packet. The same is true in reverse: picking the cleanest area can hide relevant conditions. Representative placement is the point.

If a roof has multiple materials, ages, slopes, or repairs, treat those areas separately. A porch addition installed last year should not be blended with a 15-year-old main slope. A metal accessory may show impact marks differently than asphalt shingles. A valley, ridge, or edge may have support and wear conditions that do not match the main roof field.

Field Sequence For The Crew Lead

The crew lead should run the test-square workflow in the same order every time. Consistency matters because a packet is easier to review when each inspection follows a known sequence.

1. Confirm the appointment, permission, and access plan.
2. Confirm weather status and stop conditions.
3. Record the property overview and roof areas that will be inspected.
4. Choose the first representative roof area and record the direction or slope.
5. Mark the test-square boundary when safe and appropriate.
6. Take a wide photo showing the square location.
7. Take boundary photos that make the sample area clear.
8. Inspect the square methodically, not by jumping from mark to mark.
9. Photograph candidate conditions with close-up and mid-range context.
10. Photograph non-hail conditions separately.
11. Record any roof area not accessed and why.
12. Submit the packet for supervisor review before homeowner-facing conclusions.

This sequence keeps the crew from starting with the most dramatic close-up. A packet that begins with close-ups can make later review harder because the reviewer has no location, slope, or boundary context. A packet that starts with property overview, access, roof area, square location, and then close-ups is easier to understand.

The crew lead should also control language during the inspection. Field notes can say "candidate mark," "granule loss area," "metal dent," "wear pattern," or "requires review." The notes should not say "approved," "bought," "covered," or "replacement" unless a qualified reviewer has authorized a very specific use of that language and the context supports it. Even then, coverage language belongs in the claim process, not in the crew's raw field notes.

Photo Packet Checklist

The photo packet should let a reviewer understand the roof, the square, the marked conditions, and the limits of the inspection. Blurry close-ups without context are not enough.

Capture these photo groups:

Photo group	Required view	Purpose
Property context	Front elevation, address marker when appropriate, roof overview	Ties packet to property
Roof overview	Each inspected slope or roof area	Shows roof geometry and condition
Access and safety	Ladder/access area if safe and appropriate to document	Records access context
Test-square location	Wide photo showing square on roof area	Places sample in context
Square boundaries	Clear photos of the marked area	Shows what was included
Candidate impacts	Close-up and mid-range photos	Shows condition and surrounding shingle field
Non-hail conditions	Wear, blistering, mechanical marks, foot traffic, repairs, or age signs	Shows separation work
Soft metals/accessories	Vents, flashing, gutters, caps, or other components when inspected safely	Adds context without replacing shingle inspection
Final roof notes	Any area not accessed and why	Prevents silent gaps

Each marked condition should have context. A close-up can show detail, but a mid-range photo shows whether the mark sits in a random pattern, near a traffic path, along a blistered field, near an installation issue, or beside older wear. The packet should help a supervisor ask better questions.

Avoid photo captions that overstate the finding. Use "candidate impact mark," "granule loss area," "metal accessory dent," "wear pattern," or "requires supervisor review" when the condition is not final. Save final conclusions for the qualified review step.

Condition Separation Table

A test square checklist should make the crew separate conditions before counting or summarizing. GAF's roof damage education supports regular roof inspection and professional help for roof damage assessment. The Nebraska insurance source adds the key caution that other causes may be present and that granule loss does not prove damage.

Condition seen	Document	Do not assume
Candidate impact mark	Location, size, close-up, mid-range view, surrounding field	That it is hail without review
Granule loss	Pattern, age, concentration, nearby shingles	That granule loss alone proves hail damage
Soft metal dent	Component type, location, size, pattern	That shingle damage exists nearby
Blistering or wear	Texture, pattern, roof age context	That it is storm damage
Mechanical mark	Traffic path, tool mark, scrape, directional pattern	That it was hail
Prior repair	Material difference, sealant, patch, age	That it came from the current storm
Manufacturing or installation issue	Repetition, location, fastening or alignment concern	That it is hail damage
Interior stain	Room, ceiling/wall location, homeowner report	That hail caused it without roof-side support

The table protects the crew and the homeowner. It invites careful documentation instead of forcing every condition into one bucket. It also makes the supervisor review more useful because the reviewer can see what was found and what was ruled out or left unresolved.

What To Record For Each Candidate Condition

Each candidate condition needs enough detail for a supervisor to understand it without standing on the roof. The crew does not need a long essay for every mark, but it does need consistent fields.

Record:

• Roof area or slope.
• Test-square identifier.
• Approximate location inside the square.
• Condition category.
• Close-up photo ID.
• Mid-range photo ID.
• Surrounding field note.
• Whether a similar condition appears outside the square.
• Whether non-hail causes are suspected.
• Whether supervisor review is required.

The "surrounding field" note is especially useful. A candidate mark surrounded by random similar marks may tell a different story than a mark along a walking path, next to an old repair, near a blistered field, or along a vulnerable edge. The goal is not to force the crew into a final diagnosis. The goal is to preserve enough context for the next reviewer.

If a condition cannot be photographed safely or clearly, say so. A missing image with an explanation is better than a blurry image with an overconfident caption. If the crew cannot access a slope because of safety concerns, document the reason and move the packet to review hold.

Supervisor Review Gate

Every test-square packet should pass a supervisor review before it becomes homeowner-facing language. The supervisor does not need to rewrite the whole file. The gate should answer a few specific questions.

Review question	Pass condition	Hold condition
Is roof access documented?	Safety status and access method are clear	No safety note
Is the source context neutral?	Weather note supports inspection scheduling only	Weather note claims damage
Is placement explained?	Square size, slope, and location are recorded	Square appears cherry-picked or unlabeled
Are photos clear?	Wide, mid-range, and close-up views are present	Only close-ups or blurry images
Are non-hail conditions separated?	Wear, blistering, mechanical marks, repairs, and age signs are noted	Everything is called hail
Is homeowner language factual?	No pressure or coverage promise	Script claims approval, replacement, or urgency
Is next action clear?	Repair estimate, reinspection, adjuster coordination, or no action is labeled as appropriate	No next owner

If the packet fails the gate, send it back for clarification or keep it internal. A weak packet should not become a sales script. A missing safety note, unlabeled square, unclear photo, or overconfident conclusion is a documentation problem that can create homeowner confusion.

Common packet failures include:

• No safety/access note.
• Square boundary visible in only one image.
• Close-up photos without slope context.
• No photo of the roof area outside the square.
• All marks labeled as hail without condition separation.
• Soft metal dents used as a substitute for shingle inspection.
• Homeowner summary written before supervisor review.
• Insurance language added to raw field notes.

Those errors are fixable when they are caught internally. They become harder to fix after the homeowner sees the packet, an adjuster receives it, or a sales rep turns the notes into a promise.

Homeowner And Insurance-Boundary Language

The homeowner conversation should describe what the crew did and what the packet contains. The FTC's weather-emergency scam guidance warns consumers to be careful after weather emergencies and repair situations. NAIC's post-storm guidance keeps insurance review in the proper lane and warns consumers about post-storm contractor fraud.

Use language like:

• "We documented representative roof areas and marked conditions for supervisor review."
• "The packet shows what we observed and what still needs review."
• "A test square helps organize documentation; it does not decide coverage."
• "Your insurer handles claim decisions under your policy."
• "If roof access is unsafe, we will document the access limit and reschedule when appropriate."

Avoid language like:

• "This square proves your roof is bought."
• "Every mark is hail."
• "The carrier has to replace it."
• "Sign today or the storm evidence will be gone."
• "We can climb it even if the roof is wet."

The safe version is less dramatic, but it is more defensible. It keeps the company in its lane: observation, documentation, safety, communication, and follow-up.

How RoofPredict Fits The Workflow

RoofPredict can act as the inspection workflow board. A manager can track:

• Storm source context.
• Inspection assignment.
• Safety status.
• Access method.
• Test-square location.
• Photo packet status.
• Condition categories.
• Supervisor review status.
• Homeowner summary status.
• Follow-up owner.
• Reinspection need.
• Estimate or documentation next step.

The value is control. If a crew uploads only close-ups, the packet can stay on review hold. If safety access was not documented, the supervisor can pause the workflow. If the homeowner asks for a copy of photos, the office can provide the reviewed packet instead of scattered field images.

RoofPredict can also separate workflow status from conclusions. "Photo packet complete" is not the same as "hail damage approved." "Supervisor review needed" is not the same as "claim denied." Clear labels help the team move fast without turning workflow notes into unsupported claims.

Source Limits

Source	Use it for	Do not use it for
Haag test-square article	100-square-foot test area context and representative placement concepts	Legal standard, claim approval, or policy interpretation
OSHA roof inspection and fall protection	Safety boundaries for roof work and access planning	Complete site-specific safety plan
NSSL and NWS hail context	Hail-weather education and severe-weather terminology	Property-specific roof diagnosis
GAF roof damage education	General roof damage signs and professional inspection framing	Independent inspection standard
Nebraska DOI hail guidance	Consumer caution and condition-separation reminders	Universal hail threshold or claim decision
FTC and NAIC	Consumer-protection and insurance-boundary context	State-specific legal advice or coverage decision
RoofPredict	Inspection workflow, photo packet status, review gates, and follow-up	Weather, inspection, legal, safety, or insurance decision

FAQ

Is a test square always 10 feet by 10 feet?

Haag describes test squares as 100-square-foot roof areas, commonly 10 feet by 10 feet. Crews should follow their qualified inspection protocol and document any geometry or access limits.

Does a test square prove hail damage?

No. It supports structured documentation. The packet still needs qualified review, condition separation, and policy or claim handling where applicable.

Should crews count every mark in the square?

No. Crews should document candidate indicators and separate wear, blistering, mechanical marks, foot traffic, installation issues, repairs, and other non-hail conditions.

When should the inspection stop?

Stop or hold when roof access is unsafe, weather is active, ladder setup is questionable, fall exposure is uncontrolled, homeowner permission is unclear, or the crew does not have the right equipment or qualified lead.

What does RoofPredict decide?

RoofPredict can organize inspection assignments, source context, photo packet status, review holds, and follow-up. Human review still owns safety, inspection judgment, consumer communication, and insurance boundaries.