Close date pushed too many times flag

Outcome. A deal whose close date keeps getting pushed later gets flagged after a set number of pushes, surfacing a forecast risk that a single delayed close date does not show on its own.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-027

flowchart TD
    A[Close Date changes] --> B{Close Date greater than Close Date Snapshot?}
    B -->|yes, push| C[Increase Close Date Push Count by 1]
    C --> D{Push Count >= 3?}
    D -->|yes| E[Set Push Flag = true, task + notify owner and manager]
    D -->|no| F[Copy Close Date into Close Date Snapshot]
    E --> F
    B -->|no, first time or earlier| F

When to use it, when not to

• UseUse it on deals where forecast accuracy depends on the close date being a real commitment, not a placeholder that quietly slides every review cycle.
• UseUse it as the counting companion to deal-hygiene-003 (a single overdue close date alert). This fiche tracks the pattern across multiple edits instead of one overdue moment.
• SkipDo not use it on pipelines with naturally long, uncertain cycles, enterprise procurement or public sector, where a close date moving is expected and not a red flag by itself.
• SkipDo not treat the push count as proof of a stalled deal. Pair it with deal-hygiene-001's activity check before assuming the deal is actually at risk.