Preparing VEDA Workspace
Loading workspace access...
Change assessed · Decision package dp-singapore-regulatory
Approve or reject adding Singapore MAS regulatory reporting scope to Atlas before Regional Rollout.
Why now: Singapore's regulator moved the MAS reporting deadline into this project's rollout window; the requirement did not exist when Atlas was baselined.
If no action by 2026-09-11: Regional Rollout proceeds without Singapore regulatory reporting. Singapore entities miss the statutory filing deadline the week after launch, a compliance exposure, not just a schedule one.
Options
Add the scope now: +18 days, +THB 347,000, absorbed into the current UAT/Rollout sequencing.
Launch Regional Rollout on the current scope; deliver Singapore regulatory reporting as a fast-follow within 6 weeks of go-live.
Do not add the scope to Atlas. Singapore compliance exposure is accepted or handled outside this project.
VEDA recommends: Approve, sequenced after UAT sign-off rather than inside it. See the VEDA recommendation on this page for why.
Evidence
Singapore's MAS regulator moved the reporting deadline into the Regional Rollout window (circular dated 2 Aug 2026).
14 of the 18 added work items land on or adjacent to the current critical path, which is why the schedule impact is disproportionate to the scope size.
Deferring this scope to a fast-follow project carries roughly the same total effort but exposes Singapore entities to one filing cycle without regulatory reporting in place.
Approve the change, but sequence it after UAT sign-off rather than inside it, so the Singapore work does not also inherit the current schedule risk on UAT.
Insert Singapore Regulatory Reporting as its own work package immediately after UAT sign-off, before Regional Rollout begins, pending your approval.