governed-crm-cleanup

Use this when CRM defects affect routing, reporting, pipeline reviews, or execution. Produce a baseline, an operation-level correction plan, a verified result, and a prevention backlog.

Establish the baseline

1. Snapshot the affected objects, field definitions, owners, pipeline stages, and automation rules before proposing changes. Record the extraction time and record counts.
2. Define each audit check as an explicit rule with a target population, condition, severity, and evidence. Cover duplicates, ownership gaps, stale pipeline, critical-field completeness, stage conformance, and integration drift.
3. Count findings by object, rule, owner, source, and age. Separate isolated bad records from systematic failures created by imports, forms, integrations, or team behavior.
4. Preserve ambiguous findings. An audit should expose uncertainty rather than convert it into a confident correction.

Use references/audit-rubric.md to score severity and choose the first batch.

Build the change plan

Represent every proposed change as one reviewable operation containing: