Skip down to the research record

Stage duration: 8 checks before the weekly call

Quota Forecast Editorial Team · Published · 11 min read

The Age in Days metric tracks total pipeline duration from creation to the current position, according to Freshworks.

Stage duration and history fields track how long deals sit in each pipeline phase

In Freshsales Analytics, 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 cumulative measure includes the time spent in all stages, including the ongoing time in the current stage, according to Freshworks.

For specific phase analysis, the Days in Stage metric measures the time a deal spent in each completed stage of the sales pipeline, according to Freshworks. Distinguishing these two metrics is essential for accurate stalling analysis. Total age reflects the entire lifecycle, while stage duration isolates performance within specific pipeline phases.

When reviewing pipeline health, verify which metric your reporting tool uses for a given deal. High total age with a short completed-stage duration may reflect substantial time in earlier stages; completed-stage duration does not measure time spent in the active stage. Conversely, a deal with low total age but high stage duration may be stalling in its initial phase. Confirm the specific definitions in your CRM documentation to ensure your weekly forecast call uses the correct baseline for deal movement verification.

Key takeaways for how to read stage duration and history fields in crm tools

Conversely, the Days in Stage metric measures the time a deal spent in each completed stage of the sales pipeline, according to Freshworks. For deals currently in the Demo stage, time spent in Demo will only be tracked once the deal exits this stage, according to Freshworks. In the deal detail view, you can click on the Changelog tab under the History area to view changes made to that item, sorted by date, according to Pipedrive. Verify whether your current stage duration metric excludes active time before calculating stalling averages.

A filled reference table of duration and history fields across four publishers

The table below maps the eight verification points to the specific fields and logic documented by each publisher. Each row reflects only the rules stated by that publisher for its own platform.

PublisherTotal Age MetricStage Duration MetricHistory Log AccessProgress Report LogicStage Entry DateStage Exit DateLatest Stage TimeField Edit History
FreshworksThe 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.The Days in Stage metric measures the time a deal spent in each completed stage of the sales pipeline according to Freshworks.It may take up to 5 minutes for changes to show in the Deal fields' edit history according to Freshworks.————You can only select up to 50 fields only according to Freshworks.
Pipedrive——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 according to Pipedrive.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 according to Pipedrive.————
HubSpot———The properties automatically update based on a record's current and historical stage values (e.g, if a deal or ticket is closed then reopened, the values will continue to update) according to HubSpot.Date entered [stage ID]: the date and time the record entered the stage according to HubSpot.Date exited [stage ID]: the date and time the record exited the stage according to HubSpot.Latest time in [stage ID]: the total time spent by the record in the stage since it last entered the stage according to HubSpot.—
Close—Avg Time to Advance: The average time an Opportunity spent in a Stage before advancing to any subsequent Stage (does not include any Opportunities that remained in a Stage during the specified Period) according to Close.—Skipped Stages: Opportunities that skip Stages are not included in the counts for those skipped Stages according to Close.————

Verify which of these eight fields are visible in your current deal view before the forecast call.

Total deal age and completed-stage duration

Revenue leaders must distinguish between cumulative pipeline age and the specific time a deal spends in its current active stage to accurately identify stalling opportunities. Freshsales Analytics defines the Age in Days metric as tracking the total duration a deal has existed in the sales pipeline, from its creation to its current position, according to Freshworks.

In contrast, the Days in Stage metric measures the time a deal spent in each completed stage of the sales pipeline, according to Freshworks. This distinction is critical for weekly forecast calls because the Days in Stage metric does not provide real-time updates for a deal currently in a stage. For example, time spent in the Demo stage will only be tracked once the deal exits this stage, according to Freshworks.

When reviewing pipeline health, using the Age in Days metric captures the full lifecycle of the opportunity, while the Days in Stage metric reflects historical stage completion data. If a deal remains in the Demo stage, the Days in Stage value for that specific stage remains unrecorded until the deal exits that stage. This prevents the metric from reflecting the current dwell time in the active stage.

To verify which metric your team should use for stalling analysis, check whether the deal has exited its current stage. If the deal is still active in a stage, the Days in Stage metric for that stage will not yet reflect the time spent there. The Age in Days metric, however, continues to count the total time from creation, providing a continuous measure of pipeline age.

Open your CRM's deal detail view and distinguish total age, completed-stage duration and current-stage timing before choosing a metric for your weekly stalling analysis.

How history logs and progress reports record stage changes

When verifying deal movement, distinguish between the raw change log and the aggregated progress reports. In Pipedrive, you can access the changelog by clicking on the Changelog tab under the History area in a deal’s detail view to view changes made to that item, sorted by date, according to Pipedrive. This section includes all items added and uploaded to the deal, as well as a list of all changes the deal underwent, according to Pipedrive.

Progress reports handle stage movement differently than the raw changelog. 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, according to Pipedrive. This logic applies when a deal moves backward. For skipped stages, Pipedrive indicates 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, according to Pipedrive.

Close uses a different rule for skipped stages in its reporting. Close states that opportunities that skip Stages are not included in the counts for those skipped Stages, according to Close.

To verify your data before the weekly call: 1. Check the Pipedrive changelog for specific date-sorted changes. 2. Confirm Pipedrive progress reports reflect the most recent stage location for backward moves. 3. Verify Pipedrive reports show skipped stages as entered. 4. Confirm Close reports exclude skipped stages from counts.

Field edit history limits and update rules

Freshworks documentation outlines specific technical constraints for tracking field edits on deals. The system imposes a hard cap on the number of fields you can select for history tracking. According to Freshworks, you can only select up to 50 fields only. If your pipeline uses more than 50 custom fields, you must prioritize which ones require audit trails for your weekly review.

When reviewing who made changes, the interface limits your filtering options. According to Freshworks, while filtering using the “Updated by” filter, you can filter by All users/sources or specific users/sources. The documentation specifies that you can select up to 100 items for this specific user or source filter. This limit applies when narrowing down the history log to particular team members or integration sources.

Visibility of the full contact list within the history view also has a threshold. According to Freshworks, if there are more than 30, you will not be able to view the full list. This constraint affects how you verify collaborative edits on shared deals.

Finally, there is a latency factor to consider when verifying recent changes. According to Freshworks, it may take up to 5 minutes for changes to show in the Deal fields' edit history. Do not assume a field is missing from the history immediately after an edit. Wait for this window to pass before concluding that a change was not logged.

Check your current field selection count against the 50-field limit before the next forecast call.

A blank worksheet for mapping your CRM duration fields

Create a worksheet with eight rows for the verification points below and columns for Field Name, CRM Platform, Metric Type and Verification Status. The table provides a structured space for revenue leaders to record how their platform tracks deal movement and duration data before the weekly forecast call.

The "Field Name" column is for the specific label your CRM uses for the duration metric, such as the total age field. The "CRM Platform" column identifies which tool stores that data, ensuring you distinguish between different vendors. Use the "Metric Type" column to label each row: total age, completed-stage duration, history access, reporting rules, stage entry date, stage exit date, latest stage time or field edit history. The "Verification Status" column allows you to mark whether you have confirmed the field updates correctly for open deals.

FAQ: How to read stage duration and history fields in crm tools

Does the Age in Days metric include time spent in the current stage?

Yes, the metric includes the ongoing time in the current stage. 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.

When does the Days in Stage metric update for a deal in Demo?

The metric does not update while the deal remains in that specific phase. Time spent in Demo will only be tracked once the deal exits this stage, according to Freshworks.

How does Pipedrive handle deals moved back to a previous stage in progress reports?

The report reflects the deal's latest position. 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, according to Pipedrive.

Do HubSpot stage properties update if a closed deal is reopened?

Yes, the properties continue to update after reopening. The properties automatically update based on a record's current and historical stage values (e.g, if a deal or ticket is closed then reopened, the values will continue to update), according to HubSpot.

What is the maximum number of fields you can select for field edit history in Freshworks?

You can select up to 50 fields for tracking. Note: You can only select up to 50 fields only, according to Freshworks.

Sources