What This Domain Tells You
Properties checks look at field usage, population coverage, label ambiguity, hidden dropdown values and descriptions. They assess the recorded structure and data, not the business value of every custom field.
Before You Assess
Use the correct CRM object and property inventory. Review coverage thresholds where offered. Workflow-referenced fields receive particular attention because automation depends on them.
Checks In This Domain
Your results cover only the checks selected for the assessment and supported by its evidence.
| Check | What It Looks For |
|---|---|
| Custom Properties Have Recorded Values | Each custom property has at least one populated value in the collected object population. |
| Operational Properties Meet Population Coverage | Each workflow-referenced property meets the configured population coverage percentage in the collected object population. |
| Property Labels Are Distinct | Each custom property has a distinct normalized label within its object. This checks label ambiguity, not duplication of business purpose. |
| Dropdown Option Labels Are Unambiguous | Different stored dropdown values must have distinct normalized labels. |
| Records Use Available Dropdown Options | Collected records must not retain hidden dropdown option values. |
| Operational Properties Have Descriptions | Each workflow-referenced custom property must have a nonblank description. |
How To Use The Findings
Review low-use fields with their owner before deleting anything. Fix ambiguous labels and describe operational properties. Preserve dependencies and reporting needs when replacing dropdown values.
Read The Outcome Correctly
A confirmed issue means a stated requirement was not met. A review indicator needs business context. Unavailable evidence or history means the outcome could not be established; it is not an automatic failure. Read coverage alongside any score.