If a Laptop Dies Tomorrow: Backup and Continuity for Visa Agencies

Ask most agency owners about backups and they will think about hardware. A hard drive fails, a laptop is stolen, an office floods. Those events happen, but they are rarely what actually stops a visa agency.

The realistic failures are more mundane and more disruptive. A senior consultant resigns on Friday and the WhatsApp thread with a corporate client — including three appointment confirmations and a scanned sponsorship letter — was on their personal phone. An office manager goes on leave and nobody else can log into the payment gateway because the account was created with their email. Someone sorts a shared spreadsheet by one column without selecting the others and misaligns 400 rows, and nobody notices for a week. A domain expires because the renewal notice went to an inbox that no longer exists.

What these have in common is not hardware. It is that some part of the agency existed in exactly one place, reachable by exactly one person, with no copy and no second key. Continuity work is mostly the unglamorous job of finding those single points and removing them.

The good news is that this is a finite job. Most agencies can close the serious gaps in a couple of focused afternoons, and the result is durable — you are changing where things live, not adding a process the team has to maintain forever.

Start with the same honest inventory you would do before a system migration, but ask a different question of each item: if the person who owns this were unreachable for two weeks, what would we lose?

Work through the categories. Client records — in a platform, a spreadsheet, or several spreadsheets. Documents — a shared drive, an email inbox, a messaging app, a folder on someone's desktop. Communication history — this is the one agencies systematically underestimate, because the record of what you promised a client often lives entirely in personal message threads. Financial records — the gateway, the accountant, an invoice folder. Configuration — your visa types, checklists, fee tables and templates, which frequently exist only as institutional memory in one experienced person's head. Credentials — every account, and who can recover it.

Mark each with an owner and a *what if they vanish* consequence. The rows where the consequence is severe are your work list, in order.

Agencies are usually surprised by two findings. First, how much sits with one long-serving employee. Second, how much of the operating knowledge is not written anywhere — the reason a particular embassy wants documents in a particular order, the contact at a visa application centre who resolves problems, the quirk in how one destination handles biometrics appointments. That knowledge is a continuity risk too, and the fix is to write the important parts into your checklists and process notes where they become agency property rather than personal expertise.

This is the single highest-value fix and it is almost free.

Every business account should be created on an agency-owned domain, with the owner or a designated administrator holding recovery access. Email, the CRM, the payment gateway, the domain registrar, the hosting, the analytics, the business messaging number, the cloud storage. Not one of them on a personal address, and not one of them recoverable only through a phone number that belongs to an individual.

The two accounts that cause the most damage when they are personal are the domain registrar and the primary business email. Losing control of a domain means losing your website, your email, and every account that uses that email for recovery — all at once. Check today who the registrant is and where renewal notices go. Set it to auto-renew on a company card.

Use a shared password manager rather than a document called *passwords*. Give each person their own login with their own permissions, so removing them removes their access without changing anyone else's. Enable two-factor authentication on everything financial, and make sure recovery codes are stored somewhere the owner can reach — a second person with recovery access is a control, not a risk, provided you choose that person deliberately.

Write it down. One document listing every account, who owns it, who administers it, and how recovery works. Keep it current and keep a copy somewhere that does not depend on the accounts it describes. Our answer on where visa applicant data is stored covers the questions clients and partners will ask about this.

Good continuity starts long before anyone leaves, with permissions that reflect what each person actually needs.

The default in small agencies is that everyone can see everything, which feels efficient and creates two problems. It makes offboarding an all-or-nothing event, and it means a single compromised account exposes every passport and bank statement you hold. Neither is acceptable once you are handling other people's identity documents at volume.

A workable structure is straightforward. Consultants see the cases assigned to them plus a shared queue. Senior staff see everything operational. Finance sees payments and invoices but does not need to open passport scans. The owner and one administrator see everything, including the audit trail. Contractors and part-time staff get the narrowest access that lets them work, with an end date on it.

An audit trail matters as much as the permissions. Who opened which document, who changed a fee, who exported a client list. In normal operation nobody looks at it. On the one day you need it — a suspected data leak, a client dispute, a regulator's question — it is the only thing that answers the question. Our answer on who can see client data in a visa CRM covers the model in more detail, and the controls themselves live in the admin panel.

Review permissions on a schedule — twice a year is enough. People change roles, projects end, and access almost never gets removed unless someone deliberately removes it.

Staff turnover is normal. Losing part of your operating record every time someone leaves is not, and the difference is entirely down to preparation.

Run offboarding as a checklist on the day, not as a conversation over the following weeks. Revoke platform access. Reset or suspend the email account and forward it to a manager for a defined period. Remove them from the business messaging number and shared inboxes. Change any shared credentials they knew. Collect or wipe agency devices. Reassign every open case to a named person, so no application is left ownerless. Transfer any partner or supplier relationships they held.

The part that is hard to do at the last minute is the client communication history. If your consultants talk to clients through agency-owned channels, that history is already yours and the handover is clean. If it lives in personal WhatsApp threads and personal inboxes, you cannot recover it after the fact, and the new consultant picks up the case with no idea what was promised. This is the strongest practical argument for centralising client messaging — see client communication best practices.

Be fair as well as thorough. Tell people during onboarding that client communication runs through agency systems and that access is revoked on the last day as a matter of routine. Framed as standard practice rather than as suspicion, nobody objects.

And close the loop with clients where it matters. A short message introducing the new point of contact prevents the awkward situation where an applicant messages a number that no longer belongs to your agency.

Backups are simple to describe and easy to get subtly wrong. Two questions define what you need: how much work can you afford to lose, and how long can you afford to be unable to work?

For most visa agencies the honest answers are *about a day* and *a few hours*. That points at daily automated backups of everything transactional, with a retained history going back several weeks so you can recover from a problem you did not notice immediately. A single overwritten copy protects you from hardware failure and from nothing else.

Back up the full picture, not just the database. Records, documents, message history, financial data, and configuration — visa types, checklists, fee tables, email and message templates. Configuration is consistently the forgotten one, and it is the slowest thing to rebuild by hand.

Keep at least one copy somewhere structurally separate from the live system, so that a problem affecting the primary environment cannot affect the copy too. And keep your own periodic export in a format you can read without the vendor — a CSV of records plus a document archive is enough. That is not distrust; it is the same reason you would keep your own accounts even with a good accountant.

If you run on a hosted platform, ask the direct questions and write down the answers: what is backed up, how often, how far back point-in-time recovery goes, how you request a restore, and how long it takes. Vague answers are an answer. Our answer on GDPR and visa CRM covers the compliance side, which overlaps heavily with this and with GDPR for visa agencies.

A backup that has never been restored is a hypothesis. Plenty of agencies discover during a real incident that their backups had been silently failing for months, or that the export omitted documents, or that nobody knows the procedure.

Schedule a restore test — twice a year is enough for most agencies — and treat it as a drill. Pick a date. Restore to a separate environment. Check that a sample of client records is complete, that documents open, that payment history is intact, and that your configuration came back. Time it. Write down what went wrong, because something always does, and fix that before the next drill.

Run the same drill for the human side. If the person who normally handles this is unavailable, can someone else follow the written procedure? If the answer is no, the procedure is not written well enough.

Also rehearse the smaller, likelier scenarios, because they are far more common than total loss. Someone deletes a client record that should not have been deleted. A bulk edit sets the wrong fee on 60 applications. A document is attached to the wrong case and needs removing from one place and adding to another. Knowing how to reverse a mistake within minutes is worth more day to day than a disaster recovery plan you will probably never invoke.

Write the outcome of each drill in the same document as your account inventory. Over a couple of years it becomes a genuinely useful record of how your agency's resilience has improved.

Data is the part people think about. The rest of continuity is about whether the agency can keep operating when a person, a device or a supplier is unavailable.

People. For each critical function — submitting applications, handling payments, answering the main phone line, managing partner relationships — name a second person who can do it adequately. Not perfectly, adequately. Then let them actually do it occasionally, because a deputy who has never performed the task is a name on a page.

Devices. Work should not depend on a specific machine. If everything the team needs is in browser-based systems with per-user logins, a dead laptop is an inconvenience rather than an incident: someone borrows a device, logs in, and carries on. That is a large part of the practical case for not running your agency out of local files and spreadsheets.

Suppliers. Know what happens if your payment gateway suspends your account, your email provider has an outage, or a partner disappears mid-season. You do not need a full alternative standing by, but you should know what the first hour looks like.

Clients. Decide in advance how you would tell applicants about a serious disruption, through which channel, and who writes it. Agencies handle incidents far better when the communication does not have to be invented under pressure.

And keep an offline copy of the essentials — key contacts, your account inventory, your restore procedure — somewhere reachable when the systems are not.

None of this needs to be a formal document with a version number. One page, kept current, covers what a visa agency realistically needs.

Put five things on it. Accounts: every business account, its owner, its administrator, and how recovery works. Backups: what is backed up, where, how often, and the date of the last successful restore test. Access: who has what level, and the date of the last permissions review. Deputies: each critical function and the second person who can perform it. Incident steps: the first five things to do if the main system is unavailable, including who tells clients.

Review it twice a year and after any staff change. Store it somewhere that does not depend on the systems it describes — a printed copy in the office and a copy in a personal cloud account belonging to the owner is not sophisticated, and it works.

The payoff is not only risk reduction. Agencies with this in place sell more confidently to corporate clients and B2B partners, who increasingly ask where data is held, who can see it, and what happens if you disappear. Being able to answer plainly is a commercial advantage. RotaVisa operates across more than 40 countries, and that kind of spread only works when the operation does not depend on any individual desk.

One honest note on where a platform helps and where it does not. VisaCRM is a productized service — built, branded and run for your agency, which owns it — and it removes a large class of continuity risk by putting records, documents, payments and client communication in one place with per-user access and an audit trail. It does not file government forms, it does not give legal advice, and it cannot make someone else in your team ready to cover for a departing consultant. That part is management. If you want to talk through where your single points of failure are, book a call.