What can you document without diagnosing the problem?
Start by naming the surface: building foundation, driveway, walkway, or patio. Photograph the whole area before taking close views. A close-up may show a crack but omit the connection to a doorway, drain, tree, or neighboring slab.
Describe what you see. “The patio edge sits below the adjoining path” records a condition. “The foundation failed” assigns a cause and conclusion. Keep those statements separate, including in messages to a contractor.
Use a simple sketch to mark locations. Give each photograph a matching label and date. Include a visible reference for scale when you can do so without entering an unsafe area. Do not lift loose concrete, excavate beside a foundation, or use a photograph to decide that a surface can carry a load.
How do timing and previous work add context?
Write down when you first noticed the condition and whether you have evidence of change. If you do not know when it began, say so. The date you discovered a crack is not necessarily the date it formed.
Gather earlier inspection reports, listing photographs, repair invoices, and construction records. A previous repair may explain a patch or change in finish. It does not prove the current condition has the same cause as the earlier one.
Record whether the area changed after utility work, landscaping, a leak, or another project. Report the sequence without claiming that one event caused the other. That distinction gives the reviewer useful history without narrowing the investigation on unsupported grounds.
If someone has already offered a diagnosis, include the report and the author’s role. Separate a written engineer’s opinion from an informal comment you heard during a visit.
Which water and adjacent-condition observations matter?
After rain, observe from a safe place where water collects and where it leaves the area. Photograph standing water, blocked surface drains, downspout discharge, and low points. Do not perform a water test against a building to reproduce a leak.
Note adjoining structures, door thresholds, retaining elements, and the edges between slabs. Record visible separation or different elevations without turning those signs into a structural conclusion. For vehicle-serving areas, include current traffic and any heavier use that began after construction.
Drainage and floodplain questions may need separate professional or authority review. Harris County’s floodplain management resources explain where owners can find mapping and development information. A puddle does not establish floodplain status, and a map alone does not diagnose why a slab moved.
Why isn't the crack appearance enough?
Concrete has several kinds of surface and movement concerns. The NRMCA Concrete in Practice library treats topics such as crazing, plastic shrinkage cracking, joints, and curling separately. Those distinctions show why one visual description cannot support a universal repair recommendation.
The owner does not need to classify the technical mechanism before seeking review. Your useful contribution is a clear record of location, timing, use, and connected observations. Let the qualified reviewer decide what additional measurements, investigation, or design work the question requires.
A coating, patch, or replacement finish may change appearance without answering a structural question. Before accepting surface work, ask what problem the proposed scope addresses and what it leaves unresolved. Avoid treating “we can cover that” as evidence about stability or future movement.
Which questions belong with a licensed engineer?
Route concerns about building support, structural adequacy, movement cause, and repair design to a licensed engineer. Ask the engineer to define the review scope and any information needed before a conclusion.
For a flatwork request without an established structural concern, a contractor can discuss removal, access, intended use, and a proposed construction scope. If observations raise structural questions, pause that part of the decision and obtain the appropriate review. Do not ask a contractor estimate to substitute for an engineer’s report.
Our Foundation and Concrete page distinguishes construction planning from those professional responsibilities. The review should identify the exact requested work rather than promise a permanent fix based on a crack photograph.
Concrete condition-review checklist: what should your packet contain?
Organize the information into a short folder:
Property address, use, and affected concrete category.
Overview photographs and dated close views keyed to a sketch.
Observed changes, with unknown dates marked as unknown.
Drainage observations and nearby structures or utilities.
Current loads and any planned change in use.
Prior reports, repair records, and relevant project history.
Safe-access restrictions and the people authorized to approve review.
Questions needing engineering, drainage, or authority input.
Keep copies of the original photographs. If you annotate them, save the marked versions separately. That makes it easier for the reviewer to distinguish your notes from the visible condition.
Planning this work? Explore Foundation & Concrete Work in Houston or tell us about your project.
Questions about concrete observations
No. A crack photograph does not establish structural cause or repair design. Obtain licensed-engineer review when the concern involves building support or structural movement.
Ask the reviewer first. Covering the condition can obscure useful evidence. Avoid DIY intervention in an unstable or uncertain area.
Yes, when you use the same location and include dates. They document visible change; the qualified reviewer must interpret its significance.
