What We Heard at RESO: Are We Ready to Add/Edit?

A RESO roundtable on why the Add/Edit standard sits unused, and what could finally move listing entry forward.

Briefs · Short takes, event notes and quick guides.

Brokers have wanted flexible listing input for decades. A RESO standard to support it has existed since 2013. Almost nobody uses it. At RESO in Colorado Springs on October 21, we facilitated a roundtable to find out why.

The room was mostly MLS technology and product leaders, several from markets already running data shares, plus a listing-data vendor and a technologist from outside the industry. What follows is what we heard. No one is named; the roundtable ran on candor.

The standard exists. Adoption is close to zero.

The consensus was that the current Add/Edit standard is a good base that stalled. It was written in 2013 and hasn't evolved. Its syntax follows older RETS-era conventions, and no parser is available for it, so every implementer has to build their own interpreter before writing a line of product. The community has been extending it on its own, outside the spec, which is a sign of demand, not satisfaction.

One participant is preparing a proposal to rebuild it on an existing open-source JSON library that already has parsers in most languages, extended only where real estate needs it.

Agents aren't waiting

The urgency has shifted. Agents are building their own listing tools with AI, sometimes using their own MLS credentials. Brokerages are encouraging staff to build internal software. Large brokerages are asking MLSs directly for an entry path that bypasses double entry. One MLS leader put the choice plainly: get in the way, or make it work.

The question is no longer whether multiple tools will touch the MLS record. It's whether they'll do it through a governed, compliant door.

Compliance belongs at entry

Most validation today happens after submission, in listing data compliance review, once bad data is already in the system. The room wanted the same rule set to run on the front end, in whatever tool the agent uses, and again on the back end, so a listing that passes in the tool passes at the MLS.

That sounds simple until you hit the details. Different programming languages disagree about what "empty" means. A shared rules standard has to define null, blank and missing in a way every language handles the same. One MLS ran a proof of concept for a single status change using the existing RESO metadata, and front-end validation worked with no round-trip errors. A full listing is a much bigger job.

The 90% problem

A hybrid approach came up: validate the simple rules immediately and leave the complex ones for submission. The pushback was experience-based. When tools ship at 90% coverage, the missing 10% is what users remember, and adoption stalls.

A sharper split also emerged. Quick edits, like canceling an open house on a Saturday, are common, low-risk and a far easier win than full listing creation. Separating origination from edits may be the practical place to start.

Why it hasn't happened

Demand math. A vendor serving hundreds of MLSs won't prioritize something only one is asking for.
Legacy technology. One vendor quoted three to four years just to support Add/Edit on its current stack.
Gatekeeping. Some platforms charge heavily for input access, which locks out everyone else.
Rules held close. Some MLSs don't manage their own business rules or can't access them. Some don't want to share them.

What could break it loose

Decentralized rules, shared interface. Each MLS hosts its own rules endpoint, and the tool calls the right one based on which MLS the listing belongs to. The spec already supports this pattern.

A common core. Identify the fields every MLS shares, make that an open core, and let each MLS extend it.

A collective ask. Platforms consistently say they'll build what their customers request. Enough MLSs asking for the same thing changes the demand math. Broker pressure may get there first.

A precedent closer to home. In New York, the board sets one schema and submission method, and 11 different front ends work from it. Imperfect, but working.

A neutral governing body. Other competitive, regulated industries, from finance to travel, solved standardization by creating mixed-stakeholder bodies with ongoing authority. Our industry has the stakeholders. It doesn't yet have that structure for listing entry.

What it means for leaders

Add/Edit isn't a technology problem waiting for better technology. The tools are closer than they've ever been. It's a coordination problem, which means MLS leaders have more leverage than they think. The group agreed the feedback belongs with RESO's Transport workgroup and that the standard needs a working group behind it again.

Three questions to take back to your own organization: