Tools and providers
Part of Procurement framework for property media workflows using official records as evidence
Property creators tool implementation: test gates
Property creators tool implementation: rehearse CRM, portal, video and social workflows on synthetic data, testing claims, rights, access and release gates.
Property creators tool implementation should prove a reversible workflow before live addresses, footage or enquiries enter it. The test should follow one asset from authorised intake through claim checking, accessible production, specialist approval, publication, correction, export and deletion. Passing a feature demo is not a release decision.
What to take away
- Prove a reversible workflow before live addresses, footage or enquiries enter the tool.
- Separate roles in the permissions model so only the administrator configures and the publisher releases.
- Build four linked control maps covering claims, rights, data and release before upload.
- Test the full audience journey, including accessibility and disclosure, not just the feature demo.
- Live property work stays on hold until every non-compensating gate is cleared.
Set the test boundary
Use a fictional address and claim set with licensed stock media, or material specifically authorised for the exercise. State the England operating context, intended adult audience, channels, product edition, configuration, integrations and excluded activities. Do not use a real access code, occupier detail, applicant record or unapproved interior image.
Roles and Permissions
Role
- Service owner
- Rollback authority
- Administrator
- Configure service
- Publisher
- Release output
- Reviewers
- No silent edits
- Privacy lead
- Data oversight
- Security lead
- Access control
Permission
- Service owner
- Administrator
- Publisher
- Reviewers
- Privacy lead
- Security lead
Assign a service owner, administrator, property evidence editor, media-rights owner, privacy lead, security lead, accessibility tester, publishing operator and independent release approver. Separate these roles in the permissions model. Only the administrator may configure the service; only the designated publisher may release; reviewers should not silently edit approved wording.
Build versioned control maps
Create four linked records before upload:
- The claim map connects each sentence to a property identifier, source, edition, geography, date, limitation, reviewer and expiry.
- The rights map records owner, licence, appearances, territory, channels, duration, permitted edits and withdrawal contact.
- The data map lists personal fields, purpose, lawful basis, controller, processor, location, access, retention and deletion route.
- The release map records commercial classification, disclosure, qualified reviews, accessible alternatives and publication destination.
Rehearse the property workflow
With roles assigned and the four maps built, test the actual service and edition against a connected property-marketing workflow, using only synthetic records and authorised stock:
- CRM intake:create a fictional listing record, map its fields to the claim map, and check role restrictions and the audit trail.
- Video editor and digital asset management (DAM):edit an authorised stock asset, attach rights and expiry metadata, and confirm that an unlicensed source cannot proceed.
- Listing-portal upload and social scheduler:send drafts only to a closed destination; check that listing information, price and claim qualifiers, and advertising disclosure survive the preview, and that publication remains blocked pending approval.
For listing information, check the National Trading Standards Estate and Letting Agents Team material information guidance, Parts A, B and C, and the Digital Markets, Competition and Consumers Act 2024. Test that material information and price or claim qualifiers are not omitted, and that misleading claims, drip pricing and fake-review risks are flagged before approval.
Run the gates in that order, then carry the approved draft into the closed-destination failure and exit tests below. The configured product, integrations and templates must preserve the records and release blocks; a category demo alone is not acceptance.
If HM Land Registry Price Paid Data is used in the synthetic claim exercise, preserve its England-and-Wales scope and published exclusions. Do not transform a recorded transaction into a valuation or a statement about current availability.
Configure and challenge access
Enable least privilege, multi-factor authentication, named accounts, short-lived guest access, audit logging and an approved integration list. Remove public-link defaults where the workflow does not require them. Test that an unapproved reviewer cannot download raw media, change the source card or publish.
Apply the security requirement in UK GDPR Article 32: measures must be appropriate to the risk and include technical and organisational measures. The ICO's Article 32 enforcement case records a reprimand after inadequate security measures enabled personal data to be exfiltrated. Record the exact control, tester, time, evidence and defect owner. Revoke a user and integration, then confirm what access and cached copies remain.
Test the complete audience journey
Produce a captioned asset and transcript. Check keyboard navigation, screen-reader order, zoom, contrast, form labels, errors and focus. Test the review interface as well as the public output. A supplier accessibility statement cannot demonstrate that the team's template, plug-ins and configuration work together.
For a synthetic sponsored asset, verify that the disclosure remains prominent in the preview, published view, excerpt and repost. CAP's recognising ads guidance says platform tools may not always be enough. Stop if truncation, overlay or format change hides the approved wording.
If copy is a financial promotion, a named FCA specialist must assess the communication and linked journey against FG24/1 and check the restriction in section 21 of the Financial Services and Markets Act 2000. Where approval by an authorised person is required, retain the approval against the exact final communication and linked journey. Property, consumer, privacy, rights and accessibility clearances remain separate.
Rehearse failure and exit
Publish only to a closed test destination. Introduce an expired source, wrong permission and unavailable integration. Confirm that the team can block release, identify affected assets, correct the record, withdraw the output and preserve an incident trail.
Use the NCSC's response and recovery guidance to assign reporting, containment, recovery and lessons. Export files, metadata, comments, approvals, rights and logs. Restore them outside the supplier account and compare counts and hashes. Then run the documented deletion process and record any retained backup or legal-hold limitation.
The service owner has rollback authority when access, evidence, disclosure, accessibility, export or recovery fails. Restart requires the defect owner to supply evidence, the relevant specialist to approve it and an independent retest to pass. Record the accepted configuration, residual risks, renewal date and change triggers. Live property work remains on hold until every non-compensating gate is cleared.
Before you act
- Use a fictional address and licensed stock media.
- Assign named roles and separate them in permissions.
- Create claim, rights, data and release maps.
- Test keyboard, screen-reader, zoom and contrast.
- Publish only to a closed test destination.
- Export and restore records, then run deletion.
Common questions
What should the test boundary exclude?
Do not use a real access code, occupier detail, applicant record or unapproved interior image. State the England operating context, intended adult audience, channels, product edition, configuration, integrations and excluded activities. Use a fictional address and claim set with licensed stock media, or material specifically authorised for the exercise.
What must the release map record?
The release map records commercial classification, disclosure, qualified reviews, accessible alternatives and publication destination. It is one of four linked records created before upload, alongside the claim map, rights map and data map. Only the designated publisher may release, and reviewers should not silently edit approved wording.
When does the service owner have rollback authority?
The service owner has rollback authority when access, evidence, disclosure, accessibility, export or recovery fails. Restart requires the defect owner to supply evidence, the relevant specialist to approve it and an independent retest to pass. Record the accepted configuration, residual risks, renewal date and change triggers.
