Property creators software selection: a pass or fail gate per risk

Property creators and estate agents choose software for one property-media job, not a feature comparison. Define how an authorised fact and media asset move from a client in England through verification, editing, specialist review, publication, correction and deletion. Then reject any product that cannot preserve the evidence and permissions at each hand-off.

For real-estate creators and agent marketing, this is campaign infrastructure. The software shapes listing media, walkthroughs, agent branding and lead follow-up. A failed control lane can stall a launch, expose a client or weaken an agent's market position. Treat each risk as a pass or fail gate before live property enters the system.

What to take away

Write the workflow boundary

Name the commissioning organisation, property identifier, English location, adult audience, channels and deliverables. Separate independent editorial, paid production, advertising, lead collection and any mortgage or investment language. Record excluded work such as valuation, surveying, negotiation, applicant screening and financial advice.

Create a lane for each control: property facts, media rights, personal data, editing, approvals, disclosure, accessibility, publishing and enquiries. A single application may support several lanes, but its convenience must not combine the decisions. An editing approval is not evidence that a property statement is accurate.

HM Land Registry says its Price Paid Data covers sales for value lodged for registration in England and Wales, has exclusions and can be incomplete for recent periods. If the workflow uses it, require the exact edition, transaction row, extraction date and stated limitation. Never let an automated lookup present the result as a current valuation.

Turn risks into pass or fail requirements

For each lane, record the owner, the evidence artefact and the release condition in one control register: one row per lane, with the gate wording written in the same row. Each requirement is binary, so it passes on named evidence or it fails. Nothing is scored out of ten, and an unanswered question is a failed gate. Useful requirements include:

Make privacy requirements specific. List contacts, appearances, addresses, access instructions, enquiry fields, device records and analytics. The ICO's processor-contract checklist identifies terms that must be covered when a processor acts for a controller. Match those requirements to the executed agreement, including subprocessors and end-of-contract treatment, and check them against the agency's own duties as controller under UK GDPR and the Data Protection Act 2018.

Evaluate the purchased edition

Record supplier legal entity, product name, edition, enabled add-ons, user count, billing route and renewal date. For every claimed feature, cite the current first-party service description that applies to that edition. Note whether the feature is configurable, restricted by role, excluded from the plan or dependent on another service.

The same register applies whichever category the shortlist covers: estate agency CRM and listing platforms, digital asset management and media approval tools, virtual tour and floorplan producers, and the storage, backup or enquiry-handling services attached to them.

Do not award points for unexamined labels such as secure, compliant or accessible. Ask for contract terms, data locations, remote-support access, transfer mechanism, audit or test scope, incident notice, service commitments, a WCAG 2.2 AA accessibility conformance report for the edition being bought and the deletion process. An unanswered non-compensating question remains a failed gate rather than a low score.

Trial without live property risk

Use a synthetic address, fictional claim data and licensed test media, or assets specifically authorised for the exercise. Configure least privilege. Run source-to-claim traceability, approval, disclosure, caption, transcript and enquiry-form tests. Attempt unauthorised access and publication. Export the full record, delete the test workspace, then restore the export in a separate location.

The NCSC advises small organisations to address backups, malware, devices, passwords and phishing. Convert that advice into named test cases and evidence rather than assuming cloud storage is a backup.

Define stop conditions before the trial: missing rights, a broken accessible journey, unclear processing terms, failed audit history, incomplete export or unresolved privileged access. The service owner records the decision and expiry. Qualified reviewers must clear the actual property, advertising, FCA section 21 financial-promotion sign-off, privacy, rights, security and accessibility boundaries before live material enters the system.

Common questions

How should Price Paid Data be handled in the workflow?

Treat it as a property-facts gate. The software must be able to attach the edition, the transaction row and the extraction date from HM Land Registry Price Paid Data to the claim it supports, and must carry the stated exclusions and the known incompleteness for recent periods. A product that can only pull a figure without those fields fails the gate, and the claim must not be published as a current valuation.