A contractor performance scorecard gives an insurance vendor network a consistent way to evaluate roofing and restoration partners after onboarding. Licensing, insurance, certifications, and background checks establish whether a contractor is eligible to enter a network. Performance data shows whether that contractor continues to deliver organized, timely, safe, and well-documented work once assignments begin. For regional carriers, independent adjusting firms, and managed repair teams, both layers matter.
The goal is not to compress every job into one simplistic grade. A hail claim, emergency tarp assignment, and water mitigation loss have different operating clocks and documentation needs. The useful approach is to define a small set of contractor performance scorecard KPIs, apply clear rules by assignment type, and review exceptions with context. PerilBridge's carrier overview and carrier partner information reflect that documentation-first approach to network operations.
What a contractor performance scorecard should accomplish
A useful scorecard helps vendor-management teams answer three practical questions: Is the contractor responsive enough for the assignment type? Is the file complete enough for efficient review? Is the work being performed within the network's quality, safety, and compliance expectations? It should support coaching and assignment decisions, not create an automatic coverage or payment decision. Contractors do not determine policy coverage, and a high score is not evidence that a scope, supplement, or invoice has been approved.
Before selecting metrics, define the event that starts and stops each clock. For example, “time to contact” might start when a contractor accepts an assignment and stop when documented contact is made with the property owner. “Time to inspect” might stop when the site visit is completed, not when a report is uploaded. Without shared definitions, scorecards reward different workflows rather than comparable performance.
1. Assignment acceptance rate
Acceptance rate measures the share of offered assignments a contractor accepts within its approved territory and service profile. It is most useful when paired with honest capacity data. A contractor that declines work promptly because crews are full can be more dependable than one that accepts every assignment and misses appointments later. Segment this KPI by normal operations and CAT surge periods, since demand conditions are fundamentally different.
2. Time to first contact
Time to first contact measures how quickly the contractor reaches the policyholder or designated contact after accepting an assignment. Track both the median and the percentage completed within the program target. Medians reduce distortion from a few extreme files, while the target percentage shows consistency. The record should capture attempted and successful contact separately so unreachable customers are not treated as contractor inactivity.
3. Inspection or site-arrival cycle time
This KPI measures elapsed time from assignment acceptance to documented site arrival or inspection completion. Set different targets for emergency stabilization, routine roof inspection, and restoration work. During a major event, geography and safe access can change quickly; the NOAA Storm Events Database is one public resource vendor teams can use to review documented severe-weather events, but local conditions and active emergency guidance still control field decisions. A scorecard should never encourage unsafe travel or roof access simply to preserve a metric.
4. Documentation completeness
Documentation completeness measures whether the first submission contains the program's required records. Depending on assignment type, that may include overview and detail photos, slope or room orientation, measurements, moisture readings, equipment logs, temporary-repair receipts, estimates, invoices, and signed acknowledgments. Build the score from an explicit checklist and report missing-item patterns. A single percentage is less actionable than knowing that one vendor repeatedly omits elevation context or drying records.
Restoration assignments should align required records with the applicable scope and program rules. The IICRC standards program provides industry standards for inspection, cleaning, and restoration work. Vendor managers should identify which standards, credentials, or documentation practices their own program requires instead of implying that one credential alone establishes performance.
5. Estimate first-pass quality
First-pass quality measures whether an estimate can enter review without preventable rework. Common defects include missing dimensions, unclear photo references, duplicate line items, unexplained quantities, or notes that do not connect the requested scope to observed conditions. The metric should distinguish administrative corrections from genuine differences in damage assessment, pricing, repair method, or policy interpretation. Those substantive questions require review; they should not automatically count as clerical failure.
Many property-claim workflows use Xactimate, but software familiarity is only one part of estimate quality. A clean file still needs accurate measurements, appropriate line-item support, and clear notes. Score the output that reviewers receive, not the contractor's marketing claims about a platform or certification.
6. Supplement frequency and support quality
Supplement frequency by itself is a poor quality measure. A low rate may reflect complete initial scopes, but it can also reflect under-documentation. A high rate may reflect complex losses, code requirements, concealed conditions, or weak first-pass estimating. Track frequency alongside the percentage of supplement requests that include an itemized estimate, supporting photos, measurements, invoices, code references when relevant, and a concise explanation of what changed. Do not treat submission of a supplement as evidence that an insurer owes the requested amount.
7. Milestone and completion timeliness
For production assignments, compare promised and actual dates for material ordering, work start, substantial completion, final documentation, and closeout. Exclude delays outside the contractor's control only under a defined exception process, such as unsafe weather, material backorder, customer scheduling, permit delay, or a carrier-requested pause. Tracking the reason code is more useful than silently removing delayed files, because it reveals where the network itself needs better coordination.
8. Reinspection, callback, and workmanship issue rate
Quality should be measured with observable events: required reinspections, verified callbacks, incomplete punch-list items, documented property-protection issues, and warranty service. Separate confirmed workmanship problems from customer questions or scope disputes. Use a rolling period and a minimum assignment threshold so one event does not overwhelm a small contractor's score. When a problem is confirmed, track time to acknowledge and time to correct as separate measures.
9. Safety and compliance status
Safety and compliance should operate as both a scorecard dimension and an eligibility gate. Track current licenses where required, insurance documents, training records required by the program, incident reporting, and corrective actions. For roofing work, vendor teams can use OSHA's construction fall-protection resources as an authoritative baseline while also accounting for applicable state-plan requirements. A fast contractor should not earn enough speed points to offset an expired license, missing insurance, or unresolved serious safety issue.
PerilBridge describes its network posture on the compliance page. Each carrier or IA firm should still define its own legal, procurement, credential, and escalation requirements. The scorecard is an operating control, not legal advice and not a substitute for jurisdiction-specific review.
10. Communication and customer-experience signals
Communication KPIs can include appointment confirmation, status-update cadence, response time to reviewer questions, complaint rate, and post-service feedback. Keep the survey narrow and tied to observable conduct. Questions such as whether the contractor arrived in the agreed window, explained the next operational step, protected the property, and provided requested documents are more reliable than asking a customer to rate a coverage outcome the contractor does not control.
How to weight the score without hiding risk
Start with a simple model and publish the definitions to participating vendors. Weight documentation, timeliness, quality, communication, and compliance according to program priorities, but keep critical gates outside the weighted average. A contractor with an expired required license should not remain assignment-eligible because excellent cycle time raises the overall score. Similarly, a substantiated safety concern should trigger the program's review path rather than wait for a quarterly average.
Use assignment-type cohorts so emergency tarp work is not compared directly with full roof replacement or water mitigation.
Show sample size and measurement period beside every rate.
Require reason codes for exclusions and overrides.
Give contractors a way to review underlying files and correct factual data errors.
Separate coaching thresholds from suspension or removal thresholds.
A practical scorecard review cadence
Operational teams can monitor urgent exceptions daily, review trend dashboards monthly, and hold structured contractor reviews quarterly. New vendors may need a shorter probationary review window until enough assignments exist for a stable baseline. CAT activations may require a temporary event-specific dashboard, followed by a retrospective that compares surge performance with normal-state performance.
Confirm data definitions and assignment cohorts before calculating rates.
Review critical compliance and safety exceptions first.
Compare current performance with the contractor's own prior period and the appropriate network cohort.
Identify the two or three file-level behaviors driving the result.
Document the coaching action, owner, due date, and follow-up measure.
Build a scorecard that vendors can act on
The best contractor performance scorecard is transparent enough that a roofing or restoration partner can improve from it. “Documentation score: 82%” is weak feedback. “Seven of 20 files lacked labeled overview photos, and four missed the agreed first-contact window” gives an operator something concrete to fix. It also gives the carrier or IA firm an auditable basis for coaching, changing assignment volume, or escalating a repeated issue under its program rules.
Contractors interested in a documentation-led network can review PerilBridge for contractors. Carrier vendor-management teams can book a PerilBridge demo to discuss contractor attestation, assignment workflows, and scorecard design. PerilBridge does not make coverage decisions, promise payment, or negotiate policy outcomes; those responsibilities remain with the authorized parties in the claim process.
