Property management security is also vendor accountability. Use one system for both.

1. The narrow frame of most property management security advice

Search "property management security" and the top results will cover the same checklist: door access systems, camera coverage in common areas, good lighting, visitor logs, package rooms, guard or monitoring contracts. All useful. All framed around keeping bad actors out.

The framing is incomplete because the property manager is not only defending against external threats. A property manager is running an operation with dozens of recurring vendor touchpoints every month, each one invoiced, each one mostly unverified. The cameras that watch for trespassers also watch the loading dock where the HVAC tech parks. The event log that flags after-hours pool access also logs every vehicle that pulls into the property. Both questions live in the same feed.

2. The vendor hours you pay for but never verify

A mid-size multifamily property typically has recurring weekly or monthly vendor visits from:

• Landscaping and grounds (weekly, billed by visit or hour)
• Pool service (weekly in season, billed by visit)
• Pest control (monthly, billed by visit)
• Janitorial for common areas (multiple times per week)
• HVAC preventative maintenance (quarterly, billed by hour)
• Turn contractors (painters, cleaners, flooring, billed by unit or hour)
• Package delivery and amenity vendors

On a single property these vendor lines add up to tens of thousands of dollars a year. The property manager signs off on invoices without any objective record of arrival time, departure time, or crew size. The vendor records are the only records. In a billing dispute the property manager has nothing to point at.

3. How one HDMI device covers both at once

Cyrano is a small edge AI device that plugs into the HDMI output of your existing DVR or NVR. One device handles up to 25 camera feeds. It processes them locally and writes every detection (person, vehicle, event type, zone, timestamp) to a searchable log. No camera replacement, no rewiring, no cloud video upload.

The same detection pipeline that flags trespassing in a stairwell also logs the landscaping truck at the service gate. The same zone definitions that trigger after-hours amenity alerts also track how long a janitorial crew spent in the clubhouse. You configure the alert rules separately (who gets paged, for what), but the underlying event log is one stream.

Natural language search over that log is the lever that turns passive footage into vendor evidence. You do not scrub DVR timelines. You ask a question.

4. The five queries that change vendor conversations

These are plain-English searches that a property manager can run against the event log. Each one maps to a line item on an invoice.

1. "Show all landscaping vehicle arrivals and departures last month."

   Returns the times the landscaping truck entered and left the property, every week. Cross-check against the invoiced hours.

2. "Show pool service visits in the last 30 days."

   If the service is contracted weekly and you only see three visits, the invoice is wrong.

3. "Show every vehicle at the loading dock last Tuesday between 1pm and 4pm."

   The HVAC tech billed three hours. The footage shows 42 minutes. That is a specific, documentable conversation.

4. "Show all package deliveries after 7pm in the last week."

   For on-site concierge contracts billed by coverage hours.

5. "Show crew sizes for the unit turn at building B last week."

   If the invoice says four painters and the detections show two, that is billable fraud you can now document.

These same queries work for incident reconstruction: "show everyone at the leasing office between 2am and 4am Saturday" returns the same shape of answer. The query language does not care whether you are auditing a landscaper or investigating a break-in.

5. What to set up on day one

Installation is under five minutes: HDMI in, power on, network in. The work that actually determines whether vendor audit is useful is zone configuration. Three zones cover most of the value:

• Service entry / loading dock. Every vendor truck passes through here. Tag it as a vendor arrival zone. Every detection in this zone is a potential timestamp on an invoice.
• Common area touchpoints. Clubhouse, pool deck, gym, mailroom. Janitorial and amenity vendors must be observable in at least one of these. If a janitorial visit is billed and no event fires in any of these zones during the billed window, the visit did not happen.
• Unit turn access (if applicable). Exterior entrances to vacant buildings during turns. Crew size and duration are the recurring billing disputes here.

The first month is calibration. Traffic patterns stabilize, false positives drop, and the vendor baseline emerges. After 30 days the log holds enough history to have its first useful invoice conversation.

6. What this does not replace

The event log proves presence and duration. It does not prove quality of work. A landscaping crew that spent 90 minutes on property may or may not have actually trimmed the hedges you were billed for. Quality inspection is still the on-site team's job.

It also does not replace guards for physical intervention. An AI device flags a forced entry attempt in real time and can route the alert to a monitoring center or police non-emergency line, but it does not put a body on the scene.

What it does, specifically, is convert the cameras you already pay for into a source of truth that covers both security incidents and operational spend, out of the same device and the same log.

7. FAQ

How accurate is the arrival and departure timestamp on a vendor vehicle?

Timestamps are tied to the DVR overlay and the device clock, both synced. In practice, arrival is logged within a few seconds of the vehicle entering a configured zone and departure when it leaves the last zone. Accurate enough for invoice reconciliation to the minute.

Can the system tell which vendor a truck belongs to?

It will classify vehicle type (passenger vehicle, pickup, service van, box truck) and retain plates in the clip where they are visible. The property manager attaches vendor identity based on recurring schedules and truck appearance. If you want programmatic vendor identification, license plate recognition is the cleanest path and pairs naturally with the event log.

What if the vendor parks outside camera range?

Then the audit depends on common-area detections instead of the loading dock. If a janitorial crew is billed for three hours in the clubhouse and only 20 minutes of motion is logged there during the billed window, the gap is the story. Most properties have at least one camera on every billable vendor's actual work area.

Does this create legal exposure for us with the vendor?

You are observing a commercial vendor on your own property on cameras you already operate. No new privacy ground is broken. Most vendor contracts already allow the property to verify service. What changes is that you now have specific evidence; the contract governs what you do with it.

Does video leave the property?

Processing happens locally on the edge device. Full video stays on your existing DVR. Only detection metadata and short event clips attached to alerts go to the app.

How many cameras does one device handle?

Up to 25 feeds from a single DVR via a single HDMI input. Larger portfolios deploy one device per DVR.

What does it cost relative to the savings?

$450 one-time hardware, $200 per month per device. On properties where vendor audits recover even a single disputed monthly invoice, the device pays for itself on the operational side before the security side is counted.