The Biggest ServiceNow Australia Release Updates, Explained
ServiceNow release notes aren’t exactly beach reading. They are useful, detailed, and important, but they are also written for people who need…
Status reporting takes more time than most project managers would like to admit. The inputs are scattered across people, systems, and timelines: resource numbers from one person, schedule updates from another, financial actuals that may already be a week behind. By the time a report is assembled, it’s already slightly out of date, and the process starts over the following week.
The Australia release of ServiceNow SPM addresses this with two Now Assist capabilities built directly into Project Workspace. The first automates the reporting output that project managers currently produce manually. The second runs continuously in the background between formal reporting moments, monitoring project health across multiple dimensions and surfacing findings before they become problems. They’re solving different parts of the same time problem, and they work better together than either does on its own.
Now Assist for SPM can analyze current project data and produce complete status reports without the project manager building them from scratch. Reports cover schedule performance, cost tracking, resource utilization, and key project metrics. They also include predicted health indicators, which are forward-looking signals based on current project trajectory. For example, if a project is tracking on schedule but burning budget faster than planned, the health indicator reflects that trajectory rather than simply reporting green across the board.
Two default templates are available, and they serve different audiences. The first is a one-page executive summary designed for stakeholder communication, covering headline status, key risks, and overall health without requiring the reader to interpret raw data. The second is a more detailed report suited to governance reviews or PMO oversight, covering the same dimensions with greater depth across financials, schedule variances, resource allocation, and RIDAC item status. Both templates can be customized to fit your organization’s reporting standards, and both can be scheduled to distribute automatically on a recurring basis so the report goes out on time regardless of whether anyone remembered to run it.
For project managers running multiple concurrent initiatives, the time this returns is real. The cycle of gathering inputs, drafting a narrative, formatting for the audience, and chasing approvals is happening in parallel across every active project. Automating that assembly work frees up hours per week that currently go to producing information rather than acting on it.
The Project Insights Engine works differently from the status reporting capability, and it’s worth understanding the distinction clearly. Rather than waiting for a reporting cycle, it runs continuously in the background across active projects, monitors data across multiple dimensions, and raises findings directly to the project manager on an ongoing basis.
The engine covers RIDAC items (Risks, Issues, Decisions, Actions, and Changes) alongside financial health, schedule performance, resource allocation, and task and milestone progress. Each of these dimensions has configurable thresholds and severity levels. A threshold here is a defined boundary: when a project’s data crosses it, the engine treats that as a finding worth raising. For example, a team might configure a threshold to flag any open risk item that hasn’t been reviewed in more than 10 days, or any project where actual spend has exceeded forecast by more than 15 percent. The engine monitors those conditions continuously and flags findings when they’re met.
What makes this more useful than a standard alerting system is the context the engine applies when it highlights findings. Consider a project with a milestone that has slipped by five days. In a project with available resource capacity and downstream tasks that have schedule float, that slip warrants attention but probably not an escalation. In a project that’s already over-allocated and approaching a hard external deadline, the same five-day slip is a genuinely different situation. The Insights Engine factors in those surrounding conditions, so the project manager receives a finding that already reflects the context they’d need to assess it, rather than a raw flag that sends them back into the system to gather that context themselves.
Portfolio scale is also worth considering here. A project manager carrying five projects may be able to stay ahead of each one through regular manual review. At fifteen or twenty projects, that manual scan becomes a significant part of the job, and things still get missed. The Insights Engine doesn’t have that constraint. It monitors every active project continuously, regardless of how many there are.
Project managers who’ve used both features for a few months tend to describe the change in similar terms: fewer surprises, fewer status meetings that start from scratch, and more time to think. The platform is handling the monitoring and the formatting. The project manager is handling the work that needs a person.
That’s a meaningful change in how a PMO operates day to day. Teams running fifteen or twenty projects simultaneously get a lot of value from a system that’s watching all of them at once and telling them where to look. The alternative is hoping nothing slips through between check-ins, which is a reasonable hope on a small portfolio and an unreliable one on a large one.
Both capabilities require Now Assist for SPM and the relevant store applications. The configuration work isn’t especially heavy, but there are three things worth reviewing before you enable either feature in a live environment.
The first is project data quality. The Insights Engine draws its findings from the data in the platform, so the quality of those findings depends on how consistently that data is maintained. It’s worth checking that task structures are complete and current across active projects, since the engine can’t identify meaningful schedule findings from projects where milestone dates haven’t been entered or tasks haven’t been assigned. Resource assignments should reflect current reality rather than the original plan from six months ago. Financial actuals should be reconciled frequently enough that the cost data the engine reads is accurate within a reasonable window.
The second is threshold configuration. The defaults ServiceNow ships are a reasonable starting point, but they’re not calibrated to your organization’s risk tolerance or governance standards. A PMO that treats a risk as escalation-worthy at a different point than the default will get findings that don’t match how the team actually works. It’s worth spending time with the threshold settings before go-live, and involving the project managers who’ll be receiving the findings in that conversation. Getting the thresholds right upfront leads to a much better signal-to-noise ratio from the start, and it builds trust in the tool among the people using it.
The third is template customization for Status Reports. The default templates cover the right ground, but organizations with established reporting standards or specific stakeholder expectations will often want to adjust the layout, the level of detail, or the language used in the health indicator descriptions. It’s worth getting that right before automated distribution goes live. Reports that land in stakeholder inboxes in an unfamiliar or confusing format tend to generate follow-up questions that offset a lot of the time the automation was meant to save.
The SPM Delta Deck for the Australia release on the ServiceNow Community covers both features in detail alongside everything else that shipped this cycle.
Beyond20 helps organizations configure and adopt Now Assist for SPM, including the data quality and governance groundwork that determines whether these features deliver on their potential. If you’d like a clear picture of what enablement would involve in your environment, we’d be glad to work through it with you.
