Skip to main content
All CollectionsComparative RatersComparative Rater FAQs
Why isn't 'Occupation' sent to my comparative rater?
Why isn't 'Occupation' sent to my comparative rater?

Learn more about why SALT chose not to send occupation to the comparative raters.

Updated over 6 months ago

You might be wondering why "occupation" data isn't being sent to your comparative rater. At SALT, we aim to ensure all eligible data points are transmitted correctly, but occupation presents a unique challenge.

SALT goes to great lengths to make sure the data we collect is compatible with each comparative rater. For example, gender data can be required in different formats: "Male/Female," "M/F," or "0/1." We ensure every attribute is formatted correctly.

The Problem

When it comes to occupation, each rater has its own long and mismatched list. Some require selecting an industry first, followed by an occupation. This complexity makes it difficult to support accurately.

Our Solution

After months of trying, we decided on a different approach. Instead of not supporting occupation at all, we added a plain text field for occupation and chose not to sync this data with comparative raters.

While this isn't perfect, it allows agents to manually match the occupation to the best of their ability with the rater's options. This decision balances the need for comprehensive data with a smooth user experience.

Did this answer your question?