APAC GCCs and shared services groups often buy RPA and AI tools before they install an automation Center of Excellence. A starter kit is not a bureaucracy—it is intake, prioritisation, standards, platform ops, and bot-debt control so value compounds. This guide invents no productivity percentages.

CoE mission and scope

Clarify whether the CoE owns platform, method, demand management, or all three.
Define what is in: RPA, IDP, workflow, and later agents—with stage gates.
Publish a one-page mandate signed by GCC and business sponsors.
Separate innovation sandbox from production promotion authority.
Name Singapore stakeholder roles when the GCC sits in the Philippines.

Intake and prioritisation

Standard intake form: process owner, volume, exceptions, systems, compliance class, and success signal.
Score for feasibility, risk, and strategic fit—not who shouts loudest.
Capacity view so approved work has builders and BAU support.
Explicit reject and defer reasons returned to requesters.
Link to process mining or observation before build when baseline is unknown.

Standards that prevent bot debt

Naming, logging, credential, and folder conventions.
Code review and peer build checklists.
Promotion path: dev → test → prod with evidence.
Exception taxonomy shared across bots.
Retirement criteria when applications change or volumes drop.
Documentation minimums for AMS-style support.

Platform, security, and ops

Platform ownership for orchestrators, vaults, and licence pools.
Security patterns for attended and unattended modes.
Monitoring dashboards ops will actually watch.
Incident severity for automation outages tied to business impact.
Vendor and licence roadmap reviewed quarterly.

People model

CoEs fail when they are only a tool admin team. Mix citizen-developer enablement with professional builders, and keep business process owners accountable for outcomes. Align with shared-services orchestration Insights before chasing agents.

Roles: intake analyst, builder, reviewer, platform admin, process owner.
Training paths and certification internal to the GCC.
Career path so automation skills do not become a side hustle.

Ninety-day starter plan

Days 1–30: mandate, intake, and top ten opportunity backlog.
Days 31–60: standards, first two production promotions, monitoring.
Days 61–90: bot-debt review, retirement of orphans, QBR pack for sponsors.

Failure modes

CoE as a ticket sink with no authority to say no.
Every business unit invents its own orchestrator.
Success theatre via bot counts while exceptions explode.
No Singapore sponsor visibility until something breaks.

Services map

Automation CoE design sits under intelligent automation. Soft next step via contact; treat case studies as patterns only.

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.” Write the operating rhythm into calendars: who meets, what artefacts are reviewed, and which decisions cannot wait for email. Treat this as delivery hygiene, not optional paperwork.

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.
Time-box reviews so the tracker does not become a status museum.
Capture assumptions that would force a change order if wrong.

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. A useful gate is whether a new teammate could find the decision trail without pinging three chat threads.

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.
Evidence pack linked from the same place sponsors already look.

Singapore and Philippines collaboration habits

Most APAC delivery friction is not tooling—it is delayed decisions across time zones. Protect a daily or thrice-weekly overlap window for anything that blocks build, UAT, cutover, or support. Singapore sponsors should publish decision rights; Philippines leads should publish capacity and risk early. Prefer short written decisions over long meetings that produce no artefacts.

Overlap hours on the calendar with attendance expectations.
Decision rights matrix for scope, security, go-live, and commercial changes.
Shared definitions for severity, ready, and done.
Handoff notes that a receiving shift can act on without a follow-up call.
Escalation ladder that reaches a named human within the incident window.
Respect local holidays on both sides when planning freezes and drills.

Evidence and audit readiness

Buyers, auditors, and AMS teams will ask how you know something is true. Prefer links to tickets, configs, runbooks, and sign-offs over screenshots in slide decks. When something cannot be evidenced, record it as residual risk with an owner. This habit pays off during warranty disputes, PDPA questions, and quarterly business reviews alike.

Store artefacts where retention and access control are intentional.
Separate working notes from approved baselines.
Version diagrams and decision logs when they change.
Include environment identifiers in every defect and incident record.
Sample a few closed items monthly for evidence quality—not only quantity.

Commercial and delivery alignment

Technical checklists fail when commercial schedules tell a different story. Change orders, warranty, AMS, and success criteria should reference the same severity language and evidence standards. Singapore procurement and Philippines delivery leads should see the same definitions. If the contract cannot point to the operating artefacts, expect disputes during hypercare.

Map checklist items to contract schedules or statements of work where relevant.
Keep a living assumptions log that feeds change control.
Define what “done” means for handover into AMS or BAU.
Avoid success metrics nobody can measure with available telemetry.
Revisit commercial alignment whenever scope or regulatory context shifts.
Record residual risk the business accepts with a named sponsor.

Thirty-day action plan template

Days 1–10: baseline owners, diagrams, and open risks. Days 11–20: close evidence gaps and rehearse the top failure mode. Days 21–30: decide go / no-go / proceed-with-conditions, then book the next review. Keep the plan short enough that busy sponsors will read it. Prefer fewer commitments with owners over a long wish list.

Publish the thirty-day plan in the same tracker as the checklist.
Kill or defer items that lack owners by day ten.
Demonstrate one rehearsal artefact (drill notes, restore test, or tabletop).
End with a written decision and the date of the next checkpoint.

Automation Center of Excellence Starter Kit for APAC GCCs