Dynamics 365 Project Operations Time-Phased Quotes: Rate Changes, Weekly Pricing and Recalculate Risks

Microsoft's AI at Work roadmap item 576801, titled Dynamics 365 Project Operations: Optimize Project Operations - Enable time phasing of quote and contract lines, targets that exact operational friction. Tracked for the Web platform in Worldwide (Standard Multi-Tenant) environments, the entry lists a March 2025 preview availability date and an April 2027 General Availability target while remaining in development. Because Microsoft began migrating Dynamics 365, Power Platform, and Dataverse release tracking from older Release Plans into the unified AI at Work roadmap in September 2026 —and because earlier Microsoft 365 Message Center notices such as MC1464814 previously pointed to a September 30, 2026 target —administrators should treat the April 2027 date on roadmap ID 576801 as the current planning estimate rather than an immutable shipping guarantee.

Meanwhile, Microsoft Learn documentation for Dynamics 365 Project Operations (applicable to Project Operations Core and, for quote estimation, Project Operations Integrated with ERP) already details how the underlying Time Phasing of Estimates interface, date-effective pricing, and weighted-average roll-ups work in practice. Looking past the high-level roadmap pitch reveals both the practical utility of time-phased lines and a few critical boundaries—especially around weekly date boundaries, whole-document recalculations, and multi-currency margin approximations—that enterprise admins and project managers need to understand before flipping the switch.

Roadmap Status and Governance Scope​

At its core, roadmap ID 576801 describes a system-driven way to apply sales and cost prices automatically on quote line details and contract line details based on their effective dates, rolling those period rates up into a quantity-weighted average on the parent line.

The feature is not forced on end users automatically out of the box; it requires an administrator, maker, or marketer to enable it. According to Microsoft Learn's quote and contract estimation guides, users who open the Line details tab and do not see the vertical time-phased period columns to the right of the standard grid fields must contact their administrator to ensure the Time Phasing of Estimates feature is enabled in their environment.

How Time-Phased Pricing and Weighted Averages Actually Work​

When time phasing is active on a project-based quote or contract, the Line details grid splits into two halves. On the left sit the familiar parent attributes: role, start date, end date, total quantity, unit, average price, tax, and total amount. To the right, Project Operations renders vertical period columns representing the timeline of the engagement.

[Parent Line Detail: 40 hrs | Weighted Avg: $110/hr | Total: $4,400]
   ├── Week 1: 10 hrs @ $100/hr = $1,000  (Initial Price List Rate)
   ├── Week 2: 10 hrs @ $100/hr = $1,000  (Initial Price List Rate)
   ├── Week 3: 10 hrs @ $120/hr = $1,200  (Date-Effective Rate Change)
   └── Week 4: 10 hrs @ $120/hr = $1,200  (Date-Effective Rate Change)

Instead of forcing a single flat rate across an entire engagement, each period column displays three core metrics that can be toggled on or off via the Columns menu:

• Quantity: The slice of effort or units scheduled for that specific period.
• Price: The sales (or cost) rate effective during that period, pulled from date-effective price lists or a role price override.
• Amount: The calculated financial value for that specific period.

The parent line detail then summarizes the total quantity, total amount, and the weighted-average price across all child periods. Because that average is weighted by quantity rather than simple time duration, shifting hours from a cheaper week into a more expensive week will immediately alter both the total amount and the parent line's blended unit price—even if the underlying price lists haven't changed at all.

The Midweek Override Quirk: First-Day-of-the-Week Pricing​

One of the most important technical nuances documented by Microsoft Learn involves how weekly nested lines handle midweek rate changes. In the weekly time-phased breakdown, each week retains the price applicable on the first day of that week.

Microsoft Learn illustrates this with a concrete seven-week scenario spanning January 1, 2025, to February 15, 2025, for 350 hours of work:

1. The baseline role price is $200 per hour.
2. A role price override of $250 per hour is configured with an effective date of Wednesday, February 5, 2025.
3. Because the sixth week begins on February 3, 2025 (prior to the February 5 override), that entire sixth week remains priced at $200.
4. The $250 override rate does not appear in the grid until the seventh week, which starts on February 10, 2025.
5. Across the full 350-hour schedule, the parent quote line detail rolls the periods up to a weighted average price of $206.52.

For billing managers and solution architects, this is a vital piece of business logic: weekly time phasing does not split a single week into daily sub-rates when an override lands on a Wednesday. Your effective dates need to align with your weekly boundaries if you expect a rate bump to take effect immediately inside that week's column.

Navigating and Editing Time-Phased Estimates​

Whether you are working on a bid or managing an active engagement, the day-to-day workflow in Project Operations follows a consistent path on both sides of the sales cycle.

1. Open the Estimate Grid: For quotes, navigate to Sales > Quotes, open the target project quote, and select the Line details tab. For contracts, go to Sales > Contracts, open the project contract, and select Line details.
2. Configure the Timeline: Above the period columns, use the date range selector and the previous/next navigation arrows to frame the project schedule. Use the interval selector to switch between Weekly (best for short-term planning and spotting date-effective rate transitions), Monthly (ideal for long-horizon executive summaries), or Custom intervals. Changing the display interval only regroups how numbers are shown on screen; it never alters the underlying parent total quantity or amount.
3. Adjust Quantities at Two Levels:
   • Parent-level edits: Select the parent Quantity cell, enter a new total, and save. Project Operations redistributes the time-phased breakdown and recalculates the parent weighted-average price and amount.
   • Period-level edits: Select the Quantity cell inside a specific week, month, or custom column, enter the updated effort for that window, and save. The system recalculates that period's amount and rolls the new total quantity, amount, and weighted-average price up to the parent row. Microsoft advises verifying across all periods after manual edits to ensure the full estimate still matches your intended scope.
4. Compare Sales vs. Cost Margins: The default Line details grid displays sales rates. Selecting any line detail unlocks the Open cost detail action on the subgrid toolbar, which opens an expanded view of the corresponding cost rate and cost amount. Users can also switch the form view directly to Line details: Cost to see time-phased cost prices across the grid. Updating shared attributes—such as resourcing unit, quantity, dates, role, or category—automatically syncs between the sales and cost detail records.

Operational Guardrails: What the Roadmap Description Doesn't Tell You​

While the roadmap entry emphasizes automation, reduced manual tracking, and an audit trail of pricing changes, Microsoft's official product documentation highlights three operational constraints that teams must factor into their processes:

• The "Recalculate" Button Resets the Entire Quote or Contract: If an administrator updates rates on the attached project sales price list or the contracting unit's cost price list after lines have already been generated, those changes do not silently rewrite existing estimates. Users must click Recalculate on the Quote or Contract page (or use Refresh after local quantity adjustments). However, selecting Recalculate triggers a system warning: confirming the action resets prices across all quote line details on the quote (or all contract line details on the contract) for both sales and cost. You cannot use the page-level Recalculate action to selectively refresh a single line while leaving manual tweaks on other lines untouched.
• Multi-Currency Margin Calculations Are Approximations: Sales currency defaults from the project price list effective on the line detail's start date, while cost currency defaults from the contracting unit's price list. To report overall estimated margin, Project Operations converts both into the environment's base currency. Microsoft Learn explicitly warns that because date-effective exchange rates are not available in these profitability calculations, currency rounding errors and shifted margins can occur. These numbers are built for operational contract estimation, not statutory financial reporting.
• Audit Trails vs. Line-Detail Mechanics: While the roadmap overview highlights keeping a detailed audit trail and viewing historical pricing totals, the core Microsoft Learn estimation documentation focuses on the live grid mechanics, period distributions, and recalculation prompts rather than a dedicated historical snapshot viewer. Teams requiring strict revision history should verify how their Dataverse auditing and quote revision workflows capture changes before relying on the grid alone—especially since a full Recalculate overwrites existing line-detail prices across the document.

Key Takeaways for Dynamics 365 Teams:

• Verify Feature Enablement: Ensure administrators have enabled Time Phasing of Estimates so sales and delivery teams can access the period columns on the Line details tab.
• Watch Weekly Effective Dates: Remember that weekly nested lines lock in the price effective on the first day of that week; midweek price overrides won't kick in until the following week's column.
• Use Recalculate with Caution: Refreshing price list changes via Recalculate resets both sales and cost prices across every line on the entire quote or contract.