crm-data-governance

name	crm-data-governance
description	Govern CRM and revenue-system data through field definitions, ownership, required evidence, deduplication, identity resolution, access, change control, and quality monitoring.

Crm Data Governance

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using CRM schema, integrations, user workflows, reports, identity rules, permissions, and data-quality defects. Do not fill material gaps with assumptions when they can change the result.
3. Inventory objects/fields and consumers, define canonical sources, remove redundant free text where structure matters, set validation/dedupe rules, and monitor drift.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Critical revenue fields have one meaning/source and reports no longer depend on undocumented manual conventions.