New in Allocations: Time-bound rules for clean ownership handovers

Set validity periods on allocation rules so team reorganizations never rewrite cost history.

When a team reorganizes or a service changes owner, the allocation rules that track those costs need to change too. Editing the existing rule is the common workaround, but it silently rewrites history for every past report. You end up choosing between accurate history and accurate present.

Allocation rules can now carry validity periods. Costs match the rule only within the dates you set, and historical reports stay clean when ownership moves.

• Validity periods: Set start and end dates on any allocation rule. Close one rule on March 14 and open its successor on March 15. Past reports reflect the original owner; future reports reflect the new one.
• Multiple periods per rule: Define several non-overlapping time windows on a single rule for scenarios where ownership changes more than once.
• API-first: Create and update time-bound rules through the Allocations API. A reorg script can close ten team allocations on September 30 and open the new structure on October 1, with zero console work.
• Duplicate from editor: Copy an allocation directly from the rule editor, so a handover is a quick adjust rather than a rebuild from scratch.
• Status at a glance: The allocations list shows if each rule is Active, Scheduled or Ended, and you can filter by start and end date.

To get started, open Allocations in the Cloud Intelligence™ console and add a validity period to any rule.