Outsourced Philippines guide

Write an Access Revocation Checklist for Departing Offshore Staff

A departing offshore staff member leaves accounts, delegates, and saved credentials behind. A dated revocation checklist names every access route, its owner, and the evidence that the door is closed.

A departing offshore staff member can leave with more than a vacant seat. Every account, shared inbox, saved password, and delegated calendar still points at a person who no longer works for the client. An access revocation checklist turns that risk into a dated sequence that someone owns. Build it before the last day, not after the farewell call, and keep the evidence in one place.

On this page

Start the checklist before the last day

Open the checklist when a departure is confirmed, not on the final afternoon. Name the manager who owns the exit, the client contact who confirms each system, and the date access must end. List the systems the person uses, including the ones nobody remembers because the work is rare. A revocation that depends on memory will miss the tool used twice a year, and that tool may hold the most sensitive records.

Separate a planned departure from an immediate one. A planned exit allows a knowledge transfer and a staged handover, while an immediate exit requires access to stop first and questions to be asked later. Write both paths and the trigger for each. The team should not debate which path applies while an account is still active, because that debate is how an urgent exit becomes a slow one.

Inventory every access route

Start with the identity provider and list every application attached to it. Then add the systems that sit outside single sign-on, such as a shared mailbox, a carrier portal, a bank view, or a local spreadsheet with saved credentials. Include devices, VPN profiles, and API keys. The inventory should match the client asset list rather than the worker memory, and it should be checked by someone who administers the systems.

Assign each entry to an owner who can actually revoke it. A client administrator may control one system while the staffing provider controls another. Record the owner, the method, and the expected time to complete. An entry without a named owner is a wish rather than a step, and it will be the one left open during a busy week when nobody has time to trace the right administrator.

Separate revocation from knowledge transfer

A departing worker often holds context that the next person needs. Collect that context before the final day, but do not let it delay the removal of access. Ask for a handover note that names open items, contacts, recurring tasks, and the location of working files. Review the note while the person can still answer a question, then revoke on schedule even if the note is imperfect.

Do not trade access for cooperation. If the worker refuses to hand over information, the client still removes access and works from records, backups, and the audit trail. A departure is not a negotiation over credentials. Keep the sequence fixed so a difficult exit does not become an exception that leaves an account alive, and route any missing knowledge to the manager who owns the relationship.

Handle shared and delegated accounts

Shared mailboxes and delegated calendars need special handling because removing one person does not remove the account. Review the membership list and remove the departing worker from every delegate, alias, and forwarding rule. Check rules that send copies to a personal address. A forwarding rule can outlive the account and quietly move client mail after the exit, so it deserves the same attention as a password.

Where a shared credential exists, rotate it rather than deleting the worker name from a list. Rotation closes the path even if the secret was copied. Record who holds the new secret and when it was changed. Shared credentials should be a temporary exception, and a departure is a good moment to replace them with individual accounts that can be reviewed one person at a time.

Record the revocation with evidence

Record each revocation with the system, the action, the actor, the time, and a reference to the ticket or screenshot. A status of complete without evidence is only an assertion. The record should let a client reviewer confirm that access ended without asking the team to reconstruct the day from chat. Keep it with the exit file rather than in a private message that disappears when the manager changes.

Ask the client to confirm the systems they control. A provider can only certify what it can see, and a client-owned application may need a separate sign-off. Note any system that could not be verified and the plan to check it. An honest gap is easier to manage than a false completion, because the gap can be assigned and dated while a false completion closes the file too early.

Watch for access that returns

Watch for access that comes back after the exit. A manager may re-add a former worker to a group, restore a mailbox, or share a file with an old address. Review group membership and forwarding rules thirty days after departure. The second review catches the quiet restoration that the first checklist could not see, and it takes only a few minutes when the inventory is already written.

Treat a returning account as a security event rather than an administrative inconvenience. Disable it, find who restored it, and record the reason. If the client genuinely needs the person for a short project, use a new time-bound account with a named sponsor. Reusing an old identity blurs the audit trail and the employment boundary, and it makes the next departure harder to verify.

Review the checklist after each departure

After each departure, ask three questions. Did the inventory miss a system, did an owner fail to act, and did the handover note give the next person enough to start? Add the missing field or owner to the template. A checklist improves when it is revised from a real exit rather than from an annual meeting, because the real exit shows which step depended on luck.

Keep the template short enough to finish on a normal day. A long form invites partial completion, while a short form with clear owners gets used. Store the completed checklist with the access record and the handover note. The goal is a repeatable exit that protects the client without turning every departure into a project that the team postpones until the account is already quiet.

Sources and next steps

Continue with operations support, then confirm scope, authority, and review ownership before expanding the role.

Philippines staffing

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to shape a practical Philippines staffing request.

Contact Us