Outcome. Reporting gets one date property per pipeline stage, stamped the moment a deal first enters that stage, so a velocity report can show average days spent in each stage rather than only the current one.
Workflow mapEnrollment, branches and actions at a glance
flowchart TD
A[Deal stage changes] --> B{Stage = Appointment Scheduled?}
B -->|yes| C{date_entered_appointmentscheduled blank?}
C -->|yes| D[Set date_entered_appointmentscheduled = today]
C -->|no| E[No action, already stamped]
B -->|no| F{Stage = Qualified To Buy?}
F -->|yes| G[Same blank-check and stamp pattern]
F -->|no| H[Continue through remaining stage branches]
When to use it / when not to
- Use it when leadership wants a stage-by-stage velocity report for pipeline reviews, not just a single "is this deal stalling" flag.
- Use it as the data foundation for a custom report or dashboard chart on funnel velocity.
- Do not use it if you only need an operational staleness flag on the current stage. That is a deal-hygiene use case (day-in-stage alerting), not a reporting data layer.
- Do not build this on pipelines with fewer than three stages. The reporting value rarely justifies the property maintenance overhead.



