Vendor Takeover Checklist

Prepare the building record before the vendor transition.

A practical checklist for property teams replacing, rebidding, or onboarding security, low-voltage, BMS / BAS / OT, AV, IT / Network, elevator, intercom, or sensor vendors.

Vendor Takeover

Do not replace a vendor before you know what the vendor is supporting.

A takeover, rebid, or new service contract is easier when the owner already knows the devices, closets, panels, risers, credentials, lifecycle risks, and open exceptions.

Readiness items

What to confirm before the next vendor inherits the building.

The goal is not perfect documentation. The goal is a baseline good enough to reduce unknowns before proposals, access, and takeover work begin.

Device and opening records

  • Current device counts
  • Controlled openings and readers
  • Camera locations and coverage context
  • Intercom, visitor, AV, sensor, and specialty devices

Head-end and topology context

  • MDF/IDF and rack directory
  • Panels, controllers, NVR/VMS, gateways
  • Riser and backbone relationships
  • Switch/PoE/network dependencies where known

Contract and risk review

  • Support scope vs. installed conditions
  • Abandoned or uncertain equipment
  • Lifecycle and unsupported-device flags
  • Open exceptions and owner action items