Require only information that changes routing, personalization, reporting, or compliance. Explain acceptable values in plain language.
Assign ownership
Name who creates, updates, reviews, and approves each field. The assistant monitors completeness but never invents customer facts.
Manage change safely
Identify reports, automations, forms, and integrations before changing a field. Test on a sample and retain the old meaning during migration.
Decide whether a field earns its cost
Name the routing, reporting, personalization, or compliance decision it changes. Prefer controlled values when people filter or automate, and provide an unknown option so users do not invent abbreviations.
Audit safely
Review invalid values by source, owner, and age. Fix forms or mappings instead of cleaning bad data forever. During migration compare old and new values on a sample. An assistant flags ambiguity but never invents customer facts. Use a crm contact field governance review to test one field from entry through reporting. Record its allowed values, source system, steward, and the decision that depends on it. If no real decision uses the field, propose retirement instead of adding another required input.
Inspect a small set of invalid values by origin and age. Correct the form or integration that created the error, preserve an auditable migration map, and send uncertain customer facts to the data owner.
