Application Runbook Administrator

Application Runbook Administrator - J50818

Role & responsibilities

Key Responsibilities

The Application Runbook Administrator owns day-to-day Cutover administration and enables

delivery teams to produce high-quality runbooks that are ready for controlled execution.

Administer Cutover workspaces, runbook templates, user access/roles, and configuration in

alignment with Synchrony policies.

Build and maintain standardized runbook templates (e.g., DR test, migration events)

including phase structure, task types, and required metadata.

Partner with application and platform teams to capture end-to-end cutover steps,

dependencies, owners, prerequisites, validation checks, and rollback procedures.

Ensure runbooks meet governance standards: completeness, naming conventions, task

clarity, time estimates, sequencing, and required approvals.

Coordinate cutover readiness reviews and dry runs; confirm execution owners,

communications plan, and validation criteria are in place.

Lead or facilitate runbook execution in Cutover: launch events, manage task progression,

monitor blockers, maintain real-time status, and ensure timely escalations.

Integrate Cutover usage with broader release/change processes (e.g., change records,

release calendars, maintenance windows) and maintain traceability for audits.

Manage Cutover reporting and dashboards: runbook status, completion metrics, cycle time,

missed steps, and post-event outcomes.

Maintain runbook documentation and knowledge articles; provide training and coaching for

new teams adopting Cutover.

Drive continuous improvement via post-implementation reviews (PIRs), lessons learned, and

template/process enhancements.

1. Intake: Receive request for a new/updated runbook and confirm scope, timeline, and

stakeholders.

2. Build: Draft or update runbook in Cutover using approved templates and required controls.

3. Review: Conduct readiness review with owners; ensure validations, communications, and

rollback are defined.

4. Execute: Facilitate the event; track progress, handle escalations, and provide leadership

updates.

5. Close: Capture results, evidence, and lessons learned; update templates and artifacts.