Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Provisional schedule (Balanced) — non-binding
DG-facing addendum: PDF, HTML. It supplements the options comparison’s “schedule to be confirmed” wording and creates no contractual calendar baseline.
- Planning figure: roughly 8–10 weeks to launch readiness, assuming two dedicated engineers and one DG testing week. Staffing is unconfirmed; delays add time; go-live needs separate written approval.
- Active engineering time is shown as 7–9 weeks from a ready-to-start kickoff (base 5.4–7.5 weeks plus one shared contingency of 1.1–1.5 weeks, counted once). DG waiting time is additional.
- Milestone bands (cumulative active weeks): staging demo 1–2; core workflows 3–4; approvals/notifications 5–7 (needs a verified staging email sender); ready for DG testing 6–8; engineering completion 7–9.
- Proposed DG review windows (not yet agreed): routine decisions within one business day; one consolidated testing feedback window of five business days.
- Independent QA is not included; if required and serial, allow a provisional extra 1–2 elapsed weeks. With one engineer the same scope is roughly 13–18 active weeks.
- Long-lead items: DG accounts/billing/region, identity provider, sender domain (SPF/DKIM), production domain/DNS/TLS and operational owners.
Open inputs: staffing and leave, review windows, load/recovery targets, sender and identity readiness, independent QA, operational owners.