ServiceNow cuts 287 California roles as it hires for AI skills
A 287-person California reduction in force takes effect on September 28, and ServiceNow says it will end 2026 with the headcount it started with.
ServiceNow / Product coverage
ITSM
Source-linked reporting organized by product, platform, and the topics that connect them.
Latest coverage
We were wrong, ServiceNow Brazil doc links can be pinned
A correction. We said no version-pinned Brazil documentation link existed. One does, and this is the URL form that produces it.
Brazil stops catalog roles granting access through ACLs
Most of ServiceNow's Brazil deprecation list is a planning signal. One line is a live change to how catalog role ACL grants work on upgrade.
ServiceNow's Brazil release notes arrive with a date
ServiceNow's Brazil release notes are live and dated, with a documented September 24 Early Availability date and roughly 90 product areas changed.
An analyst says Now Assist is pulling tier upgrades
Cantor Fitzgerald raised its ServiceNow target on client checks describing tier moves for Now Assist. The renewal problem that creates is yours.
ServiceNow's shift zero and the AI tools CIOs can't see
Three quarters of CIOs told diginomica they can't see every AI tool in their systems. ServiceNow's shift zero pitch depends on data they don't have.
ServiceNow's autonomous security specialists go live
The autonomous security specialists ServiceNow previewed in June reach general availability today, and the checklist for trusting them is still thin.
ServiceNow's saved-a-month claim needs a formula
Raleigh's CIO says ServiceNow AI saved a month of time. The number only means something once you know whose month, measured how.
ServiceNow MCP servers still run on your roles and ACLs
ServiceNow's MCP servers keep ACL and role enforcement in place, so what an agent can do is decided by the role model your instance already has.
Analysis and architecture
What automated discovery is actually worth paying for
An accurate CMDB is a precondition, not a benefit. Discovery repays the spend only where change, triage, licence position or security response consume the data.
Deflection design for ServiceNow customer service portals
An employee who fails at self-service tries again tomorrow. A customer may just leave, and may hold a contract saying you owe them an answer.
The platform admin job when agents do the building
Agents can build the field, the flow and the report. What they cannot do is know why your configuration looks the way it does, or which request to refuse.
Why AI consumption spend surprises you at renewal
Consumption pricing moves the spending decision into engineering. Attribute usage to owning teams and capture a baseline before the rate changes.
Six release cycles and the dates you cannot move
Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.
When ServiceNow domain separation earns its cost
Domain separation partitions ServiceNow data for a handful of real reasons and constrains the platform for years. Scoped apps and access control usually fit better.
Where one CMDB for CSM and ITSM stops being a saving
One CMDB for ServiceNow CSM and ITSM saves real work until permissions, reconciliation and asset ownership pull the two populations apart.
ServiceNow family releases and the upgrade you owe
ServiceNow supports only the current and previous release family, so falling two behind turns your upgrade into one ServiceNow schedules for you.
ServiceNow or a lighter service desk, and how to tell
Most teams buying ServiceNow need ticket capture, routing, knowledge and reporting. A real CMDB, cross-team SLAs and non-IT workflow are what justify the platform.
Where ServiceNow ITSM ends and CSM begins
Serving external customers from the ServiceNow incident table holds up until an outage, when the internal clock and the contract clock stop agreeing.
The CMDB two teams claim and nobody owns
When ITSM and security both claim the CMDB, reconciliation becomes everyone's second job, and nobody notices a stale record until a remediation deadline depends on it.
Release Radar: the quarter ServiceNow's release notes got longer
A ledger of what you skipped and a five-line summary do more for ServiceNow release review than reading the whole document ever will.
Give every Dataverse access exception an owner and an expiry
Access exceptions in Dataverse and ServiceNow outlive their reason. Give each one a named owner, an end date, and a record small enough to review.
What a ServiceNow catalog entry owes the support desk
A catalog entry for a Power Platform flow should name who gets paged, what to check first, and who can switch it off. The design document stays where it is.
What a blank Service Cloud escalation reason is telling you
A blank escalation reason usually marks a case that skipped its normal owner. Name what the blank means and route it before you make the field required.
Related guides
ServiceNow CMDB health that people actually trust
Most CMDBs are partly wrong, and the workarounds cost more than the errors. Where the effort pays: identification, relationships, precedence, retirement.
Scoping a ServiceNow ITSM programme before the build starts
Phase one lands or stalls on four calls made before build: real scope, named data owners, whether the CMDB is in, and a counted integration list.
The handover runbook you write before you leave
Writing the two week handover runbook exposes every job only you can run, and the page telling your stand-in what not to attempt is the one that saves you.
What breaks in week two after a ServiceNow go-live
Hypercare catches the loud failures. Notification rules that never fire, one-person assignment groups and SLA clocks on the wrong schedule wait for week two.
The change approval board that actually moves
Most CABs read thirty changes aloud and approve them in forty minutes. Here is a method that puts the meeting's attention on the two that could hurt you.
How to keep a ServiceNow access catalog honest
A practical method for keeping ServiceNow access requests auditable long after the project that justified them ends.
What your ServiceNow CMDB needs before an agent reads it
An agent assessing change impact trusts every CI and relationship it finds. Fix class ownership and identification rules before it goes live.
The first thirty minutes of a Power Automate incident
When a shared Power Automate flow fails, find the work that stopped, name one lead, and write the ServiceNow record before anyone resubmits a run.