Skip across the chapter
Quota Playbook

Deal stage progress: 7 checks for weekly coaching

Quota Playbook Editorial Team · Published · 12 min read

In Pipedrive, click the Changelog tab under the History area in a deal detail view to see changes sorted by date.

How to verify deal stage progress data for coaching

To calculate the time spent specifically in the current stage, refer to the “Deal stage updated at” field and compute the difference from the current date, according to Freshworks.

Key takeaways for how to check deal stage progress for coaching

  • Verify current stage duration by computing the difference from the current date using the “Deal stage updated at” field, as described by Freshworks.
  • Use the “Age in Days” metric combined with “Group By” conditions like “Deal Name” and “Stage” to see the total days a deal has been active since creation, according to Freshworks.
  • Review the Insights deal progress report to view deal movement through stages within a specified time frame, according to Pipedrive.
  • Note that if a deal moves from stage two directly to stage five, the report shows it as having entered stages three, four, and five, reported by Pipedrive.
  • Click the Changelog tab under the History area in the deal detail view to view changes sorted by date, as stated by Pipedrive.
  • Create a workflow that triggers a task for the deal owner when the deal's Date entered Contract Sent is more than 7 days ago, according to HubSpot.
  • Track field edit history for all field types, with a maximum allowance of 50 fields, according to Freshworks.

Understanding time in stage and total age

When reviewing pipeline health during a 1:1, distinguish between the time a deal has spent in its current stage and its total age in the system. These two metrics answer different questions about deal progression and require different data points to calculate.

Check 1: Stage duration metric

This method requires manual calculation based on the timestamp of the last stage change. In contrast, HubSpot provides a calculated property defined as “Time in current stage: the time the record has spent in the current pipeline stage,” reported by HubSpot. This metric is the time the record has spent in the current pipeline stage.

Check 2: Total age metric

The “Age in Days” metric tracks the total duration a deal has existed in the sales pipeline—from its creation to its current position, according to Freshworks. This metric includes the cumulative time spent in all stages, including the ongoing time in the current stage, as noted by Freshworks. When used in combination with “Group By” conditions such as “Deal Name” and “Stage,” the “Age in Days” metric provides insights into the current stage of each deal along with the total number of days the deal has been active since its creation, according to Freshworks.

Understanding the difference between these metrics is critical for accurate coaching. The current stage's duration is not included in the historical stage duration metric and only becomes available once the deal moves to the next stage, according to Freshworks. This means that if you are looking at a deal currently in the "Proposal" stage, the time spent in "Proposal" is not yet part of the finalized stage duration data until it moves to the next stage. However, the total age metric captures this ongoing time immediately.

A filled reference table for stage metrics

The table below maps the seven required checks to the specific documentation available from each publisher. Use this reference to verify which metrics are available in your CRM before starting a coaching conversation.

Publisher Stage Duration Metric Total Age Metric Progress Report View Stage Skip Logic History Log Access Workflow Trigger Rule Field Limit Check
Freshworks Use “Deal stage updated at” to compute current stage time “Age in Days” shows total days active since creation — — — — Field edit history applies to all field types, max 50 fields
Pipedrive — — Insights report shows deal movement through stages Deals skipping stages show as entering all intermediate stages Changelog tab under History shows changes sorted by date — —
HubSpot “Time in current stage” tracks time in current pipeline stage — — — — Trigger task if “Date entered Contract Sent” is more than 7 days ago —
Microsoft — — — — — Send email if “Qualify” stage is active for longer than 15 days —

According to Freshworks, the “Deal stage updated at” field allows you to calculate time spent specifically in the current stage by computing the difference from the current date. The same publisher notes that the “Age in Days” metric, when used with “Group By” conditions like “Deal Name” and “Stage,” provides insights into the current stage of each deal along with the total number of days the deal has been active since its creation. Freshworks also states that field edit history tracking is applicable to all field types, with a maximum allowance of 50 fields.

Reported by Pipedrive, the Insights deal progress report allows you to view the movement of your deals through stages within a specified time frame, showing how well your deals are progressing through your sales cycle. Pipedrive explains that if a deal has moved from stage two directly to stage five in the time frame selected, it will show as having entered stages three, four and five. Additionally, Pipedrive notes that progress reports use the most recent updates to deal stages, meaning if a deal is moved from Stage 2 back to Stage 1, the deal is represented in Stage 1. When in a deal’s detail view, you can click on the Changelog tab under the History area to view changes made to that item, sorted by date.

Published by HubSpot, “Time in current stage” is defined as the time the record has spent in the current pipeline stage. HubSpot suggests creating a workflow that triggers a task for a deal owner to follow up when the deal's Date entered Contract Sent is more than 7 days ago.

Checking progress reports and skip logic

Pipedrive’s Insights deal progress report allows you to view the movement of your deals through stages within a specified time frame, showing how well your deals are progressing through your sales cycle, as described in the Pipedrive documentation. When you measure by the number of deals, you’ll see the number of deals that have entered each stage in the timeframe selected, according to Pipedrive. This view helps you identify where deals are stalling during your weekly 1:1s by providing a clear count of stage entries.

Understanding how the system handles skipped stages is critical for accurate coaching. For example, if a deal has moved from stage two directly to stage five in the time frame selected, it will show as having entered stages three, four and five, according to Pipedrive. The entered stage deal count also includes deals that have skipped that stage while moving on to a future stage, as noted by Pipedrive. This behavior means that a rep who skips a stage is still counted in the intermediate stages for reporting purposes. Additionally, winning a deal doesn’t affect deal progress results in the stages that were skipped, according to Pipedrive.

You should also consider how the report handles deals that move backward. Progress reports use the most recent updates to deal stages, meaning if a deal is moved from Stage 2 back to Stage 1, the deal is represented in Stage 1, as stated by Pipedrive. This ensures that your coaching conversation reflects the current reality of the deal rather than a historical peak. When reviewing these reports with your team, focus on the specific stage counts to identify bottlenecks. If a rep’s deals are frequently skipping stages, discuss whether this is a strategic choice or a data entry habit. Use the progress report view to verify that the stage movement aligns with your team’s intended sales process.

Reviewing field history and edit logs

To coach on specific bottlenecks, you need to see exactly when a deal moved stages and what data changed during that time. This section covers how to access those logs in two specific CRM environments.

Pipedrive Changelog Access

In Pipedrive, you can view the history of a specific deal by navigating to its detail view. According to Pipedrive, when you are in a deal’s detail view, you can click on the Changelog tab under the History area to view changes made to that item, sorted by date. This feature allows you to see a chronological list of modifications. If the Changelog tab shows a gap between the last activity and the stage change, you can ask the rep to explain that gap during your 1:1. Changes shown there are sorted by date.

Freshworks Field Edit History Limits

Freshworks offers a different approach by tracking edits at the field level. According to Freshworks, field edit history tracking is applicable to all field types, with a maximum allowance of 50 fields. This means you can choose which specific fields you want to monitor for changes. The same source notes that you can only select up to 50 fields only. This limit is important for your setup because it forces you to prioritize which data points matter most for coaching. You might choose to track the Stage field, the Next Step field, and the Expected Close Date field. By limiting your selection to these high-impact fields, you ensure that the history log remains relevant to your coaching goals. If you try to track more than 50 fields, the system will not allow it, so you must curate your list carefully.

Practical Application for Managers

When using these tools, focus on the consistency of data entry. If a rep changes the stage but does not update the Next Step field, the edit history will show a discrepancy. You can use this discrepancy to coach on the importance of keeping all deal data synchronized. In Pipedrive, the Changelog tab gives you a broad view of all changes, while in Freshworks, the field-specific tracking lets you drill down into particular data points. Both methods provide the raw data you need to have evidence-based conversations with your team.

Setting up workflow triggers for follow-ups

When configuring automated follow-ups, the specific trigger conditions depend on the platform you use. HubSpot documentation for "Use stage calculated properties" advises creating a workflow that triggers a task for a deal owner to follow up when the deal's Date entered Contract Sent is more than 7 days ago HubSpot. This rule uses a specific date property rather than a calculated duration metric to determine when the task should be generated.

However, HubSpot also notes a critical limitation regarding calculated time properties. According to HubSpot, records won't be enrolled in workflows based on the Cumulative time and Latest time in [stage] properties if the record is currently in that stage HubSpot. For example, the Latest time in Contract Sent property will not trigger a workflow if the deal is currently in the Contract Sent stage. This means you cannot rely on cumulative time properties to trigger actions while a deal remains in the same stage; the trigger logic must account for this exclusion.

Microsoft offers a different approach in its "Best practices for using business process flow table columns - Power Automate" guide. Microsoft suggests sending an email to a user if the Qualify the stage of the Opportunity Sales Process is active for longer than 15 days Microsoft. This example demonstrates using stage duration to trigger a notification when a stage has been active for a specific period.

Check your workflow settings to confirm that the trigger conditions align with your coaching goals. For instance, if you want to flag deals that have stalled in a specific stage, ensure the trigger logic accounts for the platform's specific rules regarding stage enrollment. Review the documentation for your chosen platform to understand how it calculates stage duration and which properties are available for workflow triggers. This ensures that your automated follow-ups are accurate and relevant to the deals you are coaching.

FAQ: How to check deal stage progress for coaching

Does the time in stage metric include the current stage?

Freshsales Analytics excludes the current stage's duration from this metric, noting it only becomes available once the deal moves to the next stage Freshworks. In contrast, HubSpot defines "Time in current stage" as the time spent in the current pipeline stage HubSpot.

How does the system handle deals that skip a stage?

Pipedrive's Insights reports deal progress includes deals that have skipped a stage while moving on to a future stage in the entered stage deal count Pipedrive. This ensures skipped stages are accounted for in the movement metrics.

How many fields can be tracked in edit history?

Freshsales allows field edit history tracking for all field types, with a maximum allowance of 50 fields Freshworks.

Can a workflow trigger if a deal is currently in a stage?

HubSpot notes that records won't be enrolled in workflows based on the Cumulative time and Latest time in [stage] properties if the record is currently in that stage HubSpot. For example, a workflow will not trigger on "Latest time in Contract Sent" if the deal is currently in the Contract Sent stage.

Sources

  1. Call handling: 9 rules to check before coaching
  2. Overtime errors for non-exempt sales reps: 5 fixes
  3. Check 8 sharing limits before sending coaching files
  4. Product pricing and deal fields

More plays