Foundation Inspection Report Template: What to Capture, Photograph, and Write Before You Leave
A foundation inspection report template only helps if it matches how inspectors actually observe structure-related clues in the field.
That is where a lot of foundation reporting gets soft. The inspector notices step cracking at the brick veneer, a sloped floor at the dining room transition, or negative grading at the rear corner. But if those notes are not captured in a clean sequence while you are still onsite, the final narrative gets vague fast. Later, you remember that something looked off. You do not always remember exactly where it was, how wide it appeared, what nearby moisture or drainage clues were present, or which photos best supported the concern.
This foundation inspection report template is built for inspectors who want to leave the property with the important structural observations already organized. The goal is not to turn a visual home inspection into engineering. The goal is to help you document visible foundation conditions, movement indicators, drainage context, limitations, and recommendation language before the details blur together.
Note
Strong foundation reporting stays grounded in visible evidence. The ASHI Standard of Practice and InterNACHI's guidance on structural systems and foundations both reinforce the same basic discipline: report observable conditions, note material limitations clearly, and avoid claiming hidden structural performance you did not verify.
What a Foundation Inspection Report Template Should Actually Do
A foundation inspection report template should do more than create a blank box for "crack noted" or "recommend engineer."
For field inspectors, it should help you do five things well:
- identify the exact area, wall, room, or corner where the condition was observed
- separate observed structural clues from contributing site conditions such as drainage or moisture
- distinguish visible distress from inspection limitations and inaccessible areas
- tie every meaningful finding to supporting context and close-up photos
- turn onsite observations into report-ready language without rebuilding the story later
That last point matters. Foundation observations rarely stand alone. A crack in the garage stem wall may line up with exterior grading concerns. Interior door binding may relate to settlement patterns, or it may not. Veneer cracking may be cosmetic, or it may be part of a larger pattern worth closer evaluation. Your foundation inspection report template should help you preserve those connections while you are still looking at them.
If your current workflow relies on trying to remember all of that at the kitchen table an hour later, pair this guide with our foundation inspection, foundation crack inspection, and home inspection narrative examples.
The Best Field Order for a Foundation Inspection Report Template
A good foundation inspection report template should follow inspection logic, not software logic.
One practical sequence is:
- inspection scope and limitations
- foundation type and general context
- exterior visible movement clues
- interior visible movement clues
- moisture and drainage observations that may affect performance
- recommendation language and next step
That order works because it mirrors how inspectors build confidence in a foundation-related finding. First, you define what was accessible. Then you describe the type of structure you are looking at. Then you document what the exterior is showing, what the interior is showing, and what surrounding moisture or drainage conditions may be relevant. Only then do you move into recommendation language.
Clients follow the story more easily when the report does the same. They get confused when one sentence references a rear exterior crack, the next jumps to a sticking bedroom door, and the next jumps again to ponding near the downspout with no visible thread connecting them.
Foundation Inspection Report Template: Core Sections to Include
Below is the structure worth repeating on every job where the foundation section matters.
1. Inspection scope and limitations
Start by documenting what you could and could not observe.
That may include:
- finished wall coverings limiting full interior view
- stored items blocking garage or basement walls
- insulation, vapor barriers, or wall finishes obscuring framing or foundation surfaces
- crawlspace access limitations
- floor coverings limiting visibility of floor distress patterns
- exterior vegetation, hardscape, or cladding concealing portions of the foundation perimeter
This section matters because foundation comments carry more weight when the client understands the limits of the observation. A careful limitation statement also helps prevent the report from sounding more definitive than the inspection actually was.
2. Foundation type and general context
Document the visible basics before jumping into defect language:
- slab-on-grade, crawlspace, basement, pier-and-beam, or mixed design where visible
- approximate age context if relevant to expected materials or common movement patterns
- general site slope and water-management context
- visible retaining features or grade transitions affecting the structure
This anchors the rest of the section. A hairline shrinkage crack in a garage slab, a step crack in masonry veneer, and lateral displacement in a basement wall are not the same story. Your template should create room to identify the system clearly before the narrative gets more specific.
3. Exterior visible movement clues
Many foundation-related concerns first show up outside, not inside.
Your foundation inspection report template should leave room to capture:
- cracks in exposed foundation walls or stem walls
- step cracking in brick or block veneer
- separation at control joints, trim, or penetrations
- sloping flatwork that channels water toward the structure
- displacement at porches, stoops, or attached walkways
- visible settlement at columns, posts, or entry steps
- drainage discharge too close to the structure
The point is not to diagnose structural failure onsite. The point is to record the observable clues precisely enough that the client, contractor, or engineer can understand what you saw and where you saw it.
4. Interior visible movement clues
The interior side of the story often gives the foundation section its context.
Common items to capture include:
- cracks at drywall corners or door headers
- floor slope or uneven transitions where observable
- doors or windows that bind or fail to latch normally
- separation between trim and wall surfaces
- basement or crawlspace wall cracking
- patched structural areas where prior movement may have been addressed
These clues should not be thrown into the report as unrelated fragments. A good foundation inspection report template helps you connect them to location. "Rear-right bedroom window binds" is more useful than "window sticky." "Diagonal drywall cracking above door at central hallway" is more useful than "minor cracking observed."
5. Moisture and drainage context
Foundation reporting gets much stronger when the moisture story is documented alongside the structural clues.
Document items such as:
- negative grading toward the house
- short downspout discharge
- standing water or erosion patterns
- missing splash blocks or extensions
- crawlspace dampness or elevated moisture evidence
- efflorescence, staining, or past seepage indicators at foundation walls
This does not mean every drainage defect is causing movement. It means moisture and water-management conditions often belong in the same section because they affect risk, maintenance planning, and the logic behind your recommendations.
6. Findings, limitations, and recommendations
This is where the foundation inspection report template either keeps you disciplined or lets the section drift into vague language.
It should make it easy to separate:
- what was observed
- what was not fully observable
- what follow-up is appropriate
That separation matters because "possible structural issue" without supporting detail is weak, and "needs engineer" without tying the recommendation to a visible pattern sounds lazy. Stronger reporting connects the recommendation to the exact concern, the exact location, and the exact limitation if one exists.
What to Photograph for a Strong Foundation Inspection Report
Photos are what make the foundation section easier to trust and easier to defend.
At minimum, your foundation inspection report template should push you to capture:
- one context photo showing the overall side or corner of the structure
- one closer photo of each crack, displacement point, or separation you specifically mention
- one photo showing grade or drainage conditions when they are part of the recommendation
- one interior context photo where floor slope, wall cracking, or door misalignment is relevant
- one photo showing access limitations when visibility was restricted
- one photo that helps connect interior symptoms to exterior location when possible
The strongest photo sets usually pair context with detail.
For example:
- context: rear-left elevation showing downspout discharge and slab edge
- detail: crack or separation at the rear-left corner
That pairing saves you from the classic follow-up question: "Which crack are we talking about?"
Key Takeaway
If you are recommending further evaluation, try to leave the property with one orientation photo and one closer evidence photo for every foundation finding that materially affects the recommendation. The clearer the image sequence, the cleaner the structural narrative.
The Fastest Way to Write Better Foundation Narratives
Most weak foundation write-ups fail in one of four ways:
- they describe the conclusion without describing the visible condition
- they mention a crack without location, pattern, or relative size
- they overreach into engineering conclusions the inspection did not establish
- they ignore nearby drainage or limitation details that help the recommendation make sense
Your foundation inspection report template should help you document each finding in this sequence:
- location
- observed condition
- why it matters
- recommended action
That can be as simple as:
Location:
Observed condition:
Why it matters:
Recommended action:
Here are a few examples that fit a field-ready foundation inspection report template.
Example: step cracking at veneer
"At the left-side brick veneer near the garage corner, step cracking was observed in multiple mortar joints. Veneer cracking can reflect localized movement or differential settlement and should be reviewed in the broader context of the structure. Recommend monitoring and further evaluation by a qualified foundation specialist or structural professional as needed."
Example: basement wall cracking with moisture evidence
"At the rear basement wall, visible cracking and localized moisture-related staining were observed at the time of inspection. Cracking combined with moisture evidence can indicate conditions requiring closer review and corrective action. Recommend further evaluation and repair recommendations by a qualified contractor or structural professional."
Example: negative grading
"Along the right-side exterior, grading appeared to slope toward the structure in several areas. Drainage patterns that direct water toward the foundation can increase moisture exposure and may contribute to performance concerns over time. Recommend regrading and improved water discharge management."
Example: limitation language
"Large stored contents and finished wall surfaces limited observation of portions of the foundation and related structural components. Conditions concealed by finishes or stored materials were outside the visible scope of inspection and may not have been identified."
These examples are not there to become canned phrases for every job. They are examples of how the foundation inspection report template should preserve your field logic before it disappears into shorthand.
Common Foundation Findings Your Template Should Not Let You Miss
If you want your foundation inspection report template to be useful in practice, make sure it leaves room for the findings that repeatedly show up in real inspections:
- step cracking in veneer or masonry
- cracks in exposed concrete or block walls
- slab cracking with displacement or differential height
- sloped floors or out-of-level transitions observed in use
- sticking doors or windows associated with movement clues
- separation at trim, wall intersections, or built-ins
- moisture staining, efflorescence, or seepage indicators
- short downspout discharge or poor grade control near corners
- prior patching or repair areas that deserve documentation
A template that skips these recurring items forces you to improvise every time. A better one makes it easy to capture them consistently.
Why Capture Speed Matters More Than Perfect Wording
The best foundation inspection report template still fails if the capture workflow is clumsy.
Foundation findings are usually built from several small clues instead of one dramatic defect. You may notice grade issues outside, then see a related crack pattern inside, then see moisture evidence in the crawlspace. If your workflow makes you save all of that for later typing, you will lose specificity.
That is why many inspectors are moving toward field-first reporting instead of desk-first reporting. Instead of building the structural section from memory later, they capture the location, the photo, the limitation, and the draft narrative while standing in front of the condition.
That workflow pairs especially well with tools like an inspection photo log template, a stronger inspection notes app, and system-specific guides like our roof inspection report template.
A Better Workflow for Foundation Reporting
A strong foundation inspection report template does not just give you blank places to type. It helps you leave the property with the right structural facts already captured, the right photos already tied to the right location, and the right recommendation language already taking shape.
That is the real goal. Cleaner reporting. Better client understanding. Less vague wording. Fewer callbacks asking where the crack was or what the recommendation was based on.
If you want that workflow to move faster, ReportWalk helps inspectors document findings with voice while they are still onsite. Instead of juggling handwritten notes and later rewrites, you can capture the condition, the location, and the recommendation in the moment and turn it into a cleaner report without so much backtracking.



