Building a Simple Account Register Your Future Self Will Thank You For

An account register is a single, private list of every account you hold — the platform, the email address attached to it, the recovery method, and the date you last checked it. Nothing more complicated than that. It is not a password manager, not a spreadsheet of secrets, and not a document you show anyone. It is the map of your own digital estate, written down in one place so that you are never guessing about what you own.

Most people who hold verified accounts across several platforms do not have one. They remember the accounts they use every week and forget the ones they opened for a single purpose two years ago: the payment account tied to a side project, the exchange account used for one trade, the business account whose verification finished and was never touched again. Those forgotten accounts are not harmless. They hold balances, they receive alerts nobody reads, and they become the accounts that are hardest to recover when something goes wrong.

A register fixes that by making the invisible visible. When every account is on one list, you can see at a glance which ones matter, which ones are idle, and which ones have no working recovery method. That clarity is the whole point. You are not building a system for its own sake; you are giving your future self a list they can act on at two in the morning when a phone is lost and a password reset has to happen now.

Memory feels reliable until it is tested. Ask yourself right now, without looking: how many verified accounts do you hold, on which platforms, and which email address is attached to each one? Most people can name three or four and then stall. The rest surface later, usually at the worst moment — when a platform asks for a document, when a recovery email goes to an inbox you no longer check, when a support agent asks which accounts belong to you and you cannot list them.

Memory also decays in exactly the wrong direction. The accounts you use daily stay fresh in your mind, so you feel organised, while the accounts you rarely touch fade quietly. Those are the accounts most likely to be locked, flagged, or forgotten entirely, because nobody has looked at them in a year. A register works against that drift: the act of writing an account down creates a record that does not depend on how often you think about it.

Teams have the same problem at a larger scale. When several people can act on the same accounts, nobody knows the full list, and each person assumes someone else is keeping track. The register solves that too, provided it is kept in one agreed place and one person owns keeping it current. Without that single source of truth, a team will discover its own accounts the same way an individual does — during an incident, under pressure, too late.

Keep each entry short: platform name, the account's purpose in a few words, the email address or identifier attached to it, the recovery email and phone number on file, whether two-factor authentication is switched on and what kind, and the date of your last check. Add one line for notes — a renewal date, a verification level, the name of the person who holds the keys if it is a team account. That is enough. A register that asks for too much detail becomes a chore, and a chore gets abandoned.

The recovery information matters more than the account name itself. A platform is not asking whether you remember you have an account; it is asking whether you can prove it is yours, and the proof usually runs through the recovery email. That is why the guide on recovery email hygiene at /blog/recovery-email-hygiene-the-inbox-behind-the-account-matters is worth reading alongside this one: the inbox behind the account is often the real key, and the register should record exactly which inbox that is for each account, so there is no guessing when a reset is needed.

Also record what you do not have. If an account has no recovery phone, write that down. If two-factor authentication is not switched on, write that down too. A register that only lists the good news is a comfort blanket; a register that lists the gaps is a to-do list. The gaps are the most valuable lines in the document, because each one is a small job you can finish in a few minutes — and finishing them is what turns the register from a list into actual protection.

Never put passwords in the register. Never put recovery codes, seed phrases, private keys, or full card numbers in it either. The register is a map, not a vault: it tells you where things are and how to reach them, but it must be useless to anyone who finds it. Passwords belong in a dedicated password manager, and recovery codes belong wherever you keep things that must survive a lost device — a safe, a locked drawer, an encrypted backup. Keeping those things separate is not paranoia; it is the whole design.

For the same reason, keep the register itself private and backed up. A document on a shared drive, an email draft, a note in a shared workspace — each of these is a copy that can be read by the wrong person or lost when access changes. Store it where only the people who need it can reach it, keep one backup somewhere separate, and know who has access. If the register lists every account you own, it is a document worth protecting as carefully as the accounts themselves.

If you work with others, agree in advance who can see the register and who can change it. A register that anyone can edit will drift into contradiction — one person updates a recovery email, another still has the old one — and the contradictions will surface during an incident, when there is no time to argue about which version is right. One owner, one agreed location, and a short note each time something changes keeps it trustworthy.

Start with what you know. Open your password manager, your email inboxes, and your phone's saved logins, and list every account you can find in one sitting. Do not try to be exhaustive on the first pass; aim for the accounts that matter most — the ones holding money, the ones your business depends on, the ones that would hurt to lose. You will find more later, and the register is built to grow.

Then hunt for the ones you forgot. Search your inboxes for the words verification, welcome, and your account is ready, and look at what comes back. Check the app list on your phone for platforms you installed and never opened again. Look through old messages from platforms about limits, reviews, and password changes. Every account leaves a paper trail in your inbox, and a single afternoon of searching usually turns up two or three accounts that memory had dropped entirely.

Fill in the columns one account at a time and stop when the list feels complete enough to use. A register with twelve entries you trust is worth more than a register with forty entries half of which are guesses. Mark the entries you are unsure about, note what you still need to confirm, and set a date to finish them. The register is a living document, not a one-off project, and starting with a good version today beats waiting for a perfect version that never arrives.

A register that is never updated becomes a museum piece within a few months: accounts change email addresses, recovery phones are replaced, verification levels are upgraded, and the document quietly stops matching reality. The fix is a short monthly habit. Once a month, open the register, pick three accounts, and confirm that the details are still right — that the recovery email still works, that two-factor authentication is still on, that the last-check date is fresh. Three accounts a month means a register of thirty-six is fully reviewed within a year without ever taking more than a few minutes.

Tie the habit to something you already do. If you already rotate passwords on a schedule, do the register check in the same sitting — the password rotation guide at /blog/how-to-rotate-passwords-across-a-portfolio-without-locking-yourself-out makes the same point about small, regular work beating rare, heroic effort. If you already do a monthly finance review, add the register as one line on that list. Habits survive when they ride on habits that already exist, and they die when they depend on remembering to remember.

Also update the register the moment something changes, not at the next monthly check. A new account, a changed recovery email, a new phone number, a handover inside the team — each of these takes thirty seconds to record while it is fresh, and each becomes a mystery a year later if it is not recorded. The rule is simple: if it changes the answer to the question who can reach this account, it goes in the register today.

The register earns its keep on the bad days. A phone is lost, and instead of wondering which accounts were tied to that phone, you open the register and work down the list: change the recovery number here, move two-factor authentication there, confirm the email still works. A support agent asks which accounts belong to you, and you can answer precisely instead of guessing. A team member leaves, and you know exactly which accounts they could reach and what needs to change. In each case the register turns a scramble into a checklist.

It also earns its keep on the quiet days. When you can see every account at once, you can spot the ones that are idle and should be closed, the ones whose verification has lapsed, and the ones where the same recovery email serves five accounts that should not share one point of failure. That kind of review is only possible when the full picture is in front of you, and it is the difference between managing a portfolio and merely remembering parts of it.

Start today, while nothing is on fire. Building a register takes an afternoon, keeping it takes five minutes a month, and the person who benefits most is the one you will be a year from now — standing in front of a problem, with a list in hand instead of a memory to rely on. That is a small investment for a large amount of calm, and it is one of the few security habits that pays off whether or not anything ever goes wrong.

This article is educational and does not constitute financial, legal or tax advice. Platform rules and security features change, so always check the current guidance on the platform you use, and take professional advice where a decision affects your business, your money or your legal obligations.