Build a Salesforce campaign governance system with Claude

Write a one-page operating charter for Salesforce Campaign setup and reporting governance before exporting any data. State the exact decision this workflow supports: which campaigns are report-ready, which need repair, and which creation rules or templates must change. Define the in-scope business units, pipelines, regions, date window, record types, and exclusions, then name one analysis owner, one Salesforce data owner, and one final approver. Record the review cadence as weekly and specify where evidence, approvals, and exceptions will be stored. Review the charter with the approver and do not proceed until the scope and decision rights are accepted.

Convert the operating policy into a rule register that can be checked against Salesforce records. Create one row per rule with rule_id, rule_name, business_reason, required_fields, calculation_or_test, pass_condition, exception_code, severity, owner, and policy_version. Start with these minimum checks: campaign names match the taxonomy, parent-child hierarchy matches the reporting model, dates and status are internally consistent, member statuses include one clear responded state, and cost and attribution fields use the approved units and definitions. Give every rule an example that should pass and an example that should fail so reviewers interpret it consistently. Have the business owner approve the rule register and record any unresolved policy questions before data is scored.