Runs the weekly change advisory board on the live change calendar: every change with its risk, conflicts and affected services, and the decision written back to the change request.
Today the change manager exports the week's changes on Tuesday, pastes them into a deck, and the board spends the first 30 minutes finding out which changes touch the same servers. Decisions are typed into ServiceNow after the meeting, and the ones that were deferred are found again the next week.
The app picks up every normal change that waits for board approval and starts within the next 14 days, and shows it with its risk, its configuration items and the services those items support, the open incidents on the same items and every other change in the same window on a related item. The change owner completes the plan, test evidence and backout plan, the service owner assesses the impact on the service, and the board members review the conflicts and risk before the meeting, so the meeting itself deals with the 5 changes that need a discussion. The CAB chair records the decision and any new window in the app, and the decision, the schedule and the note are written to the change request in ServiceNow within seconds.
| Function | Level | Does |
|---|---|---|
| Change owners | Level 1: change owner | completes the plan, test evidence and backout plan |
| Service owners | Level 1: service owner | assesses the impact on the service and its users |
| Change advisory board | Level 1: board members | review risk and conflicts before the meeting and vote |
| Change advisory board | Level 2: CAB chair | decides and records the outcome |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 This week's changes | grid of changes by start, risk, service, owner and readiness; conflict and incident flags; open button |
| S02 Change detail | plan, test evidence, backout plan, affected configuration items with relations, open incidents on them, other changes in the window; complete |
| S03 Impact assessment | service owner view: services affected, users, business calendar, impact rating; confirm |
| S04 Board review | changes ready for the meeting with votes and comments; the 5 to discuss first; decision buttons: approve, approve with a new window, defer, reject; note |
| S05 Calendar | changes by day and service with conflicts highlighted; drag to a new window |
| S06 Change board | changes approved, deferred and rejected per week; changes followed by an incident; readiness at meeting time |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Change request | the change request, its type, risk, window and approval | ServiceNow |
| Configuration item | the configuration items the change touches and their relations | ServiceNow |
| Incident | open incidents on the same configuration items | ServiceNow |
| Employee | change owners, service owners and board members | ServiceNow |
| Object | What changes |
|---|---|
| Change request | board decision written to the approval record; state set to scheduled, deferred or rejected; start and end updated when the board moves the window; note added |
Start: A normal change waiting for board approval whose planned start is within the next 14 days.
# start criterion, in canonical fields; each system page shows it in that system's fields
{change.type} = 'normal' and {change.approval} = 'requested' and {change.start} <= today + 14| Step | Moves when |
|---|---|
| Change picked up | risk, configuration items, related changes and open incidents attached; readiness checklist shown to the owner |
| Ready for review | plan, test evidence and backout plan complete; service owner's impact rating recorded by Monday 12:00 |
| Pre-reviewed | board members vote and comment by Tuesday 17:00; changes with a conflict or a dissent go to the discussion list |
| Decided | CAB chair records the decision at the Wednesday meeting; a new window resolves the conflict on the calendar |
| Written back | decision, state and window written to the change request; owners notified |
| Component | Trigger → action → outcome |
|---|---|
| grd_changes | on load → read the changes in the window and their configuration items → mark the ones sharing an item or a service, count the open incidents |
| btn_mark_ready | on click → check that plan, test evidence and backout plan are attached → move the change to review, notify the service owner |
| cal_window | on drag → check the new window against the business calendar and the other changes → store the new start and end, clear the conflict flag |
| btn_decide | on click → update the approval record and the state in ServiceNow → store the sys_id, notify the change owner, refresh S01 |
| Step | Time limit and escalation |
|---|---|
| Readiness | Monday 12:00 of the board week, then the change owner is reminded and the change is listed as at risk of deferral |
| Pre-review | Tuesday 17:00, then members who have yet to vote are reminded |
| Emergency change | 2 hours for the chair and 1 member to review it from the mobile screen |
Names, places and figures are illustrative; the pattern is the catalogue's.
On Monday at 09:00 the app listed 47 changes for the week at a telecom operator in Manchester, flagged 4 that touched the same billing database within 6 hours of each other, and showed 2 open incidents on the storage array one of them used. By Tuesday evening 39 were pre-approved by the members' votes; the Wednesday meeting took 25 minutes and dealt with the 8 remaining, and the chair, Owen, moved 2 windows on the calendar and deferred 1 for a missing backout plan. Every decision was on the change request in ServiceNow before the members left the room.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 4 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of ServiceNow, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.