Combined Strategic Planning release notes for upgrades from Australia to Brazil

reference brazil Updated Nov 6, 2026 40 min read brazil-australia-strategicplanning-release-notes.md
Raw file servicenow.com

Consolidated page of all release notes for Strategic Planning from Australia to Brazil.

How to use this page

To help you prepare for your upgrade, we have combined the cross-family Strategic Planning release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Australia to Brazil.

Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

Important information for upgrading Strategic Planning to Brazil

Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed.

Release

Release notes

Australia

No updates for this release.

Brazil

No updates for this release.
## New features

Between your current release family and Brazil, new features were introduced for Strategic Planning.

Release

Release notes

Australia

Next Experience for Demand Management includes a Financials grid for demand records. This grid shows the demand's cost plans, benefit plans, and baselines. From this grid, users can:

-   Add cost plans, benefit plans, and expense lines scoped to the demand.
-   Create and compare baselines for financial data on the demand.
-   Filter by time scope and personalize the grid columns.

Next Experience for Demand Management includes a Dashboard menu for demand records. The dashboard opens by default and is organized into three tabs:

-   Overview
-   Financials
-   Data Quality

Filter dashboard data by department, business unit, portfolio, program, or demand manager. Select a widget, or select View all on a list widget, to open the underlying records with the same filters applied.

Detect similar existing demand records when creating or editing a demand using the identify similar records skill. This skill compares the Name, Description, and Business Case fields for contextual similarity.

  • RIDAC
    • Create and associate risks, issues, decisions, actions, and changes (RIDAC) with all planning items, goals, and EAP (Enterprise Agile Planning) iterations to track planning uncertainties.
    • Access a dedicated RIDAC menu in Strategic Planning Workspace for quick navigation to RIDAC items.
    • Manage RIDAC items with granular role-based access—assign read-only or full edit access to team members based on their responsibilities.
    • Run the scheduled job to populate the planning item field on the existing RIDAC records that were created earlier.
    • Track RIDAC across multiple scopes—view all RIDAC, project-specific RIDAC, portfolio RIDAC, and program RIDAC in a single unified view.
  • Creating iterations for teams in EAP

From EAP version 4.17.0, create Planning Intervals and Sprints directly from the Backlog by entering their start and end dates. The underlying planning calendar entries are created for you, so nobody has to define them before teams can plan.

The following capabilities support this flow:

-   Users with the new `sn_apw_advanced.eap_scrum_master` role create the first iteration for a set of teams that share a planning calendar. After that timeline exists, users with the `sn_apw_advanced.eap_user` role create the following iterations for the other ARTs and teams that share it.
-   Select **Have unique calendars** on an EAP configuration to give each ART that you add afterward its own planning calendar. By default, the ARTs in a configuration share one calendar and follow one cadence.
-   When an Agile Team joins an ART, the in-progress Sprint and the upcoming Sprints are created for that team automatically.
-   Planning calendar entries that your admin defined earlier remain valid. Teams can continue to create iterations within the timelines that those entries define.

Selecting Refresh in the Hierarchy tab now reloads your data without collapsing the rows you've already expanded or resetting your scroll position. Rows deleted by someone else are removed silently, and new child items appear under their expanded parent. If the grid displays more than 100 non-root items or 100 stories, you're asked to confirm before all rows are collapsed.

Select a dependency line on the Planning board to open the dependency record in a side panel, without navigating to the work item's full details page. Review the dependent and prerequisite items, or select Delete to remove the dependency directly from the panel.

Teams connected to CWM can now access the Backlog and Hierarchy tabs in EAP. Because sprints are started and completed from the CWM Board, the Start Sprint and Complete Sprint options are hidden in the EAP Backlog for these teams.

Use the Planning item lens to plan, prioritize, and roadmap work in Strategic Planning Workspace directly with planning items, without configuring organization structure, programs, portfolios, or products. The lens supports all enabled work item types, such as projects and demands, and can be used as a standalone lens or alongside other lenses.

Promote an urgent story to the top of a sprint or push deprioritized work to the bottom of a long backlog without dragging items across multiple pages. Right-click any story, feature, capability, or epic in the EAP Backlog, iteration, or team grid and select Move to top or Move to bottom to re-prioritize the work item in one action. Prioritization changes take effect across all pages, so you can act on shifting priorities even when the work item is far from its target position.

Keep working in your hierarchy without breaking your flow each time you create a work item. When you create a work item with the Hierarchy tab open, it is added to your current view immediately, so you don't need to refresh the page to see a new story, feature, capability, or epic. A new top-level item appears alongside the existing top-level items for the selected portfolio configuration. A new child item appears under its parent when that parent is expanded.

Plan and prioritize without sifting through completed or cancelled work. The Backlog section of the EAP Backlog tab now hides completed and cancelled work items by default, so the list shows only what your teams have to work on. Sprint and Planning Interval (PI) sections continue to show all work items, giving you visibility into both ongoing and finished work for each iteration.

Admins can change these settings for either sections using two new system properties: sn_apw_advanced.show_inactive_items_in_backlog_list for the Backlog section and sn_apw_advanced.show_inactive_items_in_iteration for iteration sections.

Automatically evaluate epic health across six risk dimensions using the Epic status assessment skill in Enterprise Agile Planning. Now Assist analyzes story health, blocked stories, dependencies, progress, timeline, and ownership to return a red, yellow, or green status with plain-English reasoning. Portfolio managers can quickly assess epic risks without manually reviewing stories, timelines, and assignments by selecting the Epic status button on the epic record page.

Gain AI-generated insights for planning items within a portfolio plan using the Portfolio insights skill. Identify planning items that are delayed beyond their planned end date, have delayed starts, or have misalignments between planned and approved dates. Monitor active projects that show early risk indicators but have not yet experienced delays.View AI-generated top root causes and recommended actions for each insight category to help address delays and misalignments effectively.

The AI Insights window displays a timestamp indicating when insights were last generated. You can regenerate insights and recommendations if required to see the changes based on the latest available data.

Users with the sn_align_core.apw_admin role can configure severity thresholds and scoring factors for planning items. These settings control how the Portfolio insights skill classifies insight severity as Critical, Medium, or Low.

  • AI-generated insights for goals - Generate AI‑powered insights using the goal insights skill to gain predictive, actionable visibility into goal health. By analyzing the goal, goal targets, subgoals, and aligned work, the system delivers data‑driven insights that help goal owners and contributors manage risks proactively and improve goal outcomes. Insights include AI-forecasted status, confidence of achieving the goal, targets at risk, and aligned work or recommendations that have been delayed or stalled. - View the AI-forecasted status for goals and targets in the grid, generated automatically via the Goal insights generation scheduled job, along with the rationale for the generated status. - Configure run frequency and set of goals to run the Goal insights generation scheduled job as need. The job is inactive by default.

  • Story generation for epics in Agile Development 2.0 and EAP

Generate a complete user story, including title, description, and acceptance criteria, directly from an epic instead of creating one. By providing one or two lines of context, you can generate a story and edit inline before saving. This skill is available in both Agile Development 2.0 and EAP.

Next Experience for Demand Management delivers a unified experience for managing strategic and operational demands in Strategic Planning. This Next Experience interface consolidates demand creation, assessment, collaboration, and conversion in one place, eliminating context switching and reducing reliance on the classic Demand Workbench.

Help teams manage demands with greater structure and consistency using Playbook in Next Experience for Demand Management.

Playbooks enable you to define multiple governance processes across the organization using a low‑code/no‑code configuration experience. Create clear stages and guided activities from demand intake to completion using a default playbook or a custom playbook. Custom playbooks support multiple demand management processes across your organization’s multiple demand management processes.

Use a playbook activity in Next Experience for Demand Management to associate AI systems with a demand. You can link impacted systems and add new ones directly within the demand workflow.

Generate a concise, structured summary of any demand using the demand summarization skill through the Summarize button in the demand form. The skill reviews the demand fields and helps create a clear summary of the demand.

Use boards in Strategy and Goals to organize and manage your organization’s strategic priorities and objectives. A board is a collection of strategic plans, priorities, objectives, and key results based on your selected filter criteria—helping you stay focused and manage them effectively.

-   Managing boards:
    -   Create boards step by step, choosing whether to base them on strategic plans, priorities, goals, or both. Define what items to display using advanced filter conditions.
    -   Build boards tailored to specific goals by entity type and entity, ensuring focus on the goals that matter most.
    -   Share boards with stakeholders to align efforts and drive shared outcomes.
    -   Add boards to your favorites for faster navigation.
-   Managing strategy and goals using boards:
    -   Create and organize strategic plans, strategic priorities, goals, and key results in a single, focused view.
    -   Associate work or planning items with goals or targets to align your current or future work with your strategic priorities, helping your team achieve goals and targets efficiently.
    -   As the goal or process owner, send notifications to target owners or contributors to ensure timely updates of target actuals.
    -   Target owners and contributors receive reminder notifications for check-in updates before the due date.
    -   With ServiceNow Otto for Strategic Portfolio Management, generate measurable targets for your goals to reduce the effort of defining clear success criteria, and gain actionable insights to identify at‑risk goals, assess forecasted status, and act on AI‑driven recommendations.
  • Portfolio plan goals enhancements
    • Owners and contributors are notified when they’re mentioned in a goal, target, or when comments are added.
    • Define targets across multiple organizational levels with the Assigned entity field in the target form. This enables targets created at higher levels (for example, Company) to be directly assigned to lower levels (for example, Business Unit, Department), eliminating redundant subgoal creation, and streamlining overall goal management.
    • Status — Green, Yellow, Red, or None — rolls up automatically from target breakdowns to the target for targets set to cumulative distribution, and from targets and subgoals to the goal.
  • Portfolio plan enhancements
    • Visualize planning items in lanes with the new Kanban tab in the Planning page and access the Hierarchy tab directly from the same location. These tabs replace the previous access point in the Prioritization tab, offering a more streamlined way to view and manage planning items.
    • Save filter views specific to the Kanban tab and the Hierarchy tab without affecting views in the Prioritization tab.
    • View planning items in the new Hierarchy tab on the Planning page, now sorted using global rank when available. Drag and drop is supported for lowest‑level items, enabling you to rerank them within their groups.
    • Share a portfolio plan using the Copy link option. This provides access to existing users who have access to the portfolio plan.
    • Make a portfolio plan public and share the copied link with Strategic Planning Workspace users, without inviting them individually or as a group. Note that users accessing a public portfolio plan with the shared link cannot view scenarios within the plan.
    • Expand or collapse portfolio plan header to maximize screen space while planning.
    • Edit the default view within a portfolio plan and save changes using the Save view option.
    • View additional status attributes — cost, resource, schedule, and scope — for planning items in Strategic Planning Workspace. For project planning items, these attributes are synced automatically from the latest published project status report. For other planning items, these attributes can be set manually. Note that project status report attributes synced from the Project status (project_status) table are read-only in Strategic Planning Workspace and can't be edited directly.
    • Set planning item status to No status when a status has not been determined, in addition to the existing Green, Yellow, and Red values, giving planners the flexibility to update the status as needed. By default, the status is set No status when a planning item is created.
    • Display rollup bars at parent levels in the hierarchy view and choose the date type to display — approved, planned, or actual. Use the comparison option to compare date types, such as approved versus planned dates, to identify schedule misalignments.
  • Hierarchy tab for EAP teams

Gain visibility into how your work connects to broader organizational goals by viewing the complete work item hierarchy directly in the EAP workspace. Expand any epic to see its capabilities, features, and stories across Solution Trains, ARTs, and Agile Teams without switching between multiple screens or running separate reports.

Customize your view by selecting which columns appear in the hierarchy grid and adjusting column widths to match your workflow. Your column preferences persist across sessions, so your configured view is ready each time you return.

The Hierarchy tab requires your admin to enable it through the sn_apw_advanced.enable_hierarchy_view system property. See Enable Hierarchy tab in EAP.

Open work items from the EAP Backlog and Hierarchy pages in a new browser tab, so you never lose your context. Right-click any work item, or use the item options menu, to open its full details in a separate tab. This feature lets you review and compare multiple work items side by side without losing your current view.

  • Financials for planning items

    • Migration of financial baselines:
      • Migrate the financial baselines of projects, which includes investment currency support.
      • While migration, financial baselines will now include actuals, costs, benefits, and budget values from the project currency to the investment currency.
    • Streamlined currency fields while using multicurrency:
      • New and existing customers will now see only investment currency fields in demand and project records.
      • Planned costs, actual costs, planned benefits, actual benefits, and budget fields are included in the financial baselines.

  • Admin role enhancements in Feedback

The read role sn_align_core.pf_read and write role sn_align_core.apw_admin are added to the following system properties in Feedback and Product idea:

-   sn\_apw\_advanced.product\_feedback\_allowed\_non\_planning\_items\_for\_link\_item
-   sn\_apw\_advanced.product\_feedback\_product\_idea\_filters
-   sn\_apw\_advanced.product\_feedback\_feedback\_filters
-   sn\_apw\_advanced.feedback.idea\_feedback\_queue\_address

Brazil

Create, edit, and break down goal targets on fiscal calendars. The supported calendar types are Standard, 13-Period, 4-4-5, 4-5-4, and 5-4-4. Target breakdowns, due dates, and roll-ups follow the fiscal periods of the active calendar. Gregorian calendar behavior does not change.

Set the goal calendar to Gregorian, which is the default, or to fiscal. Fiscal calendars come in three types: Regular, 4-4-5, and 13 Period. Switch from Gregorian to fiscal in the sn_gfa.calendar_type system property. Switch between fiscal types by changing the fiscal calendar type property, setting the fiscal unit, and regenerating the fiscal periods. A calendar change can make targets stale.

Set check-in due dates by fiscal period for goal targets. When you enter actuals on a target breakdown, the check-in due date updates to match the fiscal period. Reminders for the Period check-in frequency follow the fiscal calendar.

View goals in fiscal mode in the Strategic Planning workspace. The planning range, time scale, saved preferences, graph, stale target actions, and check-in panel all use the fiscal periods of the active calendar. The grid and goals list show the generated fiscal period names.

Choose a check-in frequency that the active fiscal calendar supports. The target form offers only the frequencies that are valid for the calendar and the target date range, including Period. The target breakdown preview shows each generated period with its display name. The server validates every frequency and period on save, so a rejected change keeps the current breakdowns and shows the reason.

Identify goal targets that become stale after a goal calendar change. Only targets with breakdowns can become stale, and stale targets stay locked until they are recovered. Recover a stale target in one of two ways. An administrator runs the Goal calendar alignment - Reset check-in frequency for stale targets scheduled job, and the target owner then selects a check-in frequency again. Or the target owner duplicates the target and sets a check-in frequency on the copy. The copy starts without the remarks, work notes, and history of the stale target.

Generate goal targets with the AI target generation skill on fiscal calendars. Generation uses the active calendar, the allowed frequencies, and the generated period names and dates. The server validates the generated output before it fills the new target form. Goal insights read fiscal period history in period order and do not assume Gregorian months or quarters.

Automation writes target values into the breakdown of the current fiscal period, using the fiscal period boundaries in the fiscal calendar time zone. Check-in history records take their reporting period from the fiscal calendar, and the roll-up remark shows the fiscal period name.

Teams that do several kinds of work in one state can't see where that work waits. Substates divide a state into steps that match how your team works. A scrum master creates substates on the Substates tab of Team Settings, sets their order, and marks one default for each state. When you change the state of a story, the substate changes to the default of the new state. The Substate field is hidden for teams that have no substates.

A lane that holds more work than planned can hide where work is stuck. WIP limits make those lanes visible on the Planning board. Each lane header shows the number of stories and the limit, for example 3/5. An amber header marks a lane at its limit. A red header with an alert icon marks a lane over its limit. Counts update as you move stories, and a limit never blocks a move.

Each team works differently, so each team sets its own limits. A scrum master selects Team Settings on the Planning board and adds limits on the Kanban WIP limits tab. Choose a lane, which is a state or a substate of the team, and enter the limit. The Team field is set automatically, and each lane can have one limit.

Partition demand data by any criteria, such as department or business unit, using Enterprise-Wide Deployment (EWD) partitioning on the Demand table and related entities. Demands are stamped with a matching partition, and users see only the demands, list views, search results, and dashboards for the partitions their role grants them.

EWD for demands includes the following functionalities:

-   Demand experiences: Define the way a particular demand should work including its form view, modules, and dynamic attributes. For example, a particular view or certain functions available on a demand or menu items hidden or visible for different types of demands.
-   Demand partitions: Control the data visible to different users.
-   Demand partitions dashboard: Dedicated dashboard for different demand partitions.

Smart assessments are now available for demands, which are triggered on moving the demand to screening. These assessments are controlled by the sn_align_ws.enable_smart_assessments system property. After this property is enabled, smart assessments are triggered for the new demands and the ones that aren't yet in the screening state.

The smart assessment form is more intuitive and supports text-based questions. The assessments are available at the individual demand record and in a consolidated Smart Assessments module in the main navigation menu. This module displays all assigned smart assessments across demands.

Plan and manage resource assignments for a demand from the Resources tab in Next Experience for Demand Management. The resource board shows assignments alongside resource capacity so you can confirm availability before converting a demand to a project. Create, copy, move, split, end, or reassign resource assignments directly from the grid, group by primary group, role, or skill, and use the allocation heatmap to identify over-allocated and available resources. Use the Resource Finder to get fit-scored, ranked resource recommendations with rationale for unassigned work.

Run Scrum and Kanban teams under the same Agile Release Train (ART). Select a planning methodology when you add a team to an ART, or set the Planning methodology field on an existing team. Kanban teams plan from the team backlog: sprint controls are hidden, planning intervals skip them, and the Home page shows the Kanban Team dashboard. Both team types appear side by side on the ART planning board.

Track targets that must hold steady across every check-in period using the Maintain above, Maintain below, and Maintain constant target types. Each breakdown period's planned target defaults to the final target value, or 0 if no final value is set, and you can edit it for each period. Target progress is the share of periods that met the condition: at or above the target for Maintain above, at or below it for Maintain below, and within a tolerance band around it for Maintain constant. The default tolerance band is ±5%, and administrators can change it with the sn_gf.maintain_constant_tolerance_percent system property. For example, a Maintain above target of 75 with quarterly actuals of 78, 72, 80, and 76 shows 75% progress, because one of the four quarterly actuals didn't meet the target.

When you change the start date, end date, or final target value, the breakdowns and planned values adjust automatically and actuals in the remaining periods are kept. The Target value distribution field is hidden for Maintain types.

Differentiate goals and targets that share a name across teams by using the Number field. Goals use the OBJ prefix and targets use the KR prefix, for example OBJ0004512 and KR0009871. The number appears on goal and target forms, list views, board views, and exports. The GF - Override Goal and Target Number fields with customized prefixes scheduled job updates existing GOAL and TRGT numbers to OBJ and KR and keeps the numeric portion. An administrator can run the scheduled job to override default populated prefixes.

Access portfolio risks, issues, decisions, actions, and requested changes (RIDAC) directly from the portfolio plan using the dedicated RIDAC page within the portfolio plan. View all portfolio governance items in a single, integrated interface without navigating to the separate RIDAC menu. The RIDAC page reduces context-switching and improves portfolio visibility by consolidating governance data. The portfolio plan RIDAC displays the RIDAC items that match the portfolio plan's criteria or belong to the planning items of that portfolio plan.

As a portfolio manager, show or hide the RIDAC page of your portfolio plan. This capability helps you share only the portfolio plan data that matters to your stakeholders and restrict access to the other data.

Access dedicated program planning views automatically created with zero setup. Navigate to the new Programs menu and click any program to open its dedicated plan with Prioritization, Roadmap, Kanban, and Financials views. New programs get plans instantly; existing programs receive them through an automatic one-time backfill (500 at a time, newest first). Role-based access ensures users with the sn_align_core.ap_read_only role can read, users with the sn_align_core.apw_user role can manage items, and program managers are automatic plan owners.

View and manage program-scoped planning data in a focused, streamlined interface. Program plans display only that program's planning items. The Financials tab defaults to your fiscal calendar; if the fiscal calendar doesn't span the program dates, the system gracefully falls back to Gregorian with an explanatory message. Making the portfolio plan public and scenario planning for these program portfolio plans are hidden.

Receive email notification when a scenario is approved. The system sends the notification to the scenario approver and portfolio owner. During the approval process, the portfolio plan becomes read-only to prevent unintended modifications and maintain data integrity.

Automatically determine target status based on actual achievement percentages. When you enter actual values for a target period, the system compares the achievement percentage against predefined thresholds and automatically assigns a status (Green, Yellow, or Red). This eliminates manual status selection, reducing data entry errors and improving organizational governance.

Status is calculated and updated when you enter actual values using the formula: ((Actual Value - Start Value) / (Planned Target - Start Value)) x 100. Target owners can override automatically calculated status values at any time. If you update the actual value after a manual override, the system recalculates the status automatically.

Enable administrators to customize automatic status calculation thresholds and enable or disable the feature based on organizational requirements. By default, automatic status calculation is enabled with system-defined thresholds of Green (≥90%), Yellow (75-89%), and Red (<75%).

Administrators can adjust threshold percentages using the system property sn_gfa.target.auto_status.thresholds. To disable automatic status calculation and revert to manual status selection, set the system property to false.

Set up teams that run Sprints without a Planning Interval above them by using the Scrum Configuration in Enterprise Agile Planning. It defines a single team level of the type Agile Team and allows the Epic and Story work item types. Story is the default work item type for that level and is mapped to the new Scrum Sprint planning calendar. The Epic methodology field is set to Scrum. Like the other default configurations, the Scrum Configuration is inactive until you activate it.

Let each team set its own iteration dates by selecting Allow unique cadence for each team on an Enterprise Agile Planning configuration. If the configuration has planning calendars at more than one team level, each top-level team receives its own calendar. If the configuration has a single level of iterations, such as Sprints only, the iterations carry their own start and end dates instead of following a planning calendar entry. Teams that you add after you select this option receive a unique calendar, and teams that already exist continue to use the default calendar of the configuration.

See how the scope of a Sprint moved during its run by using the Spillover and New scope fields on the Enterprise agile iteration [sn_apw_advanced_eap_iteration] record. Spillover is the sum of the story points of the committed stories that are no longer in the iteration when it completes. New scope is the sum of the story points of the stories that were added after the iteration started. Both fields are read-only and are calculated when you complete the iteration. Select a value to open the stories that it counts.

Tailor demand summaries to your organization's process by copying the base demand summarization skill and customizing it with your own input fields, related entities, and prompt. When you activate a copy of the demand summarization skill, the previously active skill, either the base skill or an earlier copy, is automatically deactivated. Only one version of the skill can be active at a time.

Create and track demands without leaving the conversation-first Employee Slate workspace. Describe the demand in a conversation to have matching catalog items identified and relevant fields prepopulated from your message, then track its status, activity, and progress using the new My Demands widget on your canvas or the standard Requests widget. Demands appear in Employee Slate only when both Project Workspace and Employee Slate Core apps are installed.
## Changes

Between your current release family and Brazil, some changes were made to existing Strategic Planning features.

Release

Release notes

Australia

The demand summary is generated in the AI Overview tab instead of the Details tab. The skill is set to trigger automatically, that is, the summary is generated on landing in this tab. Auto-generation is on by default and applies to demands in Submitted, Screening, Qualified, or Approved states. You can define the trigger to manually trigger as well, where users must select the Summarize button to generate the summary.

ServiceNow Otto introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto® is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.

The execution URL is updated on the planning item demand. New planning items demand will automatically use the new execution URL. The execution URLs on existing planning item demands continue to work but doesn't reflect the updated navigation. Run the Update Demand Planning Item Execution URL scheduled job to update the execution URL on the existing demands.

The EAP role hierarchy is updated. The sn_apw_advanced.eap_admin role now contains sn_apw_advanced.eap_scrum_master, which in turn contains sn_apw_advanced.eap_user. The sn_apw_advanced.eap_admin role no longer contains sn_apw_advanced.eap_user directly.

As a result, the following actions require the sn_apw_advanced.eap_scrum_master role:

-   Changing the start date or the end date of an iteration.
-   Creating, editing, and deleting planning calendars and calendar spans.

Because sn_apw_advanced.eap_admin contains sn_apw_advanced.eap_scrum_master, users with the admin role keep access to these actions.

The demand summarization skill incorporates data from related entities when generating a summary. In addition to demand record fields, the summary includes insights from demand tasks, cost plans, monetary and non-monetary benefit plans, resource assignments, and work notes. The generated summary covers business requirements, timeline, risks, stakeholder comments, cost, effort, monetary and non-monetary benefits, and ROI.

  • Next Experience for Demand Management - The Demands icon has been added to the Strategic Planning L1 menu to open the All Demands home page. - The State field on the All Demands page has been color-coded for each state value. - The Playbook, Details, and Docs tabs have been added to the L2 menu of each demand to clearly and consistently group information.
    • The Details tab has been added to add and manage demand information such as financials and resource assignments.
    • The Playbook tab has been added to define clear stages and guided activities to read and follow. Selecting the name of a stage or activity navigates you to that stage or activity in the playbook. The Skip, Update, and Mark Complete options have been added to the activities of the playbook.
    • The Docs tab has been added to view and manage the documentation on the demand.
-   If you have the AI Control Tower plugin installed and the investment type of the demand is set to artificial intelligence:
    -   The **AI Associations** section in the Demand details is displayed. The following fields are included:
        -   **Product**: Enables you to select the product or system that the demand relates to.
        -   **Impacted AI systems**: Links the impacted AI systems with the demand. You can select existing AI systems from the list or remove systems that are no longer relevant.
    -   The **AI Checkpoint** stage is added to the demand default playbook. This stage includes the **Product** and **Impacted AI systems** fields.
    -   The **Create AI System** option is added to the **Details** page of a demand for users with the sn\_ai\_steward role.
-   [Australia Patch 5](https://www.servicenow.com/docs/access?context=australia-patch-5&family=australia&ft:locale=en-US)The **Financials** grid is added to the navigation menu of a demand. It has options to create cost plans, monetary benefits plans, expense lines, and create and compare baselines.
-   The **Dashboards** menu item is added for demands, providing **Overview**, **Financials**, and **Data Quality** tabs.
-   The following items have been added to the demand form and are available if you have the identify similar records AI skill activated:
    -   The **Identify similar demands** button, which identifies and displays similar demands.
    -   The **Similar Demands** tab in **Details**, which displays the list of similar demand records identified by AI.
-   The **AI Overview** tab is added to the navigation menu of a demand. It generates a demand summary on landing if the skill trigger is set to automatic. If the trigger is set to manual, a **Summarize** button is available to generate the summary.

The following fields have been added to the Target form to support defining targets at multiple organizational levels.

-   **Assigned entity**
-   **Company**
-   **Business Unit**
-   **Department**
-   **Portfolio**
-   **Product model**
-   **Value stream**
-   **Initiative**
-   **Strategic Program**

The Status field has been added to the Strategic Priority form, enabling you to set the status of a strategic priority as None, Green, Yellow, or Red.

The Kanban and Hierarchy views have been removed from the Prioritization page and are now available as separate tabs in the Planning page. This change improves navigation by consolidating all planning-related views in one place.

The Now LLM Service is no longer the default model provider for new or inactive AI assets. A third-party LLM is now selected by default, while existing configurations using the Now LLM Service continue unchanged. The Now LLM Service is still available for manual selection.

Brazil
  • Target import check-in frequencies

Target import accepts Period as a check-in frequency. Import rejects a check-in frequency that the active calendar does not allow and shows a message that states the reason.

When you duplicate a target, the copy keeps the source check-in frequency only if the active calendar supports it. The copy gets new breakdowns from the active calendar and never copies the source breakdowns. The source target does not change.

When open child sprints prevent you from completing a Planning Interval, you must know which sprints to close. The completion alert now lists every open sprint by team. Each sprint links to the Agile board of the team for Agile Development 2.0 sprints. CWM teams link to the CWM board. All other sprints link to the EAP Backlog of the team.

Sprints that aren't complete are cancelled when you set a team's Planning methodology to Kanban, including the team's current sprint. Completed and cancelled sprints aren't changed, and work items stay assigned to the sprints that were cancelled. A team connected to Collaborative Work Management (CWM) can't be switched to Kanban while it has active or planned sprints.

Each existing agile team is assigned a planning methodology when you upgrade: Scrum if the team or its configuration has a business calendar, Kanban if neither has one. Because Kanban teams don't show sprint controls, review any team created without a business calendar and set its Planning methodology to Scrum if that team plans in sprints.

Automatic status calculation extends to Maintain type targets. Each breakdown period is set to Green when its actual meets the Maintain condition and Red when it doesn't.

Change a target's type after actuals are recorded, without deleting and recreating the target. Actuals to date are kept and recorded in the latest breakdown period. Planned values are recalculated for the new type, and progress is evaluated under the new type's logic. A confirmation message appears before the change is applied, and selecting Cancel keeps the previous type and data. Type changes are captured in the audit history.

Select the target type before the unit of measure when you create a target. Milestone sets the unit of measure to Yes/No, and Maximize, Minimize, and Maintain types default to Count. Later type changes keep the unit of measure you selected. If it isn't valid for the new type, you're prompted to pick one. This applies to the target modals in Enterprise Goals and portfolio plan goals, and to inline editing in the target list.

The None status choice is labeled No status for goals, strategic priorities, targets, target progress, and target breakdowns.

View decisions alongside other RIDAC items for portfolios and programs when you open RIDAC from the Strategic Planning Workspace RIDAC menu. The Portfolio Risks and Program Risks menus are renamed RIDAC by Portfolio and RIDAC by Program.

Generate Maintain above, Maintain below, and Maintain constant targets with ServiceNow Otto target generation skill for goals that sustain a level rather than move toward one, such as platform uptime, a cost ceiling, or team headcount. When a Maintain type is suggested, the target modal shows the threshold value and hides the start value field. Review the suggested type and change it if needed before you save the target.

ServiceNow Otto goal insights include Maintain-type targets (Maintain above, Maintain below, and Maintain constant) when summarizing goal progress.

When a demand with resource assignments is converted to a project, assignment offsets are recalculated against the project's schedule, which counts only the working days defined in the project schedule, instead of the demand, which has no schedule and counts every calendar day.

Run the Update Demand Planning Item Execution URL scheduled job to update the execution URLs on your existing demands to the latest format.

The maximum date range for exporting a roadmap to PowerPoint increased from 1 year to 3 years, within the start and end dates of the portfolio. The exported timescale adjusts to the range you select: months for a range of 1 year or less, and quarters for a range longer than 1 year.

  • Program portfolio plan enhancements

    • Program details — Select the information icon next to the program name to view the planning item types, program timeline, and program manager.
    • Program value for new items — When you create a demand or project from a program portfolio plan, the Program field is prefilled with that program.
    • Prioritization default layout — The default Prioritization view shows the Rank, Name, Planning state, Planning item type, Status, Cost status, Resource status, Schedule status, Scope status, Percent complete, Primary goal, and Owner columns.
    • Goals tab — Program portfolio plans include the Goals tab, which shows all primary and non-primary goals linked to the planning items in the plan, along with goals assigned directly to the program.
    • Public views — Any user who can access a program portfolio plan can create and update its public views. Previously, only plan editors could create or update public views.

  • Financials

Added in-context help (hover info icons) on the Financials page widgets, explaining how the key fields like Budget, EAC, Planned Cost, Actuals, Return, ROI, and NPV are calculated.

  • Enterprise Agile Planning configuration options
    • The Have unique calendars option is renamed to Allow unique cadence for each team.
    • An EAP admin can now clear the Allow unique cadence for each team option after selecting it. Selecting the option doesn't change the calendars or the iterations that already exist.
    • The Scrum Sprint planning calendar type is available by default, alongside Planning Interval and Sprint.
  • Iteration dates in Enterprise Agile Planning
    • The Enterprise agile calendar entry field on the Enterprise agile iteration [sn_apw_advanced_eap_iteration] table is no longer mandatory, which supports iterations that carry their own start and end dates. A fix script makes the field optional when you upgrade.
    • Users with the sn_apw_advanced.eap_user role can set the start date and the end date while they create an iteration. They can change those dates afterward on an iteration that doesn't follow a planning calendar entry. However, changing the dates on an iteration that follows a planning calendar entry still requires the sn_apw_advanced.eap_scrum_master role.
  • Sprint sync with Agile Development 2.0
    • Sprints that don't follow a planning calendar entry now sync to Agile Development 2.0 by using the start date and the end date on the iteration.
    • Changing the start date or the end date of an iteration now updates the dates on the corresponding Sprint in Agile Development 2.0.
  • Program planning updates and enhancements
    • Programs menu addition — A new Programs menu has been added to the workspace as L2 menu, positioned below Portfolio Plan. This menu lists every program in your portfolio and provides single-click navigation to each program's enhanced planning view.
    • Role-based access for program planning — Users with the sn_align_core.ap_read_only role have read access to program plans (where they already have program-level read access). Users with the sn_align_core.apw_admin and program manager roles receive full access to create, update, and manage planning items within program plans
  • Summarize demands using AI

The default trigger is not set to Automatic for demands in any state. You can select how you want the skill to be triggered for any state.
## Removed

Between your current release family and Brazil, some Strategic Planning features or functionality were removed.

Release

Release notes

Australia

No updates for this release.

Brazil

No updates for this release.
## Deprecations

Between your current release family and Brazil, some Strategic Planning features or functionality were deprecated.

Release

Release notes

Australia

No updates for this release.

Brazil
  • Now LLM Service

Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. The latest industry advancements are available alongside sovereignty-focused options. All models are hosted and governed by ServiceNow with the same infrastructure and data protections. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the KB3066214: ServiceNow Otto Model Upgrades article in the Now Support Knowledge Base.

  • Process Mining

Starting Brazil release, Process Mining Content Pack for SPM (com.snc.itbm_po) will be migrated to Process Mining Content Pack store application. Upgrade your instance to Brazil or higher releases. For more information, see Process Optimization documentation.
## Activation information

Review information on how to activate Strategic Planning.

Release

Release notes

Australia
  • Activation information

Install Strategic Planning by requesting it from the ServiceNow Store. Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

Important: Strategic Planning is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes.

Brazil
  • Activation information

Install Strategic Planning by requesting it from the ServiceNow Store. Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store.
## Additional requirements

If any additional requirements were introduced or changed for Strategic Planning we have noted them here.

Release

Release notes

Australia

No updates for this release.

Brazil

No updates for this release.
## Browser requirements

If any specific browser requirements were introduced or changed for Strategic Planning we have noted them here.

Release

Release notes

Australia

No updates for this release.

Brazil

No updates for this release.
## Accessibility information

Review details on accessibility information for Strategic Planning, such as specific requirements or compliance levels.

Release

Release notes

Australia

No updates for this release.

Brazil

No updates for this release.
## Localization information

If there are specific localization considerations for Strategic Planning we have noted them here.

Release

Release notes

Australia

No updates for this release.

Brazil

No updates for this release.
## Highlight information

If there are specific highlight considerations for Strategic Planning we have noted them here.

Release

Release notes

Australia
  • Identify similar demand records in Next Experience for Demand Management based on contextual similarity in the name, description, and business case content using the identify similar records AI skill.
  • View and manage cost plans, benefit plans, and expense lines directly from the demand records in the Financials page in Next Experience for Demand Management.
  • Monitor demand distribution, financials, and data quality at a glance using Dashboard in Next Experience for Demand Management.
  • Create and manage demands from the Next Experience for Demand Management in Strategic Planning. Guide demand managers and users through predefined stages and actions for each demand process using Playbooks in Next Experience for Demand Management.
  • Link AI systems to a demand using a playbook activity in Next Experience for Demand Management. Generate a concise summary of a demand using the demand summarization skill.
  • Use boards in Strategy and Goals to group and manage strategic priorities and objectives for your organization. Use the goal insights skill to generate insights for goals to gain predictive, actionable visibility into goal health.
  • Send notifications to target owners or contributors to ensure timely updates of target actuals. Define targets across multiple organizational levels with the Assigned entity field in the target form.
  • Consistent financial reporting across all baselines by support of investment currency on migrated financial baselines.
  • Simplified user experience and focus on investment level financials view on investment currency fields for new customers. Complete and accurate currency data in all financial baselines for existing customers are now upgraded to include investment currency values.

See Strategic Planning for more information.

Brazil
  • Define and manage strategic plans, goals, and targets while aligning planning items across portfolio plans, enterprise agile iterations, and organizational hierarchies to drive business outcomes.
  • Prioritize, roadmap, and score work items using predefined or custom lenses, with support for capacity planning, financial planning, and scenario planning to optimize portfolio decisions.
  • Capture and assess customer feedback and demands through configurable playbooks, using AI to summarize, identify similar items, and accelerate prioritization before converting them into work items.
  • Track risks, issues, decisions, actions, and changes (RIDAC) across planning items, iterations, and goals, and gain actionable insights through dashboards covering strategy, planning, feedback, and execution.

See Strategic Planning for more information.
**Parent Topic:**[Products combined by family](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/delta-australia-brazil/rn-combined-intro.md)
Search documentation
Search document titles and file paths on the brazil branch