Build a Secure Relocation Document Vault
A method for keeping relocation paperwork usable from another country. The two clocks that fight each other, the register that tracks them, and the phone number that can lock you out of everything.
Reviewed September 2026. A relocation generates more sensitive paperwork in six months than most people produce in a decade: passports, background checks, apostilles, bank statements, medical records, lease contracts and application decisions, for every person in the household. This page is a method, not a legal requirement. It exists because the predictable failure is not losing a document. It is needing one, from another country, on a borrowed device, in a week when three other things are also going wrong.
Two clocks run in opposite directions
This is the part a filing system alone does not solve, and it is why the register below is worth more than the folder.
Some documents are slow to obtain and leave little room to speed up. Others have a short validity and start dying the moment they are issued. Order the short-lived ones too early and they expire before the appointment; start the slow ones too late and nothing else can proceed.
| Behaviour | Examples | What it forces |
|---|---|---|
| Slow, no expiry pressure | Passport renewal, the FBI Identity History Summary, apostilles | Start first. The FBI gives no individual priority, so everything downstream inherits its timing |
| Fast, short validity | Medical certificates, some bank and civil-status certificates | Order only once the appointment date is visible |
| Slow and short-lived | A background check that must also be recent when submitted | The squeeze. This is what the register exists to watch |
The register
One row per document, per person. A spreadsheet is fine. What matters is that these columns exist, because each one answers a question you will actually be asked.
| Column | The question it answers |
|---|---|
| Person | Whose document is this? Two adults means two of almost everything |
| Owner | Who is chasing it? Unowned documents are the ones that stall |
| Issuer and official URL | Where to re-order or verify it |
| Date requested | Whether a delay is normal or a problem |
| Date received | When any validity window started |
| Validity rule | Does it expire, and on whose calendar |
| Original, apostilled or translated | Stops the wrong version being submitted |
| Shared with | A disclosure trail, which matters more than it sounds |
| Recovery location | Makes loss manageable rather than fatal |
Three copies with different failure modes
- Working copy: encrypted storage on the device used for applications.
- Offline copy: an encrypted drive kept physically separate from that device.
- Recovery copy: a reputable encrypted cloud account protected by strong multifactor authentication.
The point is not redundancy for its own sake. It is that a stolen laptop, a failed drive and a locked-out account are three different disasters, and no single copy survives all three.
The phone number that locks you out of everything
This is the most damaging and least discussed failure in the whole move, and it has nothing to do with documents.
CISA describes multifactor authentication as a code texted to a phone or generated by an authenticator app. Most Americans are on the first version. Then they cancel the US mobile number after moving — and every account secured by a text message becomes unreachable at once: the bank, the brokerage, the tax account, the email address that recovers all the others.
Recovering from this from Spain, with institutions that want to verify you by sending a code to the number you no longer have, is genuinely hard. Do this before you cancel anything:
- List every account that uses SMS for login or recovery. It will be longer than you expect.
- Move each one to an authenticator app where the institution supports it.
- Save the recovery codes offline, in the vault, not in the same password manager they protect.
- Keep the US number alive through the transition rather than cancelling on departure. Parking it is cheaper than the alternative.
- Update the contact details your US institutions hold while you can still pass their checks.
Naming that survives stress
Use a predictable pattern such as PERSON_DOCUMENT_ISSUER_YYYY-MM-DD_STATUS. Keep the original scan immutable, and create a separate, clearly named file for a translation, an apostille or a redacted sharing copy. You will be searching this at speed, in a hurry, possibly on someone else’s screen.
A relocation makes you a target
You are about to transfer a large sum internationally, rent a property sight unseen, and share identity documents with people you have never met. That profile attracts fraud, and the attempts are well built: the fake landlord who wants a deposit before a viewing, the “visa service” that asks for passport scans, the email changing the bank details on a payment you were already expecting.
CISA’s baseline applies here more than usual: unique passwords held in a password manager, multifactor authentication switched on, suspicious links and attachments treated as suspicious rather than urgent, and software kept updated. On top of that, two relocation-specific habits:
- Confirm payment details through a second channel before sending money, using a number you already had, not one from the email.
- Do not email a full document pack because one page was requested. Send the page. Redact identifiers that are not needed, use expiring links where available, and delete shared folders once their purpose is complete.
The recovery drill
Before departure, pretend the phone and the laptop are gone. Can you reach the recovery copy, get past multifactor authentication, contact the banks, retrieve passport copies and find the insurance certificate? Fix every “no” while you still have access to the original institutions and a working US phone number.
Run it once more after arrival, when the phone number, the address and the devices have all changed. The answers are usually different, and that is exactly the point.
What not to keep
A vault is not an archive. Superseded drafts, expired certificates and duplicate scans add risk without adding use. Once a document is replaced, delete the old copies from working and shared locations and keep one clearly marked historical version only where you have a reason to. And never store a photograph of a document in a phone gallery that syncs to a general cloud account.
Sources
Most of this page is operational method rather than regulation, and we say so rather than dressing it as a requirement. The security baseline it rests on is published:
- CISA — Secure Our World, consulted 29 September 2026: strong unique passwords with a password manager, multifactor authentication, recognising and reporting phishing, and keeping software updated. CISA publishes general guidance; the application to relocation documents here is ours, not theirs.
Continue your plan
- Build the FBI certificate, apostille and translation chain, the slowest items in the register.
- Save the live checklist from the consulate responsible for your state.
- Track validity windows and dependencies on the timeline.
- Give every document one task and one owner.
- Keep the evidence of the origin of your funds, which a Spanish bank can ask for after the transfer has landed.
- Prepare the tax handover pack without leaving sensitive records in email.
Common questions
What documents do I need to keep for a move to Spain?
Passports, criminal record certificates, apostilles, sworn translations, bank statements, medical records, lease contracts and application decisions, for every person in the household, each with its own issue date and validity rule.
What happens if I cancel my US phone number after moving?
Every account secured by a text message becomes unreachable at once: the bank, the brokerage, the tax account and the email that recovers the others. Move those accounts to an authenticator app and keep the number alive through the transition.
How should I store relocation documents safely?
Three copies with different failure modes: an encrypted working copy, an encrypted offline drive kept separately, and a cloud recovery copy protected by strong multifactor authentication.
Official sources
Sources recorded for this page. Check the linked authority for current requirements; review dates are shown for each source.