Property Preservation Website vs Field Operations Software: What Should Own What?

Overview

Property-preservation companies need a public acquisition system and an operational field system for fundamentally different jobs.

The public front office needs to know:

The field platform needs to know:

• which client is interested;
• where coverage is needed;
• what services;
• expected volume;
• property types;
• reporting expectations.
• which property;
• which work order;
• which line item;
• which vendor;
• what proof is required;
• what was completed;
• what failed QA;
• what gets invoiced.

What the public website should own

Usually:

Current OneStudio features fit this layer.

• services;
• buyer pages;
• coverage pages;
• public RFQ;
• ordinary prospect/client history;
• sales/onboarding calls;
• marketing analytics.

What preservation software should own

Current specialist platforms manage combinations of:

That is the operational truth.

• work orders;
• properties;
• vendors;
• dispatch;
• bids;
• inspections;
• photo documentation;
• geolocation;
• QA;
• revisions;
• invoices;
• compliance evidence.

Keep the RFQ separate from the client program

Prospect:

Need lock changes, lawn cuts and winterizations across 18 counties, roughly 300 orders/month.

Accepted client program may later contain:

Keep both.

The RFQ preserves the commercial request.

The operations system controls the actual program.

• service standards;
• pricing;
• SLAs;
• order channel;
• documentation rules;
• counties;
• escalation.

Keep client and property separate

A servicer may send thousands of properties.

CRM can own:

the institutional relationship

The preservation system should own:

each property and its work orders

Keep work orders specialist

Preserve Solution explicitly manages:

That is not an ordinary CRM workflow.

• work orders;
• vendor dispatch;
• inspections;
• photos;
• bids;
• invoicing.

Keep vendors specialist

ArvoFlow manages:

The website can recruit vendors.

The operational system should decide who gets the job.

• coverage;
• vendor capabilities;
• bids;
• assignment;
• dispatch;
• performance;
• proof.

Keep field evidence specialist

Preservyte and NVMS demonstrate the importance of:

Do not recreate audit evidence as website media uploads.

• standardized photos;
• notes;
• geolocation;
• timestamps;
• reports;
• QA.

Keep bids/estimates specialist

XactPRM supports:

Keep this in the estimating/field stack.

• line-item estimates;
• cost data;
• bid tracking;
• photos;
• job status.

Keep QA and revisions linked to evidence

A failed or incomplete scope may require:

The preservation platform should keep the full chain.

• revision request;
• additional photo;
• corrected work;
• reinspection;
• approval.

Keep invoicing and vendor payment specialist

A completed order can produce:

Keep this in the operational/finance workflow.

• client invoice;
• vendor payment;
• chargeback;
• approved line items;
• supporting documentation.

Keep client and vendor portals authoritative

REOTOOLBOX and other field platforms provide shared client/vendor access to:

If a provider offers a portal, it should read from the operational system.

Do not manually maintain a second status in the marketing site.

• project progress;
• reports;
• photos;
• files.

Use one explicit handoff

Choose:

Property-preservation RFQ/program accepted into field operations

Before handoff:

After handoff:

• website;
• RFQ;
• ordinary prospect/client;
• onboarding conversation;
• marketing source.
• client program;
• properties;
• work orders;
• vendors;
• dispatch;
• evidence;
• QA;
• estimates;
• invoices.

Source-of-truth matrix

A 30-point buyer test

1. Website and preservation platform have explicit roles.
2. RFQ and accepted client program are separate.
3. Client and property are separate.
4. Submitted volume/coverage remain historical.
5. Handoff has one explicit trigger.
6. Client program has one owner.
7. Property has one owner.
8. Work order has one owner.
9. Scope/line item has one owner.
10. SLA has one owner.
11. Vendor has one owner.
12. Vendor coverage has one owner.
13. Assignment has one owner.
14. Dispatch has one owner.
15. Field photo has one owner.
16. Geolocation/timestamp has one owner.
17. Inspection result has one owner.
18. QA decision has one owner.
19. Revision has one owner.
20. Bid/estimate has one owner.
21. Completion has one owner.
22. Client invoice has one owner.
23. Vendor payment has one owner.
24. Public CRM excludes live work-order status.
25. Public CRM excludes property evidence.
26. Public CRM excludes vendor dispatch.
27. Public CRM excludes compliance/QA truth.
28. Website can survive operations-software changes.
29. Public analytics exclude property-level evidence.
30. Staff can explain the boundary in one sentence.

Give the website the institutional opportunity and the field platform the property truth

The public layer should help the provider win the account.

The specialist layer should make every property, order, vendor and proof item traceable.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask