The Unique Licensee Identifier

One stable identifier for each licensed real estate professional, carried alongside the identifiers everyone already has.

A licensee working several markets holds a separate record in each, created independently and under names and office affiliations that rarely agree. Production splits across them, data shares carry every version, and no back office can reconcile them. Nothing identifies the records as one licensee.

The RESO Unique Licensee Identifier (ULI) is that identifier. It links a licensee’s records across markets and systems. It does not merge them and it replaces nothing: every record keeps its own identity and its own local ID.

How It Works

No central database. A participant asks the network whether anyone already holds a licensee. Every participant answers from its own data, and the network itself stores nothing.

Matching is evidence, not a guess. Each identifier that agrees counts according to how much it narrows the field. Two strong identifiers are always required, and one alone is never enough.

Each identifier proves its own origin. A ULI is signed by the organization that created it, and an authorized party holding the identifier can confirm that signature without calling anyone.

Documentation

• White PaperThe problem, the business case and what the ULI does and does not do.
• MethodologyHow a licensee is resolved, step by step, with the protocol detail for implementers.
• SpecificationThe ULI Resolution Protocol, RCP-54, as proposed on RESO Transport.
• GuideRun a node, load a roster and resolve a licensee, task by task.

Playground

A browser playground runs the matcher on sample data, or on a roster imported as a CSV file or as the pilot’s template workbook. Nothing loaded into the page leaves the browser, and the page has no means of sending it anywhere.

Pilot Program

An earlier pilot ran against real licensee data and has been taken down. RESO is rebuilding it on the protocol as specified. Contact RESO to take part.