Phase 7: Go Live

The go-live phase has tasks leading up to the go-live date, the day before, the day of, the day after, and the remainder of the week.

Duration: Approximately 1 week (including preparation and initial support)

Approach

The go-live approach will be documented in the go-live plan, which outlines:

• Tasks required to transition the organization to the software

• Support model during go-live

• Dates and timelines

• Required resources

• Prerequisites and status for all activities

These tasks will be developed and reviewed collaboratively with the project core team, RADPAIR, other vendors, and key stakeholders involved in the go-live process.

Go-Live Timeline

1

Pre Go-Live (1-2 Weeks Before)

• Final system configuration verification

• Integration testing sign-off

• Training compliance verification

• Go/no-go decision meeting

• Communication to all stakeholders

2

Day Before Go-Live

• Final system checks

• Support team briefing

• Command center setup

• Communication reminders to users

• Legacy system preparation

3

Go-Live Day

• System activation

• Command center operational

• Real-time support and monitoring

• Issue tracking and resolution

• Status updates to leadership

4

Day After Go-Live

• Morning status review

• Issue prioritization and resolution

• User feedback collection

• Continued support coverage

• Daily status report

5

Remainder of Week

• Continued support with reduced intensity

• Ongoing issue resolution

• User adoption monitoring

• Daily status updates

• Transition planning to post go-live

Support

The go-live support structure will outline:

Element	Description
Resource Schedule	Coverage times for core team members, super users, radiologist super users, and project leadership
Command Center	Central hub for project team and help desk
Help Desk Process	Logging, tracking, and resolving issues
Communication Approach	Status updates and escalation procedures

Command Center

A dedicated command center will be established to serve as the central hub throughout the go-live period.

Command Center Components:

• MS Teams call for virtual coordination

• Physical command center (when appropriate)

• Issue tracking system

• Communication channels to all stakeholders

A clearly defined process for logging, tracking, and resolving issues must be in place to ensure timely resolution and effective communication.

Support Team Coverage

Role	Go-Live Day	Day 2-3	Day 4-5
Project Leadership	Full coverage	Full coverage	As needed
Core Team Members	Full coverage	Full coverage	Reduced
Super Users	Full coverage	Full coverage	Reduced
Radiologist Super Users	Full coverage	Full coverage	On-call
RADPAIR Team	Full coverage	Full coverage	Reduced

Go-Live Plan Components

Your go-live plan should include:

• Go/no-go criteria and decision process

• Detailed task list with owners and timelines

• Support team schedule and coverage

• Command center setup and logistics

• Issue management process

• Communication plan and escalation procedures

• Rollback plan (if needed)

• Success metrics and monitoring

Phase Deliverables

By the end of the Go-Live phase, you should have:

• Successfully transitioned to RADPAIR

• Resolved critical go-live issues

• Documented remaining issues for post go-live

• Completed daily status reports

• Gathered initial user feedback

• Readiness assessment for post go-live transition