What do you know about the existing slab and base?
Start with records rather than a product choice. Gather the driveway’s construction date if known, previous repairs, coating or sealer history, and any available design information. Mark gaps in the record. A surface photograph does not establish what supports the slab.
Describe cracks, uneven areas, patches, and water accumulation as observations. Include overview images so the reviewer can see how the driveway meets the garage, street, and adjacent paths. Do not classify a crack’s structural cause from appearance or assume a patch proves stability.
If a proposal retains existing concrete, ask how the contractor will evaluate the retained material and conditions beneath it. An overlay decision needs more than agreement that the top surface looks worn. The proposal should explain what review it includes and which uncertainties remain.
Why can covering concrete retain the original problem?
The new surface does not remove the existing slab or reveal all of its concealed conditions. If the underlying support, movement, or water path remains unresolved, a proposal must address that limitation rather than describe added concrete as a cure.
Ask the reviewer what specific problem the approach intends to solve. Improving surface appearance differs from correcting an elevation mismatch or responding to settlement. If the concern involves structural cause or adequacy, obtain a licensed engineer’s opinion before choosing construction work.
The NRMCA Concrete in Practice library covers multiple concrete condition topics, including joints and slab curling. That range is a reason to investigate the actual condition, not a checklist for an owner to diagnose the driveway. Avoid universal promises about preventing cracks or stopping movement.
How does the added elevation affect feasibility?
An overlay raises the finished surface. Ask the design team to compare the proposed elevation with garage thresholds, gates, drainage features, walks, curb connections, and other fixed points. Do not assume that a small-looking change has no effect at an edge.
Look at the entire driveway, not one worn panel. Raising an area near the garage may change the transition to a retained area. Raising a street approach may create different public-interface questions. Mark those connections on the sketch and ask how the proposed design handles them.
Drainage needs the same review. Record standing water and existing runoff routes, then obtain qualified evaluation of the proposed elevations. An owner should not solve ponding by directing runoff toward an adjoining property or assume the current drain can accept a changed water path.
Which installation assumptions should a proposal identify?
Ask for the exact proposed system, preparation, retained-base assumptions, connections, joints, and limitations. “Resurface driveway” could refer to different approaches. Confirm what material the contractor proposes and which documented requirements apply.
Compare that approach with removal and replacement using the same work boundaries. Removal can allow review and preparation beneath the existing surface, but it also introduces demolition, disposal, equipment access, and restoration to define. Retaining the slab may reduce disturbance while leaving more existing conditions in place.
The purpose is to understand the tradeoff, not to presume either method wins. Request an explanation of how each approach addresses the problem you reported and what further review could change the recommendation. Treat unknown conditions as unknown rather than embedding them in a confident price comparison.
What happens where the driveway meets the street?
Show the curb, sidewalk crossing, ditch, culvert, or other approach details in your review packet. Identify whether the proposal changes those surfaces or only the private portion.
The Houston Permitting Center’s Right of Way – Traffic and Mobility resources identify city review responsibilities for driveway and sidewalk matters. Verify the address, boundaries, and applicable authority before assuming an overlay needs no review. Greater Houston jurisdictions and specific scopes differ.
Keep approval and construction responsibilities separate in the proposal. A contractor’s preferred method does not establish permission to modify a public interface.
Driveway overlay-review checklist
Prepare these questions before comparing options:
What problem should the work solve: appearance, damage, drainage, or another concern?
What do records establish about the existing slab and base?
Which cracks, patches, elevation differences, and water conditions need investigation?
How will the approach change garage, gate, path, and street transitions?
What vehicles and loads will use the finished area?
Which preparation, joint, connection, and system details does the proposal include?
What public-interface or engineering responsibilities remain open?
How do retain, overlay, and removal options differ in assumptions and limitations?
Ask for a documented recommendation after review, including exclusions and the procedure for newly discovered conditions. Do not treat an initial photo discussion as final design approval.
Planning this work? Explore Concrete Driveways in Houston or tell us about your project.
Overlay questions owners ask
Do not assume that. The reviewer must evaluate the reported condition and retained support. Structural cause or adequacy questions need a licensed engineer.
No. Retained conditions, preparation, elevation changes, demolition, and interfaces may differ even when the area matches. Compare the defined scope and limitations.
No blanket service promise follows from this educational discussion. The exact system, property, condition, and delivery scope require confirmation.
