Skip to content

Stage-entry timestamp properties for pipeline velocity reporting

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Deal5 stepsUpdated for HubSpot seat pricing
OutcomeReporting 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 mapreporting-alerts-002
Deal stage changes leads to Stage = Appointment Scheduled?. Stage = Appointment Scheduled? leads to yes: date_entered_appointmentscheduled blank?; no: Stage = Qualified To Buy?. date_entered_appointmentscheduled blank? leads to yes: Set date_entered_appointmentscheduled = today; no: No action, already stamped. Stage = Qualified To Buy? leads to yes: Same blank-check and stamp pattern; no: Continue through remaining stage branches. yes yes no no yes no Deal stage changes Stage = Appointment Scheduled? date_entered_ appointmentscheduled blank? Stage = Qualified To Buy? Set date_entered_ appointmentscheduled = today Same blank-check and stamp pattern Continue through remaining stage branches No action, already stamped
Deal stage changes leads to Stage = Appointment Scheduled?. Stage = Appointment Scheduled? leads to yes: date_entered_appointmentscheduled blank?; no: Stage = Qualified To Buy?. date_entered_appointmentscheduled blank? leads to yes: Set date_entered_appointmentscheduled = today; no: No action, already stamped. Stage = Qualified To Buy? leads to yes: Same blank-check and stamp pattern; no: Continue through remaining stage branches. yes no yes no Deal stage changes Stage = Appointment Scheduled? date_entered_ appointmentscheduled blank? yes Set date_entered_ appointmentscheduled = today no No action, already stamped Stage = Qualified To Buy? Same blank-check and stamp pattern Continue through remaining stage branches

When to use it, when not to

Use it

  • 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.
Read more on when to use itShow less

Skip it

  • 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 5 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library