The buyer’s rep is going to ask about the DVR. Put a 90 day indexed incident log in the OM before they do.
Every search result for “multifamily properties for sale” is a listing marketplace. LoopNet, Crexi, CBRE, Marcus & Millichap, Ten-X, Zillow Commercial. They all index the same financials and the same rent rolls. None of them have a line item for operational security data, because until now there was nothing verifiable to put there.
This guide is for the GP, the asset manager, and the listing broker who want to flip the information asymmetry on security before the buyer’s rep does it at the LOI table. The playbook is a pre-listing HDMI tap on the DVR already in the office closet. Output: a 9 field event log, one CSV, one PDF, and a thumbnail gallery that sits in the data room next to the T-12.
Put indexed incident data in the OMFrom listing decision to closing day, one tap in the closet
Day T minus 90. The decision to list.
Why the top search results for this keyword are no help to a seller
Type “multifamily properties for sale” into Google. The first page is LoopNet, Crexi, CBRE Deal Flow, Marcus & Millichap, Ten-X, and Zillow Commercial. These are inventory marketplaces. Their product is an adjustable filter on cap rate, unit count, submarket, and year built. Their audience is buyers. None of them have ever published a seller playbook for operational security disclosure, because security has not historically been a measurable line item in an OM.
Search the natural sibling query, “multifamily offering memorandum template,” and the top results come from Multifamily.loans, Crexi, Adventures in CRE, and JLL. Every template lists the same eight sections: executive summary, property overview, financial summary, rent roll, market overview, comparable sales, location, and investment highlights. Not one of them has a section for operational security data, because until you could produce that data at a fair cost there was nothing standardized to put there.
The gap is the entire page. A pre-listing HDMI tap on the DVR already in the closet produces the data, in a shape that fits cleanly into the Operational Data section of the OM, with no cooperation from the recorder’s admin UI. The rest of this page is the playbook.
The LOI table, with and without the pre-listing tap
Flip between the two views. The property is the same. The DVR is the same. The only thing that changes is whether the seller arrived at the negotiation with measured incident data or without it.
The OM is silent on incidents. The buyer’s rep inserts a generic security-risk assumption into the underwriting model. They ask for the DVR password during due diligence.
- Seller cannot produce DVR admin credentials
- Remote access to recorder is broken
- Buyer invents worst-case incident narrative
- Price concession shows up at LOI on vague grounds
- Seller cannot refute the narrative with data
90 days of tap, one data room folder
The pre-listing flow has five steps and nothing that depends on a cooperative DVR admin. Steps one and two happen in the office closet. Steps three through five happen in the broker’s OM draft file and the data room.
Seller pre-listing data flow
HDMI tap on DVR
Read-only inline on the cable already running to the wall monitor. No DVR credentials.
Indexing starts
Cyrano decodes each tile, masks overlays, writes 9 field records at median 7 second latency.
Dashboard accrues
30 to 90 days of events with tile.label, event_class, and iso8601_ts across all 25 tiles.
Export bundle
CSV, PDF with charts, 480x270 JPEG thumbnail gallery. Dropped into the data room folder.
OM references it
One line in Operational Data. Serious buyers route to the folder. Incident data is now part of the deal.
The OM Operational Data section, before and after
Same template. One new subsection. This is the JSON shape of the Operational Data section as it shows up in the OM generator tool most brokers use today (Crexi OM builder, JLL template, Multifamily.loans boilerplate), on the left, and as it looks with a 90 day indexed log appended, on the right.
om_operational_data.json
{
"section": "Operational Data",
"subsections": {
"financial": "T-12, rent roll, estoppels, loan summary",
"physical": "PCA summary, roof, HVAC, envelope, site",
"market": "comp set, submarket report, absorption",
"legal": "title commitment, zoning, leases, OMC"
},
"security_disclosure": null,
"incident_log": null,
"coverage_map": null
}The 9 field payload is identical across recorder brands, which makes portfolio roll-up possible
Every Cyrano unit writes the same nine fields per event, regardless of whether the DVR in the closet is a 2017 Hikvision DS-7716NI-K4 or a 2023 Reolink NVR: tile.label, tile.index, tile.coords, property, layout_id, overlay_mask, event_class, iso8601_ts, latency_ms. Plus a 480x270 JPEG thumbnail. This is the shape that lets a listing broker reduce the whole 90 day log to one OM line: “indexed incidents per 1000 resident-days”, comparable across every asset in a portfolio sale.
That one ratio is the operational-security analog of economic occupancy. It fits cleanly next to the financial metrics the OM already discloses. Buyers can underwrite against it. Lenders can audit it. Insurance carriers can benchmark it. And because the shape is standardized at the edge device level, the ratio is not re-computed by every party with a different methodology. It is produced once, at the source.
How the buyer’s rep reads the data room folder
The broker does not pull the data room folder together by hand. Cyrano writes the bundle directly, and the buyer’s rep reads it with zero dependency on the seller’s IT. Here is the message sequence in a typical pre-LOI review.
pre-LOI data room: seller, data room, buyer's rep
One OM. Many stakeholders. One shape.
The same 9 field export answers questions for every party attached to a disposition. Broker uses it for the OM summary. Lender uses it for the loan package. Carrier uses it for renewal pricing. GP uses it for the LP update. Buyer’s rep uses it for underwriting. No party has to request a recorder-specific export from a different admin UI.
event
log
The 4 step seller playbook
Scope
Identify the DVR in the office closet, note brand and tile count. Under 5 minutes, usually done during broker site walk.
Tap
Plug Cyrano unit into the HDMI output inline with the wall monitor. Under 2 minutes, no DVR admin credentials.
Accrue
30 to 90 days of events written to the dashboard. Broker watches the dataset grow without any recurring effort.
Export
CSV, PDF, thumbnails generated on demand, dropped into the data room folder that the OM references.
Representative numbers from a 90 day pre-listing tap
From a 312 unit Class B multifamily property in Texas, tap started 94 days before listing, 16 active tiles on a Hikvision DS-7716NI-K4. Data taken from the dashboard session logs, not a seller memorandum.
“At one Class C multifamily property in Fort Worth, Cyrano caught 20 incidents including a break-in attempt in the first month. Customer renewed after 30 days.”
Fort Worth, TX property deployment
“We used to answer the buyer's security question with a one line email that said 'we have cameras.' Now we hand them a 90 day CSV and a thumbnail gallery and the question stops there.”
Tap the DVR before the OM goes out
15 minute walkthrough. We plug into the HDMI of a live multifamily recorder and show you the 9 field export shape that goes into the data room alongside the T-12.
Book a call →Frequently asked questions
I am a GP or asset manager preparing to list a stabilized multifamily asset. Why run a pre-listing HDMI tap at all?
Because the part of the asset buyer due diligence wants the most, and cannot get from your T-12 or rent roll, is operational security data. Crime, loitering, package theft, parking-lot incidents. Today the buyer asks for the raw DVR and discovers the log is unreadable, the password is lost, retention is 7 days not 30, and remote login does not work. That discovery lands in their risk narrative and shows up as a price concession at the LOI table. A pre-listing HDMI tap lets you surface the same data yourself, in a clean 9-field exportable shape, so the buyer is evaluating your packaged disclosure instead of inventing their own risk story.
How long should the pre-listing tap run before I send the OM?
The shortest deployment we have seen generate a usable baseline is 72 hours, but we recommend 30 to 90 days. A 30 day tap gives you roughly 7,000 indexed events on an average 16 camera property, which is enough to chart incident density by tile.label, by hour-of-day, and by event_class. A 90 day tap covers a full operating month plus seasonality and is the shape most brokers now want to drop into the OM data room. Once the unit is plugged in, the data accrues whether or not the property is on the market, so taps started 6 to 12 months out cost nothing extra and produce a richer graph at listing time.
What exactly does the buyer's rep see in the data room?
A one page summary, a CSV, a PDF, and a thumbnail gallery. The summary has four numbers: indexed events per 1000 resident-days, events-per-tile ranked, events-by-hour distribution, and events-by-class distribution. The CSV has one row per event with the nine field payload (tile.label, tile.index, tile.coords, property, layout_id, overlay_mask, event_class, iso8601_ts, latency_ms). The PDF is the summary with chart panels suitable for attaching to the OM. The thumbnail gallery is 480x270 JPEGs with filter bar so the buyer's rep can spot-check any event class or tile without asking the seller for DVR access.
Does this have to go in the OM, or can I save it for the data room?
Either works. The public OM usually summarizes at the property level (one paragraph plus a single chart), and the data room holds the CSV, the PDF, and the thumbnail browser. Brokers we have seen list with the 9 field export tend to put a one-line disclosure in the OM (Section: Operational Data, sub-bullet: Indexed Incident Log, 90 days, exportable) and route serious buyers to the data room for the full pull. The value is the same either way: buyer sees a measured incident rate, not a speculative one.
Why would plugging into HDMI be better than giving the buyer the DVR password?
Three reasons. First, most sellers cannot produce the DVR password because the recorder is five years old and the admin credential was rotated by a property manager who is no longer at the company. Second, even when the password works, the DVR's built-in search is a motion scan keyed on channel number, not an event-classified log. The buyer can stare at the timeline for 45 minutes and get nothing actionable. Third, the HDMI tap is one-way and read-only, so the seller is not handing over administrative control of a device that is still recording on the day the buyer's rep is looking at it. The DVR keeps running. Cyrano sits inline on the HDMI cable and reads the multiview the recorder is already rendering.
What if my DVR is an older brand the buyer's rep has never seen?
Cyrano ships overlay mask templates for Hikvision DS-7xxx, Dahua XVR and NVR, Lorex, Amcrest, Reolink NVR, Uniview, Swann, Night Owl, Q-See, ANNKE, EZVIZ, Bosch DIVAR, Honeywell Performance, and Panasonic WJ-NX. The overlays are how the detector blanks the clock, the camera-name strip, and the channel bug so they do not pollute the event log. The 9 field payload is identical across brands. The buyer's rep sees the same schema whether the recorder in the closet is a 2017 Hikvision or a 2023 Reolink.
My broker argues that putting security data in the OM invites more buyer questions, not fewer. Is that real?
It is, but the alternative is worse. When the OM is silent on operational security, buyers project their worst-case assumption onto the property and price the asset accordingly. When the OM shows a measured incident rate, with a real CSV in the data room and a standardized event shape, the buyer has something to benchmark instead of a blank. Brokers who run this playbook consistently report fewer security-related concession requests at the LOI, because the risk has been priced at the sell side rather than invented at the buy side.
What does the buyer do with this after close?
Nothing, if they want. The Cyrano unit stays plugged into the HDMI on the recorder in the office closet and the 9 field log continues to accrue under the new owner. The buyer inherits the seller's event history as a queryable archive, and the first 30 days under new ownership are directly comparable to the trailing 30 days under old ownership. Most buyers keep the unit. A few unplug it and use the $450 hardware at another acquisition. The subscription is per-unit, per-month, and transfers with the property at close.
Is there any scenario where running this tap before listing hurts the seller?
The one scenario is a property with a hidden chronic problem (for example, nightly loitering in a specific breezeway that has never been reported to the office or the MLS). The tap will surface it, and the seller will have to decide whether to fix it before listing, disclose it in the OM, or pull the tap. This is a feature, not a bug, because the buyer's rep would find the same pattern in the first week after close, and the resulting litigation or concession dispute is far more expensive than a quiet pre-listing fix. Running the tap 90 days out gives the seller a decision window that no last-minute buyer discovery ever does.
How does this compare to hiring a security consultant to produce an operational audit before listing?
A security audit is a point-in-time walkthrough plus a report. A 90 day indexed log is a time-series dataset with 20,000 to 30,000 event rows and JPEG thumbnails. The audit tells the buyer what a consultant saw on one day. The log tells the buyer what the property actually does across 90 days. The audit is $5,000 to $15,000 per property. The pre-listing tap is $450 in hardware plus $200 per month per property. On a 90 day tap the total is under $1,050, the output is richer, and the file is one that a lender or carrier can independently audit.
Can the same unit stay deployed through the hold period of the next owner?
Yes. The hardware is not tied to a specific recorder brand, a specific DVR UI, or a specific property-management system. If the next owner swaps the DVR, the HDMI output of the new recorder still feeds the same Cyrano unit, and the unit picks up the new tiles under their labels. If the next owner sells the property five years later, the same tap produces their own 90 day pre-listing export and the cycle repeats. Most operators treat the unit as a permanent fixture of the asset, the way they treat a smart thermostat or a keybox.
Adjacent reading for multifamily sellers and brokers
Real Estate Multifamily For Sale: The DVR in the Office Closet
The buyer-side companion to this page. What a new owner inherits on the recorder, and how to get a queryable event log on day one after close.
Multifamily Security Program NOI Impact
How a measured security program shows up in NOI, in cap rate, and at disposition. The financial case for the pre-listing tap.
Quality vs Price in Multifamily Security Providers
How to judge a security vendor during the hold period so the pre-listing data you produce at disposition is clean and credible.
Comments (••)
Leave a comment to see what others are saying.Public and anonymous. No signup.