The Monday before Thanksgiving starts with a password that does not work. The year-end appeal is supposed to go live on the website this week, the donation page needs a new line of text, and the login you have used since spring returns the same message three times. The second administrator was the volunteer who moved away in August. The two-factor codes lived on his phone. By nine o'clock you have also discovered that the registrar account and the organization's Facebook page were registered under his personal address, and that the renewal notice for the domain went there too.
That is the shape of the lockout most small organizations eventually meet: several doors at once, discovered at the worst moment, with the keys belonging to someone who left on good terms and never thought about this. The retail version is the same story with a checkout page instead of a donation page and Black Friday instead of Giving Tuesday. This post is the calm sequence for that morning, drawn from the Locked Out playbook in the Web Emergency Playbook, and it ends with the question that keeps the page from ever being needed.
Put the keyboard down
The first instinct is to keep trying passwords, and it is the one move that reliably makes a lockout worse. Repeated failed attempts trigger provider security lockouts that convert a fifteen-minute recovery into a multi-day one. Stop guessing. The fastest way back in is almost never the login box, and the first five minutes are better spent diagnosing than typing.
Name each lockout
For every account you cannot reach, write down three facts, because every recovery path branches on them. Which account, exactly: the platform, the username or email on it, and what it controls. What kind of lockout: a forgotten password, a lost or unavailable second factor, an account owned by someone who left, an account suspended by the provider, or credentials changed by someone else. And how urgent, honestly. A locked content management system (CMS) with a running site is an inconvenience. A locked registrar with a renewal date in the next thirty days is an emergency. Match the urgency to the blast radius rather than to the adrenaline, and work the list in that order: registrar, email, hosting, then the CMS and the social accounts.
One warning belongs here. If a password you know stopped working and you did not change it, treat the lockout as a possible hijack rather than a memory problem, and skip ahead to the section on hijacked accounts.
The two boring doors
Most lockouts end at one of two doors in under fifteen minutes, which is why both exist.
The first is the second administrator. Any account with two named admins can be recovered without the provider ever being involved: the other admin resets the password, re-invites you, or hands control back. Earlier this month the Saturday quick win named a second administrator on every critical account; if that work got done, the morning above is shorter by a week.
The second is the vault. Check the password manager for the credential, the backup codes, and the two-factor authentication (2FA) seed. Backup codes exist precisely for the lost-phone morning, and a vault with emergency access configured means a second person can open it when the first cannot.
If either door opens, go straight to closing the loop at the end of this post.
The official recovery flow, once
Go to the provider's real recovery page, by typing the address or using the link in your inventory, never from a search ad or an email. Run the flow once, completely, and read every screen. Half-finished recovery attempts stack up and can flag the account for review.
Recovery flows lean on whatever the account has on file: a recovery email, a recovery phone, a billing card. This is the moment many organizations discover that all three point at a person who left in 2021. A dead end there is not failure; it is the cue for the next step.
The support case, and the evidence that moves it
Contact support through the provider's official channel and state the situation in one sentence: you manage the web presence for the organization, you are locked out of the account under this email, it controls these things, the person who held recovery access is no longer available, and you can verify ownership. Then let them drive their process.
A case moves at the speed of your documentation, so gather the evidence before you write. Past invoices or receipts with the account number. The last four digits of the card on file. Proof of domain control, such as access to DNS or a mailbox at the domain. Business registration or letterhead, and government identification if asked. For social platforms, the official recovery page you noted on your setup sheet, not a form found through search. Expect registrars and social platforms to take days rather than hours, and log every case number with the date opened and the follow-up promised.
If the account was hijacked
When someone else changed the credentials, the lockout is a security incident wearing a login problem's clothes. Report it as a compromise, in those words, through the provider's account-compromise channel; that queue moves faster and can freeze the account against further changes. From a clean device, rotate the passwords on every account that shared the same password or recovery email, hosting, registrar, and email first. Check the accounts you still control for quiet changes: forwarding rules in the mailbox, added administrators, changed payment methods, changed recovery addresses. Once you are back in, run the hacked-site playbook's closing steps and write the log entry.
Close the loop
A lockout is over when the next lockout would be boring. Rotate the password and store it in the vault. Turn on 2FA with the seed and backup codes in organizational custody rather than on one personal phone. Name and confirm a second administrator, never exactly one. Point the recovery email and phone at role-based, organization-controlled destinations. Update the account's inventory row, and write an incident log entry that records how long recovery took and what evidence support asked for; the next person will want that list.
The question worth asking before Thanksgiving
If you were locked out of every critical account tonight, would each one be an inconvenience handled by the second administrator, or an extinction? Any account where the honest answer is the second kind belongs on this week's list, not this quarter's. Year-end giving and holiday sales both arrive on a schedule nobody can move, and a login you cannot reach is a door your donors and customers cannot walk through.
Get the triage page first. When more than one thing is wrong at once, the "Everything Is On Fire" master triage sampler tells you which fire to open first; the Locked Out playbook is one of the five it points to. Print it this week, while the only thing wrong is a Tuesday.

