The Weekly 15-Minute Account Health Check

Most account problems do not arrive suddenly. They build quietly: a recovery email that stopped working months ago, a session left open on a device you no longer own, a document expiring next week that nobody noticed, a payment method that quietly failed. By the time the platform flags something, the small thing has become a large one. A weekly health check exists to catch these things while they are still small.

The check takes fifteen minutes because it is a check, not a project. You are not reorganising your accounts or reading every policy update. You are confirming five things: that your logins look right, that your recovery details still point at you, that your limits and balances are where you expect them, that your documents and verification status are current, and that your own notes match reality. If all five are fine, you close the tab and get on with your week.

Pick a fixed time for it — Sunday evening, Monday morning, whatever you will actually keep — and treat it the way you would a weekly tidy of a workspace. The value is not in any single check. It is in the habit: a small, regular look that means nothing about your accounts ever goes unnoticed for long.

Accounts change slowly, and most of what changes is visible in the places you already visit. A login alert you dismissed, a new device in your sessions list, a balance that moved without you — all of these show up in the account itself, not in a separate monitoring tool. Fifteen minutes is enough because you are looking at the account's own record of itself, and that record is usually short.

The other reason the check is short is that it is regular. A monthly check has to cover a month of changes, which is why monthly checks take an hour and get skipped. A weekly check covers a week of changes, which is why it fits into a coffee break and actually happens. Frequency is what makes the routine cheap: the shorter the gap, the less there is to review.

It also helps to keep the check separate from other account work. Do not combine it with a big task like moving funds or changing a password. If the check finds something that needs action, note it and deal with it afterwards. A check that turns into a project every week is a check you will stop doing.

Start with your login alerts. Open the security or notification area of each account you use regularly and look at the recent sign-ins. You are looking for anything you do not recognise: a location you have not been in, a device you do not own, a time you were asleep. Most platforms let you see the device and the approximate location for each sign-in, which is usually enough to tell your own logins from someone else's.

If something looks wrong, do not just dismiss the alert. Change the password from a device you trust, review the active sessions, and sign out anything you do not recognise. The post at /blog/what-to-do-in-the-first-hour-after-a-security-alert walks through those first steps in detail, and it is worth reading before you need it rather than during a real incident.

Then look at the sessions list itself. Sessions accumulate: a phone you replaced, a browser on a computer you no longer use, a tablet at a relative's house. Sign out of anything you no longer use. Fewer live sessions means fewer doors into the account, and it also means the next time you look at the list it will be short enough to scan at a glance. The guide at /blog/session-management-staying-logged-in-without-triggering-reviews explains how to keep sessions tidy without triggering a review by signing in and out too often.

Recovery details are the part of an account that fails silently. A recovery email you stopped using, a phone number from an old SIM, an authenticator app on a phone you replaced — none of these announce themselves until the day you actually need them, which is exactly the wrong time to discover the problem. Once a week, confirm that the recovery email and phone number on each account are ones you can still reach.

Check the authenticator setup too. If you use an authenticator app, make sure it is still installed and working, and that you know where the backup or recovery codes are stored. If you changed phones recently, this is the check that catches the app that never got moved across. A recovery code you cannot find is the same as no recovery code at all.

While you are here, confirm the recovery email itself is healthy. The post at /blog/recovery-email-hygiene-the-inbox-behind-the-account-matters explains why the inbox behind an account matters as much as the account itself: if the recovery inbox is compromised or abandoned, the account's recovery path is compromised with it. A quick look at that inbox — is it receiving mail, is anything odd in the spam folder — is part of this check.

Next, look at the practical side: limits, balances and anything pending. Check that the balances on the accounts you use are roughly where you expect them, and that there is no transaction you do not recognise. You are not reconciling a ledger here — you are looking for surprises, and surprises are usually obvious once you look.

Look at any pending items as well: a withdrawal that has not completed, a transfer still processing, a verification step waiting for a document, a payment hold that has not cleared. Pending items are normal, but a pending item that has been pending for a week is a question worth asking. The post at /blog/how-payment-holds-work-and-how-verified-history-shortens-them explains what holds usually mean and when a hold is worth chasing up.

Limits deserve a look too. If a limit changed — a daily withdrawal limit, a sending limit, a transaction cap — you want to know about it now, not when you are trying to make a time-sensitive payment. The guide at /blog/account-limits-explained-what-raises-them-and-what-freezes-them covers what usually moves limits in either direction, and what to check first when one changes unexpectedly.

Verification status is another thing that changes quietly. A platform may ask for documents again after a policy change, or a document you submitted may be approaching expiry. Open the verification or identity section of each account and confirm the status is still what you expect — verified, current, no action requested. If the platform is asking for something, deal with it promptly rather than letting the request sit.

Pay attention to expiry dates on the documents themselves. An identity document or proof of address that expires next month will become a problem next month, and the platform will usually ask for a replacement before then. Noting the expiry date now means you can prepare the replacement at your own pace instead of rushing it under a deadline.

If a platform has asked for documents again, do not treat it as an accusation. Re-verification is a normal part of how platforms operate, and the post at /blog/when-platforms-ask-for-documents-again-handling-re-verification-calmly explains how to handle it without stress. The weekly check simply makes sure you see the request in the first week it arrives, rather than discovering it weeks later.

The last check is against your own records. If you keep an account register — a simple list of your accounts, their recovery details, and any important dates — compare it with what you just saw. Did you change a password this week and forget to note it? Did you add a new payment method? Did a document expiry date change? A register that is a week out of date is still useful; a register that is six months out of date is a fiction.

If you do not keep a register yet, the weekly check is the easiest way to start one. Write down what you just checked, one line per account, and add to it each week. The post at /blog/building-a-simple-account-register-your-future-self-will-thank-you-for shows a simple way to set one up that takes minutes and pays for itself the first time you need it.

Your notes should also record anything the check turned up: an alert you dismissed, a session you signed out, a document that expires soon. That way next week's check starts from a short list of things to follow up on, instead of from scratch. Over time the register becomes the account of your accounts — the one place where the whole picture lives.

The hardest part of a weekly check is the second week. The first week feels productive because you find things to fix. The second week feels pointless because everything looks fine — and that is exactly the week that matters, because a routine that only happens when there is a problem is not a routine at all. Keep the check even when it finds nothing. Finding nothing is the result the routine is designed to produce.

Keep it small on purpose. Fifteen minutes, five checks, same time every week. If you find yourself spending an hour, you have let the check grow into something else — split the extra work out and do it separately. And if you miss a week, do not try to make up for it with a longer session. Just do the next check on time. A missed week is a gap of two weeks; a skipped routine is a gap that never closes.

After a month of weekly checks you will notice the change. Logins you recognise at a glance, recovery details you trust, documents with no surprises, and a register that matches reality. That is what account health actually looks like: not a single dramatic fix, but a quiet confidence that nothing has been left unnoticed. The post at /blog/what-a-clean-account-history-looks-like-to-a-risk-team describes the same idea from the platform's side — a history that reads as steady, consistent and cared for.

This article is educational information about managing verified accounts. It is not financial, legal or tax advice, and it is not a recommendation to buy or sell any account. Platform features, limits and verification requirements differ and change over time, so check the current settings and rules of each platform you use before you act.