Projects end; production does not. AMS handover between Singapore sponsors and Philippines delivery fails when artefacts are incomplete, SLOs are vague, and access still lives in a hero laptop. This runbook focuses on evidence-based handover—no invented uptime statistics.

Artefact checklist

Architecture diagrams current to the release you are handing over.
Runbooks for top incidents and batch jobs.
Known-defect list with workarounds.
Access matrix and vault ownership transferred.
Observability dashboards and alert routes verified.
Dependency and vendor contact list with escalation paths.
Backup/restore and DR notes with last test date.

SLO and support model clarity

Severity definitions shared with hypercare and AMS.
Response and restore objectives stated as targets with measurement method.
Maintenance windows and change process agreed.
RACI across vendor AMS, internal IT, and business owners.
Exit and re-bid assistance terms if AMS is outsourced.

Shadow and reverse-shadow period

Run a defined shadow period where AMS handles tickets with project team backup, then reverse-shadow where project staff watch AMS lead. Protect SG–PH overlap for the first weeks. Link to SLO buyer Insights and hypercare exit criteria.

Access and security

Remove project-only credentials. Enforce least privilege. Confirm logging of privileged actions. Align with zero-trust ODC access themes when Philippines engineers remain in the support path.

Exit criteria from project mode

No Sev-1 owned solely by a named project hero.
Alert noise reduced to an agreed actionable level.
Documentation accepted by AMS lead in writing.
Commercial AMS schedule signed or internal funding confirmed.
Follow-up review date booked.

Services map

Handover quality is a Managed Scale concern—see Managed Scale and neighbouring support-SLA Insights. Soft next step via contact when you need a structured transition plan.

Week-by-week handover plan

A four-week pattern works for many mid-size systems: week one artefact freeze and access audit; week two shadow support; week three reverse shadow; week four steady-state with project on backup only. Adjust length for complexity, but do not skip reverse shadow. Singapore sponsors should attend the entry and exit reviews even if day-to-day triage is Philippines-led.

Entry review: artefact checklist scored pass/fail with owners.
Midpoint review: ticket quality, alert noise, missing runbooks.
Exit review: residual risks, commercial AMS confirmation, follow-up date.
Hard stop rule: no exit if Sev-1 ownership still depends on a rotating project hero.

Knowledge transfer formats that stick

Prefer paired incident handling and recorded walkthroughs of crown-jewel flows over 100-page novels nobody reads. Keep a living FAQ from real tickets. Archive decision records. Link observability SLO expectations so AMS inherits measurable targets rather than vibes.

Top twenty incident playbooks rehearsed once.
Architecture office-hours twice during handover.
Credential and vault drill with AMS performing the steps.
Customer communication templates practised once.

Commercial and contractual hooks

Handover quality should affect final project payments or acceptance where contracts allow. AMS scope must list inclusions/exclusions: enhancement hours, third-party vendor chasing, and major version upgrades. Ambiguity here returns as conflict in month two.

Signals the handover is fake

Alerts still route to personal emails of project staff.
Runbooks open with “ask John”.
Production changes happen outside the AMS change process.
No dashboard AMS can use without project VPN heroes.
Known defects rediscovered weekly because the list was never transferred.

Field notes from SG–PH delivery programmes

Across Singapore sponsors and Philippines delivery squads, the same failure pattern repeats: documents exist, but owners and dates do not. Convert every checklist in this article into a tracker with evidence links. Protect overlap hours for decisions. Treat residual risk as something sponsors can hear in plain language. When in doubt, slow the go-live rather than silently accepting unnamed risk.

Write the owner’s name, not a team alias, on every critical row.
Link artefacts in the ticket—not in a private chat thread.
Rehearse the top failure mode once with the people who will be on call.
Archive the decision with date and rationale when you accept residual risk.
Book the follow-up review before anyone declares the work finished.
Keep case studies as pattern references under /case-studies/—never as invented proof points.

How to use this Insight next week

Pick five items from the checklists above. Assign owners by Friday. Review in seven days. If an item remains blocked on access or data, escalate rather than marking it complete. Map execution to the relevant services pillar and continue through neighbouring Insights linked in this article. Soft CTA remains via /contact/ when you want help structuring the operating rhythm—without invented ROI.

Share this page with both Singapore and Philippines leads in the same thread.
Agree which five items matter for your current stage.
Put them in the same tracker you already use for delivery risks.
Reject status updates that lack evidence links.
Revisit weights or thresholds only with a written reason code.

Practical cadence for the next thirty days

Day one through seven: socialise this checklist with Singapore sponsors and Philippines leads in one shared thread, pick the five highest-risk items, and put them in your existing RAID or delivery tracker with owners and due dates. Day eight through fourteen: gather evidence links, bounce incomplete artefacts, and escalate anything blocked on access or data. Day fifteen through twenty-one: rehearse the top failure mode once—tabletop is enough if production rehearsal is unsafe. Day twenty-two through thirty: close what you can, write residual risks in plain language, and book the follow-up review before anyone declares victory.

Publish the five-item shortlist with named owners by the first Friday.
Require artefact URLs before any item can move to done.
Keep a single source of truth—do not fork trackers across email and chat.
Protect at least three overlap-hour sessions across the thirty days.
Record decisions with date, rationale, and who dissented if anyone did.
Share a one-page status that executives can read without a decoder ring.

Language that keeps sponsors aligned

Replace vague status words with evidence words. “On track” becomes “acceptance cases A–D passed in UAT build 1.8; Sev-2 items 12 and 15 waived with sponsor signature on date.” “Almost ready” becomes “blocked on production-like data refresh owned by name, due date.” Soft language hides risk until it is too late for Singapore–Philippines teams to recover inside the release window.

Ban status colours without a linked artefact or ticket.
Write residual risk as something a non-engineer sponsor can repeat accurately.
When waiving a control, state the compensating control and review date.
Prefer short written decisions over long meetings with no archive.
If two owners disagree, escalate within two business days—do not let silence win.

Use neighbouring Insights and the services map to place this work under the right pillar. Treat case studies as pattern references only. When you want help turning the checklist into an accountable operating rhythm across Singapore and the Philippines, start via the contact page—without expecting invented metrics or ROI promises.

Implementation notes for busy teams

Checklists only work when they become trackers with owners, dates, and evidence links. Review weekly until closed. Across Singapore sponsors and Philippines delivery, protect overlap hours for decisions that otherwise wait a full day. If an item cannot be evidenced, keep it open as residual risk—not as “mostly done.”

Put every critical item in a shared tracker with owner and due date.
Require artefact links before marking anything closed.
Escalate blockers older than five business days.
Keep Singapore and Philippines owners visible on critical rows.
Archive decisions with date and rationale.
Rehearse the top failure mode once before you scale.

What good enough looks like before you proceed

Proceed when residual risks are named, owners exist, and compensating controls are written. Do not proceed when critical access, data, or rollback questions remain unanswered. Sponsors should hear residual risk in plain language—not buried in a RAID log nobody opens.

Critical-path owners reachable in the next incident window.
Data and access questions answered with diagrams or configs.
Rollback or remediation path for top failure modes.
Commercial schedules match the operating model agreed.
Follow-up date booked before anyone declares victory.

AMS Handover Runbook for Singapore–Philippines Delivery