The person who ran the website is gone as of this morning. Maybe they gave notice on Friday and their last day arrived faster than anyone planned for. Maybe they were walked out an hour ago. Maybe they simply stopped answering. What they left is a sticky note on the monitor, a password document of uncertain age, and a hosting invoice from a company you have never heard of. The websites, the accounts, and the renewals are now running on momentum, and you are the person holding the momentum.
This is the first Emergency File, and it covers the emergency that creates most accidental web managers in the first place. Nothing is on fire yet. That is exactly why the next 72 hours matter: the two instincts this day produces, cleaning things up and assuming someone else is handling it, both make the week worse. What follows is the calm sequence instead, in the order that protects the organization while you learn what it owns.
What usually happened
Digital responsibilities accumulate in organizations one good decision at a time. A domain registered for a product launch, an email marketing account opened during a fundraising push, a website built by a contractor whose login got forwarded twice and then forgotten. Over a decade of those decisions, the organization ends up renting a dozen digital properties with no landlord of record, and one person who understood most of it.
When that person leaves, the responsibility flows downhill to whoever is nearest and most capable. Nobody in the pattern acted carelessly. The trap is built from good intentions and missing paperwork, which is why it catches careful people.
The wrong first moves
Two instincts arrive within the hour. The first is to start changing things: cancel the subscription nobody recognizes, delete the departed employee's accounts, tidy the shared drive, open the conversation about a redesign. Every change made before you understand the stack destroys information you will want next week. The departed employee's mailbox is the map to everything, and the map is easiest to lose in the first three days.
The second instinct is quieter and more dangerous: assuming someone else has it. As of this morning, there is no someone else.
One rule governs the day. Understand before you touch. The stack ran yesterday without you; it can run 72 more hours while you learn it.
The first 72 hours, in order
First, secure your own seat. Before touching anything your predecessor ran, make sure the accounts you will work from are solid: your own email with a strong password and two-factor authentication (2FA) turned on, and whatever access you already hold to the website or shared drives confirmed working. Open a document titled with today's date. Every discovery, login, and question goes into it from this hour forward.
Next, declare the freeze. Tell whoever needs to hear it that for the next three days nothing gets canceled, deleted, cleaned up, or redesigned, and nobody but you touches the web accounts. Say it plainly to leadership: "I have it. For the next three days I am locating and securing everything before we change anything, and I will have a status summary by Friday." Ask IT or the office manager to hold the predecessor's laptop and phone unwiped until credentials are salvaged; 2FA codes may live on that phone.
Then find the one date that can kill everything. Of everything you do not yet know, one unknown has a fuse on it: the domain expiration date. It requires no login to check. Look up every domain you know of on ICANN Lookup (lookup.icann.org) and write down the expiration date and the registrar. Any date inside 60 days makes renewing the domain today's job. While you are there, note whether the registrant is the organization or a person. If it is a person, you have found this month's most important task.
Then send three emails, today. To the predecessor, if reachable and the exit was decent: a warm note asking where the logins live, which services bill the organization, and whether thirty paid minutes on a call this week would be possible. To the predecessor's manager or IT: preserve and forward the mailbox, hold the laptop, and list any accounts in their name. To finance: send the last three months of statements for any card that pays for software or subscriptions. Those three messages buy back weeks of later pain.
Then take the pulse. You cannot yet fix what you find, but you can know whether anything is quietly failing. Load the site from a phone on cellular data. Send an email to the organization and from it. Confirm a backup exists somewhere, even an untested one, and write down where. If no uptime monitor exists, a free one takes ten minutes and tells you about the next outage before a customer does.
Finally, start the unknowns list. The takeover ends not when everything is known but when the unknowns are written down. Open the inventory workbook and start with what the statements, the mailbox, and the pulse check surfaced. Three columns matter this week: what it is, who can get in, and when it renews.
When it is also a security event
A normal departure gets the sequence above. Treat the takeover as a security incident, with password rotations coming before understanding, when any of three things is true: the departure was hostile or for cause; something has already changed that nobody changed, such as failing passwords or missing files; or the predecessor retains access you cannot revoke, with accounts in their personal name or 2FA on their personal phone. The 72-hour freeze still applies to everything else.
Hour 72
The freeze lifts into a plan rather than a scramble. Send leadership the status summary: what is secured, what is still unknown, and what the next 30 days hold. Finish the log entry with what a proper handoff file would have saved. Then start that file for yourself, this week, while the lesson is expensive and fresh. However this week goes, it should be the last unplanned takeover this organization ever runs.
Get the triage playbook. The free "Everything Is On Fire" sampler from the Web Emergency Playbook is the one page to open when you do not yet know which emergency you have. It points you to the right first move for each one, including this one. Get it today by completing the form below.