Fast Track Mapping Workflow

DD 2.1 Documentation

When certification flags a resource, field, expansion or lookup value that a provider sends, these questions decide what happens next. They summarize the Fast Track Mapping Workflow. The examples are from Data Dictionary 2.1.

Local The provider’s own name or valueStandard A Data Dictionary elementSynonym Cannot stay
Certification flags something a provider sendsIs it a name or a lookup value?

A Resource, Field or Expansion Name

Is it a field the Data Dictionary records as a synonym of a standard field?Expansions are fields, so their recorded synonyms count too.
Yes If yes:
Disallowed

Serve the standard field

A disallowed synonym cannot stay, even as a local field.

Property field
ListingStatus→MlsStatus
Property expansion
GreenBuildingRating→GreenBuildingVerifications
No If no, the next question.
Can it map to a Data Dictionary resource or field?A local resource or field that a standard one covers.
Yes If yes:
Map and keep

It must map, and the local one may stay

Serve the Data Dictionary resource or field. The provider may keep its local one alongside it.

Resource
Listing→Property
A Listing resource that looks like the Property resource is flagged and must map. Listing may stay alongside it.
Resource
Agent→Member
No If no, the next question.
Otherwise:
May stay

Local resources and fields may stay

Providers may always add resources and fields the Data Dictionary does not have. A local name for a standard expansion may stay, as long as the standard expansion is provided too.

A Lookup Value

Is the enumeration closed?A closed enumeration takes no local values.
Yes If yes:
Required

Data Dictionary values only

StandardStatusclosed · single
Only its 11 values. A local status goes in MlsStatus, and each one maps to a single StandardStatus.
No If no, the next question.
Does a Data Dictionary value’s definition cover it?The same thing, or a more specific kind of it.
Yes If yes:
Map and keep

Send the Data Dictionary value and keep the local one

In a multiple enumeration the local value may stay alongside it. In a single enumeration the standard field carries the Data Dictionary value, and the local value may go in a local field.

Pellet Insert→Insert
Insert is “a device inserted into an existing masonry or prefabricated fireplace,” so it covers a pellet insert. Insert is sent, and Pellet Insert may stay alongside it.
Special Residential→Residential
Residential goes in PropertyType. Special Residential may go in a local field.
No If no, the next question.Check the definition, not the name. A Garden Tub is not a Soaking Tub.
Is it more general than the Data Dictionary’s values?A broader term than any standard value.
Yes If yes:
Map where supported

Map to the specific value the data supports

A general term in common use that the Data Dictionary does not have is considered case by case.

LotFeaturesmultiple
Sprinklers→Sprinklers In Front
Sprinklers is broader than Sprinklers In Front or Sprinklers In Rear. Sprinklers may stay, and Sprinklers In Front is sent alongside it only when the listing says the sprinklers are in front.
No If no, the next question.
Otherwise:
Fast Track

No Data Dictionary value fits: send it to Fast Track

Every case starts with usage analysis across providers and markets. It presents the facts. Usage alone does not decide; it is analyzed in the groups.

What Fast Track approves is for the next major version. Providers may adopt it now, and certification warns them about approved items that will affect them.

Versions and Decisions

Today’s mappings are frozen

The Fast Track mappings providers are flagged on today were approved before DD 2.0 was ratified.

Changing one would change the testing rules on an existing element, which only a major version may do. A request to change one comes back to Fast Track.

When the flag itself is wrong

False positive. A provider fails when it should pass. RESO fixes it.

False negative. A provider passes when it should fail. It goes to the Transport Workgroup.

Never a reason by itself

Being more specific is never, by itself, a reason to ignore a flag.

Usage alone does not decide. It is analyzed in the groups.

Existing ignores and the monthly review

Existing ignores stay in force through DD 2.x. Revisiting them is a DD 3.0 question.

Each month, RESO brings the items sent to Fast Track, with their review history and significant comments.

Source: RESO Fast Track Mapping Workflow. Element names, definitions and enumeration types from Data Dictionary 2.1.

Terms and DefinitionsGenerated November 19, 2026
🔍

Search across all Data Dictionary resources, fields and lookup values.

Press Esc to close

No results found. Try a different search term or filter.

Data Privacy

This site uses Google Analytics to understand which pages and search queries are most useful so the documentation can be improved over time.

No personal data is collected and no individuals are tracked. IP addresses are anonymized.

For RESO's full privacy practices, see the RESO Privacy Policy (PDF).