Punchlist Manager

Punchlist Manager, built by Verisk, is warranty management software for homebuilders, it automates the process of logging, routing, and resolving homeowner warranty service requests after closing. ProPay integrates with Punchlist Manager so that the claim itself, intake, triage, authorization, parts, and payment, is executed on top of it, rather than replacing it.

What ProPay does with Punchlist Manager

ProPay reads coverage and claim context from Punchlist Manager, homeowner service requests, punchlist items, and builder warranty terms, and writes the resulting claim progress back as the work happens. At first notice of loss, ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates that coverage against what Punchlist Manager holds before dispatch.

ProPay’s homeowner triage runs over SMS, capturing model and serial numbers, photos, and symptom detail directly from the homeowner’s phone, with 80 to 83 percent of homeowners responding after a claim is opened. That conversation, not a call center script, is what feeds the record in Punchlist Manager.

Where a truck roll is warranted, ProPay applies your configured business rules, repair versus replace, auto-approval inside a threshold, then sources parts across suppliers, tracks the order through delivery and return, and validates the resulting invoice against the authorization record before payment releases. Every step writes back to Punchlist Manager as the record of what happened.

How the Punchlist Manager connection works

Punchlist Manager connects through Verisk’s data exchange layer, which is where ProPay reads open service requests and writes resolution status.

Where Punchlist Manager doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking Punchlist Manager to change. Modules go live independently, FNOL, triage, authorization, parts, and payment can each be switched on against Punchlist Manager one at a time.

What stays in Punchlist Manager

Builder warranty terms and the punchlist tracking homeowners see stay inside Punchlist Manager.

What changes is how much of the routine claim work a person has to do by hand inside Punchlist Manager. ProPay handles the repetitive execution and routes exceptions to a human, so your team spends its time on the claims that actually need judgment.

Data handling and security

Each ProPay client, including the connection to Punchlist Manager, runs on a company-specific instance, one carrier’s claim data and contract terms are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.

Every recommendation ProPay makes against Punchlist Manager’s data carries a confidence level and the inputs behind it, and is logged. Recommendations above your configured thresholds route to a person rather than executing automatically.

Deploying the integration

A dedicated Forward Deployed Engineer works alongside your team to build and maintain the Punchlist Manager connection, mapping fields and handling the edge cases specific to how your program is configured inside Punchlist Manager today.

Frequently asked questions about ProPay and Punchlist Manager

Does ProPay replace Punchlist Manager?

No. Punchlist Manager keeps logging and routing builder warranty requests; ProPay adds triage and parts execution to requests that need a technician.

How does ProPay connect to Punchlist Manager?

Punchlist Manager connects through Verisk’s data exchange layer, which is where ProPay reads open service requests and writes resolution status. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does Punchlist Manager still control after ProPay is connected?

Builder warranty terms and the punchlist tracking homeowners see stay inside Punchlist Manager.