In-House IT vs. Managed IT for Senior Living Communities

For most senior living communities the better question is not which option costs less. It is which one covers the hours you actually operate. One employee covers a working day. Your nurse call system, door controllers and medication carts run every hour of every day, and that gap is the whole decision. This sits inside managed IT for senior living, and the cost side of it is answered separately in what managed IT costs for a senior living community.

This post is about the part the cost comparison does not settle. Two options can land at a similar annual number and still buy you completely different things.

What Each Option Actually Covers

Start with hours, because everything else follows from them. A full-time employee works roughly 40 hours a week, minus vacation, sick days and holidays. Call it about 1,850 working hours a year. There are 8,760 hours in a year. A single hire covers a little over a fifth of the time your building is operating.

The other four fifths are not idle. Overnight is when a failing network switch takes the nurse call system with it. Weekend is when a ransomware operator prefers to start, because they know who is not watching. Neither of those waits for Monday.

The second difference is range. One person is one skill set. Senior living technology asks for several at once: the network in the building, the cybersecurity posture around it, the compliance documentation that proves the posture exists, the life-safety systems that have to keep running, and vendor management across the record system, the phone system and the nurse call vendor. A capable generalist covers some of that well and the rest by learning on the job while it is live.

The third is continuity, and it is the one operators underestimate. When one person holds the knowledge, the knowledge has the same availability that person does.

The Three Gaps a Single Hire Cannot Close

Coverage outside working hours

This is arithmetic, not a criticism of any employee. Nobody is on call every night indefinitely without either burning out or being paid to be a team. Communities that hire one person and expect around the clock response usually get around the clock response for a while, then get a resignation.

Depth in more than one specialty

Cybersecurity and compliance are their own disciplines now, not a subset of general IT. The documentation a cyber insurance carrier wants at renewal, and the risk analysis regulators ask for after an incident, are specific work products with specific requirements. A generalist can produce them. Whether they produce them to the standard that survives scrutiny is a different question, and the answer usually arrives at the worst time.

What happens when they leave

Turnover in technology roles is normal and not a sign of anything wrong. The problem is what leaves with the person. If the only record of how your buildings are wired, which vendor holds which contract, and what the workaround is for the medication cart lives in one employee's memory, then a two week notice period is also the window you have to reconstruct it. This is worth planning for before it happens, not after.

Note that the labor market is not making this easier. The Bureau of Labor Statistics projects employment of computer support specialists to decline 3 percent from 2025 to 2035, with median annual wages of $61,860 for computer user support specialists and $76,220 for computer network support specialists as of May 2025. A shrinking pool of candidates is not a reason to avoid hiring, but it does mean a vacancy may stay open longer than your plan assumes.

When Hiring In-House Is the Right Call

It genuinely is, in three situations, and it is worth being straight about them.

When there is enough work for a team rather than a person. At sufficient scale the arithmetic reverses. Enough units and enough buildings will support several people with different specialties, and at that point an internal department gives you responsiveness and control that is hard to buy. The threshold is not a fixed number, but it is well above a single community.

When the work is genuinely hands-on and continuous. A community in the middle of a multi-year renovation, or one standing up a new building, has a volume of physical work that benefits from someone on site most days. That is a real job with real hours behind it.

When a specialized system needs an owner. If you run an application that is unusual, heavily customized, or central to how your organization operates, an employee who works with it daily will always know it better than an outside provider. That knowledge is worth employing.

What does not justify a hire on its own is frustration with a current provider. If the problem is that your provider is slow, does not understand senior living, or cannot produce documentation when you ask for it, hiring someone is an expensive way to solve a problem that changing providers also solves. It is worth separating those two before you write a job description. Our guide on what to look for in a senior living IT provider covers what to expect before you conclude the model is the problem.

The Hybrid Most Portfolio Operators Land On

The framing of this decision as either-or is mostly an artifact of how it gets discussed in a budget meeting. In practice a lot of operators run both, and the split is not arbitrary.

The internal person takes what benefits from being present and known: setting up new hires, handling devices, walking a caregiver through something at the nurse station, being the person staff can find. That work is easier and better when someone is in the building and has a relationship with the team.

The provider takes what does not fit inside one person or one schedule: monitoring after hours, cybersecurity, compliance documentation, vendor management, and coverage during vacations and vacancies. That work is easier and better when it is a team with more than one specialty and a rota.

The reason this arrangement holds up is that each side is doing what its structure suits. It is also more resilient than either alone, because neither the internal person nor the provider is a single point of failure for everything.

What Changes When You Operate More Than One Community

If you run several buildings, the harder problem is not support. It is standardization.

One IT employee splitting time across multiple sites will work on whichever building is loudest that week. That is a rational response to the workload and it is also how communities drift apart. One site gets a new access point layout and another does not. One gets multi-factor authentication turned on for staff email and another has it on the list. Nobody decided this. It accumulated.

The bill for that arrives at a specific moment: a survey, an insurance renewal, a refinancing, or a sale, when somebody asks you to show that every community is protected to the same standard. The honest answer at that point is often that you do not know, because nobody has compared them. Running the same standard across every building is a portfolio-level job, and it is one of the clearest arguments for a model that is not one person's calendar. There is more on the operational side of this in our business continuity guide for senior living.

How to Decide

Four questions, in this order. They are quicker to answer than a spreadsheet and they get to the real constraint faster.

1. What has to keep working overnight? List the systems where a failure at 2 a.m. affects a resident rather than an office. If that list is not empty, you need coverage that is not one person's working day.
2. Who produces your compliance documentation, and has anyone read it? If the answer is that it exists somewhere and nobody has looked recently, that is a specialty gap, not a staffing gap.
3. What happens the week your IT person is on vacation? If the honest answer is that things wait, decide now whether that is acceptable for every system on your list from question one.
4. Would you get the same answer at every building you operate? If not, standardization is your actual project, and it should shape the model you choose rather than being something you hope to get to later.

If those four point toward a provider, the follow-on question is which one, and specialization matters more in this vertical than in most. An IT company that has never supported a nurse call system or sat through a state survey will learn on your building. Our post on managed IT versus break-fix support covers the other half of that decision.

Frequently Asked Questions

Should a senior living community hire an IT person or use a managed provider?

For most communities under roughly 150 units, a managed provider is the better fit, because the decision is about coverage rather than cost. One employee covers a working day. Nurse call systems, door controllers, medication carts and the network they depend on run continuously. A single hire also carries single-person risk: when they take vacation or resign, coverage goes to zero and undocumented knowledge leaves with them. Hiring in-house becomes reasonable at larger scale, when there is enough work to justify a team rather than one person.

What does an in-house IT hire cost a senior living community?

The Bureau of Labor Statistics reports a median annual wage of $61,860 for computer user support specialists and $76,220 for computer network support specialists as of May 2025. Salary is not the full figure. Benefits, payroll taxes, tools, training, certifications and management time all sit on top of it. The full cost comparison, including what managed services typically run, is covered separately in our guide to what managed IT costs for a senior living community.

When does hiring in-house IT actually make sense?

Three situations justify it. First, scale: enough communities or units that the work supports a team with more than one skill set, not a single generalist. Second, a large amount of genuinely hands-on work, such as an ongoing construction or renovation program where someone needs to be physically present most days. Third, a specialized in-house application that no outside provider will ever know as well as an employee who works with it daily. Below that threshold, one hire usually produces one person's availability rather than a department.

Can a community use both an in-house person and a managed provider?

Yes, and this is what many portfolio operators settle on. The internal person handles what benefits from being in the building and knowing the staff: new hire setup, device handling, walking a caregiver through a problem, being the face of technology on site. The provider carries what does not fit in one person or one schedule: after-hours monitoring, cybersecurity, compliance documentation, vendor management and coverage when the internal person is away. The split works because each side is doing what it is structurally suited to.

What changes when you operate more than one community?

Standardization becomes the harder problem than support. One IT employee splitting time across several buildings tends to work on whichever site is loudest that week, so each community drifts toward its own way of doing things. Differences accumulate quietly and surface during a survey, an insurance renewal or a sale, when someone asks for evidence that every building is protected the same way and the honest answer is that it is not.