How the New Home Buying System Fits Together

A lot of new language has arrived in home buying at once. Smart Data, data standards, trust frameworks, data exchange, orchestration, open-loop and closed-loop. It can sound like a wall of jargon, but underneath it is a simple idea wearing technical clothes.

Most of us already use this system in our daily lives. When you tap your card in a shop, or email someone who uses a different provider, a lot happens underneath that you never see, and it works because everyone agreed on a few shared rules. The future of home buying is being assembled on the same principle. Here is the whole thing, one layer at a time.

The layers, from the ground up

Picture a stack. At the bottom is the raw material. At the top is the experience the customer feels. Each layer does one job.

Smart Data

What it is: the secure, consent-based sharing of your (customer or business) data with authorised third-parties.

A real-world example: when you authorise a business to see your bank transactions because you gave it permission via Open Banking.

A home-buying example: you prove who you are once, and that proof (the validated check, not the documents themselves) can be reused, instead of digging out your passport and a utility bill for the agent, then the broker, then the lender, then the conveyancer.

Smart Data in home-buying:

The buyer or seller

• Verified identity result
• Proof of address
• Source of funds / source of wealth evidence
• Bank and transaction data
• Credit score
• Consent records (what the customer has agreed to share, with whom, and for how long)

The property

• Title and ownership data
• Tenure and lease terms
• Boundaries and geo-spatial data
• Existing charges and restrictions
• EPC
• Planning history, building control and permitted development
• Searches: local authority, environmental, water, draining, flood risk
• Council tax band

Mortgage

• Decision in principle and product details
• Valuation result
• Mortgage offer
• Existing charge or redemption figures

Data standards

What it is: an agreed-upon set of rules and conventions that define how data is structured, formatted and shared so that data collected in one system can be reliably interpreted or shared with other systems. It is the difference between everyone filling in the same form and everyone inventing their own.

A real-world example (format): when asked for your DOB, forms can vary in format from DD/MM/YYYY or DDMMYY or DD MM YY. With a data standard, the format will be the same across all data – e.g. using ISO 8601 for dates such as YYYY-MM-DD

A real-world example (structure): think of a contact record in your phone. It’s one person with separate labelled fields that include name, surname, mobile, email, home address. That contact can be shared across devices and operating systems, so it works whether you’re accessing it on iOS or Android.

Data standards in home-buying:

Format

• UPRN (Unique Property Reference Number)
• Postcode Address File
• EPC rating A – G / 1 – 100 score
• ISO 8601 date format
• Whole number and currency prices (250000 GBP)
• QES (Qualified Electronic Signature)

Structure

• Property information – tenure, EPC, council tax band, title number
• Property title – proprietor(s), UPRN, charges and restrictions
• Property lease – term, ground rent, service charge
• Material Information – Trading Standards Parts A, B and C
• Protocol forms – TA6, TA7, TA10, TA11

Trust framework

What it is: an agreed set of rules, governance and protocols that allow organisations, systems and individuals to safely interact and share data as a foundation of ‘digital trust’. It ensures all participants in a digital ecosystem play by the same rules.

A real-world example (structure): now fully digital, your car MOT is a great example of a Trust Framework we all use today. If you buy a used car, you trust the MOT certificate because it was issued by an approved test centre that follows a defined standard, the centres are audited and it’s used by insurers, the police, DVLA and new buyers. It’s not the MOT test itself; it’s the scheme that defines who can provide the service and how everyone else relies on the result.

Trust Frameworks for home buying:

• Accreditation rules – who can provide data and the bar they must meet
• Approved register – a live list of who currently holds accreditation
• Removal and audit – how participants are monitored for adherence
• Defined credentials – what checks the framework covers
• Reliance rules – explicit rules that a check meets the standards for reuse
• Issuer and timestamp – who verified the data and when
• Tamper evidence – proof the result hasn’t been altered since issue
• Audit trail – record of use downstream so trust is traceable
• Customer authority – a record of consent for data sharing
• Scope and expiry – what the consent covers and how long it lasts

Data Exchange

What it is: a digital rail for transferring information between different systems, organisations or stakeholders, that’s structured and secure.

A real-world example: whenever you tap your card to pay in a shop, that interaction travels from the shop’s bank (to request the money) to your bank (to acknowledge the request) back to the shop’s bank (to complete the payment), all in a matter of seconds. The transaction travels across institutions that have no direct relationship to one another, but they all connect to the same network, where the data moves along the rail.

Data exchange in home buying:

• Connection: a single connection for each organisation to the exchange
• Requests: APIs that request and return data automatically
• Payload: verified checks, property, transaction and mortgage data

Orchestration

What it is: the automated management, scheduling and monitoring of data pipelines, where multiple independent steps (pulling data, organising data, providing data) are coordinated to manage dependencies, automate execution and handling errors.

A real-world example: Air traffic control is a great example. Planes are independent of one another (owned by different airlines and individuals), and don’t answer to one another. In the air and at airports, they need precise coordination to ensure timetables are maintained, safety is upheld, and unpredictable events can be navigated. Every air controller and pilot work off the same radar state (data exchange) for a shared, live picture of what’s happening. Air traffic control doesn’t fly the planes, it coordinates the pilots.

Orchestration in home buying:

• Instructs each step in the right order: data, decisioning, facilitation, settlement
• Triggers the next step automatically
• Handles dependencies such as knowing what must finish before the next thing can start
• Manages exceptions if a step stalls or fails

The complete picture for home buying

• Smart Data is the raw material
• Data Standards and Trust Framework provide the aligned structure, format and rules to create secure parity for all participants
• The data exchange provides the rails for the data to move
• Orchestration coordinates and sequences the transaction
• Converge below, compete above

Design decisions: open loop versus closed loop

There is no right or wrong answer when it comes to designing or choosing open loop or closed loop access to the home buying infrastructure. But there are important differences.

Closed Loop

A closed loop is a system where everyone takes part through the same product.

Benefit: because everything sits inside one product, it can be tightly integrated and quick to get working, and one provider is accountable for the whole thing.

Trade-off: it works for the parties on that product, and not beyond it, so reach becomes the critical success factor.

Real world examples:

• A store card, gift card or loyalty card
• WhatsApp, iMessage, FaceTime
• Fitness tracking apps or devices

Closed loop in home buying:

• Member only participation
• Hard edge to data transfer beyond the product or platform
• Rules governed by the operator

Open Loop

An open loop system is a shared set of rules that everyone follows, so different systems work together without anyone joining a central product. There’s no hub in the middle.

Benefit: anyone who follows the shared rules can take part, whatever system they use

Trade-off: it needs agreement on common rules first, which can be slower to establish

Real world examples:

• Sending an email where you are with Gmail, and the person you are emailing is using Hotmail. Your messages reach each other because email is an open standard rather than singularly owned
• Paying by card works in almost any shop, on almost any terminal, because they all sit on the same open network

Open loop in home buying:

• Any and all participants, provided they align to the shared standard
• Verified results travel to any firm that meets the shared standards
• An open directory where you choose your participants and journey

HDI (Horizontal Digital Integration)

You now have the parts: Smart Data, standards, trust frameworks, the data exchange, orchestration, and the open-or-closed choice that decides participation. What none of that tells you is how to put them together, because these are component parts, not a purchase decision. That is an operating-model question that Horizontal Digital Integration designs: not another layer in the stack, but the operating framework that wraps around it. HDI defines how you combine and govern the layers, which loop and standards you commit to, and how you redesign your own journey, so a check done once upstream is trusted rather than repeated. The infrastructure is here; HDI is how you implement it.