Creating a minimal account operations record

An account operations record is a small spreadsheet that answers three questions about every account you run: what it is for, who handles it, and what needs attention next. It becomes valuable as soon as you manage more than a handful of profiles for clients, campaigns or a team, because logins scattered across chats and notes slow everybody down.

When an order is delivered, you receive a TXT file with one line per account, in the form username:password:email:email_password:auth_token (the exact fields vary by category). This guide shows how to turn that file into a clean inventory sheet, which columns to add, where the sensitive parts should live, and how to keep the record accurate over time.

Start from your delivery file

The delivery TXT is your raw material. Download it from the order page, store the original untouched, and build your working sheet from a copy. Every line becomes one row and every colon-separated field becomes one column.

The free split by delimiter tool pulls out only the columns you need, for example just the username or the username and email, so you do not have to edit hundreds of lines by hand. If a list uses a different separator, run change delimiter first, and use remove duplicates when you merge several orders into one sheet.

Give every account a short internal ID such as A001, A002 and so on, and record the order number and category it came from. That habit makes any line easy to find later and makes batches comparable, for example phone verified aged accounts next to a batch of stat accounts priced by follower count, where the follower count at purchase deserves its own column.

Choose the columns that matter

Keep the sheet to what people actually use. A column nobody updates is worse than no column. A practical starting set:

• Internal ID, username, order number and category
• Project or client the account belongs to
• Assigned operator and a backup operator
• 2FA status: whether the secret is saved and where it is stored
• Recovery email and who controls that inbox
• Last checked date and result from the account checker
• Status: ready, in use, resting or needs attention
• Notes for onboarding steps and handover details

If an account uses an authenticator secret, the 2FA code generator lets you confirm that the saved secret produces valid codes before you hand the account to someone.

Keep secrets in a vault, references in the sheet

The inventory should be easy to share with your team, which is exactly why it should not hold every secret. Store the password, email password, auth token, backup codes and 2FA secret in a password manager or encrypted vault, and keep only a reference in the sheet, such as "vault entry A017". Give each operator access only to the entries for the accounts they run.

Keep the original TXT in the same protected place and delete extra copies once the vault is filled. For storage habits see keeping delivered credentials and order files private, and for recovery setup read two-factor authentication and recovery planning.

Review on a schedule

Choose a rhythm, weekly for active accounts and monthly for resting ones, and update the sheet whenever something changes: an operator joins or leaves, a password or 2FA setup is rotated, an account is paused, or a new batch arrives. Run the checker on each batch and write down the date next to the result, because a result describes that moment only. When an operator leaves, rotate the password and the 2FA secret so the record and reality stay aligned.

You can open your order history with an email verification code to get back to your completed orders and their TXT files. For order questions, support is on Telegram, and the contact page has the details. If you are scaling up, larger orders get an automatic volume discount, and bulk categories such as 2007/2026 Twitter accounts allocate accounts randomly, which is one more reason to log each batch the moment it arrives.

Frequently asked questions

Should the operations record contain account passwords?

Keep the sheet to references and status, and store passwords, tokens and 2FA secrets in a password manager or vault. That way the whole team can use the sheet without every person holding every login.

What is the smallest useful set of columns?

Internal ID, username, order number, category, assigned operator, 2FA status, last checked date and status. Add more only when someone will actually keep them up to date.

How do I turn the delivery TXT into a sheet quickly?

Download the TXT, keep the original untouched, then use the split by delimiter tool to extract the fields you need and paste them into your sheet. Add the internal ID and order number next to each row.

How often should I update the record?

Update it whenever an operator, password, 2FA setup or account status changes, and review it weekly or monthly. Write the date next to each checker result so you know how fresh it is.