Private equity and portfolios
Restoration roll-ups: unifying job files and program data
By SourceX Editorial · Updated
Short answer
Restoration roll-up integration means bringing each add-on's job files, estimates, drying logs and carrier program records into one structure without breaking program obligations. Check every carrier and TPA program agreement before moving claim-related data, standardize the job file first, migrate non-program work before program work, and keep program-sourced records tagged so their terms follow them.
Key takeaways
- Treat each carrier or TPA program agreement as a data contract and read its confidentiality, audit and data-use terms before integration.
- Standardize the job file first: loss intake, scope, estimate versions, drying logs, photos, change orders, invoices and signed authorizations.
- A change of ownership can trigger notice or requalification in a program, so confirm program standing before rebranding any add-on.
- Keep policyholder and claim details out of platform-wide analytics until each program's terms are confirmed.
What sits inside a restoration job file?#
A restoration job file is the full record of one loss, from first notice through the certificate of completion. In a roll-up, every add-on assembles it differently: one keeps everything in a job management system, another splits it between an estimating platform such as Xactimate, a photo documentation app, paper moisture maps and a shared drive.
Agreeing what a complete job file contains is the first integration decision, because it sets what each add-on must export and what the platform system must hold.
| Job file component | Where add-ons keep it | Integration note |
|---|---|---|
| Loss intake and assignment | Program portal, phone intake, job management system | Carry the program's claim number as a key on the platform job |
| Scope and estimate | Estimating platform | Keep every estimate version and supplement, not only the final |
| Moisture readings and drying logs | Drying apps, paper forms | Capture readings with dates, rooms and equipment; scan paper logs |
| Photos and video | Documentation apps, technician phones | Link each file to the job and room before an app account closes |
| Change orders | Email, estimating platform | Record who approved each change and when |
| Invoices and payments | Accounting system | Reconcile to the estimate and to carrier payments |
| Signed authorizations and certificates | Paper, e-signature tools | Keep the signed originals; they prove authority to work |
Why carrier program data needs separate checks#
Carrier program data needs separate checks because it is created under program agreements that set rules on confidentiality, audits, reporting and use of claim information. Preferred vendor and TPA programs usually supply the claim, the policyholder contact and the adjuster relationship; the contractor supplies the work and the documentation. The agreement, not possession of the files, decides what the platform may do with them.
Program scorecards and performance reports deserve the same caution. They are useful for managing add-ons, but programs may treat them as confidential to the participating vendor.
| Program term | What to check | Why it matters for integration |
|---|---|---|
| Confidentiality | Whether claim and policyholder information is program confidential information | Limits copying into central systems or sharing across add-ons |
| Data use | Whether records may be used only to perform the assignment | Shapes any later analytics, AI or licensing plans |
| Audit and retention | How long job files must be kept and in what form | Sets the archive policy for retired systems |
| Assignment and change of control | Whether a new owner triggers notice, consent or requalification | Affects whether new claims keep flowing to the add-on |
| Systems and reporting | Required portals, file formats and upload rules | Decides when the add-on can move to platform software |
| Vendor identity | Whether the entity name and licenses must match program records | Matters before rebranding or merging entities |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
The integration sequence with program checks#
The integration sequence puts program checks ahead of rebranding and migration, because a lapsed program relationship costs more than any system saving. Non-program jobs move first, since they carry fewer outside rules.
- List every program each add-on participates in, with the participating legal entity and the program contact.
- Pull each program agreement and record confidentiality, data-use, audit, assignment and systems terms in one register.
- Complete any notice, consent or requalification the ownership change requires before changing names or entities.
- Define the platform job file standard and naming rules for jobs, claims and properties.
- Migrate open and closed non-program jobs, then program jobs once each program's systems rules are confirmed.
- Tag program-sourced records so access, retention and later uses follow that program's terms.
- Archive retired systems read-only for the longest period any program, contract or law requires.
Choosing one job management system without losing history#
Choosing one job management system works when the decision is made on job file completeness and program compatibility, not on which add-on shouts loudest. The platform system must accept every component of the standard job file, keep program claim numbers as searchable keys, and meet the portal and reporting rules of the programs the add-ons belong to.
Closed jobs raise a separate choice: migrate them in full or keep them in a read-only archive. Full migration helps estimators and project managers who reuse past scopes, but it is slow when attachments are scattered. Many platforms migrate open jobs and recent closed jobs fully, archive the rest with a searchable index, and keep paper drying logs scanned and linked to their claim numbers rather than retyped.
Mistakes that put program standing at risk#
The mistakes that put program standing at risk are mostly sequencing errors. Rebranding an add-on before the program has been told, merging the legal entity that holds the program credentials, or routing a program claim to a sister company that is not an approved vendor can each breach an agreement the platform paid to acquire.
Data mistakes follow close behind: sharing one program's claim data with add-ons outside that program, closing a documentation app account before photos are exported, and discarding paper drying logs after scanning only some of them. Each one weakens the file if a claim is later disputed or audited.
Illustrative: a water mitigation platform with four add-ons#
Illustrative: a fictional restoration platform has acquired four water mitigation and reconstruction companies across two states. Two of them participate in the same TPA program through different legal entities, one relies mostly on direct homeowner and commercial work, and one keeps drying logs on paper.
The operating partner builds the program register first and learns that one program requires notice before any change in ownership or name, so rebranding waits until that notice is acknowledged. Non-program jobs migrate into the platform's job management system first. Program jobs follow with claim numbers carried as keys and records tagged by program. Platform analytics use only operational fields, such as material types, equipment days and drying outcomes, while policyholder details stay inside each add-on's program workspace.
Unified job files beyond operations, and the SourceX approach#
Unified job files, with scopes, estimate versions, drying logs, photos and change orders linked to outcomes, are the kind of operating records AI developers look for when building estimating and documentation tools. The same files also carry the tightest constraints in the business, because policyholder details and program terms travel with them.
SourceX approaches these records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The Rights step separates program-governed records from the platform's own, Preparation removes policyholder names, addresses, claim numbers and identifying photo details, and each package carries a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. The supplier approves every step.
Frequently asked questions
Can a platform route program claims to whichever add-on has capacity?
Only if the program allows it. Programs typically assign work to an approved vendor entity and service area, so sending a job to a sister company can breach the agreement unless that company is also approved. Confirm program rules before building shared dispatch across brands.
Who owns photos and moisture logs from a program job?
The contractor usually creates them, but the program agreement and the property owner's authorization can limit how they are used. Treat them as documentation that supports the claim, and get written confirmation before any other use, such as training internal tools or sharing outside the add-on.
Should we merge add-on legal entities to simplify program administration?
Merging can simplify accounting, but it can also force requalification in every program the merged entity joins. Many platforms keep participating entities in place until each program's change-of-ownership process is complete, then consolidate on a schedule agreed with the programs.
How long should retired restoration systems be kept?
As long as the longest requirement among program agreements, customer contracts, warranty commitments and applicable law, which counsel and finance should confirm. Keep the archive read-only and searchable by claim number, property address and date of loss.
Do estimating platform files need to come out of the old account?
Yes, where the add-on's estimating account will close or merge. Estimate versions and supplements explain how a final number was reached, which matters in disputes and audits. Check the vendor's documentation for export options and confirm that attachments come out with each estimate.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.