IT for condo associations in Honolulu is usually the line item nobody on the board wants to own. There is a computer in the building office, a camera system somebody put in years ago, a door system with its own vendor and its own invoice, a resident network half the owners have an opinion about, and a management company in the middle of all of it. AOAO IT support in Hawaii is a real category of work, and it is not the same job as supporting a thirty person company. Here is what a board should expect from whoever is doing it.
Why a building office is different
A company hires people, keeps them for years, and gives each one a computer. A building does almost none of that, and every difference shows up as an IT problem.
The site manager changes. Sometimes a promotion, sometimes a resignation on a Friday. Either way the person who knew the passwords is gone, and the association still needs the vendor invoices, the minutes and the resident contact list on Monday. The fix is structural: accounts belong to the role and not the person, files live in association storage rather than on the office desktop, and passwords live in a shared vault the board can reach. Then a handover is disabling one login and issuing another.
The office PC is shared. One machine, several people, often one login everybody uses. That means no way to tell who did what, and no way to remove one person's access without changing everyone's. Separate logins on the same machine cost nothing and take an afternoon.
Board members serve from home, on their own laptops, using whatever email address they already had. That is understandable and it creates a records problem, which is a big enough subject that we wrote it up separately: board email that holds up.
Residents are on the network. Lobby and amenity wireless is a service to owners, not a branch office. It should sit on its own network with its own password, unable to see the office computer, the camera recorder or the door controller. That separation is a setting on the building's router and access points, and it is the difference between a guest device being a nuisance and a guest device being a way in.
The building systems have their own vendors. Access control, cameras and the intercom are usually sold, installed and serviced by companies that are not your IT provider. Those systems still sit on the building network, still need firmware updates, and still hold recordings somebody will ask for after an incident. Nobody coordinates that unless someone is given the job.
The management company is in the middle. It has its own systems and its own IT, and its staff work in your office. Workable, but only if it is written down: which accounts belong to the association, which belong to the management company, and what happens to each if that contract ends.
The test for all of it: if the site manager and the management company both changed next quarter, could the board still open the books, read the mail, pull last month's camera footage and open the front door? If the honest answer is not yet, that is the project, and it is not an expensive one.
What managed should mean for a building
The word gets used loosely. For an association it should mean these things happen whether or not anyone reports a problem.
- An inventory that includes the building systems. Every computer, the network gear, and the door, camera and intercom equipment, with the support contact for each, so the board is not discovering equipment during an outage.
- Patching on a schedule, applied on a cycle and reported, rather than left to whoever clicks the reminder.
- Backup with a tested restore. Not that the backup ran. That someone restored a file from it recently and wrote down the date.
- Account lifecycle. New staff get accounts on their first day, departing staff lose them the same day, and the list is reviewed on a set cadence.
- Multi factor authentication on email and remote access, including the board seats. Association email is where payment instructions travel, which is why it is worth attacking.
- A named response commitment. How fast someone answers, during which hours, on Hawaii time, and what happens to a request that arrives at 4:30pm.
- Documentation the board owns. Network diagram, account list, vendor list, and where the passwords are. Handed over on request, not held back as a bargaining chip.
The questions to ask a bidder
Take these to the walkthrough
- Who will hold the administrator account, and is the association named as the owner of it?
- Show me your last restore test, with the date.
- How do you handle a site manager departure, start to finish, and how long does it take?
- Is resident wireless separated from the office and the building systems, and how would you prove it?
- Who do you call for the door system and the cameras?
- What is your response time during our business day, measured, not promised?
- If we leave, what do you hand over and how long does that take?
- What is not included, in writing?
The last one matters more than boards expect. Most disputes with an IT provider are not about the work. They are about whether something was in scope, discovered after the invoice.
Storm season readiness
Hurricane season runs through November, and the failures are boringly consistent. It is rarely the equipment that goes first. It is the battery backup nobody tested, the generator that starts but does not carry the office circuit, and nobody knowing how to open the gate when the controller loses power.
The short list for a building: pull the plug on the battery backups and time how long the office and network gear stay alive, confirm what the door and gate systems do on a power loss and who holds the manual key, check that resident notification does not depend on the office computer, and keep a printed vendor contact list somewhere that is not the network. The longer version is our storm season checklist.
Why a monthly minimum beats calling when it breaks
A building office is small, so break-fix looks sensible. Pay when something is wrong, pay nothing when nothing is wrong. The problem is what falls into the gap.
Nobody calls an hourly provider to check that backups restore, to review who still has an account, or to notice the camera recorder stopped writing in March. Those tasks prevent the expensive events, and they are exactly the tasks nobody requests, because nothing looks broken. A monthly minimum is how a board buys the maintenance it would never think to order.
It also changes the incentive. Under hourly billing a recurring problem is revenue. Under a monthly agreement it is cost, so it gets fixed properly the first time.
Common questions
Who owns the association office computer, the board or the management company?
Whoever holds the administrator account owns it in practice. Name the association as the account owner, with the management company and the IT provider added as administrators. Then a change of either one is a permission change rather than a recovery project.
Should board members use their personal email for association business?
No. Give each seat an address the association owns, so correspondence stays with the building when the seat changes hands.
Does a small building office need a monthly IT agreement?
A monthly minimum buys the work that only happens if nobody has to ask for it: patching, backup checks, account reviews and offboarding. Break-fix pays for repairs after the damage instead.
Who handles the cameras, the door system and the intercom?
Usually a separate vendor with its own contract. The IT provider should still hold the inventory and know which network each system sits on, because they share the building network whether anyone planned it or not.
Want a walkthrough of your building?
We will inventory what the association owns, including the door, camera and network equipment, and tell you where the handover risk sits. The findings are yours to keep either way.
Book a building walkthroughEmail info@enlightentechhi.com, call 808-451-3630, or book a time that suits the board.
Practical guidance for boards, not legal advice. Your governing documents and your association attorney govern what the board is required to do.