Someone Is Moving In for a Few Months: The Tech Setup Nobody Plans For

It happens to a lot of households and it is almost never planned. A parent comes to stay for a course of treatment. An adult child moves back for a semester, or between leases. A relative arrives after surgery and stays until they are steady. A sibling flies in for eight weeks because someone has to be here. The spare room gets made up, and everybody assumes the rest will sort itself out.

Then it does not. Somebody cannot print the form that is due tomorrow. Two people have calls at ten and one of them keeps freezing. A bank refuses a login it has never seen from this city, and the code to prove it is you appears on a tablet charging on a nightstand three hundred miles away.

Search for help with any of this and you will be handed the same answer: buy an extender, move the router, consider a mesh system. Those are decent answers to a signal question, and this is not a signal question. What changed is the household — how many working adults are on one connection, whose accounts are pointed at which address, and who is allowed to print. This is a networking-and-accounts piece, not a medical or elder-care one, and it applies just as well to the adult child in the back bedroom as to the parent in the front one.

Uploads are the narrow lane, and a second working adult lands right in it

Home internet is lopsided on purpose. The number on your bill is the download number, and the upload number — the one that matters when you are the person talking — is a fraction of it. This is not a conspiracy; it is what the whole industry was built around, and the regulator builds around it too. When the FCC raised its benchmark for high-speed fixed broadband on 14 March 2024, it set it at "download speeds of 100 megabits per second and upload speeds of 20 megabits per second," which it described as "a four-fold increase from the 25/3 Mbps benchmark set by the Commission in 2015." Even the long-term goal it adopted in the same report is asymmetric: 1 Gbps down against 500 Mbps up.

Here is why that matters the week somebody moves in. Streaming is a download. Two people watching different things almost never collide, because that is the lane with all the room in it. Video calls are the opposite, and they are the one ordinary daily activity that pushes hard in the direction where there is least space.

Zoom publishes its own numbers, and they are worth reading closely because of which one is bigger. For group video calling it lists "1.0 Mbps/600kbps (up/down)" for high-quality video, "2.6Mbps/1.8Mbps (up/down)" for 720p, and "3.8Mbps/3.0Mbps (up/down)" for 1080p. Read the pairs again: on a group call the upload requirement is the larger of the two. A one-to-one call is gentler — Zoom lists 600kbps up and down for high-quality video — but a daily check-in with a clinic, a standing team meeting and a class are all group calls.

So stack them. Two adults on group calls at the same time is realistically four to six Mbps of upload before anything else happens. Add a cloud backup that woke up, a phone quietly uploading a month of photos to iCloud or Google Photos, and a laptop pushing a big file to a work drive, and a 20 Mbps upload has a genuine traffic problem. On an older plan with 10 Mbps up, or on some cable tiers with less, it is not a traffic problem, it is the reason one of you sounds like a robot.

What to do about it, in order. First, find out what you actually have rather than what you were sold: run a speed test on a wired computer at a quiet hour, and again at seven in the evening, and write both numbers down. If your upload is comfortably above about 20 Mbps you can mostly stop worrying and skip to the next section. If it is in single digits, treat upload as a shared resource and say so out loud — agree that the two standing calls do not overlap where they do not have to, and that is a five-minute conversation, not a purchase.

Second, deal with the silent uploader. Cloud backup and photo sync are the two that eat a connection without anyone noticing, because nobody is watching them. Both can be scheduled or paused; set them to run overnight for the length of the stay. Do not turn them off and forget — a stay is exactly the period when somebody is living out of one laptop and can least afford to lose it.

Third, if one person will be on calls every single day, wire that desk rather than buying anything wireless. A marginal wireless link does not show up as a slow web page, it shows up as freezing on a call, and it is the workload least tolerant of a weak signal.

The guest network is right for a weekend and usually wrong for a season

The reflex is to put the arriving person on the guest network. For a weekend that is exactly right. For three months it is usually wrong, and the reason is worth understanding rather than guessing at, because the guest network is doing precisely what it was designed to do.

TP-Link says it plainly in its own support documentation for Deco systems: "When Deco works in the Router mode, the guest network and the main network are isolated." Isolated means isolated. A laptop on the guest network cannot see the printer, cannot cast to the television, cannot reach a shared drive or a network scanner, and in many cases cannot see the other guest devices either. That is the whole point of the feature, and every other manufacturer builds some version of it.

There is a wrinkle worth knowing before you go hunting through the app for a switch that will fix it. TP-Link notes that when the same hardware runs in access-point mode instead of router mode, an "Allow Local Access" toggle appears that controls whether the guest network is isolated from the main one — and it adds that "Some Deco models do not support this feature." So the setting may not exist on your gear, and on other brands it may be called something else or not be offered at all. Do not plan around finding it.

The decision, then, is a household one rather than a technical one. A visitor for a weekend goes on the guest network and never notices. A person who is going to live here until December, print insurance paperwork on a deadline, and put something on the television every evening is not a guest in the network sense, whatever they are in the family sense. Put them on the main network and treat them as part of the household. If what is making you hesitate is file visibility — who can see whose documents once everyone is on the same network — that is a real question with a real answer, and we have written it out in full for house-shares; the same settings work here.

Whichever you choose, do the one thing almost nobody does: tell them at the door which network they are on and what it will not do. Most of the friction in the first fortnight is one person quietly failing to print and assuming they have broken something.

About the far room — read the two we have already written

The spare room is very often the worst room, because spare rooms are at the ends of houses and the router is wherever the cable came in. That is a real problem and we are not going to pretend otherwise. We are also not going to re-explain it here, because it is the one part of this situation the internet already covers well, including by us: start with whether you need a mesh system or just a better single router, then read why extenders so often make things worse rather than better, and if the room has a coaxial or telephone jack in it, look at getting a real wired connection to it without opening a wall.

The one thing to add that is specific to a stay like this: choose the room before you buy the hardware. If the person moving in will be on daily calls, the correct room is the one you can run a cable to, even if it is the smaller one. If they will mostly be reading and watching television, the far bedroom is fine and you may need nothing at all.

The real problem is not the Wi-Fi. Their accounts still live at the other address.

This is the part that catches nearly everyone, and it is not really a technology failure. A person can move. Their accounts cannot, and they go on quietly assuming the world looks the way it did the day they were set up.

Start with where the sign-in codes actually land. Apple states that the six-digit verification code is "automatically displayed on your trusted devices or sent to your trusted phone number." Read that as a logistics problem rather than a security one: if the iPad that displays the code is sitting on a nightstand at the other house, then for the length of the stay the person cannot sign in to anything new without phoning someone and asking them to read out a number. The same shape applies to any account whose second step is tied to a specific device or a specific phone line — a landline that still rings in an empty house is the worst version of this.

So the single most useful thing you can do before the drive, not after, is a fifteen-minute audit of two or three accounts that matter. Email first, always, because email is the recovery route for nearly everything else, then the bank, then whatever portal the stay actually revolves around. For each one: check which device or number receives the codes, and make sure that device is the one travelling.

Then print the backup codes. Google will give you a set on request — its own documentation says "You can get a new set of 10 backup codes whenever you want," and warns that "After you use a backup code to sign in, that code becomes inactive." Ten codes, one use each, and they are only useful if they exist before the emergency. Print them, put them in the bag with the passport and the insurance card, and do not photograph them onto the phone you are worried about losing. Most major providers offer some equivalent; generate them while you are still at a kitchen table with time to spare.

Expect the second thing too: a bank or a portal that asks for extra verification the first time it sees a sign-in from a new city on an unfamiliar network. That is the system working correctly, and it is not something you can pre-empt by changing a setting on your router. What you can do is make sure the contact details on file are current, because that is where the extra verification will be sent. An old landline, a former address, a work email nobody reads any more — any of those turns a five-second confirmation into a phone queue on a bad day.

The third one is the quietest and it is not about codes at all. In most families, one person set up the accounts. One person knows the pharmacy login, one person has the patient portal password, one person is the named account holder on the utility, and if that person is the one who is unwell, travelling, or simply asleep, nobody else can get in. This is worth writing down before it is urgent. A shared vault in a password manager is the clean version and is what we would set up. A sealed envelope in a drawer, with a note of who holds what rather than the passwords themselves, is the version that families actually do, and it beats nothing by an enormous margin.

One thing not to do: do not solve any of this by sharing a single login between two people, and do not have codes permanently forwarded to somebody else. The goal is that the right person can get in from where they are now — not that everybody can get into everything.

Paperwork turns up during a stay like this, and it turns up on a deadline

Nobody puts this on the list, and it generates more panicked evening phone calls than the Wi-Fi does. Stays of this kind come with forms — authorisations, insurance, a leave request, an enrolment, a lease addendum, something that has to be signed and returned today. Printing and scanning stop being occasional and become weekly.

Three practical things. Put a working printer within reach of where the person actually sits, not in the office at the other end of the house; a stay is not the time to be walking a form down a corridor twice. Make sure somebody in the house can scan to PDF, and check it before you need it — scan-to-email in particular is notorious for failing silently months after it last worked, and we have written up why that happens and how to get it back. And keep the returned documents in one folder on one computer, backed up, rather than scattered through an email thread; six weeks in, "which version did we send" is a real question with a real cost.

If there is no printer and buying one is not worth it, a phone camera scanning app will produce a genuine PDF that most portals accept — but check the portal's file-size limit before you rely on it, because a multi-page scan at full resolution will often be rejected without a useful error.

When it is the other way round, and the room comes with Wi-Fi you do not control

The mirror image of all this is just as common: the person is not moving in with you, they are moving into a room somewhere else — a care community, a senior apartment, an extended-stay place, a relative's spare room — and the network there belongs to somebody else. You cannot change a setting on it and you should not try.

What to expect, so it is not a surprise: a sign-in page before anything works, devices that cannot see each other so a portable printer or a casting stick will not be found, and sometimes blocked ports that stop a work VPN or a remote-desktop connection from connecting at all. If the sign-in page will not appear on a laptop — which is the single most common complaint — that is a known and fixable problem and we have a walkthrough for it.

What genuinely helps: ask whether a wired connection is available in the room and use it if it is; ask whether there is a device limit, because there usually is and it is usually lower than the number of things a person travels with. Some people bring a small travel router that puts their own devices on one private network behind the building's — that works, but check the house rules first, since plenty of managed networks explicitly forbid it. And if the person is renting rather than staying as a guest, what you are and are not allowed to change about the internet in a home you do not own is worth reading in full.

The wind-down, which nobody schedules

Stays end, usually a little abruptly, and the tidying up gets skipped because everyone is busy with the actual departure. It takes about twenty minutes.

If they were on the main Wi-Fi and the password had been passed around, change it. Look at the router's device list and remove the entries that have gone. Check the television and streaming boxes for accounts signed in during the stay, and sign them out — this is the one that gets discovered months later, usually as a billing surprise. If they added your printer to their laptop, remove it, or the next time they hit print at home the job will sit in a queue pointed at a machine in another county. Collect the borrowed things: the cable, the spare charger, the drive.

The two that actually bite are less obvious. First: if you moved a second factor onto the device that travelled, move it back, or the first sign-in from their own home goes to the wrong house all over again and you have simply reversed the problem. Second: if their laptop was backing up to a drive in your house, that backup stops the moment they drive away, and it stops silently. Set up something that runs where they live now, before the departure rather than after, and check that it has run once.

How we can help

The whole of this is a two-hour job for somebody who has done it before and a fortnight of small aggravations for somebody who has not. We will set up the room the person is actually going to use: a real connection to that desk rather than a hopeful wireless one, the printer reachable and tested, scanning that works the first time it is needed, and the backups and photo syncs rescheduled so they stop fighting the calls.

We also do the account side, which is the half people do not think to ask about — working out which device is receiving the sign-in codes and getting it onto the right one, generating and printing backup codes for the accounts that matter, setting up a shared password vault so more than one person in the family can get into the things the family depends on, and doing the wind-down properly at the other end.

We look after homes and small businesses across Southern California, and this comes up constantly — around the hospitals and treatment centres in the San Gabriel Valley, in Duarte and Pasadena, in the multi-generational houses across Anaheim Hills and Corona, and in the desert cities where a family member arrives for a season. We do not sell hardware and we take nothing from any provider, so if the answer is that you need nothing, that is what we will tell you.

Bottom line

The advice you will find online treats a person moving in as a coverage problem, and it is not. It is a household problem with four moving parts: the upload lane, which is the narrow one and is where a second working adult lands; the guest network, which is genuinely isolated by design and therefore the wrong home for somebody staying a season; the paperwork, which arrives on deadlines; and the accounts, which stay pointed at the address the person just left.

Do three things before they arrive. Measure your upload and agree out loud who gets it when it is scarce. Decide deliberately which network they are on, and tell them what that network will not do. And spend fifteen minutes making sure the sign-in codes for their email and their bank will land on a device that is coming with them, with ten printed backup codes in the bag as insurance.

Then put a note in the calendar for the week the stay ends, because the tidying up is short, easy, and never happens on its own.