Outsourced CompanyPowered by StealthAgents

Philippines staffing guide · Published

Build an access removal checklist for outsourced staff turnover

A departure exposes every account nobody tracked. Pull the list from systems, name an owner for each line, and prove the removal with a live test.

Build an access removal checklist for outsourced staff turnover operations illustration

The short answer

Access removal works when the account list comes from systems, every line has an owner, and a second person tests the result. Rotate shared credentials, document exceptions with an expiry date, and review the friction after each exit.

Why removal is harder than setup

Access is usually granted in a hurry and removed slowly. A new coordinator needs mail, files, and a queue login on the first morning, so someone approves the requests together and moves on.

The exit has no matching deadline, which means each removal waits for a convenient moment. That asymmetry is how dormant accounts survive long after the person has left the role.

The risk is not only a former worker with a live password. Shared logins, delegated mailboxes, and saved browser sessions can keep working without anyone noticing.

A vendor may still hold a token, and a client may still list the person on a distribution group. A removal checklist is useful because it covers the accounts nobody remembers to check.

List the accounts before the last day

Build the account list from systems, not from memory. Pull the identity provider record, the password manager entries, and the open access requests from the last quarter.

Add the client tools that live outside single sign-on, because those are the ones most often missed. The list should be specific enough that a reviewer can check each line.

Ask the coordinator to confirm the list rather than trusting it. People remember the tools they use daily and forget the ones they touched once during a launch.

Check browser bookmarks and the mail archive for service names that never appear in the identity system. A short interview often reveals two or three accounts that no inventory captured.

Separate owner-approved access from shared credentials

Every line on the list needs a named owner who can approve removal. An owner is the person accountable for the system, not the person who happened to share the password.

If no owner is recorded, the removal becomes a debate about whether the account matters. Assign the owner while the access is still active, not after the exit.

Shared credentials need a different treatment. A team login that several people use cannot simply be deleted for one departure. Rotate the password, remove the person from the distribution group, and record who still needs the new secret.

If the shared login cannot be rotated without disrupting service, schedule the change and note the window. Leaving it unchanged is a decision, so write it down.

Verify removal with a live test

A closed ticket is not proof that access is gone. Test the login after the account is disabled and record the result with a timestamp.

Check the mailbox delegation, the calendar sharing, and any forwarding rule that could still deliver mail. The test should be done by someone other than the person who performed the removal.

Use a short script so the test is repeatable. Open the identity console, search the account, and capture the status. Send a test message to the mailbox and confirm that no forward leaves the organization.

Then check the file shares and the queue groups the person belonged to. Save the evidence beside the checklist instead of describing it from memory.

Record the evidence and the exception

Keep one record per departure with the date, the systems, the approver, and the test result. The record should show what was removed, what was transferred, and what was deliberately left in place.

Exceptions are normal, but they need a reason and an expiry date. An exception without an expiry date becomes permanent by default.

Store the record where the next reviewer can find it. A folder that only the manager can open is a weak control because nobody else can confirm the work.

Give the record a stable name and link it to the role as well as the person. When an auditor asks who still has access, the record should answer the question in one place.

Review the checklist after each exit

Run a short review after every departure and note where the process slowed down. A missing owner, an unresponsive client, or a shared login that could not be rotated is a repair item. Assign each item to a person and a date.

The checklist improves when the friction is recorded rather than absorbed. Keep the review to fifteen minutes and record only the steps that needed a workaround.

Use the next exit to test the repair. If the same step fails again, the problem is the rule, not the person.

Rewrite the rule with the people who perform the removal and keep it short enough to use under time pressure. Access removal is a routine control, and routines only hold when they are practiced.

Keep the checklist usable during a busy exit

A checklist that takes an hour will be skipped on the day it is needed. Keep it to one page with the systems, the owner, and the test step for each line.

Pre-fill the owner contacts so the reviewer does not have to search during the exit. The goal is a document that a busy manager can follow without a meeting.

Bring the checklist to the final handover conversation and complete the first lines together. Confirm the last working day, the client contact, and the mailbox plan while the person is still available.

Assign the remaining lines to a named reviewer with a date. Then send a copy to the person so they can raise anything that was missed.

Questions to copy for the sales call

  • "Which accounts would still work if this person left today?"
  • "Who owns each client tool outside single sign-on?"
  • "Which shared credential needs rotation, and when is the safe window?"
  • "Who will test the removal and where will the evidence live?"

Sources

Common questions

When should access removal start?

Start before the last working day. The list, owners, and approvals should be ready while the person is still available to confirm the accounts.

What if a client owns the account?

Send the removal request early and keep the confirmation. Record the client contact, the date sent, and the date confirmed so the gap is visible.

Should shared passwords be rotated for every exit?

Rotate any shared credential the person could read. If rotation would disrupt a live service, schedule the change and record the risk in the departure file.

Who should test the removal?

Someone other than the person who performed it. A second tester catches missed delegations and forwarding rules that the first pass overlooked.

Philippines staffing intake

Define the position before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us