An interactive schedule for the database move. Pick a start date to see where the work lands, or enter a target go-live and we'll work backwards — flagging any date that can't be reached from today.
Prepared for Raizcorp·Advantage Learn·~2.5 weeks start → cut-over
Plan your date
The first day of real work. Must be after today, and after the report inventory is delivered.
The evening the platform switches over. Enter this to work back to the required start.
Lead engineer — Advantage Learn (Nick) Assisting engineer — Advantage Learn (Paul) Raizcorp Shared / both parties Cut-over milestone Before Day 0 (inputs & scheduling)
Phase / task
What this schedule assumes
Why ~2.5 weeks, not days
The work runs in sequence. The new database must exist before it can be rehearsed with real data; reports can only be rebuilt on that data; the switch-over only happens once reports and testing pass. That dependency chain — not the raw effort, which is modest — sets the calendar.
The pacing items are reporting and QA, plus the genuine waits: validating reports against real data, the fixed 3-day post-cut-over monitoring window, and Raizcorp's sign-off.
This is a focused pace. It uses most of the available engineering time each week, so it is not padded — but it also has little slack. Protecting that time is what keeps the date.
What moves the date
The assisting engineer's availability. The code → test-environment → QA chain is the critical path — so the assisting engineer's time on the early tracks is the single biggest driver of the date.
When the inputs land. The report inventory (Subash) gates reporting, which feeds the cut-over — the earlier it arrives, the firmer the date.
Raizcorp's report rebuild & sign-off. The easy reports and final validation sit in Raizcorp's column (ochre).