A stage report audit checks configured stages, reporting tables, pipeline structure, and funnel counting behavior.
Key takeaways for what should a stage report audit check for a weekly pipeline review?
-
Check stage configuration: Retrieve the configured stages for your pipeline using the documented API request method. HubSpot specifies that you make a GET request to
/crm/v3/pipelines/{objectType}/{pipelineId}/stagesto retrieve all stages in a pipeline. -
Identify the reporting table: Verify which table your report queries before interpreting stage data.
-
Separate distinct processes: Do not force structurally different workflows into a single pipeline definition.
-
Interpret funnel movement: Check backward movement and direct stage conversion before you trust the funnel.
Stage report audit: checks for definitions and counting
Start by verifying the stage definitions your team uses in the weekly review. The audit must confirm that the stages displayed in your report match the configured stages in your CRM. The configured stage list provides the baseline for what stages exist before you evaluate how they are counted or reported.
The four checks in this audit separate configuration from counting. First, inspect the stage configuration to ensure labels and order are correct. Second, identify the correct reporting table, as different systems store process data in different structures. Third, review the pipeline structure to distinguish between separate sales processes and segmentation within a single pipeline. Fourth, test your interpretation of funnel movement to understand how backward and forward transitions are counted.
Before the review, inspect configured stages and changes
Check the configured stages and their change history before the weekly forecast review. HubSpot provides separate API requests for retrieving stages, editing details, and inspecting changes, allowing you to verify the current state of your pipeline definitions.
This endpoint returns the full list of stages currently defined for the specified pipeline. To inspect a single stage, make a GET request to /crm/v3/pipelines/{objectType}/{pipelineId}/stages/{stageId}, according to HubSpot. Use this individual retrieval when you need to verify the specific properties of one stage without pulling the entire pipeline structure.
When you need to confirm what details are editable, check the stage configuration. To edit a stage’s details, such as label or display order, make a PATCH request to /crm/v3/pipelines/{objectType}/{pipelineId}/stages/{stageId}, according to HubSpot. This distinction matters because the audit process requires knowing which attributes can be modified directly rather than those that are fixed by the pipeline structure.
Verify the integrity of your pipeline definitions by reviewing the change history. This pipeline-level audit log helps identify if the overall pipeline structure was altered recently. To view changes made to a specific stage, make a GET request to /crm/v3/pipelines/{objectType}/{pipelineId}/stages/{stageId}/audit, according to HubSpot. This stage-level audit allows you to view changes made to a stage.
Reviewing these separate endpoints ensures your weekly report reflects the current configuration. The pipeline audit and stage audit endpoints provide distinct views of historical changes, so inspect both to catch any discrepancies between the pipeline structure and individual stage definitions.
- Retrieve all stages using the pipeline stages endpoint.
- Inspect individual stages using the stage-specific endpoint.
- Check editable details like labels and display order.
- Review pipeline-level change history.
- Review stage-level change history.
Use these checks to confirm that the stage definitions in your CRM match the expectations of your forecast model. If a stage label or order has changed, update your reporting filters accordingly. The separate audit endpoints for pipelines and stages allow you to pinpoint exactly where a configuration change occurred, supporting a more accurate interpretation of the data in your weekly review.
During the audit, identify the business process reporting table
When your weekly pipeline review relies on Microsoft Dataverse, the first step is to locate the correct data source. In versions 9.0 and higher, each business process flow creates its own Dataverse table, usually with the same name as the business process flow, according to Microsoft. This structural change means the table you query for stage data may differ from the legacy entity table you used previously.
The documentation notes that legacy process-related columns in tables is deprecated, according to Microsoft. Specifically, the deprecation of the Active Stage (activestageid) column on related tables creates two ways to report on business process flows, according to Microsoft. Your audit must determine which of these two reporting approaches your current views and charts are using.
To report on the business process flow, select the table for the business process flow you want to report on, and then create views and charts, just as you did before, according to Microsoft. This direct selection of the flow-specific table is the primary method for ensuring your stage-based pipeline report pulls from the correct source. An advantage of this approach is that you can use a single view or chart to report on business process flows that span multiple tables, according to Microsoft. This capability is particularly relevant if your sales process moves deals across different entity types, such as from a lead to an opportunity.
Check your current report definitions to see if they point to the flow-specific table or the legacy entity table. If you are using a single view to cover multiple tables, confirm that the view logic correctly handles the stage data from each source.
For your weekly review, open the report builder and verify the data source. If the source is the legacy entity table, switch it to the specific business process flow table. This ensures your stage counts and funnel movements reflect the current data structure. If you use multiple business process flows, create separate views for each. Do not assume that the table name matches the flow name in every case; verify the exact table name in your Dataverse environment.
After inspecting configuration, test your interpretation of funnel movement
Once you have verified the stage definitions and the reporting table, the final check is how the report counts movement between those stages. Different systems apply different rules to backward movement and direct conversions, so the same pipeline can produce different funnel numbers depending on the counting logic.
Pipedrive pipeline segmentation
When deciding whether to split your data into multiple pipelines or keep it in one, check the structural differences in your sales processes. Use multiple pipelines when your sales processes differ in structure or complexity, according to Pipedrive. If your processes are similar, keeping pipelines focused makes them easier to manage, while fields and filters help you segment deals within a single pipeline, according to Pipedrive.
Before you test funnel movement, confirm the specific configuration options enabled for each pipeline. Name your pipeline, customize its stages and configure options like stage and deal probabilities or the Rotting feature, according to Pipedrive. These settings influence how deals are tracked and reported within the pipeline structure.
Close funnel counting rules
For systems that generate funnel reports, you must understand how backward movement and conversion rates are calculated. Backward Movement: For Opportunities that move backwards in a Pipeline, we will not include any “undone” forward movement in the Funnel, according to Close. This rule means that if a deal moves forward and then back, the forward step is excluded from the funnel count.
Conversion Rates: Conversion Rates between Stages only represent Opportunities that converted from the previous Stage directly to the next Stage, according to Close. If a deal skips a stage or moves through multiple stages before reaching the next one, it does not count toward the direct conversion rate between those two specific stages.
Testing your interpretation
To test your interpretation, select a small sample of deals that moved backward or skipped stages during the last week. Check if the funnel report excludes the undone forward movement as described by Close. Verify that the conversion rate only includes deals that moved directly from the previous stage to the next, according to Close.
Review the Open, won, and lost stage rules in 4 sales tools to compare how different systems handle stage transitions. Check the Stage duration: 8 checks before the weekly call to ensure your time-based metrics align with the counting rules.
Publisher reference table for stage reporting checks
The table below maps each publisher to the specific configuration check and reporting behavior documented in their sources. Use these rows to verify that your weekly pipeline report reflects the correct underlying definitions before the review.
| Publisher | Configuration Check | Reporting or Counting Behavior |
|---|---|---|
| HubSpot | Retrieve the configured stages through a GET request to the pipeline stages endpoint, according to HubSpot. | The API distinguishes between retrieving all stages and inspecting individual stage details or pipeline changes. |
| Microsoft | Identify the process table, as each business process flow creates its own Dataverse table in versions 9.0 and higher, according to Microsoft. | Reporting is documented through the specific business process flow table rather than legacy process-related columns. |
| Pipedrive | Separate different sales processes by using multiple pipelines when sales processes differ in structure or complexity, according to Pipedrive. | The platform distinguishes structurally different sales processes from segmentation within a single pipeline. |
| Close | Interpret backward funnel movement by excluding any “undone” forward movement from the Funnel for Opportunities that move backwards, according to Close. | Stage conversion is counted only when opportunities move directly from the previous stage to the next. |
Review each row against your current CRM setup to confirm that the report you are using aligns with these documented behaviors.
Illustrative example of a four-stage week
A report lists 4 stages and 20 deals in one pipeline. The stage names and order match the configured list. Two groups, split by a field, hold 10 deals each. In the funnel, 2 deals moved forward and then back, so those undone forward steps stay out. Another 3 skipped a stage and stay out of the direct count. The other 15 moved directly from one stage to the next.
Stage report audit checklist
The primary next action is to take the stage-based report used in your weekly review and run the four checks below.
- Check configured stages against the stages returned for that pipeline.
- Identify the reporting table your weekly report queries.
- Separate sales processes that differ in structure or complexity.
- Test backward movement and direct stage conversion in the funnel.
Start by confirming the specific endpoint for retrieving a single stage definition. This specific request path distinguishes the retrieval of a single stage from broader pipeline queries.
When auditing the configuration, verify that the stage identifier matches the object type and pipeline ID in the URL structure. The documentation specifies the exact path format for this operation, ensuring you are querying the correct record within the pipeline hierarchy. Use this endpoint to validate that the stage details align with the definitions expected in your weekly forecast review.
FAQ: pipeline configuration and funnel counting
What should a stage report audit inspect?
A stage report audit should inspect configured stages, the reporting table, pipeline structure, and funnel counting behavior. These four areas define how the pipeline data is stored, displayed, and calculated within your CRM. Reviewing these specific elements ensures you understand the underlying rules before interpreting weekly numbers.
How can I inspect HubSpot pipeline and stage changes?
To view changes made to a pipeline, make a GET request to /crm/v3/pipelines/{objectType}/{pipelineId}/audit, and to view changes made to a stage, make a GET request to /crm/v3/pipelines/{objectType}/{pipelineId}/stages/{stageId}/audit, according to HubSpot.
When does Pipedrive recommend multiple pipelines?
Pipedrive recommends multiple pipelines when your sales processes differ in structure or complexity, according to Pipedrive. If your processes share the same structure, a single pipeline with segmentation fields is sufficient.
How does Close count backward movement and direct stage conversions?
For Opportunities that move backwards in a Pipeline, the system will not include any “undone” forward movement in the Funnel, and conversion rates between stages only represent opportunities that converted from the previous stage directly to the next stage, according to Close. This rule excludes reversed actions from the funnel count.