What happens to your automations when the person who built them leaves

When the person who built an automation leaves, it usually stops within days, because it was running on their login, their computer, or both. Switching off their account during offboarding is the right thing to do, and it’s exactly what breaks the automation. The good news: once you know the three ways an automation depends on one person, you can find them and fix them before anyone leaves.

Why it happens

Most small-business automations aren’t planned. Someone notices a boring, repeated task and automates it in an afternoon: a report that emails itself every morning, a sync that copies new orders into the accounting system, an AI assistant that drafts replies. It works, so everyone starts relying on it. Nobody thinks about who it belongs to.

Behind the scenes, it almost always depends on the builder in three ways.

Their login. The automation signs in to your systems as them. That might be their Microsoft 365 or Google account, their Zapier or Make account, or a personal AI subscription. When IT disables their account on their last day, the automation loses access at the same moment.

Their computer. Many automations run on the builder’s own laptop or desktop: a script on a schedule, a spreadsheet that refreshes when it’s opened, an AI chat someone runs every Friday. When that computer is wiped, returned or simply turned off, the job stops.

Their head. Even when the login and computer survive, the knowledge doesn’t. Nobody else knows what the automation does, where it lives, or what to do when it fails.

The hardest part is that automations rarely fail loudly. There’s no alarm. A report just doesn’t arrive, or orders quietly stop syncing, and it can be weeks before someone asks why.

What to check first if something has already stopped

1. Find out where it ran. Ask the people who used the result. Look at the sender of the last email it produced, the account that created the last records, or the tool named in any old notifications.
2. Check the account it used. If it was the former employee’s account, that’s almost certainly the cause. Don’t reactivate their account to fix it; that reopens access you closed for good reasons.
3. Check the computer. If it ran on their machine, find out whether the machine still exists and whether the files were kept before it was wiped or reassigned.
4. Look for failure notices. Many tools email the account owner when something fails. Those messages may be in the former employee’s mailbox. Follow your company’s policy on accessing it.
5. Rebuild it on a business account. Recreate the automation using an account the business owns, not a personal one, and write down what it does as you go.

How to stop it happening again

You don’t need new software to fix most of this. You need to know what you’re running and make sure none of it belongs to one person.

• Make a list. Write down every task that happens automatically, even small ones. For each, note where it runs, whose login it uses, and who would notice if it stopped. An hour is usually enough for a first pass.
• Move logins off people. Where you can, have automations sign in with an account set up for that purpose and owned by the business, rather than an employee’s own account. Store its password somewhere the business controls, not in one person’s browser.
• Move jobs off laptops. Anything the business depends on should run somewhere that’s always on and isn’t someone’s personal device.
• Add an alert. Every automation that matters should tell someone when it fails or doesn’t run. “Someone would notice eventually” isn’t an alert.
• Write three sentences. For each automation: what it does, where it lives, and what to do if it stops. That’s often enough for someone else to take over.
• Add automations to your offboarding checklist. Before switching off a departing person’s account, ask them, and check, what’s running under it.

Imagine one of your staff took a surprise two-week holiday starting tomorrow. Which reports, syncs or AI helpers would stop, and how long before anyone noticed? If you can’t answer quickly, that’s your starting point.

Checklist

• List every automation, even the small ones.
• For each: where it runs, whose login it uses, who would notice if it stopped.
• Move anything on a personal account to a business-owned account.
• Move anything the business depends on off personal laptops.
• Give each important automation an alert.
• Write three sentences about each: what, where, and what to do if it stops.
• Add “what’s running under this account?” to your offboarding checklist.

How StackProbe handles this

StackProbe takes automations like these off individual laptops and logins and runs them in a sealed workspace that belongs to your business, using your own business accounts. Every job is checked every five minutes, and when one fails, our team is alerted and fixes it. If you’re not sure what you’re running, the free stack check is a five-minute way to find out what’s fragile.