The thirty-minute agenda compares C01 at 10:00–10:30 UTC with baseline and revised C02 windows. The calculator reports fifteen minutes of baseline overlap and zero for the 10:45 revision while retaining missing verification and rollback evidence.
Use the worked example
Enter 10:45 for C02's start and 11:15 for its end, then select Compare windows. Use revised proposal enters those values for you. The result becomes zero minutes of overlap while D02 and R01 remain unresolved; the page does not provide an authorization form.
Keep the decision attached to its evidence
Use the change authority named in your team's policy when recording a decision. CAB advice can identify a dependency or request more evidence, but it does not supply that authority by itself. Atlassian discusses the range of possible roles and advisory models in its change-management responsibilities guide.
C02 also proposes starting at 10:15, before C01's planned end at 10:30. D02 requires verification, which requires a separate record, beyond the arrival of 10:30 on a clock.
Keep the baseline and revised windows in the meeting notes so the reason for the change remains clear. Moving C02 from 10:15 to 10:45 creates a fifteen-minute gap after C01's planned finish, but no amount of empty calendar space proves that a verification occurred.
Useful questions are “What does T01 establish?”, “Where is R01's verification evidence?” and “Which record satisfies D02 before C02 can start?” Leave actual answers and reviewer advice blank until documented. Do not invent deployment commands or a rollback procedure to fill the agenda.
Use the agenda's readback to identify which question is still open and who will supply its answer. Record a proposed follow-up separately from an actual decision. A useful meeting can end with a condition to satisfy rather than a claim that either change is ready.
| Change | Synthetic subject | Proposed October 20 window, UTC | Supplied evidence or gap |
|---|---|---|---|
| C01 | Index-configuration change affecting Service A | 10:00–10:30 | Fictional test reference T01 supplied; rollback verification R01 unknown |
| C02 | Routing-configuration change affecting Service A | 10:15–10:45 | Dependency D02 requires C01 verification before C02 starts |
The actual service details, year, change owners, risk assessment, test results, rollback verification, notifications and approved windows remain blank or TO CONFIRM. A test-reference ID is not, by itself, evidence that the change is ready.
| Check | Baseline C02 | Revised C02 proposal |
|---|---|---|
| Window overlap with C01 | 15 minutes | None |
| C01 verification evidence | Not supplied | Still not supplied |
| C01 rollback verification R01 | Unknown | Still unknown |
| Actual authorization | Blank | Blank |
The later start is not proof that the missing evidence will exist by then. Leave dependency readiness unresolved until the responsible authority has the actual supporting record.
The segments total 5 + 8 + 8 + 5 + 4 = 30 minutes. The duration is proposed, not a policy requirement.
Copy a prompt for this example
Create a single HTML CAB meeting worksheet that compares two proposed change windows and keeps dependency questions beside the arithmetic. Use two labeled time inputs, a prominent overlap result, and a compact thirty-minute agenda.
C01 affects fictional Service A from 10:00 to 10:30 UTC. Its test reference is T01; rollback verification R01 is unknown. C02 affects the same service and initially runs from 10:15 to 10:45 UTC. Its dependency D02 requires C01 to be verified before C02 starts.
Calculate the shared interval in minutes. The baseline overlap is fifteen minutes, from 10:15 to 10:30. Provide a Use revised proposal button that sets C02 to 10:45 through 11:15 and recalculates to zero overlap. Both results must still state that C01 verification is missing, rollback verification is unknown, and authorization has not been recorded.
Accept valid same-day HH:MM times with the end later than the start. Show a useful correction message for an invalid window and remove the old calculation. Editing either time should require a new comparison. Reset restores the baseline times.
The agenda allocates five minutes to context and authority, eight to C01 evidence, eight to the C02 dependency, five to questions, and four to readback: thirty total. Use readable type, clear time labels, and a layout that stacks on small screens. Return one complete HTML file; keep schedule advice separate from an actual change decision.
Bring the paired windows and the missing-evidence questions to the change authority named by your policy. You can preview the sanitized HTML agenda in NOS before the review. Record advice and authorization separately, and ask which evidence must exist before C02 may start.