Your hotel's plumbing belongs to Engineering. Your servers belong to IT. Where do your smart TVs belong?
If your hotel installed its first TVs in the 1990s, they came with a coaxial cable and a rabbit-ear antenna. Installing them was physical work. Maintaining them meant occasional tuning, the odd power-supply replacement, and a screen swap every decade or so. The Engineering department was the right owner — these were audio-visual devices, physical infrastructure, the same category as plumbing and HVAC. The pattern held for thirty years and there was no reason to disrupt it.
Modern hotel TVs are not audio-visual devices. They are networked computers — they run operating systems, consume bandwidth, depend on firmware updates, store guest data, and integrate with property management systems. That is a different kind of object from the screen-and-tuner of the 1990s, and it quietly reopens a question most hotels settled three decades ago and have not looked at since. This guide works through it: what it costs a hotel while the question goes unanswered, and how the answer is put into practice once a hotel reaches it.
We see this pattern frequently across hotels we audit. IT managers who already know the property is buying the wrong TVs but lack the formal authority to redirect the decision. Engineering managers carrying responsibility for a system their department was never structurally designed to manage. Both sides are visibly relieved when someone says out loud that the structure is the problem, not the people inside it — and that most properties can put it right without alienating anyone.
Article 1 named five procurement traps and one shared defence: validate the critical capabilities in writing, with vendor accountability, before signing. But that defence requires someone in the building with the authority to refuse a wrong purchase. The question this article addresses is: who in your hotel has that authority? Until that question is answered, Article 1's five-trap discipline has no one in the building to execute it. The ownership question sits upstream of every trap.
Why has Engineering always owned hotel TVs?
Engineering has always owned hotel TVs for a reason that was entirely sound at the time. For three decades a hotel TV was physical audio-visual equipment — a screen and a tuner, maintained with hand tools — and physical building equipment is Engineering's job.
The work was straightforward and skilled: wall mounting, cable routing, power and coaxial connections, the occasional failed power supply or damaged screen, the odd re-tune. There was no software in the modern sense — no apps, no operating system, no network, no updates. It sat squarely in the same skill set that handles HVAC, electrical, mechanical and plumbing.
Legacy IPTV did not change the picture. Coaxial gave way to category 5 cable and tuners to set-top boxes, but the TV was still a passive endpoint; the set-top box did the computing. The ownership model stayed put, and there was no reason to disrupt it.
The Engineering teams who own this work today are not making a mistake. They are honouring a logic that was correct for the era in which it was set. The shift this article describes is not a critique of Engineering's stewardship — it is a recognition that the device underneath the bracket has changed category.
Does that logic still hold?
No. The device under the wall bracket has quietly changed category — the screen still looks like a television, but what sits behind it is a networked computer, and a computer needs the lifecycle discipline IT runs, not the physical-maintenance model Engineering was built for.
The legacy stack was four physical layers: TVs with tuners, channel subscriptions, coaxial infrastructure, and sometimes legacy IPTV with set-top boxes. The modern stack runs on a different substrate entirely: smart TVs running operating systems, streaming applications, LAN and WLAN networks, modern IPTV with casting, and hospitality-grade management platforms above all of it. Every layer has changed.
The most consequential change is the nature of IPTV itself. Modern IPTV is not audio-visual — it is a networked application. It depends on Wi-Fi and LAN infrastructure. In a well-designed hotel network it runs reliably without degrading guest Wi-Fi; in many properties the design has never been made, and guest experience and IPTV degrade each other by default. It integrates with property management systems for room state, language preference, guest name, and folio posting. It manages guest application sessions and authentication. It generates security and privacy obligations under GDPR, PDPA, and equivalent local regimes. These are IT concerns, not Engineering concerns.
Smart TVs themselves are assets that need lifecycle management, not installations that need maintenance — firmware updates, OS compatibility checks, application support tracking, warranty management, security patching. Engineering departments were never structurally set up to perform that kind of asset management. IT departments already do it for every other computer in the hotel: laptops, servers, point-of-sale terminals, PMS workstations, kiosks, mobile devices. Extending it to TVs is not a new capability requirement; it is removing an anomaly.
The reputational risk arrives when that discipline is missing. A smart TV running 18-month-old firmware starts refusing Netflix logins, and the guest complains. Five rooms fail in one week because the OS stopped supporting a critical app, and the hotel cannot sell those rooms with confidence until the failures are fixed. Engineering teams, who are not running patch schedules because patch schedules were never their job, hear about the failures the way everyone else does — from guest feedback.
IT should be responsible for TV lifespan and functionality because TVs are computers and IT is what keeps computers useful inside the hotel. Most properties already split this way for laptops and servers — the TV is the last device left outside that split.
What happens when Engineering owns TV decisions?
When Engineering owns hotel TV decisions, five predictable failures follow: IT cannot support guests because no accurate inventory exists, failing TVs are replaced with whatever is on promotion, consumer TVs get bought by mistake, firmware and OS updates are skipped, and unmanaged smart TVs create data-privacy breaches.
These are not rare edge cases. They are the predictable consequences of treating a networked computer as an audio-visual device, and they show up consistently across properties and years.
1. IT cannot support guest requests because no inventory exists
IT managers at hotels we work with frequently cannot produce an accurate inventory of installed TVs — brand, model, OS version, RAM, firmware level, warranty status. The inventory either does not exist or sits in an Engineering maintenance log that lists make and model but nothing about software. When a guest calls reception with a TV problem, the hotel cannot give specific technical support. IT absorbs the blame for a system it did not procure and does not track. The first symptom of misallocated ownership is usually this support gap, and it is the symptom IT teams recognise instantly when they read it.
2. Failing TVs get replaced with whatever is on promotion
Engineering replaces a failed TV with the model available at the best price that week. Over 24 months, a 200-room property ends up with five or six different brand-model-OS combinations. Fleet management becomes effectively impossible — there is no single hospitality platform that supports every consumer OS, and the cost of running parallel platforms exceeds the savings on the original purchases. Guest experience becomes uneven across rooms. Casting works in room 412 but not in 415. The Netflix app is current in some rooms and three versions out of date in others. Each individual replacement decision was reasonable in isolation; the aggregate is a mess that cannot be untangled without a full refresh.
3. Consumer TVs get bought because they look identical to hospitality TVs
One property we recently approached was proud of a 100-unit LG TV purchase. They had negotiated what felt like a strong deal. Only when they contacted Nettify about deploying IPTV and casting did they discover the TVs were consumer-grade LG models running consumer webOS. Not one of their fleet of over 200 TVs could run our software without an added set-top box. A six-figure capex now required a five-figure follow-on spend to become usable for the intended purpose, plus the operational overhead of two devices per room where one would have sufficed. If IT had been involved at the specification stage, this would have been prevented.
4. Firmware and OS updates get skipped entirely
Engineering departments are not set up to run patch schedules. A smart TV deployed three years ago and never updated will have known security vulnerabilities, broken app compatibility, and degraded performance. The guest-facing consequence is a TV that no longer streams Netflix, no longer accepts casting from a phone, or no longer responds to the remote consistently. The revenue-facing consequence is that the hotel cannot sell those rooms with confidence until the failures are corrected, and the corrections are slow because nobody owns the patch schedule. Firmware update discipline is standard for every other computing asset in the property. The TV is the last device for which it is missing.
5. Smart TVs without hospitality management create data privacy breaches
A smart TV without a hospitality-grade management platform is a privacy breach waiting to happen. Guest Netflix credentials remain logged in after checkout. Guests can accidentally cast to any TV in any room on the same network. Personal photos and documents stay in the TV's app caches. These are not hypothetical concerns — they are direct consequences of deploying smart TVs without IT's awareness that they are computers with session-management requirements. The exposure under GDPR, PDPA, and equivalent local privacy regimes is real, and it is precisely the kind of exposure IT departments are already trained to manage everywhere else in the hotel.
The common thread
All five failures share a root cause: a smart TV is a computer attached to a screen, and Engineering's ownership model was never built to maintain computers. The pattern is structural, and recognising it is the first step out of it.
What do hotel chains do that independents don't?
Hotel chains tend to handle TV ownership better because brand-standards frameworks formalised the question two decades ago — not because chain IT teams are more skilled. Independents and smaller chains get no such framework for free; they have to build the same discipline themselves.
The picture is more variegated than "chains have solved this." Some chains have a mature framework that holds up consistently across properties. Others still operate in the audio-visual-era ownership model and produce the same failures as independents. Even within a single chain, the framework can vary by region, by property tier, by whether the property is brand-managed or franchised, and by how active central IT is in enforcing brand standards. The chain advantage is real but not absolute.
In a chain property that does have the framework in place, central IT publishes a TV specification: approved models, minimum RAM, required operating systems, hospitality-grade only. The property's procurement team buys from the approved list. Property IT reviews and signs off. Engineering confirms installation feasibility (physical dimensions, electrical load, bracket compatibility) and handles the physical work once the order is placed. The TV becomes part of the brand audit. Compliance is verified annually. Deviations require approval. The framework is mature and largely invisible to the staff who operate inside it.
Many independents, particularly those that explicitly chose independence to preserve their identity, have to build the equivalent locally. The middle path most independents are currently on is letting Engineering procure and IT firefight, which is the path that produces the most expensive long-term cost.
The independent-scale version of what disciplined chains do is not complicated. The core mechanism is: IT sets specifications, Engineering confirms installation feasibility, GM or ownership signs the vendor contract (with regional pattern variations covered in the next section). Budget owner is IT. Asset register owner is IT. Project management for any TV refresh sits with IT. Installation still happens in Engineering's hands. This works at any property size, from a 30-room boutique to a 400-room resort.
Nettify has seen this framework adopted at independent properties of varying sizes, including some that built it after experiencing one of the five failure modes firsthand. The first refresh after the framework is in place is materially cleaner than every prior refresh, and the GM is usually the one who notices, because the operational complaints stop arriving on the GM's desk.
What actually moves from Engineering to IT?
Four things move from Engineering to IT: the authority to specify what TVs to buy, the capex budget line, the asset register, and project management for refresh cycles. Physical installation explicitly stays with Engineering, and one element — contract-signing authority — varies by region.
The handoff is concrete. Here is what each part involves.
Budget line item
The TV capex line should move from Engineering's budget to IT's budget. This is not bureaucratic theatre. It signals to the rest of the organisation that ownership authority sits with IT and that the hotel recognises the rising importance of IT in operations and guest experience. The signal matters internally — it changes whose voice is loudest in a year-end refresh discussion.
Asset register
TV inventory should live in IT's asset management system, not Engineering's maintenance register. The IT asset register should capture brand, model, operating system, RAM, firmware version, warranty status, installation date, last patch date, and hospitality management platform binding. This enables proactive firmware updates, planned refresh cycles that begin before failures occur, and accurate technical support when guests report problems. Many independent hotels currently track TVs only in Engineering maintenance logs that capture make and model but nothing about software state — the data structure cannot answer the questions IT needs to answer.
Project management
No smart TV should be deployed on its own, without a hospitality-grade management platform already specified. Every TV refresh becomes an IT project, with Engineering as the installation partner rather than the project owner. The order of operations changes: software stack chosen first, hardware specified against the software's requirements, installation scheduled once the procurement is confirmed. The legacy order (hardware bought, software fitted on top, gaps filled with extra hardware) is the order that produces the failure modes in the previous section. (Vendor selection within an IT-led procurement is its own discipline, covered in Article 7: One vendor for hotel Wi-Fi, IPTV, casting, signage, presentations, and the digital concierge — or six? — coming soon.)
Contract-signing authority varies by region
The signing authority for technology contracts is one of the few elements of this framework where there is no single correct pattern. In most European hotels, the IT or Engineering department has both budget authority and full contract-signing authority for technology purchases — the department head signs the vendor contract directly. In most Asian hotels, the IT or Engineering department holds the budget and proposes the spend, but final sign-off rests with the GM or ownership. Neither pattern is universal: some European hotels follow the Asian pattern, and vice versa, and ownership-led signing is common at independent properties everywhere.
The signature is the last step in the procurement process, not the decision moment. The decision moment is the specification, which is upstream of any signature. The point is not which signing pattern your hotel follows — it is that whichever pattern you follow, the decision should originate from IT specifications, with Engineering confirming installation feasibility, regardless of who holds the pen. That is where the org shift this article describes actually lives.
Coordination between IT and Engineering stays essential
Even after the decision moves to IT, coordination between the two departments is required, and the work goes better when both share the same brief from the start. The TV must fit the physical and electrical limitations of the guest rooms. Mounting brackets must be ordered to the right specification. Installation schedules must align with renovation timelines and existing occupancy. The change is in who specifies — not in whether the two departments work together. The best properties we audit treat the IT-Engineering relationship on TVs the same way they treat the IT-Maintenance relationship on every other networked device in the hotel: clear remit, shared brief, mutual respect.
| What moves to IT | What stays with Engineering |
|---|---|
| Authority to specify what TVs to buy | Physical installation (mounting, cabling, power) |
| Capex budget line for TV refreshes | Installation feasibility sign-off |
| Asset register — brand, model, OS, RAM, firmware, warranty, last patch, platform binding | Mounting bracket selection and electrical compliance |
| Project management for TV refresh cycles | Cabinet ventilation and physical environmental fit |
| Firmware and OS lifecycle management | Ongoing physical maintenance |
| Hospitality management platform ownership | Screen, power-supply, port, and connector repair |
| Integration with PMS and guest data flows | Schedule coordination with renovation and occupancy |
What does Engineering continue to own?
Engineering continues to own all of the physical work — installation, installation-feasibility sign-off, and ongoing hardware maintenance. The transition moves decision authority to IT; it does not withdraw Engineering's role, and the hotel still needs that physical work done well.
This section exists for two reasons. First, every property we have helped through this transition has produced an Engineering manager who wanted the boundary spelled out in writing, and that is a reasonable request. Second, the practical work itself remains substantial, and treating Engineering's continuing role as residual would be both unfair and operationally inaccurate.
Physical installation work
Wall mounting, cable routing through furniture cutouts, power and HDMI connections, electrical compliance, mounting bracket selection, cabinet ventilation, and integration with built-in millwork. These are skilled installation tasks. They require trade competencies that IT departments do not have and should not be expected to develop. Engineering continues to do the installation work — and Engineering's installation discipline is, in our experience, frequently the difference between a TV refresh that finishes on schedule and one that runs three months late.
Installation feasibility sign-off
When IT specifies a TV model, Engineering confirms it fits the physical and electrical limitations of the guest rooms. TVs with unusual depth, weight, or power requirements need validation before the purchase order is placed. This is not optional and not nominal — it is a required coordination step, and the cost of getting it wrong is a delivery that cannot be installed without rework, or warehouse-rotting hardware that was specified for the wrong space.
Ongoing physical maintenance
Power supply failures, port failures, mounting issues, screen damage from guest misuse, cabinet ventilation problems. When a TV fails physically, Engineering handles the repair or replacement decision. IT handles the logical failures (firmware, OS, app compatibility, network, PMS integration). The split is based on what broke, not on who owns the asset register. The two teams work the same call from different angles depending on whether the diagnosis is mechanical or computational.
What if you can't move the TV budget yet?
If your hotel cannot move the TV budget this cycle, the minimum is far simpler: require IT sign-off on every TV purchase before the order is signed.
Moving the TV budget from Engineering to IT is the right structural answer. But many hotels face real organisational friction in making the budget move — budget codes are slow to restructure, asset management systems were built when TVs were AV devices, and the political cost of reassigning a department's line item is non-trivial. If the full transition is not achievable in the current cycle, the floor is much lower than the ceiling.
IT sign-off is the bare minimum: a governance change that costs nothing, moves no budget lines, and reassigns no headcount — and still prevents most of the failure modes described earlier in this article.
What IT sign-off actually prevents
Consumer-grade purchases disguised as hospitality. Wrong OS families for the planned tech stack. Insufficient RAM configurations that will become unusable inside the warranty period. Missing certifications on set-top boxes. Incompatible brand standards for chain-affiliated properties. Casting capability omitted from the specification entirely. These are all preventable at the specification stage if someone with technical judgment reviews the spec before the purchase order is signed.
The sign-off process in practice
A one-page IT review of any proposed TV or STB purchase. IT confirms: the model runs the correct OS family for the planned software stack; RAM meets the minimum threshold; certifications are verified; hospitality features are present; software compatibility is validated against the existing or planned IPTV and casting platforms. Takes under an hour. Prevents six-figure mistakes.
This is the part of every hotel's procurement process where we recommend the most discipline. Across hundreds of properties globally, the failures Nettify traces back to a missing sign-off step are the most preventable in the entire procurement lifecycle. A one-hour review by someone whose primary skill is reading specifications saves the property from a five-figure correction six months later. The arithmetic is hard to argue with.
If your property cannot move the budget yet, start with the sign-off. The full transition can follow once the sign-off discipline has demonstrated its value, which it usually does within the first procurement cycle in which it prevents a wrong purchase.
Continue your journey
The ownership question is the upstream decision. The downstream decisions (which TVs to buy, how consumer and hospitality models actually differ, which IPTV architecture to run, which vendors to consolidate around) are covered in the next articles in this series. Article 1's five-trap framework is developed across Articles 5, 6, 7, and 8, with each trap in its natural home.
Continue to Article 3: Chromecast alternatives for hotels →
← Back to the full series: Hotel In-Room Entertainment in 2026
Frequently asked questions
Should IT or Engineering own hotel TVs?
IT should own the procurement, specification, and asset management decisions for hotel TVs. Engineering should continue to handle physical installation, installation feasibility sign-off, and hardware-level maintenance. The shift reflects that modern hotel TVs are networked computers — they run operating systems, consume bandwidth, integrate with property management systems, and require the same lifecycle management as every other computer in the hotel. Engineering's role in installation does not change. The decision authority does.
What is the difference between hotel IT and hotel Engineering responsibilities?
Hotel Engineering handles physical infrastructure — HVAC, electrical, mechanical, plumbing, mounting, cabling, and building systems. Sometimes called Maintenance, Facilities Engineering, or Building Services depending on the property and region. The function is the same. Hotel IT handles networked and computing systems — networks, servers, property management systems, point-of-sale, and increasingly the smart TVs and in-room technology that used to sit outside IT's remit. The line was clearer when TVs were analogue devices. In 2026, smart TVs cross that line decisively and belong in IT's responsibility, while the physical installation work continues to require Engineering's trade skills.
How do large hotel chains handle TV ownership?
Large hotel chains typically solve this through brand standards. Central IT sets TV specifications — approved models, minimum RAM, required operating systems, hospitality-grade only. Property IT signs off on local purchases. Engineering confirms installation feasibility and handles the physical work. The TV becomes part of audit compliance, and deviations require formal approval. Independents and smaller chains do not get this framework for free and must build the equivalent locally — the core mechanism (IT specifies, Engineering validates feasibility, GM or ownership signs the contract) works at any property size from 30 to 400 rooms.
Why do hotels buy the wrong TVs?
The most common reason is that TV procurement sits in the Engineering or ownership budget without IT input at the specification stage. Engineering teams optimise for screen size, mounting compatibility, and installation feasibility. Procurement teams optimise for unit price. Neither specifies the operating system, RAM, certifications, or software compatibility requirements that determine whether the TV can actually run the hotel's planned IPTV and casting software. The result is TVs that look fine on the showroom floor but cannot run the software the hotel actually needs. The mistake is preventable at the specification stage with a one-hour IT review before the purchase order is signed.
Who signs off on hotel technology purchases?
Contract-signing authority varies by region. In most European hotels, the IT or Engineering department has both budget authority and full contract-signing authority for technology purchases. In most Asian hotels, the IT or Engineering department holds the budget and proposes the spend, but final sign-off rests with the GM or ownership. Neither pattern is universal — some European hotels follow the Asian pattern, and vice versa, and ownership-led signing is common at independent properties everywhere. The signing pattern matters less than who specifies — the decision should originate from IT specifications with Engineering confirming installation feasibility, regardless of who holds the pen.
How do hotels manage smart TV inventory?
Best practice is to maintain an IT asset register that captures brand, model, OS, firmware version, warranty status, and hospitality platform binding for each unit (full field list developed in the body of this article). This enables proactive firmware and OS updates, refresh cycles planned before failures occur, and accurate technical support when guests report issues. Many independent hotels currently track TVs only in Engineering maintenance logs that capture make and model but nothing about software state — the data structure cannot answer the questions IT needs to answer when a problem arises.
Does moving TVs to IT require a formal budget restructure?
Not necessarily. The ideal is to move the TV capex line from Engineering's budget to IT's budget, signalling organisational recognition that modern TVs are IT assets. But many hotels face real friction with budget-code restructures, particularly in asset-management systems that were built when TVs were AV devices. If the full budget move is not feasible in the current cycle, the minimum viable change is requiring IT sign-off on every TV procurement decision before the purchase order is issued. This prevents the most expensive mistakes — wrong OS, consumer TVs bought as hospitality, non-certified set-top boxes, incompatible software stacks — without requiring organisational restructure. The full transition can follow once the sign-off discipline has demonstrated its value.
Do hotel IT departments have the capacity to manage TVs?
Yes, because TVs are computers and IT already manages every other computer in the hotel. Adding TVs to the existing asset management and patch discipline is typically less ongoing work than the alternative — which is firefighting failures that could have been prevented with proactive lifecycle management. The ongoing time commitment is small compared to the avoided failure cost. In properties that have made the shift, IT managers consistently report that the new workload is offset by the reduction in guest complaints, support escalations, and procurement corrections.