Insurance, Safety, and Liability: What to Require From an Onsite IT Support Company

Quick answer: Before an onsite IT support company sends technicians to your sites, collect certificates of insurance for general liability, professional liability (E&O), cyber, workers’ compensation and commercial auto, and write ladder, electrical and lifting rules into the scope. Falls, slips and trips killed 844 US workers in 2024 (BLS, 2026).

When a technician is on a ladder mounting an access point above a reception desk, or pulling a server from a rack in a crowded closet, the risk is not only technical. People can get hurt. Property can be damaged. Data can be exposed. When that happens, the question becomes whose responsibility it is and whose insurance pays.

This guide explains what insurance, safety standards and contract terms to require when you buy onsite IT support services, how to verify them, and how to run the paperwork across dozens or hundreds of locations without slowing down dispatch. It is a practical buyer’s guide written from the IT operations side, not legal or insurance advice. Involve your risk, legal or insurance advisors for specific limits and wording.

What risks does onsite IT work create?

Most onsite IT tickets are routine: swap a laptop, re-patch a switch, replace a failed printer, check a circuit. The risks come from the setting, not the task. Technicians work at height, in tight network closets, around live equipment, inside other people’s buildings and near sensitive data. Each risk maps to a type of coverage and a control you can put in writing.

The data row deserves more weight than buyers often give it. The average US data breach cost reached $10.22 million, and supply chain compromises were the second most common initial access vector at nearly 15% of breaches (IBM via CyberScoop, 2025). Any vendor that touches your devices is part of that supply chain.

What insurance should an onsite IT support company carry?

A credible onsite IT support company should be able to show the following coverage types and explain how each applies to work at your sites.

Limits should reflect your risk. A provider supporting retail stores faces different exposure than one working in hospital data centers or bank branches. Your risk or insurance advisor can recommend minimums, and your largest landlords will often have their own. Set one standard for the program and note any site that needs more.

How are independent technicians covered?

Many onsite IT support companies, including networks that dispatch an IT field technician to hundreds of cities, work with independent technicians. That model is common and workable. What matters is that coverage is clear before something goes wrong. Ask:

• Does the provider’s policy cover technicians working on its behalf?
• Are technicians required to carry their own coverage, and does the provider verify it at onboarding and at renewal?
• Which policy responds first if a technician damages property or is injured at your site?
• Does the provider’s E&O and cyber coverage extend to work performed by subcontracted technicians?
• Who handles the claim and communicates with you and your landlord?

Clear, written answers matter more than which model is used. Pair this with the provider’s screening process; see how onsite IT support companies vet technicians and our explainer on what an IT field technician does.

How do you verify an onsite IT support company’s insurance?

Verification is where most programs break down. A COI on file from three years ago does not protect anyone. Use this sequence:

1. Request certificates of insurance (COIs) before work begins, listing coverage types, limits and policy periods.
2. Ask to be named as an additional insured where appropriate, especially on general liability, and confirm whether the certificate reflects an actual endorsement.
3. Check expiration dates and set a reminder 30 days before each one to request the renewed certificate.
4. Confirm each landlord’s requirements. Many commercial leases require vendors working in the building to provide COIs naming the landlord or property manager. Building management may refuse entry without them.
5. Keep COIs on file by vendor and by site, so a branch manager or dispatcher can confirm coverage in minutes.
6. Re-verify after any change: new provider entity, new state, new type of work (for example, moving from desk-side support into cabling or ceiling work).

A provider that takes weeks to produce a COI is sending a signal. A reliable one can issue standard certificates quickly and turn around landlord-specific certificates without holding up the ticket.

How do building COI requirements affect multi-location IT support?

For multi-location IT support, landlord paperwork is often the real bottleneck. A technician can be ten minutes away, but if the property manager needs a certificate with specific wording and has not received it, the technician waits in the lobby or gets turned away. That turns a one-hour fix into a two-day outage.

Practical ways to avoid this:

• Build a site record for every location with the property manager’s contact, COI wording requirements, loading dock rules, after-hours access rules and escort requirements.
• Send landlord-specific certificates when a site is onboarded, not when the first urgent ticket arrives.
• Track which buildings require advance notice for above-ceiling work, riser access or work in shared telecom rooms.
• Note any union or building-trade rules that limit what a vendor can do in that building.

Commercial real estate teams and property-heavy businesses run into this constantly; see how we approach real estate IT support across managed buildings.

What safety standards should onsite technicians follow?

Insurance covers what goes wrong. Safety standards prevent it. OSHA’s preliminary list for fiscal year 2026 again ranks fall protection as the most cited standard, with ladders at number five (OSHA, 2026). Those are construction standards, but access point mounts, ceiling cabling and rack work raise the same hazards. Write these expectations into your scope of work.

Ladders and heights

• Use the right ladder for the height; never stand on chairs, desks or file cabinets.
• Follow building rules for ceiling access and replace tiles exactly as found.
• Use two people for heavy mounted equipment such as displays and large access points.
• Stop and escalate if work requires a lift or scaffold the technician is not trained for.

Electrical

• Technicians work on low-voltage IT equipment only.
• No work on building electrical circuits unless licensed and authorized.
• Report hazards such as overloaded power strips or daisy-chained UPS units rather than improvising fixes.

Lifting and equipment handling

• Use proper lifting technique for servers, UPS batteries and heavy devices.
• Use rack lifts or a second person for heavy rack-mounted equipment.
• Secure equipment during transport and keep sensitive devices in the technician’s control.

Restricted areas

• Respect restricted zones (labs, clean rooms, clinical spaces, cash handling areas, vaults).
• Follow escort and sign-in requirements.
• Wear required PPE in industrial or healthcare environments.

Worksite conduct

• Leave the work area clean and safe; do not leave cables across walkways.
• Close and lock network closets and IDFs when work is finished.
• Report hazards found onsite to the site contact, with a photo.

Which safety rules apply to which types of onsite work?

Not every visit carries the same risk. Matching the rules to the task keeps the scope realistic and keeps technicians from being buried in boilerplate.

How should drives and devices be handled to limit data liability?

Physical safety gets the attention, but the costliest onsite incidents are often quiet: a failed drive left in a closet, a laptop shipped without tracking, a replaced firewall that still holds configs and credentials. Require:

• A documented chain of custody for any device leaving a site, with serial numbers, who took it, when and where it went.
• Clear rules on whether drives are wiped onsite, destroyed onsite or returned to you.
• Photos or signed confirmation at handoff points.
• Reporting to your security team within an agreed time if a device goes missing.

For the detail, see our guide to drive sanitization during onsite IT support.

What should happen when something goes wrong onsite?

Define an incident process before you need it, and make sure every technician and branch manager knows it.

1. Immediate safety first. Injuries are addressed and emergency services called if needed.
2. Notify the site contact and the provider’s coordinator right away.
3. Document the incident with photos, time, people involved and a short description.
4. Report to your IT owner and, if needed, your risk or legal team.
5. Provider submits a written incident report within an agreed timeframe.
6. Insurance notification follows each party’s policy requirements, which often include prompt notice.
7. Review and fix the cause: update the site record, runbook or safety rule so it does not happen again.

For data-related incidents, follow your security incident process and the breach notification terms in your contract. See outsourced IT support contract clauses.

How should the contract address liability?

Insurance requirements only work if the contract ties them together. The terms usually sit in the MSA, with site-specific details in each SOW; see SOW vs MSA for IT field support services. Make sure the agreement covers:

• Indemnification for injuries and damage caused by the provider’s work.
• Liability caps with appropriate carve-outs (for example, data breaches or gross negligence).
• Insurance requirements with minimum limits by coverage type.
• An obligation to maintain coverage for the contract term and notify you of cancellation or material change.
• Flow-down of insurance and safety requirements to subcontracted technicians.
• Incident reporting timelines and who owns communication with landlords.
• Compliance with your site rules, background check requirements and confidentiality terms.

Have counsel review these terms. They are the backbone of the relationship if something serious happens.

What do regulated industries ask for beyond the basics?

Expectations rise with the sensitivity of the site.

• Banks and credit unions often require background checks, escorts in secure areas and documented vendor risk reviews; see IT services for banks.
• Law firms focus on confidentiality, device custody and minimal disruption during client hours.
• Healthcare sites add PPE, infection control and clinical-area rules.
• Retail and branch networks care most about after-hours access, cash-handling areas and keeping work out of customer paths.

Capture these in the site record so the technician arrives knowing the rules rather than learning them at the front desk.

What mistakes do buyers make with vendor insurance and safety?

• Collecting COIs once and never again. Policies lapse and renew; track dates.
• Assuming the provider’s coverage extends to every technician. Ask how subcontractors are covered.
• Ignoring the landlord. The building’s requirements, not yours, decide whether the technician gets in.
• Writing safety rules no one reads. Keep them short and tied to the type of work.
• Treating data handling as an IT detail. It is often the largest financial exposure in an onsite visit.
• No incident drill. Branch managers should know whom to call before the first incident.

The bottom line

Onsite IT work carries physical, professional and data risk. Require the right insurance from your onsite IT support company, verify it with current COIs, write safety standards into the scope, and define an incident process. These steps are easy to set up and invaluable on the rare day you need them. To see how dispatch and site records fit together, read how Techmate dispatch works.

Need COIs for your building management or a walkthrough of Techmate’s safety standards? Contact our team.

This article is general information and not legal or insurance advice.

Frequently Asked Questions

What insurance should an IT support vendor have?

Commonly commercial general liability, professional liability (errors and omissions), cyber liability, workers’ compensation where required, commercial auto where vehicles are used for the work, and often umbrella or excess coverage. Your risk advisor and your landlords’ lease requirements should set the minimum limits for your program.

What is a certificate of insurance?

A certificate of insurance (COI) is a document issued through the vendor’s insurer or broker that summarizes coverage types, limits and policy periods. Buyers and landlords use it to verify insurance before work begins. It summarizes coverage but does not change the policy, so confirm any additional insured status is backed by an endorsement.

Why does my landlord need the IT vendor’s insurance certificate?

Many commercial leases require vendors working in the building to carry insurance and name the landlord or property manager as additional insured. Building management may deny entry without a compliant certificate, which can delay urgent repairs. Collect each building’s requirements when you onboard the site, not during an outage.

Can IT technicians work on electrical circuits?

IT technicians typically work only on low-voltage IT equipment such as network devices, cabling, computers and AV gear. Work on building electrical circuits, panels or new outlets generally requires a licensed electrician. Technicians should report power hazards to the site contact instead of improvising fixes.

What should happen if an IT technician damages property?

Make the area safe, notify the site contact and the provider, document the damage with photos, and report it internally. The provider should submit a written incident report within the agreed timeframe. Insurance notice then follows each party’s policy requirements, and the root cause should be fixed in the site record or runbook.

Are independent IT technicians insured?

It depends on the provider. Some cover technicians working on their behalf under their own policies; others require technicians to carry their own coverage and verify it. Ask which policy responds first, how coverage is verified at onboarding and renewal, and whether E&O and cyber coverage extend to subcontracted work.

Should an onsite IT support company carry cyber liability insurance?

Many buyers now require it. Technicians handle laptops, drives, firewalls and other devices that hold sensitive data, and supply chain compromises are a common breach path. Cyber coverage, combined with documented chain of custody and drive handling procedures, limits your exposure if a device is lost or mishandled.

Want a second set of eyes on your vendor insurance, site records and dispatch process? Book a free 30-minute IT support audit and we will walk through where your multi-site program is exposed.