When an employee leaves, check both their access and the work that still depends on them. Identify every account and device they can use, transfer open checks and pending approvals, disable their access, and confirm that past transactions still show who performed them.
Do this for planned departures and unexpected exits alike. The timing may differ: a scheduled departure gives you time to prepare a handoff, while an immediate departure may call for access to be disabled before the next shift. Assign one manager to coordinate the checklist so that nobody assumes someone else handled a connected system.
1. Inventory accounts and connected devices
Start with the employee’s individual restaurant POS login or PIN. Then follow their actual work. A shift manager who can approve refunds may also have access to reporting, an owner dashboard, online ordering administration or a device used outside the dining room.
Make a list of each account, how the person signs in, who administers it and what needs to happen. Include access through personal email addresses and phones as well as restaurant-owned devices. Depending on your setup, check:
- POS terminals, tablets and manager approval credentials.
- Sales reports, exports and any separate management dashboard.
- Online ordering, reservations, kitchen displays or kiosks the employee could administer.
- Payment, delivery and other connected provider accounts, if the employee had their own access.
- Shared inboxes, password managers, Wi-Fi and remote access used for restaurant work.
Check with the person’s direct manager rather than relying only on a job title. Two employees with the same title may have different accounts because one covered a vacation or helped set up a device. Look for temporary access that was never removed.
For each item, distinguish a personal login from a shared credential. Disabling one person’s account may not change a password known to several employees. Record the owner who can make the change; do not put passwords or PINs in the departure checklist itself.
Also identify physical items to recover: keys, access cards, tablets and any restaurant POS hardware assigned to the employee. Returning a device and disabling an account are separate tasks. A returned tablet does not necessarily end a session on another device.
2. Transfer open work before the handoff closes
Review what is still in progress with the departing employee when appropriate, then name a replacement for each item. The goal is to keep a check, approval or customer request from sitting in a queue that nobody else watches.
Start with open guest checks. Ask the manager to identify checks assigned to the employee, their current status and who will finish them. Follow the POS provider’s process for transferring or closing them; do not close a check just to clear an employee profile. Confirm that the receiving employee can find the check and knows what remains to be done.
Next, review pending refunds, voids, discounts and other actions that need manager approval. If an approval is scheduled or waiting in a queue, assign an authorized manager to review it. The replacement should check the underlying transaction, not simply approve everything left behind.
Look beyond the register for open responsibilities: an unresolved online order, a reservation change, a report due to the owner, a device issue or a vendor request. Give the receiving person enough context to act, including the due time and where the relevant record lives. Avoid passing along the departing employee’s password as a shortcut.
The following is a hypothetical handoff for a restaurant whose closing manager is leaving after a scheduled final shift. The items are separate pieces of work, not a claim about any particular POS product.
| Open item | Handoff decision | Completion check |
|---|---|---|
| Two open guest checks | Assign another server to finish them using the POS process. | Receiving server can locate both checks and knows their status. |
| One pending refund review | Assign an authorized manager to examine the transaction. | Manager confirms the review is in their queue or otherwise recorded. |
| Next week’s sales report | Assign the owner or another report user to prepare it. | Replacement can access the report without using the former manager’s login. |
In this example, the restaurant should not disable the manager’s access and assume the handoff is complete. It should confirm who owns each item, then remove access at the agreed departure time. If the departure is immediate, disable access first and have an authorized manager reconstruct and reassign the work using available records.
3. Disable access, sessions and shared credentials
At the agreed time, disable the employee’s individual accounts and POS credentials. Work through the inventory rather than stopping after the first login. Have the administrator record the time and result for each system, including any item that requires a provider’s help.
Ask your provider how disabling a user affects active sessions. A login that no longer works on a new device may leave an existing session open until it expires or is explicitly ended. Ask whether an administrator can revoke sessions across terminals, browsers and mobile devices, and how to confirm the result.
Handle shared credentials separately. Change a shared password or code the departing employee knew, then give the replacement only to people who still need it. Plan this change around service: identify affected devices and integrations, update them where necessary, and make sure an authorized employee can still do essential work. Ask the provider how changing a credential affects connected devices before making the change.
Check access granted through the employee’s email or phone as well. If that address receives password resets or approval notices, move those responsibilities to an appropriate restaurant-controlled contact. Review saved sign-ins and remote-access methods on restaurant-owned devices. For a personal device, ask the provider how to revoke access remotely rather than assuming you can inspect the device.
Confirm the changes with a simulated check that cannot take a payment, send a guest message or dispatch a courier. For example, ask the provider how to verify that the disabled user cannot sign in and that the replacement can reach an appropriate non-transaction screen. Do not use the former employee’s credentials without authorization or create a real guest transaction as a test.
A live service pilot is different from that simulation. If you want to observe the new handoff during an actual shift, assign a manager to watch legitimate work, answer staff questions and record problems. Use normal service controls; do not create a real payment, guest message or courier dispatch merely to test access.
4. Keep a useful review trail without keeping access
Before removing a user, ask what happens to historical records when that user is disabled, archived or deleted. You want authorized managers to understand who performed past actions without leaving the former employee able to sign in. Ask whether the employee’s name or identifier remains attached to transactions, approvals and changes, and whether reports remain available to current administrators.
Disabling and deleting are not necessarily the same operation. Ask the provider which option preserves the history your restaurant needs and whether either action can be reversed. Do not assume that keeping an active account is necessary to preserve attribution, or that deletion will leave every record intact.
Keep a short departure record in a restricted location. Include the employee identifier, departure date, systems reviewed, person responsible for each change, completion times and any unresolved items. For the open-work handoff, record the receiving owner and where to find the underlying record. Leave out passwords, payment details and unnecessary personal information.
Set a follow-up date for anything that cannot be completed immediately. A manager might need a provider to terminate a session or another administrator to remove access from a connected account. Mark the task open, name its owner and confirm completion rather than treating a support request as the finished change.
When evaluating restaurant management software, bring this checklist to the provider. Ask them to show how an administrator finds users, transfers open responsibilities, ends sessions and reviews historical activity. Also ask which connected accounts must be handled separately and what happens when a shared credential changes.
Next step: Choose one recent role in your restaurant and map its accounts and open-work handoff. Then discuss those requirements with Fleksa or your POS provider before the next departure.
Frequently asked questions
Should I disable access before transferring open checks?
For a planned departure, prepare and confirm the handoff before the agreed access cutoff. For an immediate departure, disable access first and have an authorized manager find and reassign the open work.
Does removing a POS user also remove access to connected services?
Do not assume it does. List each connected account and ask its administrator or provider how access and active sessions are revoked.
How can I retain transaction history without leaving the account active?
Ask the provider which user status preserves attribution and reporting while preventing sign-in. Confirm the result with an authorized administrator and record any follow-up needed.
