What the Material Information rules mean for estate agents in 2026

The material information landscape for UK estate agents in 2026 is more complicated than it should be. The National Trading Standards Estate and Letting Agency Team (NTSELAT) three-part guidance that gave many agencies a clear checklist has been withdrawn, but the Consumer Protection from Unfair Trading Regulations 2008 (CPRs) that underpinned it remain fully in force. What the material information rules mean for estate agents in 2026 is, in short, that the legal exposure is unchanged and the signposting has gone. Agents cannot wait for new formal guidance and assume nothing applies in the interim. A buyer who misses a critical piece of information about a property, and later shows they would not have proceeded had they known it, still has grounds for a complaint under the CPRs regardless of whether any checklist told the agent to include it.

Why the withdrawal of NTSELAT guidance has not removed the risk

The NTSELAT Parts A, B and C framework was not the source of the legal obligation. It was an interpretation of what the CPRs require in a property context. Part A set out minimum information for all listings: price, tenure and council tax band. Part B expanded this to physical characteristics including construction type, internal dimensions, EPC rating, utilities, heating type and parking. Part C covered issues a buyer would consider material: flood risk, ground stability, building safety, planning restrictions, rights of way and, for leasehold properties, lease length, service charge and ground rent terms.

With that guidance withdrawn, the CPRs still require that agents do not omit information a buyer would consider material to their purchasing decision. The test is not whether the information appeared on a checklist. It is whether a buyer, knowing that the property was in a flood risk zone or sat on a short lease, would have made the same decision. Trading Standards retains the power to investigate and prosecute under the CPRs. Property portals continue to apply their own listing requirements for fields introduced during the NTSELAT era. An agent who stops completing those fields on the basis that the guidance has gone is taking a risk the withdrawal was not intended to create.

For lettings, the position is similar. Requirements to include EPC ratings, licence status, deposit terms and permitted fee disclosures sit partly in separate legislation and partly in the CPRs. Neither set of obligations changes because the NTSELAT framework has been removed.

What AI can actually do here

The gap in material information compliance is rarely an agency's unwillingness to include the right data. It is the friction of capturing it consistently across every instruction. A negotiator working on fifteen active listings, handling portal enquiries and running valuations is not going to complete every CRM field without prompting. The information is often available but not entered, and the result is a listing that goes live with gaps the agency does not know are there.

The fix follows the same event-triggered loop that Sortd applies across its estate agency automation: trigger, read context, reason, take action, log.

Trigger. When a property record moves to an active listing status in the CRM, the agent fires. The check happens at the point the listing is about to go live.

Read context. The agent pulls the property record and checks it against a configurable set of required fields. For a residential sales listing, this covers tenure, council tax band, EPC rating, construction type, leasehold terms if applicable, flood risk zone and any logged planning restrictions. The required fields are agreed with the agency at build and can be updated as portal requirements evolve or as the agency's own compliance policy is reviewed.

Reason. The agent identifies which fields are missing or flagged as incomplete. It does not attempt to fill them in. That task requires information from the vendor, the local authority or a physical inspection, and it belongs to a person. The AI's job is to catch what is absent before the listing goes live, not to generate answers for fields that need verification.

Take action. Two outputs run in parallel. The negotiator receives a Slack message or email listing the gaps for that specific property and a suggested action for each one. The vendor receives a draft message requesting the missing information, written in the agency's tone and referencing the property. That draft passes through the same approval layer used across Sortd's vendor updates and inbox copilot builds. The negotiator reads it, edits if needed and approves. Nothing goes to the vendor automatically.

Log. The compliance check is written back to the property record in the CRM: which fields were checked, which were missing, what messages were sent and when. If a buyer later raises a CPR issue, the agency can show the check was run and document when the information was obtained and by whom.

What it looks like for an agency

A five-branch independent running eighty active sales instructions. A negotiator adds a new listing on Alto: a three-bedroom semi-detached on a modern estate. The record goes to active status at 4:30pm.

At 4:32pm, the negotiator receives a Slack message. The listing is missing the council tax band, flood risk zone confirmation and a note on parking. The EPC is present. Tenure is freehold and logged. The message includes a draft email to the vendor requesting the three items, with a short note explaining that the council tax band is also available from the local authority's public database if the vendor does not have it to hand.

The negotiator adjusts one sentence in the draft and clicks send. The vendor responds the following morning. The fields are completed before the listing is promoted to Rightmove, Zoopla and OnTheMarket.

The log entry on the property record shows when the gap check ran, which three fields were missing, the date the information came back and which negotiator approved the outbound message. If Trading Standards or the TPO ever ask, the audit trail is there.

Once the listing is complete and accurate, any lead qualification on buyer enquiries is working from a record the agency is confident is correct, which matters when the AI is helping a negotiator respond to questions about the property's tenure or flood history.

Compliance and integration reality

The AI processing involved in a material information compliance build touches vendor contact data, property records and communication logs. Under UK GDPR, this requires a documented lawful basis. Legitimate interests is the appropriate basis for compliance-related data processing: the agency has a clear obligation, the processing is proportionate, and it is in the interests of both the vendor and any prospective buyer that the listing is accurate. A Legitimate Interests Assessment should be written and held on file before the agent operates on live data.

A signed Data Processing Agreement with the AI provider is required before any client data is transferred. Data must be held within UK or EU infrastructure. Sortd runs on UK and EU servers by default.

The TPO code requires that property listings are accurate and not misleading. A material information check catches missing data. Verification of the accuracy of information received from vendors remains a person's responsibility. The AI does not sign off on what the vendor tells you.

CRM integration covers the platforms UK independent agencies use most: Alto, Jupix, Reapit, Vebra, Dezrez and agentOS. The compliance field configuration adapts to each CRM's data model.

The Consumer Protection from Unfair Trading Regulations 2008 is the authoritative legal text. Property Industry Eye carries regular coverage of Trading Standards enforcement activity and the evolving portal requirements that followed the NTSELAT guidance.

Approaching material information as an estate agent in 2026

The practical starting point is a field audit. Pull a sample of twenty active listings from your CRM and check each against the fields that Parts A, B and C required, treating those as a working proxy for what a buyer would reasonably consider material. Count the gaps. The result will show whether you have a systematic problem with specific field types, a volume issue that better tooling can address, or a knowledge gap that needs training rather than automation.

If the audit reveals consistent missing fields, an AI compliance check at the point of instruction is the most direct way to close it. Sortd builds a working version of the compliance loop against your CRM and listing workflow at no cost before any build touches live data. You define the required fields. You approve every vendor message. The check runs automatically on every new instruction.

If you want to see what that looks like against your own listing data, book a discovery call.