The Scenario
The infrastructure team is scheduling the next round of server patching. A change planner has an Excel workbook with 25 configuration item sys_ids — the servers being patched — in column A. Before any change requests get submitted, the team needs to know the first three available change windows for each CI so they can pick dates that do not conflict with business-critical maintenance freezes. Getting that data out of ServiceNow and into the planning workbook is today's task.
The bad version:
- Open ServiceNow Change Schedule, search for the first CI sys_id, navigate to the schedule view, identify the next three available windows, write down the start times.
- Repeat for all 25 CIs.
- Discover that for 6 of them the schedule view does not show future windows because they are under a different maintenance group, so you have to look those up separately.
Infrastructure maintenance planning requires actual dates. This process of manually pulling schedule data and writing it into a planning workbook is where projects stall — not because the information is not there, but because getting it out is surprisingly painful.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Excel workbook. It reads the CI sys_id column, queries the ServiceNow change schedule for each, and writes the next available windows directly into the planning workbook.
For each CI sys_id in column A, get the available change schedule windows from ServiceNow and write the next 3 available start times into columns B, C, and D
What You Get
- Three available change window start times per CI sys_id, written into columns B, C, and D
- Windows reflect the current ServiceNow change schedule and maintenance freeze calendars
- CIs with no available windows in the next 90 days receive "NO WINDOWS" in column B
- The full batch runs in one pass — no tab-by-tab navigation
What If the Data Is Not Quite Ready
You need window end times and duration alongside the start times
The patch coordinator needs to know how long each window is to schedule the team.
For each CI sys_id in column A, get the next 3 available change schedule windows from ServiceNow and write the start time, end time, and duration in minutes into columns B, C, and D for the first window, E, F, G for the second, and H, I, J for the third
Some CIs do not have individual schedules and inherit from a parent CI
Inherited schedules need to be pulled from the parent CI rather than the CI directly.
For each CI sys_id in column A, get the available change schedule windows from ServiceNow — if the CI has no individual schedule, fall back to the parent CI's schedule — and write the next 3 available start times into columns B, C, and D, noting any fallbacks in column E
You only want windows that fall within a specific date range for the patch cycle
The patching cycle runs from June 1 to June 30 only.
For each CI sys_id in column A, get available change schedule windows in ServiceNow between June 1 and June 30, 2026, and write the first 3 start times into columns B, C, and D; write "NO WINDOWS IN RANGE" if none are available
Full kill chain: pull windows, flag CIs with no availability, sort by earliest window
For each CI sys_id in column A, get available change schedule windows in ServiceNow between June 1 and June 30, 2026, write the next 3 start times into columns B through D, flag any CI with no available windows in that range as "BLOCKED — NO WINDOW" in column E, and sort the result by the earliest available start time ascending so the patch coordinator can schedule in order
The patch schedule is ready to present without anyone spending an afternoon in ServiceNow Change Schedule.
Try It
Get the 7-day free trial of SheetXAI and open the Excel workbook with your CI sys_id list, then ask it to pull the ServiceNow change schedule availability for all 25 servers at once. For submitting change requests once dates are selected, see the bulk-create-change-requests spoke or return to the ServiceNow hub.