Current Quality5/10?

How do you measure procurement stall days by opportunity stage in Dynamics 365?

📖 2,168 words🗓️ Published Jun 20, 2026 · Updated Jun 30, 2026

Direct Answer

How do you measure procurement stall days by opportunity stage in Dynamics 365?

Start by fixing the workflow gap named in your question on dynamics 365 on one pod or segment for two weeks. Document the before/after on a single report; only then turn on automation. Most teams automate a broken manual process and wonder why the workflow gap named in your question persists.

flowchart TD A[Identify Opportunity Stages] --> B[Define Stall Criteria] B --> C[Capture Stage Entry Date] C --> D[Capture Stage Exit Date] D --> E[Calculate Days in Stage] E --> F[Flag Stages Exceeding Threshold] F --> G[Report Stall Days by Stage] G --> H[Analyze and Improve Process]

Context — tied to your question

You asked about the workflow gap named in your question on dynamics 365. Generic RevOps advice fails here because the fix is operational: who enforces which field, when records get downgraded, and what managers inspect every Monday. Pick three required proofs per stage and enforce with validation before save

CRO SYNDICATE

What to do

Name an owner for the workflow gap named in your question; publish a one-page definition of done tied to dynamics 365 objects
Baseline the pain: export 30 recent records where the workflow gap named in your question showed up in forecast or handoffs
Configure Core object required fields, ownership, stage definitions, activity logging
Pilot on one segment for 10 business days—no company-wide rollout
Run manager inspection weekly using one saved report; downgrade or fix records that fail the definition
Only after fill rate beats 80% on required fields, add automation (routing, alerts, or sync)

Dynamics 365 configuration focus

Objects to touch: Core object required fields, ownership, stage definitions, activity logging
Enforcement: validation on save beats post-hoc cleanup for the workflow gap named in your question
Inspection: one saved report filtered to pilot segment; same view every week

Metrics (pick one primary)

Primary: Duplicate or routing error queue depth week over week
Hygiene: % pilot records passing all required fields
Failure signal: same exception recurring after two inspection cycles

What good looks like

Managers can open one report and see which deals fail the workflow gap named in your question standards
Reps know which fields block saves—no surprise at commit time
Automation is off until manual discipline holds for two weeks
Handoffs use the same field definitions across teams

Common mistakes

Buying another point solution before dynamics 365 rules exist
Optional fields for the workflow gap named in your question—reps skip them under quarter pressure
Company-wide rollout before the pilot segment proves fill rate
Inspection meetings that read narratives instead of opening dynamics 365 records

Manager inspection script (15 minutes)

Open the pilot saved report in dynamics 365. Sort by exception flag. For each record: name the missing field, assign owner, set due date before next forecast. No narrative readouts—only record fixes. Downgrade forecast category when evidence fields are empty on Commit deals.

Rollout phases

Phase	Duration	Scope	Exit criteria
Baseline	Week 1	Export 30 failure examples	Written definition of done for the workflow gap named in your question
Pilot	Weeks 2–3	One segment	≥80% required field fill rate
Expand	Week 4+	Adjacent teams	Same inspection report, same fields
Automate	After expand	Workflows/routing	Automation off if fill rate drops 2 weeks straight

Data & integration notes

Document which objects sync from warehouse or billing before enabling automation. If IT blocks integrations, run the pilot with CSV exports and manual upload twice weekly—do not wait for perfect plumbing.

RevOps without a big team

One owner can run this if they have write access to dynamics 365 validation rules and a manager who enforces the inspection report. Block calendar time for configuration; do not stack fixes only on Friday afternoons before board meetings.

Enablement & documentation

Publish a one-page definition of done for the workflow gap named in your question inside your sales wiki. Link the dynamics 365 report URL, required fields, and two annotated screenshots. New hires should pass a 10-minute quiz on which fields block saves before receiving live opportunities in the pilot segment.

Stakeholder alignment

Stakeholder	What they need	Cadence
CRO / sales leader	Pilot metrics vs baseline	Weekly 15 min
Finance	Booking rules unchanged	Once at pilot start
IT / security	Field list + integration scope	Before automation
Reps	Office hours on new validations	Twice during pilot

Discovery questions for your next inspection

Ask the pilot pod: Which deals failed the workflow gap named in your question rules two weeks in a row? Which field was empty on every loss? What would have blocked the save if validation were on? Capture answers in dynamics 365 notes so the definition of done evolves with real failures—not generic enablement slides.

Post-pilot scale checklist

Required fields copied to adjacent teams unchanged
Same saved report URL pinned in the Monday leadership agenda
Automation tickets list the field API names, not vendor feature names
Success metric frozen for one quarter before changing again

Dynamics 365 admin notes (copy/paste ready)

Create a validation rule or required-field set on the object where the workflow gap named in your question appears. Name the rule with the problem keyword so admins can find it later. Add a custom field Exception_Reason__c (or equivalent) for temporary waivers—managers must fill it or the record cannot reach Commit. Archive waivers monthly; patterns indicate bad rules, not bad reps.

When leadership pushes back

If executives want a faster rollout, show the pilot fill-rate chart and the forecast error before/after. Offer parallel rollout only after two clean inspection weeks. Buying tools without field discipline repeats the workflow gap named in your question at higher license cost.

Tie to forecasting

Map each required field to a forecast category rule: if economic buyer role is missing, the deal cannot sit in Best Case. Managers downgrade in the same meeting they inspect the workflow gap named in your question—do not allow verbal commits without dynamics 365 evidence. Re-run the baseline export after 30 days to prove the fix held. Share results with finance and RevOps in the same slide.

flowchart LR A["Define problem"] --> B["dynamics 365 fields"] B --> C["Pilot segment"] C --> D["Weekly inspection"] D --> E["Automation last"]

Related on PULSE

[How are large buying committees in 2027 using consensus tools to stall deals?](/knowledge/q16522)
[How can I phrase a question to help a rep distinguish between a real objection and a stall?](/knowledge/q14364)
[How Do I Negotiate a Food Hall Stall Lease and Buildout?](/knowledge/q13779)
[Top 10 buying committee veto triggers that stall deals](/knowledge/q13562)
[What's the sequence for getting executive sponsorship aligned before deal stall explodes into budget carry-forward?](/knowledge/q284)
[How do you audit data center leasing pipeline opportunity hygiene in Dynamics 365 during AE-led pods to prevent duplicate contacts after acquisition when multi-currency ARR rollups?](/knowledge/q10787)

Setting Up Stage-Specific Duration Tracking in Dynamics 365

To measure procurement stall days by opportunity stage, you first need to ensure your system captures the right timestamps. In Dynamics 365, each opportunity stage transition is logged in the Opportunity Close entity or via custom workflow logging. A reliable approach is to create a custom field on the Opportunity entity called "Stage Entered Date" that updates automatically when a stage changes.

Use a real-time workflow or Power Automate flow triggered on stage change to stamp the current date/time into this field. Then, create a second custom field for "Days in Stage" that calculates the difference between the stage entry date and the current date (or the date the stage was exited). This gives you a live, per-opportunity view of how long each deal has been sitting in procurement review, legal approval, or any other stage.

For reporting, build a custom view in the Opportunities area that groups records by stage and sums the "Days in Stage" field. You can also export this data to Power BI for trend analysis—look for stages where the average stall days exceed 30% of your typical sales cycle length. This is a strong signal that a process bottleneck exists.

Analyzing Stall Patterns with Built-in Analytics

Dynamics 365 includes Out-of-the-Box (OOTB) analytics under the Sales Insights module that can help identify procurement stalls. Navigate to Sales > Analytics > Pipeline and filter by your opportunity stages. The Pipeline History chart shows how long deals stay in each stage over time, but it aggregates all stages—you need to customize it.

To isolate procurement-related stages (e.g., "Procurement Review," "Legal Review," "Contracting"), create a custom stage category in your opportunity sales process. Then, use the Stage Duration metric in the Pipeline Analytics dashboard. This metric calculates the average, median, and maximum days per stage. A median above your target (e.g., 14 days for procurement review) indicates a stall.

For more granularity, enable Predictive Scoring in Sales Insights. The Lead Score model can incorporate stage duration as a negative factor—deals stuck in procurement for too long get lower scores, alerting your sales team to intervene. You can also set up automated alerts via Power Automate: when an opportunity exceeds a threshold (say, 21 days in procurement), send an email to the sales rep and manager with a link to the record.

Creating a Custom Report for Procurement Stall Days

If OOTB analytics aren't enough, build a custom report using Dynamics 365's Advanced Find and Excel Online integration. Start by creating an Advanced Find query that returns all opportunities with a stage name containing "Procurement" or "Legal." Include fields: Opportunity Name, Stage Name, Stage Entered Date, Days in Stage (calculated field), and Owner.

Export this data to Excel Online (or use Power BI Desktop connected to your Dynamics 365 instance). In Excel, create a PivotTable with Stage Name in rows and Sum of Days in Stage in values. Add a slicer for Owner or Date Range to filter by team or time period. This report can be refreshed daily and shared via a Power BI dashboard pinned to your team's Teams channel.

For a more automated approach, use Power Automate to run this query weekly and email the report as a PDF. Include a summary row showing total stall days per stage and a comparison to the previous week—this helps your team spot sudden increases in procurement delays without manual data pulls.

Sources

Microsoft Dynamics 365 documentation — official product guides on sales and procurement processes.
Gartner — industry analysis on procurement metrics and sales cycle measurement.
APQC (American Productivity & Quality Center) — benchmarks and best practices for procurement performance.
Forrester Research — reports on sales process optimization and pipeline management.
Harvard Business Review — articles on business process measurement and organizational efficiency.
Procurement Leaders — industry publication covering procurement analytics and KPIs.

FAQ

What exactly are procurement stall days in Dynamics 365? Procurement stall days measure the time an opportunity spends in a stage where the buyer is waiting for internal approvals, budget sign-off, or legal review. In Dynamics 365, you can track this by comparing the actual days in a stage against your expected duration, often using workflow timestamps or custom fields.

How do I calculate stall days per opportunity stage? Create a rollup field or use a workflow that records the entry and exit dates for each stage. The stall days are the difference between the actual time spent and your predefined benchmark (e.g., 5 days for "Proposal" stage). No exact formula is built-in, so you’ll typically use Power Automate or a plugin to log the duration.

Can I automate stall day reporting without custom development? Partially. Out-of-the-box, Dynamics 365 doesn’t have a native "stall days" metric, but you can use the "Time in Stage" report or configure a custom dashboard with calculated fields. For full automation, you’ll likely need Power Automate flows or a third-party tool like a RevOps platform.

What’s a reasonable stall day threshold for common stages? It varies widely by industry and deal size, but a rough range is: 3-7 days for "Qualification," 5-14 days for "Proposal," and 10-30 days for "Negotiation." Anything beyond 30 days in a single stage often signals a stalled deal that needs intervention.

How do I identify which stages cause the most stalls? Run a report grouping opportunities by stage and calculate the average days per stage. Compare against your sales process targets. The stages with the highest deviation—like "Legal Review" or "Budget Approval"—are your bottleneck. You can also use the "Pipeline by Stage" view with a custom duration column.

Does measuring stall days help improve close rates? Yes, but only if you act on the data. Tracking stall days reveals where deals get stuck, allowing you to coach reps, adjust stage definitions, or automate follow-ups. Without action, it’s just a number. Most teams see a 10-20% improvement in cycle time after addressing top stall stages.

Bottom line

Fix the workflow gap named in your question on dynamics 365 with owner + enforced fields + weekly inspection. Scale only what improved a number in the pilot—not what sounded modern in a vendor demo.

Download:

![How do you measure procurement stall days by opportunity stage in Dynamics 365?](https://carldesouza.com/wp-content/uploads/2019/12/img_5de73dd7c0695-1024x691.png)

## Direct Answer

![How do you measure procurement stall days by opportunity stage in Dynamics 365?](https://pulserevops.com/img/auto/q10449.svg)

Start by fixing **the workflow gap named in your question** on **dynamics 365** on **one pod or segment** for two weeks. Document the before/after on a single report; only then turn on automation. Most teams automate a broken manual process and wonder why the workflow gap named in your question persists.

```mermaid
flowchart TD
A[Identify Opportunity Stages] --> B[Define Stall Criteria]
B --> C[Capture Stage Entry Date]
C --> D[Capture Stage Exit Date]
D --> E[Calculate Days in Stage]
E --> F[Flag Stages Exceeding Threshold]
F --> G[Report Stall Days by Stage]
G --> H[Analyze and Improve Process]
```

## Context — tied to your question

![How do you measure procurement stall days by opportunity stage in  — Context — tied to your question](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20Context%20%E2%80%94%20tied%20to%20your%20question%20How%20do%20you%20measure%20procurement%20stall%20days%20by%20opp%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=84500)


You asked about **the workflow gap named in your question** on **dynamics 365**. Generic RevOps advice fails here because the fix is **operational**: who enforces which field, when records get downgraded, and what managers inspect every Monday. Pick three required proofs per stage and enforce with validation before save

## What to do

![How do you measure procurement stall days by opportunity stage in  — What to do](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20What%20to%20do%20How%20do%20you%20measure%20procurement%20stall%20days%20by%20opportunity%20stage%20in%20Dyn%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=80189)


1. Name an owner for **the workflow gap named in your question**; publish a one-page definition of done tied to dynamics 365 objects
2. Baseline the pain: export 30 recent records where **the workflow gap named in your question** showed up in forecast or handoffs
3. Configure Core object required fields, ownership, stage definitions, activity logging
4. Pilot on one segment for 10 business days—no company-wide rollout
5. Run manager inspection weekly using one saved report; downgrade or fix records that fail the definition
6. Only after fill rate beats 80% on required fields, add automation (routing, alerts, or sync)

## Dynamics 365 configuration focus

- **Objects to touch:** Core object required fields, ownership, stage definitions, activity logging
- **Enforcement:** validation on save beats post-hoc cleanup for **the workflow gap named in your question**
- **Inspection:** one saved report filtered to pilot segment; same view every week

## Metrics (pick one primary)

- **Primary:** Duplicate or routing error queue depth week over week
- **Hygiene:** % pilot records passing all required fields
- **Failure signal:** same exception recurring after two inspection cycles

```mermaid
flowchart LR
  A["Define problem"] --> B["dynamics 365 fields"]
  B --> C["Pilot segment"]
  C --> D["Weekly inspection"]
  D --> E["Automation last"]
```

## What good looks like

- Managers can open one report and see which deals fail **the workflow gap named in your question** standards
- Reps know which fields block saves—no surprise at commit time
- Automation is off until manual discipline holds for two weeks
- Handoffs use the same field definitions across teams

## Common mistakes

- Buying another point solution before dynamics 365 rules exist
- Optional fields for **the workflow gap named in your question**—reps skip them under quarter pressure
- Company-wide rollout before the pilot segment proves fill rate
- Inspection meetings that read narratives instead of opening dynamics 365 records

## Manager inspection script (15 minutes)

Open the pilot saved report in dynamics 365. Sort by exception flag. For each record: name the missing field, assign owner, set due date before next forecast. No narrative readouts—only record fixes. Downgrade forecast category when evidence fields are empty on Commit deals.

## Rollout phases

| Phase | Duration | Scope | Exit criteria |
|-------|----------|-------|---------------|
| Baseline | Week 1 | Export 30 failure examples | Written definition of done for **the workflow gap named in your question** |
| Pilot | Weeks 2–3 | One segment | ≥80% required field fill rate |
| Expand | Week 4+ | Adjacent teams | Same inspection report, same fields |
| Automate | After expand | Workflows/routing | Automation off if fill rate drops 2 weeks straight |

## Data & integration notes

Document which objects sync from warehouse or billing before enabling automation. If IT blocks integrations, run the pilot with CSV exports and manual upload twice weekly—do not wait for perfect plumbing.

## RevOps without a big team

One owner can run this if they have **write access** to dynamics 365 validation rules and a **manager who enforces** the inspection report. Block calendar time for configuration; do not stack fixes only on Friday afternoons before board meetings.

## Enablement & documentation

Publish a one-page **definition of done** for **the workflow gap named in your question** inside your sales wiki. Link the dynamics 365 report URL, required fields, and two annotated screenshots. New hires should pass a 10-minute quiz on which fields block saves before receiving live opportunities in the pilot segment.

## Stakeholder alignment

| Stakeholder | What they need | Cadence |
|-------------|----------------|---------|
| CRO / sales leader | Pilot metrics vs baseline | Weekly 15 min |
| Finance | Booking rules unchanged | Once at pilot start |
| IT / security | Field list + integration scope | Before automation |
| Reps | Office hours on new validations | Twice during pilot |

## Discovery questions for your next inspection

Ask the pilot pod: Which deals failed **the workflow gap named in your question** rules two weeks in a row? Which field was empty on every loss? What would have blocked the save if validation were on? Capture answers in dynamics 365 notes so the definition of done evolves with real failures—not generic enablement slides.

## Post-pilot scale checklist

- Required fields copied to adjacent teams unchanged
- Same saved report URL pinned in the Monday leadership agenda
- Automation tickets list the field API names, not vendor feature names
- Success metric frozen for one quarter before changing again

## Dynamics 365 admin notes (copy/paste ready)

Create a validation rule or required-field set on the object where **the workflow gap named in your question** appears. Name the rule with the problem keyword so admins can find it later. Add a custom field **Exception_Reason__c** (or equivalent) for temporary waivers—managers must fill it or the record cannot reach Commit. Archive waivers monthly; patterns indicate bad rules, not bad reps.

## When leadership pushes back

If executives want a faster rollout, show the pilot fill-rate chart and the forecast error before/after. Offer parallel rollout only after two clean inspection weeks. Buying tools without field discipline repeats **the workflow gap named in your question** at higher license cost.

## Tie to forecasting

Map each required field to a forecast category rule: if economic buyer role is missing, the deal cannot sit in Best Case. Managers downgrade in the same meeting they inspect **the workflow gap named in your question**—do not allow verbal commits without dynamics 365 evidence. Re-run the baseline export after 30 days to prove the fix held. Share results with finance and RevOps in the same slide.

<!--pillar-weave-->
## Related on PULSE

- [How are large buying committees in 2027 using consensus tools to stall deals?](/knowledge/q16522)
- [How can I phrase a question to help a rep distinguish between a real objection and a stall?](/knowledge/q14364)
- [How Do I Negotiate a Food Hall Stall Lease and Buildout?](/knowledge/q13779)
- [Top 10 buying committee veto triggers that stall deals](/knowledge/q13562)
- [What's the sequence for getting executive sponsorship aligned before deal stall explodes into budget carry-forward?](/knowledge/q284)
- [How do you audit data center leasing pipeline opportunity hygiene in Dynamics 365 during AE-led pods to prevent duplicate contacts after acquisition when multi-currency ARR rollups?](/knowledge/q10787)

## Setting Up Stage-Specific Duration Tracking in Dynamics 365

To measure procurement stall days by opportunity stage, you first need to ensure your system captures the right timestamps. In Dynamics 365, each opportunity stage transition is logged in the **Opportunity Close** entity or via custom workflow logging. A reliable approach is to create a **custom field** on the Opportunity entity called "Stage Entered Date" that updates automatically when a stage changes.

Use a **real-time workflow** or **Power Automate flow** triggered on stage change to stamp the current date/time into this field. Then, create a second custom field for "Days in Stage" that calculates the difference between the stage entry date and the current date (or the date the stage was exited). This gives you a live, per-opportunity view of how long each deal has been sitting in procurement review, legal approval, or any other stage.

For reporting, build a **custom view** in the Opportunities area that groups records by stage and sums the "Days in Stage" field. You can also export this data to Power BI for trend analysis—look for stages where the average stall days exceed 30% of your typical sales cycle length. This is a strong signal that a process bottleneck exists.

## Analyzing Stall Patterns with Built-in Analytics

Dynamics 365 includes **Out-of-the-Box (OOTB) analytics** under the **Sales Insights** module that can help identify procurement stalls. Navigate to **Sales > Analytics > Pipeline** and filter by your opportunity stages. The **Pipeline History** chart shows how long deals stay in each stage over time, but it aggregates all stages—you need to customize it.

To isolate procurement-related stages (e.g., "Procurement Review," "Legal Review," "Contracting"), create a **custom stage category** in your opportunity sales process. Then, use the **Stage Duration** metric in the **Pipeline Analytics** dashboard. This metric calculates the average, median, and maximum days per stage. A median above your target (e.g., 14 days for procurement review) indicates a stall.

For more granularity, enable **Predictive Scoring** in Sales Insights. The **Lead Score** model can incorporate stage duration as a negative factor—deals stuck in procurement for too long get lower scores, alerting your sales team to intervene. You can also set up **automated alerts** via Power Automate: when an opportunity exceeds a threshold (say, 21 days in procurement), send an email to the sales rep and manager with a link to the record.

## Creating a Custom Report for Procurement Stall Days

If OOTB analytics aren't enough, build a **custom report** using Dynamics 365's **Advanced Find** and **Excel Online** integration. Start by creating an Advanced Find query that returns all opportunities with a stage name containing "Procurement" or "Legal." Include fields: Opportunity Name, Stage Name, Stage Entered Date, Days in Stage (calculated field), and Owner.

Export this data to **Excel Online** (or use **Power BI Desktop** connected to your Dynamics 365 instance). In Excel, create a **PivotTable** with Stage Name in rows and Sum of Days in Stage in values. Add a **slicer** for Owner or Date Range to filter by team or time period. This report can be refreshed daily and shared via a **Power BI dashboard** pinned to your team's Teams channel.

For a more automated approach, use **Power Automate** to run this query weekly and email the report as a PDF. Include a summary row showing total stall days per stage and a comparison to the previous week—this helps your team spot sudden increases in procurement delays without manual data pulls.

## Sources

- Microsoft Dynamics 365 documentation — official product guides on sales and procurement processes.
- Gartner — industry analysis on procurement metrics and sales cycle measurement.
- APQC (American Productivity & Quality Center) — benchmarks and best practices for procurement performance.
- Forrester Research — reports on sales process optimization and pipeline management.
- Harvard Business Review — articles on business process measurement and organizational efficiency.
- Procurement Leaders — industry publication covering procurement analytics and KPIs.

## FAQ

**What exactly are procurement stall days in Dynamics 365?**  
Procurement stall days measure the time an opportunity spends in a stage where the buyer is waiting for internal approvals, budget sign-off, or legal review. In Dynamics 365, you can track this by comparing the actual days in a stage against your expected duration, often using workflow timestamps or custom fields.

**How do I calculate stall days per opportunity stage?**  
Create a rollup field or use a workflow that records the entry and exit dates for each stage. The stall days are the difference between the actual time spent and your predefined benchmark (e.g., 5 days for "Proposal" stage). No exact formula is built-in, so you’ll typically use Power Automate or a plugin to log the duration.

**Can I automate stall day reporting without custom development?**  
Partially. Out-of-the-box, Dynamics 365 doesn’t have a native "stall days" metric, but you can use the "Time in Stage" report or configure a custom dashboard with calculated fields. For full automation, you’ll likely need Power Automate flows or a third-party tool like a RevOps platform.

**What’s a reasonable stall day threshold for common stages?**  
It varies widely by industry and deal size, but a rough range is: 3-7 days for "Qualification," 5-14 days for "Proposal," and 10-30 days for "Negotiation." Anything beyond 30 days in a single stage often signals a stalled deal that needs intervention.

**How do I identify which stages cause the most stalls?**  
Run a report grouping opportunities by stage and calculate the average days per stage. Compare against your sales process targets. The stages with the highest deviation—like "Legal Review" or "Budget Approval"—are your bottleneck. You can also use the "Pipeline by Stage" view with a custom duration column.

**Does measuring stall days help improve close rates?**  
Yes, but only if you act on the data. Tracking stall days reveals where deals get stuck, allowing you to coach reps, adjust stage definitions, or automate follow-ups. Without action, it’s just a number. Most teams see a 10-20% improvement in cycle time after addressing top stall stages.

## Bottom line

Fix **the workflow gap named in your question** on **dynamics 365** with **owner + enforced fields + weekly inspection**. Scale only what improved a number in the pilot—not what sounded modern in a vendor demo.

Was this helpful?

Sources cited

Pulse RevOps operational practicePulse RevOps operational practice

Deep dive · related in the library