Association count cap per company (portfolio hygiene flag)

Outcome. Companies that have accumulated an unusually large number of associated contacts get flagged for a portfolio review, catching runaway association growth, a shared catch-all company absorbing every unrelated inbound lead for example, before it distorts account-level reporting.

Workflow map Enrollment, branches and actions at a glance data-quality-045

flowchart TD
    A[Monthly scheduled sweep of non-excluded companies] --> B[Custom code: count associated contacts]
    B --> C{Count exceeds threshold?}
    C -->|yes| D[Flag Exceeds threshold, add to list, create task]
    C -->|no| E[Normal]

When to use it, when not to

• UseUse it on portals where a small number of generic or catch-all company records, an "Unknown company", a large account with subsidiaries incorrectly rolled into one record, tend to accumulate an outsized number of associations that skew per-account metrics.
• UseUse it as a periodic sweep, not a real-time check. A company crossing a threshold rarely needs same-hour attention, a weekly or monthly review is normally enough.
• SkipDo not use it on a genuinely large, correctly-modeled enterprise account with hundreds of legitimate contacts. Set the threshold and, if needed, an exclusion checkbox for known large accounts so this does not generate noise on records that are correctly large, not incorrectly large.
• SkipDo not use it to automatically split or reassign associations. This only flags a count for a human to investigate; the actual remediation, splitting a company into subsidiaries, reassigning contacts, is a data modeling decision.