Property Preservation Wizard (PPW) in 2026: What It Does, What It Costs You in Manual Work, and What You Can Build On Top

Property Preservation Wizard — PPW — is the platform most property preservation and mortgage field services back offices run their business on. It receives and manages work orders, dispatches crews and vendors, tracks bids, produces invoices, and gives field crews a mobile app for orders and photos. Verisk owns it, alongside Pruvan and XactPRM, in the same product family — which makes PPW less a standalone tool than the center of a stack.

What almost no one writes about is the part that decides your automation strategy: PPW’s automation is tier-gated. The rules engine, the SLA configurations, the order-frequency controls, and the API all live on the Enterprise tier. A Premium back office — and Premium is where most small and mid-size preservation companies live — runs the same core work-order platform with none of those levers. Every “just use PPW’s rules engine” recommendation you have read is advice for a tier you may not be on.

This deep-dive is written for the back office: regional and national field services and preservation companies with coordinators processing orders, managing vendors, QC-ing photos, invoicing, and defending chargebacks. It covers what PPW actually does, how Pruvan fits, exactly what Premium and Enterprise include, where the manual gap costs you hours, how XactPRM and RepairBASE handle the estimating layer, and what a no-code layer can carry on top of PPW without the Enterprise API. For the full category landscape — every platform and portal in the defaulted-property world — start with our complete guide to property preservation software; this article goes deep on one platform.

What is Property Preservation Wizard (PPW)?

Property Preservation Wizard is a work-order management platform, owned by Verisk, built for the companies that maintain defaulted and REO properties — and for the lenders and servicers who assign them that work. Its job is the full order lifecycle: receive the order, dispatch it to a crew or vendor, capture the field results, prepare the bid, produce the invoice, and keep the client’s timeline visible. Verisk’s own positioning names field service companies, lenders, and servicers as its buyers, and the platform earned the 2025 MortgagePoint Tech Excellence Award per Verisk’s product page.

What does PPW actually do for a preservation back office?

For a back office, PPW is the system of record for work: orders in one place, statuses visible, results attached, invoices generated from the work performed. Vendor listings describe the operational core consistently — building orders, viewing job progress in real time, verifying property visits through mobile check-in, and a dynamic form builder that captures structured information from the field. The mobile app puts work orders and photo capture in the crew’s pocket. Verisk states the platform has handled more than 31 million work orders — a vendor figure, cited as such — and its central function is the one that matters in this industry: producing defensible proof that work was performed on time and to specification.

Who owns PPW — and what is the Xactware family?

Verisk owns Property Preservation Wizard, and it sits in Verisk’s Xactware product family alongside Pruvan and XactPRM. One naming note worth knowing: Verisk’s current product pages use the long form “Property Preservation Wizard,” while the login domain and older releases read “Property Pres Wizard” — same product, and the long form is the vendor’s current canonical name. The single-parent structure is strategic context for everything below: the tools most preservation back offices run for orders, field evidence, and repair pricing are siblings, designed to connect to each other.

How do PPW and Pruvan fit together?

PPW and Pruvan are complements under one parent, not competitors — and any framing that pits them against each other misreads the stack. PPW is the work-order backbone: orders, dispatch, bids, invoices. Pruvan is the field-evidence layer: geocoded, timestamped photo, video, and mobile-form capture that certifies what happened at the property. Verisk owns both, and Pruvan’s own support center documents the direct integration into PPW.

	PPW	Pruvan
Role in the stack	Work-order backbone — orders, dispatch, bids, invoicing, client timelines	Field-evidence layer — geocoded, timestamped photos, video, mobile forms
Owner	Verisk (Xactware family)	Verisk (Xactware family)
Who lives in it daily	Back-office coordinators	Field crews and subcontractors
How they connect	Receives Pruvan’s certified field results against the order	Documented native integration into PPW, per Pruvan’s support center

What does Pruvan’s tiering mean for a back office?

Pruvan is tiered, and the tiers decide how much of your vendor network it covers. Per the vendor’s current pricing: Solo at $47, Team at $187, and Business at $390 per month — with premium integrations capped at two, four, and unlimited respectively, and subcontractor management available only on the Business tier. For a back office coordinating a vendor network rather than employed crews, that last line is the one that matters: the coordination capability sits at the top of the ladder. It is the same lesson PPW’s own tiering teaches, one product over.

What does PPW cost, and what does your tier actually include?

PPW’s published entry point is $199 per month for the first five users on the Premium tier, with Enterprise priced by quote — and the difference between the tiers is not polish, it is automation itself. Per Verisk’s tiering, the System Rules Engine, SLA configurations, order frequency controls, and PPW Link — the API — are Enterprise-only. Premium runs the same core work-order platform with none of those four. This is the single most consequential fact in any PPW automation plan, and no comparison article we have found states it.

Capability	Premium ($199/mo, first 5 users)	Enterprise (quote)
Core work-order management — orders, dispatch, bids, invoicing, mobile app	✓	✓
System Rules Engine	—	✓
SLA configurations	—	✓
Order frequency controls	—	✓
PPW Link (API)	—	✓

What is PPW Link?

PPW Link is PPW’s API — the programmatic doorway other systems use to read and write orders, results, and statuses — and it is an Enterprise-tier capability. That placement shapes the whole integration conversation: a Premium back office cannot hand a developer an API key, because there is no API on its tier. Integration for Premium runs through what the platform does expose — its exports, its notifications, and the tools Verisk natively connects, like Pruvan.

Check your tier before you plan your automation

The most common automation advice in this market — “start with PPW’s rules engine; you are already paying for it” — is false for every Premium customer. Premium customers are not paying for a rules engine; it is not on their tier. So the honest first step of any PPW automation plan is one question: which tier are you actually on? Enterprise back offices should absolutely wring the native Rules Engine, SLA configs, and PPW Link for everything they offer before adding anything else. Premium back offices need a different map — one that starts from the manual gap in the next section, and builds around the platform rather than inside it.

What does the manual gap cost a Premium back office?

The manual gap is the set of motions PPW’s Premium tier leaves to humans: getting orders in from client portals, building PCRs and invoice line items, QC-ing photos before upload, and assembling chargeback defenses. None of these is a knowledge problem — your coordinators know exactly what to do. Each is a motion problem: the same reading, re-keying, checking, and compiling, order after order. Here is the anatomy, lane by lane.

Portal-to-PPW order intake

A preservation back office answers to the portals its clients run — HUD’s P260, Equator on the servicer side, and each national order source’s dedicated portals — while running its own work in PPW. The manual state: a coordinator reads the new order in the client portal, then re-keys it into PPW — property, order type, due date, instructions — for every order, every day. The gap between the portal and PPW is where the double entry lives, and it is the first lane worth relieving because it runs at order volume. It is the same portal-to-platform seam we map across the servicer world in our automated mortgage processing guide — different portals, identical anatomy.

PCR building, bids, and invoice line items

A property condition report is structured data — conditions observed, actions taken, quantities, photos — and a preservation invoice is a list of priced line items that must match the order, the allowables, and the evidence. The manual state: coordinators assemble both by hand, transcribing field results into the client’s required structure and typing line items one at a time. The work is rules-based, repetitive, and error-priced: a line item that does not match the evidence is a discount waiting to happen. This assembly lane — results in, structured deliverables out — is the second cost center of the Premium gap.

Photo QC before upload

Field evidence only defends you if it meets the client’s requirements — right angles, right counts, right timestamps, right property. Pruvan certifies that photos are geocoded and timestamped; a human still has to check that the set is complete and matches the work claimed before it goes up to the portal. The manual state: coordinators eyeball photo sets against requirement checklists at volume. QC is exactly the kind of read-and-flag work that should be triaged by a system and decided by a person — the machine checks completeness and consistency; the coordinator rules on anything flagged.

Chargeback defense and the paper trail

A chargeback dispute is won with assembled evidence: the order, the timestamps, the geocoded photos, the invoice lines, the communications — compiled into one coherent story fast enough to meet the dispute window. The manual state: a coordinator rebuilds that story by hand from PPW, Pruvan, email, and the portal, per dispute. Everything needed already exists in the systems; the cost is the assembly. A back office that can produce the complete evidence package on demand defends margin that a slower one simply concedes.

What about the estimating layer: XactPRM and RepairBASE?

Repair pricing sits in its own layer of the stack, and in the preservation market that layer is a two-name landscape: XactPRM, Verisk’s own repair-pricing and estimating tool, and RepairBASE, from Bluebook International. They are not a rivalry to adjudicate — which one touches your work is usually decided by your client’s requirements, not your preference. What a back office needs is to know what each is and how each connects.

	XactPRM	RepairBASE
Owner	Verisk (Xactware family)	The Bluebook International, Inc.
What it is	Repair-pricing and estimating for the preservation market	REO/preservation repair-cost estimating on nationwide standardized data, localized to the 5-digit zip code
How it connects	XactPRM Connect — the documented link into PPW	XML/API and web-services integration, per Bluebook
Institutional weight	Same parent as PPW and Pruvan	Used by HUD since 2011 to validate FHA repair costs; Bluebook states it is used by 7 of the top 10 preservation and maintenance providers (vendor figure)

What is XactPRM Connect?

XactPRM Connect is the documented link between XactPRM and PPW — the path by which Verisk’s repair pricing meets Verisk’s work-order platform. For an Enterprise-minded back office standardizing on the Xactware family, that connection is the argument: pricing, orders, and field evidence under one parent, designed to talk to each other.

What is RepairBASE — and why does HUD’s use of it matter to your bids?

RepairBASE is Bluebook International’s repair-cost estimating solution: standardized national cost data, localized to the 5-digit zip code, positioned by the vendor as compliant with HUD requirements. The institutional fact that matters to a preservation back office: HUD adopted RepairBASE in 2011 to confirm repair, replacement, preservation, maintenance, and improvement costs on FHA single-family homes, and renewed on a five-year contract in 2013. When the entity auditing repair costs on FHA properties runs a specific cost dataset, bids priced against that same dataset are speaking the auditor’s language. That is the practical reason RepairBASE shows up across this market — and the reason your estimating lane deserves a deliberate choice rather than an inherited habit.

What can you build on top of PPW without the Enterprise tier?

You can build a workflow layer around Premium PPW using the surfaces it does expose — its exports, its notifications, and its natively integrated tools — without the Enterprise API. The layer’s job is the manual gap above: intake staged from portal data, PCR and invoice assembly drafted from field results, photo sets pre-checked against requirements, chargeback evidence compiled on demand. WisdomStream builds this layer for field services and preservation back offices as DefaultFlow. It does not replace PPW; it moves the work between PPW and everything around it.

What “reads, drafts, flags, and tracks” looks like on one work order

Take one order, end to end. The layer reads the new order as it appears — and stages the PPW entry a coordinator confirms instead of re-keys. When field results land, it drafts the deliverables: the PCR structure filled from the captured data, the invoice line items assembled against the order. It flags what a human must rule on — a photo set short of the requirement, a line item that does not match the evidence, a due date at risk. And it tracks every open order’s status to invoiced-and-paid, so nothing lives in one coordinator’s head. The system reads, drafts, flags, and tracks. Your coordinators decide. Honesty about the mechanism matters here: without PPW Link, the layer works with what Premium exposes — which is precisely why the tier question comes first in every plan we map.

What stays human

Bid judgment stays human — what the property actually needs, and what it is worth bidding. Dispute strategy stays human: which chargebacks to fight and how hard. Client relationships, vendor decisions, and anything where the back office’s judgment is the product stay with your people, because judgment is what your clients are paying for. The layer’s purpose is to return your coordinators’ hours to exactly that work.

When Enterprise is the right answer instead

Sometimes the honest recommendation is the upgrade. A back office at high order volume, with complex SLA obligations across many clients, and an appetite to integrate deeply, is describing the Enterprise tier’s exact feature set — the Rules Engine, SLA configurations, order frequency controls, and PPW Link were built for that profile. In that world, wring the native capabilities first; a layer still earns its keep at the portal seam and in evidence assembly, but it should complement the platform’s own automation, not substitute for levers you now own. Tier first, then map, then build.

How do you roll this out without breaking your order flow?

Rollout is incremental and runs in parallel with your manual process — nothing is retired until a full order cycle proves the automated lane against it. Six steps:

1. Map one order type end to end as it actually runs today — portal to PPW to field to invoice to paid — including every re-key and every checklist.
2. Confirm your PPW tier and write down what it includes — the table above is the difference between building inside the platform and building around it.
3. Pick one lane by volume and error cost — portal intake and invoice assembly usually rank first.
4. Pilot with one coordinator who owns that lane today; their exception list is the real specification.
5. Run one full order cycle in parallel — automated lane beside the manual one — and compare outputs before anything manual stops.
6. Expand one lane at a time, folding each rollout’s exceptions into the next one’s rules.

The full rollout discipline — pilot selection, baselines, and the measurement frame for a preservation back office — is covered in the rollout section of our property preservation software guide; this sequence is the PPW-specific cut.

Glossary — PPW and Preservation Terms

Property preservation

The inspection, securing, and maintenance of defaulted and vacant properties on behalf of mortgagees, servicers, and investors.

Mortgage field services

The industry term for the companies performing property preservation, inspections, and related on-site work at scale.

Work order

The instruction that assigns specific work at a specific property, with scope, pricing basis, and a due date.

PCR (property condition report)

The structured report of a property’s observed condition and the actions taken, assembled from field results.

Bid

A priced proposal for work beyond the standing scope, submitted for client approval before performance.

Allowable

A client- or investor-set price cap for a standard preservation task.

Chargeback

A client’s clawback of paid or invoiced amounts, typically for claimed deficiencies in work or documentation.

Conveyance

The transfer of a foreclosed FHA property to HUD, with condition obligations attached.

REO

Real estate owned; property held by the lender or investor after foreclosure.

Occupancy check

An inspection to determine whether a property is occupied or vacant.

Winterization

Preparing a vacant property’s systems against freeze damage.

Vendor network

The subcontractor crews a field services company dispatches and manages.

Geocoded photo

A photograph carrying embedded location data, certifying where it was taken.

SLA

Service-level agreement; the timeliness and quality obligations attached to order completion.

Default servicing

The servicer-side management of delinquent loans, within which preservation work is ordered.