Root Cause Tracking enables your team to categorize the underlying cause of a warranty issue. Consistently logging root causes over time helps identify patterns across your communities — such as recurring installation errors or material defects — so you can address them at the source.
Steps
Open the Service Request
From the Service Requests tab, click the relevant request.
Select the Issue
Under Home Issues, click the specific issue you want to categorize.
Select a root cause
From the Root Cause dropdown, choose the option that best describes the underlying cause of the issue.
Key Notes
Root cause is logged at the Issue level, not the Service Request level. Each individual issue can have its own root cause.
Root cause categories are customizable during implementation. Foundation configures them based on your team's workflow, but typical options include things like vendor error, material defect, homeowner damage, settlement, and construction error.
Use high-level root cause categories in the dropdown and add detailed context in the Internal Notes field. This keeps your reporting clean while still capturing the full story.
Why Root Cause Tracking Matters
Root cause data isn't just for record-keeping — it drives real business decisions:
Back charge analysis → Helps determine which vendor should be back charged when an issue was their fault.
Warranty budget analysis → Understand where your warranty dollars are going and why.
Trend identification → Spot recurring issues across communities, products, or trades before they become larger problems.
Purchasing decisions → Provide tangible data to show your purchasing team why certain product or material choices create downstream warranty costs.
Recall management → Quickly identify which homes have specific products installed when a recall is issued.
All root cause data flows into your reporting dashboard, giving your team visibility into patterns over time.