T-Minus Actions
A structured pre-migration preparation framework. T-Minus tasks are triggered at defined days before go-live, ensuring communications, backups, approvals, and validations happen on schedule — not as last-minute scrambles.
Overview
The T-Minus framework provides a structured set of pre-migration actions that are triggered at defined days before the migration go-live date. The name comes from the NASA launch countdown tradition — T-Day (or T-0) is the go-live date, and each task is assigned an offset such as T-30 (30 days before go-live) or T-7 (7 days before go-live).
Without a T-Minus framework, preparation activities tend to pile up in the final week before go-live, creating a high-pressure scramble that leads to missed steps, late communications, and last-minute surprises. T-Minus spreads these activities across the entire preparation timeline with clear ownership and due dates.
T-Minus Runbooks are event-specific instances, while T-Minus Templates are reusable blueprints that can be applied to any new event. Build your standard template once and reuse it for every migration.
T-Day — The go-live date set on the Migration Event. T-0.
T-Minus Offset — Days before T-Day. T-30 = 30 days before go-live. Always expressed as a negative number (e.g. -30).
T-Minus Runbook — A set of T-Minus tasks created for a specific Migration Event.
T-Minus Template — A reusable task blueprint saved for future events.
Automation Level — Whether a task is Manual, Semi-Automated, or Automated.
When to Use
- At the start of migration planning — create a T-Minus Runbook immediately after creating the Migration Event, so the full preparation timeline is visible from day one.
- To manage communications — T-30 and T-14 tasks typically include sending stakeholder communications. Having them scheduled means they happen on time, not when someone remembers.
- To ensure backups and approvals happen on schedule — T-7 and T-1 tasks for backup verification and change freeze windows must happen at the right time or the migration cannot proceed.
- To avoid last-minute scrambles — if you find yourself doing 10 preparation tasks the night before go-live, you need a T-Minus runbook.
- For recurring migration programmes — build a standard T-Minus Template once and import it for every subsequent event.
Key Features
Step-by-Step Instructions
Navigate to Migrations → T-Minus Runbooks (or Governance → T-Minus Runbooks depending on your navigation layout). Click Add T-Minus Runbook. Select the parent Migration Event. Give the runbook a name (e.g. Wave 1 T-Minus Plan). Click Save. The runbook is created with an empty task list, and task due dates will be calculated from the event's go-live date.
With the runbook open, click Import from Template. Select the template you want to apply (e.g. your organisation's standard Standard Migration T-Minus template). Review the task list preview and click Confirm Import. All tasks from the template are added to the runbook. Task due dates are automatically calculated using each task's T-Day offset combined with the event's go-live date.
Click Add Task within the runbook. Fill in the Task Name, Description, T-Day Offset (e.g. -30 for T-30, -7 for T-7, 0 for T-Day), Owner, Estimated Minutes, and Automation Level. Click Save Task. The task appears in the runbook timeline at the correct position.
In the runbook view, tasks are automatically sorted by T-Day offset from largest negative number (earliest, e.g. T-30) to zero (T-Day). Each task shows its calculated calendar due date alongside the T-Day offset. Review this view to confirm that tasks are correctly distributed across the preparation timeline and that no week is overloaded.
As each task's due date arrives, the task owner opens the T-Minus Runbook and updates the task status to Completed. If a task cannot be completed on schedule, set it to Blocked and add a note explaining why — this flags the issue to the PM. Overdue incomplete tasks are highlighted in the runbook view for easy identification.
Navigate to T-Minus → Templates → Add Template. Give the template a name (e.g. Standard Migration T-Minus — 30 Day). Add tasks using the same process as step 3 — each task gets a T-Day offset, owner template (role or person), and description. Once saved, this template can be imported into any future T-Minus Runbook.
Fields Reference
| Field | Required | Description |
|---|---|---|
| Task Namerequired | Yes | A clear, action-oriented name for the pre-migration task (e.g. Send T-30 stakeholder communication). |
| Descriptionoptional | No | Detailed instructions for the task owner — who to contact, what to include in a communication, what to validate, etc. Invest time here for frequently reused tasks. |
| T-Day Offsetrequired | Yes | Days before T-Day (go-live). Must be a negative number or zero. Examples: -30 = 30 days before, -7 = 7 days before, -1 = the day before, 0 = T-Day itself. Do not enter positive numbers. |
| Ownerrequired | Yes | The individual responsible for completing this task. Must be a named person. Receives reminders as the due date approaches. |
| Estimated Minutesoptional | No | How long this task is expected to take. Used for workload planning — helps identify weeks where the owner has too many tasks. |
| Automation Levelrequired | Yes |
Manual — task must be completed by the owner.Semi-Automated — task involves a system process but requires human confirmation.Automated — task is triggered and completed by an integrated system.
|
| Statusrequired | Yes | Current state: Pending, In Progress, Completed, or Blocked. Updated by the task owner. Overdue tasks are highlighted automatically. |
Example Workflow
A PM creates a T-Minus Runbook for Wave 1 — Datacentre A to Cloud (go-live: 15 March). She clicks Import from Template and selects the organisation's Standard Migration T-Minus — 30 Day template, which contains 20 tasks spanning T-30 to T-0.
The runbook view shows the tasks with calculated calendar dates. She immediately notices a problem: today is 19 February, which is T-24 (24 days before go-live). The T-30 task (Send initial stakeholder communication) was due 6 days ago and is marked as Pending — it was never done.
She contacts the comms owner, who sends the communication immediately and marks the task Completed. She also checks T-28 and T-25 tasks and finds they were completed informally. She marks them as Completed with a note.
The remaining tasks are correctly scheduled. She reviews each one, confirming the owners are assigned and descriptions are current for this specific event. On T-7 (8 March), the system sends reminders to all task owners whose T-7 tasks are due. The backup verification and change freeze tasks are completed on schedule, and Wave 1 goes live without any last-minute surprises.
Tips
Build your standard template before your first migration. A well-constructed T-Minus Template covering T-30 through T-0 is one of the most valuable assets in your migration toolkit. Invest time building it once — it will save hours on every subsequent event and ensure nothing is missed.
Set the go-live date on the Migration Event accurately. All T-Minus task due dates are derived from the event's go-live date. An approximate date is fine initially — update it as plans firm up, and all task dates recalculate automatically.
Review the T-Minus runbook at least weekly in the lead-up to go-live. A T-Minus runbook that is created and then not checked until T-3 is nearly useless. Build a weekly cadence of reviewing and updating task statuses into your migration governance process.
Common Mistakes
Not creating a T-Minus Runbook at all. This is the most common and most damaging mistake. Without a T-Minus runbook, preparation activities have no schedule, no owners, and no tracking. The result is always the same: a panicked scramble in the days before go-live where everyone discovers that communications weren't sent, backups weren't verified, and change approvals weren't obtained.
Setting T-Day offsets incorrectly. The T-Day Offset field expects a negative number. Entering 30 instead of -30 will schedule the task 30 days after go-live — well past the point where it has any value. Always double-check that your offsets are negative.
Not assigning owners to T-Minus tasks. A T-Minus task with no owner is a task that belongs to no one and will not be completed. Distribute ownership across the project team, matching tasks to the people with the right skills and access. The PM should not own every task.