Sample Template: IT Separation Work Plan

Project Overview

• Scope: list key systems, infrastructure, and security components in separation perimeter.
• Objectives: operational continuity, TSA exit in ⟨mm/yy⟩, zero critical incidents.
• Budget: $ ⟨amount⟩ one-time separation spend; $ ⟨amount⟩ annual run-rate.

Governance and Roles

• Program Sponsor: ⟨Name, Title⟩.
• IT Separation Lead: ⟨Name⟩.
• Workstream Owners: ERP ⟨Name⟩; Infrastructure ⟨Name⟩; Security ⟨Name⟩; Data Migration ⟨Name⟩; Vendor Contracts ⟨Name⟩.
• Steering-Committee Cadence: bi-weekly until cut-over; weekly for 30 days post-Day 1.

Key Milestones and Target Dates

• Complete application and infrastructure inventory — ⟨dd/mm/yy⟩.
• Finalise target architecture and budget approval — ⟨dd/mm/yy⟩.
• Sign high-risk vendor novations — ⟨dd/mm/yy⟩.
• Finish mock data migration cycle 2 — ⟨dd/mm/yy⟩.
• Pilot network cut-over at low-risk site — ⟨dd/mm/yy⟩.
• Identity-platform go-live — ⟨dd/mm/yy⟩.
• Production cut-over and Day 1 operations — ⟨dd/mm/yy⟩.
• First TSA exit checkpoint — ⟨dd/mm/yy⟩.
• Final TSA termination and post-implementation review — ⟨dd/mm/yy⟩.

Workstream Activity Checklist

• ERP: licence novation, data migration, interface rebuild, user-acceptance testing, cut-over rehearsal.
• CRM: data extraction, cleansing, SaaS tenancy provisioning, security configuration.
• HRIS & Payroll: employee-master load, parallel payroll, statutory filing validation.
• Infrastructure: procure edge devices, build cloud foundations, deploy SD-WAN, implement monitoring.
• Network Segmentation: allocate new IP ranges, configure firewalls, establish inter-company tunnels, schedule phased decommissioning.
• Identity & Access: create new domain, migrate users and groups, enforce MFA, terminate legacy trusts.
• Security: deploy EDR agents, integrate logs into new SIEM, run penetration test, remediate findings.
• Data Migration: finalise mapping sheets, execute ETL, validate record counts, secure data-destruction certificates.
• Vendor Contracts: complete consent negotiations, sign replacement agreements, update SAM records.
• TSA Management: confirm scope, SLAs, pricing; create exit checklist; monitor performance and ramp-down dates.

Resource Plan

• Internal FTEs required by workstream and month.
• External partners: systems integrator, cloud MSP, data-migration vendor, security tester.
• Contingency pool: ⟨X⟩ percent of total hours for unplanned spikes.

Risk and Issue Log (Top Entries)

• Data-quality defects delaying ERP migration — owner ⟨Name⟩; mitigation: additional cleansing sprint.
• Vendor consent fee escalation — owner ⟨Name⟩; mitigation: bundle contracts, escalate to procurement VP.
• Bandwidth constraints on TSA tunnels — owner ⟨Name⟩; mitigation: procure temporary capacity boost.

Cut-Over Command Centre Plan

• War-room location or virtual bridge details.
• Roster of on-call engineers and decision-makers by hour.
• Go/No-Go criteria for each critical system.
• Escalation ladder up to CIO and Steering Committee.

Post-Day 1 Stabilisation Metrics

• System availability target ≥ 99.8 %.
• First-time-right incident resolution ≥ 95 %.
• TSA service credits ≤ ⟨amount⟩.
• Cyber-incident count = 0.

Populate this template, update weekly, and use it as the authoritative schedule, status, and escalation reference for the entire IT separation programme.