Aftercare, Maintenance & Warranty Information
A successful asphalt project doesn’t end when the crew leaves. Proper aftercare and routine maintenance play a major role in performance and lifespan—especially in Wisconsin’s freeze-thaw climate. Below are recommended aftercare procedures, maintenance guidance, and an overview of how warranty situations are handled.

(Note: warranty terms can vary by project type and will be defined in your proposal/contract.)
Immediately After Paving (First 72 Hours)
Traffic & Cure Time
Asphalt continues to cure and harden over time. The first few days are the most important.
We recommend:
Avoid parking in the same spot repeatedly for the first few days.
Avoid sharp turns while the surface is new.
Keep heavy vehicles off new asphalt as directed in your proposal.
Use caution with kickstands, jacks, dumpsters, and trailers (point loads can indent the surface).
Weather Considerations
Heat can soften new asphalt temporarily; cold can slow curing. We’ll advise any special timing recommendations based on season and conditions.
First 30 Days—Best Practices
Keep the surface clean (debris holds moisture).
Avoid allowing water to pond; report major standing-water concerns early.
Avoid fuel/oil spills when possible; clean promptly if they occur.
Do not use harsh chemicals or excessive de-icers directly on fresh pavement.
If you notice unusual settling or a concern, report it with photos and location notes.
Maintenance Guidance (Long-Term)
Crack Care
Cracks happen over time—especially with Wisconsin weather. Routine crack filling helps prevent water intrusion and freeze-thaw damage.
Sealcoating Timing
Sealcoating is typically recommended after the asphalt has had time to cure (timing varies by conditions and project type). We will provide guidance on the best window for your specific surface.
Drainage Matters
Water is pavement’s biggest enemy. Good drainage improves lifespan significantly. If drainage patterns change on your property (downspouts, grading changes, landscaping), pavement performance can be affected.
What’s Normal vs. What’s Not
Normal / Common Asphalt Characteristics
- Minor surface hairline cracking over time
- Slight texture variation depending on mix and season
- Faint roller patterns or seams typical of asphalt work
- Small aggregate “pop-outs” that do not affect structural integrity
Concerns Worth Reporting
- Rapid pothole formation
- Significant sinking or settlement
- Large or expanding cracks shortly after completion
- Drainage issues causing major standing water
- Edge collapse from unstable shoulder/base
Company Warranty (How We Handle It)
If your project includes a workmanship warranty, it will be stated in your written proposal/contract, including:
- What is covered
- Warranty length
- Any exclusions or conditions
- How to submit a warranty request
Typical Warranty Exclusions (Example Language)
Warranty coverage commonly excludes issues caused by:
- Damage from heavy trucks, dumpsters, or repeated heavy loads not disclosed
- Snowplow gouging, abuse, or impact damage
- Water infiltration from changes in drainage, downspouts, or grading after completion
- Utility work cuts/trenching performed by others
- Chemical spills (oil, fuel, solvents)
- Lack of routine maintenance (such as unsealed cracks over time)
(Exact warranty terms must match your contract.)
Wisconsin Warranty & “Right to Cure” Handling
Wisconsin has a consumer process commonly referred to as a “right to cure” approach for dwelling construction defect claims, which generally involves providing notice and an opportunity to inspect/repair before escalation.
Our Commitment
Regardless of project type, if you have a concern:
Contact us promptly with details and photos
We schedule a site review.
If covered and confirmed, we coordinate repairs or next steps.
We aim to resolve issues professionally and efficiently.
How to Submit an Aftercare or Warranty Request
Please provide:
- Name, address, and best phone number
- Job number (if available)
- Description of the issue
- Photos and approximate location on the pavement
- When the issue was first noticed










