How PDTF Works
A framework for standardised property data exchange — not a platform, but shared rules that enable interoperability.
The Highway Code Analogy
PDTF works like the Highway Code for property data. Different vehicles, different roads — but everyone follows the same rules.
PDTF
The Rules
Like the Highway Code
Apps
Moverly, Kotini...
Like cars
Data
Property packs
Like passengers
Networks
NPTN, Coadjute...
Like roads
PDTF doesn't replace existing software or networks. It provides common standards so they can all work together.
Participant Roles
The framework defines clear roles for different types of participants in the property data ecosystem.
Relying Party Software Providers
Software that receives, interprets, and stores property data. Examples include conveyancer case management systems and lender platforms.
- • Receive data from the framework
- • Display data to users
- • Store and manage data
Attribute Service Providers
Services that collect, create, check, and share property attributes. This includes search providers, EPC issuers, and identity verification services.
- • Collect property information
- • Verify and validate data
- • Publish to the framework
Orchestration Service Providers
Infrastructure that enables secure data sharing between participants. They provide the "pipes" for data exchange, consensus, and audit trails.
- • Route data between participants
- • Maintain audit trails
- • Enable subscriptions
How data moves through the ecosystem
flowchart LR ASP[Attribute Service Providers (searches, EPC, IDV/AML)] --> OSP[Orchestration Service Providers (networks & pipes)] OSP --> RPSP[Relying Party Software Providers (CMS, lender platforms)] Consumer[Property owner / Consumer] --- ASP Consumer --- RPSP style ASP fill:#E7F7EF,stroke:#38A169 style OSP fill:#EEF2FF,stroke:#4F46E5 style RPSP fill:#EFF6FF,stroke:#2563EB style Consumer fill:#FFF7ED,stroke:#E97B2D
What's in a Property Pack?
The digital property pack covers everything needed for a property transaction, all in standardised formats.
Material Information
Role & Contact Details
IDV and AML
Ownership
Conservation & Listing
Legal Information
Utilities
Title Deeds
EPC
Searches
Survey/Valuation
Mortgage Offers
Provenance: Trust the Data
Every piece of data in PDTF carries provenance metadata — you know who said what, when, and with what evidence.
Levels of Provenance
Plain Data
No provenance attached
Vouched
Seller says "EPC rating is B"
Vouched + Evidenced
Seller says "B" + attached scanned certificate
Electronic Record
Retrieved from propertyInfo.co.uk
Verified Identity Vouched
Verified-identity seller attests to data
Verifiable Electronic Record
Cryptographically verified from gov.uk trusted source
Using the OpenID Connect 'verified claims' standard, provenance is attached at the individual attribute level.
FAIR Data in Practice
PDTF implements the FAIR principles across every aspect of the framework.
Findable
UPRN (Unique Property Reference Number) as global identifier. Supports complex multi-UPRN and multi-title relationships.
Accessible
Standard REST API with OpenAPI spec. POST claims, GET claims/state/provenance, manage subscriptions.
Interoperable
Common data schemas using JSON Schema, standard vocabulary, designed for industry-wide adoption.
Reusable
Data standards plus provenance metadata attached to every data element. Trust follows the data.
Ready to Learn More?
Explore how PDTF benefits your role in the property ecosystem, or dive into the technical documentation.