Philippine shared services centres choosing RPA must decide attended versus unattended bots with clear eyes: exception rates, audit needs, volume shape, and human-in-the-loop design. The wrong mode creates shadow IT on desktops or brittle overnight farms. This decision frame invents no FTE-savings percentages.

When attended RPA fits

High judgement or frequent exceptions that need an agent at the keyboard.
Processes triggered by live customer or employee conversations.
Systems that only expose fragile desktop UIs with session affinity.
Early discovery phases where you are still learning exception taxonomy.
Compliance steps that require a named human attestation at the point of action.

When unattended RPA fits

Stable, high-volume batches with well-defined inputs and SLAs.
Clear system APIs or reliable UI automation with low change volatility.
Overnight or follow-the-sun windows without needing an agent present.
Centralised credential and vault patterns already approved by security.
Monitoring and restart playbooks owned by an ops function—not a lone developer.

Decision criteria checklist

Exception rate and cost of a wrong automation action.
Audit and evidence requirements for regulators or internal audit.
Change frequency of underlying applications (ERP, banking portals, HRIS).
Credential custody model: attended user context versus service accounts.
Peak volume versus average—and whether queues can absorb delay.
People impact: training, role design, and escalation paths.

Hybrid patterns that often win

Many Philippine SSCs start attended to capture exceptions, then peel stable paths into unattended. Human-in-the-loop queues can sit between modes. Process mining before RPA reduces guessing which path dominates.

Attended for edge cases; unattended for the happy path after metrics stabilise.
Shared exception taxonomy across both modes.
Single automation CoE standards for naming, logging, and promotion.
Explicit kill switches for unattended farms when upstream systems change.

Security and control differences

Attended: endpoint hardening, user training, and preventing local credential sprawl.
Unattended: vaulted secrets, jump hosts, network allowlists, and job scheduling controls.
Both: logging that supports audit without storing unnecessary PII.
Both: change control when target applications upgrade.

Common failure modes

Unattended bots built on processes still changing weekly.
Attended bots that become mandatory workarounds nobody documents.
No exception playbook—agents invent steps in chat.
Success measured only by bot count, not process outcomes and risk.
Ignoring neighbouring RPA exception and HITL Insights.

How to decide in thirty days

Week one: map volume and exceptions. Week two: security and audit constraints. Week three: pilot one path with clear exit criteria. Week four: decide mode and CoE standards. Delivery patterns sit under intelligent automation Philippines; use 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.

Attended vs Unattended RPA Decision Frame for Philippine Shared Services