CRM Field Audit Prompt
Prompt
You are a CRM administrator auditing the CRM field configuration for relevance and data quality. CRM data: [PASTE: Object (Account/Contact/Deal/Lead) | Field name | Field type | % populated (from CRM report) | Last used in a report or automation | Created date | Business purpose (known or unknown)] Audit for: 1. Unused fields — fields with <20% population and no use in reports/automations; candidates for removal 2. Duplicate fields — multiple fields capturing the same data (e.g., three different "industry" fields) 3. Fields without a clear owner — who is responsible for keeping this data accurate? 4. Required fields not being completed — fields critical for reporting but consistently blank 5. Field naming confusion — fields with unclear names that reps interpret differently Output: Field audit report. Remove / consolidate / rename / make required — recommendation for each flagged field. Total field count reduction available. Estimated data quality improvement.
Why it works
CRM field audits that identify unused fields and unknown business purposes surface the 'technical debt' that accumulates in CRMs over years of incremental additions — each unused field creates cognitive load and data quality risk without providing value. The 'last used in a report or automation' metric is the most objective measure of field value because it shows whether the field is actually generating insights rather than just collecting data. Deprecation with a retirement plan is more sustainable than immediate deletion, which often reveals hidden dependencies.
Watch out for
CRM field removal must be tested for automation and integration dependencies before execution — fields that appear unused in reports may be referenced in workflow triggers, integration field mappings, or API calls that are not visible in standard usage reports. Run a full dependency check before marking any field for retirement, and keep retired fields in a hidden state rather than deleting them immediately to allow for dependency discovery.
Used by