How many questions should we ask during the first vendor meeting?

Start with the 15-question shortlist. Use the more detailed questions when the board is comparing final proposals or reviewing a contract.

How many vendors should the HOA speak with?

Three written proposals often provide a useful comparison. The appropriate number may depend on the project, purchasing rules, and available providers.

Should every vendor receive the same questions?

Yes. Give every vendor the same description of the community's problem and ask the same priority questions. This makes the answers easier to compare.

Should the board require a site visit?

For a permanent system, a site assessment is usually important. Camera performance depends on placement, lighting, distance, vehicle speed, power, connectivity, and the property layout.

Can we rely on a vendor's accuracy percentage?

Treat it as one piece of information. Ask how it was measured and request testing at the property. Performance can change with angle, lighting, speed, weather, and plate condition.

Should all promises appear in the contract?

Important promises about features, installation, pricing, support, privacy, retention, access, and performance should appear in the agreement or another binding document.

Is a pilot always necessary?

No. A pilot is most useful when the board needs to test uncertain locations, performance, workload, resident response, or operating procedures.

Guide · Evaluate solutions

Questions to ask a camera or ALPR vendor

Estimated reading time: 9 minutes

A vendor presentation can make a camera system sound simple.

The camera captures useful information. The software makes it easy to search. Alerts arrive quickly. Installation and support are handled for you.

The details matter.

Before recommending a system, the board should understand what it will see, what it will miss, who can access the information, what the community will need to manage, and how much it will cost over time.

You do not need to ask a vendor a hundred questions during the first meeting. Start with the six topics in this guide. Each section includes five priority questions, followed by a few additional questions when the subject needs a closer look.

Ask vendors to show important features rather than simply describing them. Get the final answers in writing.

Before speaking with vendors

Write down the problem the community is trying to address.

Examples include:

Vehicle break-ins
Vehicle theft
Gate damage
Package theft
Vandalism
Trespassing
Unauthorized parking
Illegal dumping
Activity near a mailroom or clubhouse

Also note:

Where incidents have occurred
Whether vehicles are usually involved
What safety measures already exist
What information was missing after earlier incidents
Who would operate the system
The board's approximate budget
Concerns residents have already raised

Share the same summary with every vendor.

This helps keep the conversation focused on the community's needs rather than the vendor's full product catalog.

1. Does the proposed system fit the problem?

The first question is whether the vendor understands what the HOA is trying to accomplish.

A camera system can be technically impressive and still be a poor fit for the community.

Five priority questions

What specific problem is your proposed system intended to address?
Why have you selected these camera locations?
What should each camera capture, and what will probably remain out of view?
Could a smaller or simpler system still address the main problem?
What other changes should we consider, such as lighting, locks, gate repair, landscaping, or access procedures?

Ask the vendor to provide a simple site map showing:

Each camera location
The direction it will face
The area it is intended to cover
Any entrances or areas that will remain uncovered

A broad coverage circle on a map is not enough. The board should understand the purpose of every proposed camera.

Go deeper when needed

Will any camera include private windows, patios, balconies, or unit doors?
Can private areas be blocked or masked?
Does the design rely on another system, such as a gate or internet connection?
Are some cameras included mainly because they are part of a standard package?
Can the system be expanded later if the first phase proves useful?

2. Will the cameras work at this property?

Camera performance depends heavily on placement and conditions.

A general accuracy claim or a demonstration from another property does not show how the system will perform at your entrance, parking lot, or mailroom.

Five priority questions

What image quality should we expect here during the day and at night?
What conditions are most likely to produce an unclear image or missed event?
Will you test the proposed locations before the final installation?
Can you show us successful, failed, and incorrect results from similar conditions?
How will we confirm that each camera is working properly after installation?

Ask for testing that reflects the actual property:

Normal vehicle speeds
Headlights at night
Existing lighting
Shadows and glare
Lane width
Trees and landscaping
Gates, signs, and other obstructions

For an ALPR system

Also ask the vendor to demonstrate:

A clear plate read
A plate the system could not read
A plate the system read incorrectly
A temporary paper plate
A partial-plate search
A vehicle-description search, if offered

The board should understand the difference between:

A vehicle being detected
A plate image being captured
The plate characters being read correctly

These are related, but they are not the same result.

Go deeper when needed

Can the camera cover more than one lane?
Can it read front plates, rear plates, or both?
What happens when vehicles pass close together?
Can a user correct an inaccurate plate reading?
How do rain, fog, bright sun, or dirty plates affect performance?
How often will a camera need cleaning or realignment?

3. What information will the system collect and help us find?

The board should see a normal record before approving the system.

Do not rely only on feature names such as “advanced search,” “vehicle intelligence,” or “smart video.”

Five priority questions

What information is collected each time the camera records an event?
Does the system store still images, recorded video, plate records, audio, or a combination?
What can an authorized user search for later?
How long is the information kept, and can the HOA choose a shorter period?
Can you show us a normal record, a search result, an export, and the audit log?

For an ALPR system, a normal record may include:

Plate characters
Plate image
Wider vehicle image
Date and time
Camera location
Vehicle color or type

For a conventional camera, the system may provide:

Live video
Recorded video
Motion events
Person or vehicle detection
Timeline search
Selected-area search
Other visual analytics

The exact features vary by product.

Ask about alerts

If the proposal includes alerts, clarify:

What triggers them
Who creates the alert rules
Who receives them
Who verifies the result
What the recipient is expected to do

An automated alert should be treated as information to verify. It does not prove that the reading is correct or that the vehicle or person is involved in an incident.

Go deeper when needed

Can users search by partial plate?
Can users search by vehicle color, make, model, or body type?
Does the system offer free-text or natural-language searches?
Can searches cover information from other locations?
Can users preserve a record connected to an incident?
Is the reason for preserving or exporting information logged?
What happens to exported records after the normal retention period?

4. Who can access or share the information?

Access and sharing settings can affect the community as much as the cameras themselves.

The board should understand the actual controls proposed for its account.

Five priority questions

Which HOA employees, board members, contractors, or vendor staff can access the system?
Can every authorized person have an individual account with limited permissions?
Is every search, view, download, export, and settings change recorded?
Can law enforcement or any outside organization search the system directly?
Is the HOA's information part of a wider network that other customers or agencies can search?

Ask the vendor to demonstrate:

How a user is added
How permissions are limited
How access is removed
What appears in the audit log
How outside access is approved or revoked

Board membership alone should not automatically provide access.

The HOA should identify a small number of trained users and give each person only the access needed for their role.

Law-enforcement access

Be precise about the difference between:

Sharing a record related to one incident
Giving an agency ongoing access
Allowing the agency to search the system directly
Participating in a broader information-sharing network
Receiving alerts based on an outside watchlist

These are different arrangements.

Go deeper when needed

Is outside access enabled by default?
Can access be limited to one camera or time period?
Will the HOA be notified when an outside agency searches?
Can the vendor share information without first contacting the HOA?
What happens if the vendor receives a subpoena or court order?
Are vendor employee searches shown in the audit log?
Can information be used to train or improve the vendor's systems?
Can the vendor combine HOA information with data from other customers?

5. What will installation and ongoing operation require?

The proposal should clearly divide responsibilities between the vendor and the HOA.

A camera can be easy to purchase and difficult to operate if power, connectivity, maintenance, and internal responsibilities have not been resolved.

Five priority questions

What work must be completed before the cameras can be installed?
Who provides power, connectivity, poles, permits, and any electrical or network work?
How will the HOA know when a camera or connection has failed?
Who repairs, cleans, realigns, or replaces the equipment?
What work will the community manager or another HOA representative need to perform after launch?

Ask for a written list of:

Vendor responsibilities
HOA responsibilities
Third-party contractor responsibilities
Possible causes of additional charges
Expected installation timeline

Understand outages

Ask what happens if:

The internet goes down
Cellular service fails
A camera loses power
Local storage fills
A battery runs low
The camera moves out of alignment
Landscaping blocks the view

A physically installed camera is not necessarily a functioning camera.

The system should notify an authorized person when a device is offline or failing.

Go deeper when needed

Does the camera continue recording while offline?
How much information can it store locally?
Does information upload after the connection returns?
Are on-site service visits included?
What response and repair times are promised?
Is damage or vandalism covered?
Who trims vegetation that blocks the camera?
What happens when a camera model is discontinued?
Are software and hardware upgrades included?

6. What will the system really cost?

Ask for the complete cost, not only the price of the cameras.

Compare proposals over the same time period, preferably three or five years.

Five priority questions

What is the full cost in year one and over five years?
Which costs are one-time, and which recur each year?
What is included in installation, storage, connectivity, maintenance, and support?
How can the price change at renewal or during the contract?
What will it cost to add, move, replace, remove, or stop using a camera?

Ask for an itemized quote that separates:

Equipment
Installation
Poles and mounts
Electrical work
Network work
Software
Storage
Cellular or internet service
Maintenance
Support
Training
Permits
Taxes and shipping
Optional features

If a cost is included, the quote should say so.

Contract questions

The board should also understand:

Initial contract length
Automatic renewal
Cancellation notice
Early termination fees
Service commitments
Renewal pricing
Hardware ownership
Insurance requirements
Data export
Equipment removal

Important promises made during the sales process should appear in the contract or another binding document.

Go deeper when needed

Is there a minimum number of cameras?
Can the HOA start with a smaller pilot?
Are all users included?
Does longer retention cost more?
Are integrations included?
What conditions create a change order?
Is payment required in advance?
Can the vendor change features or policies during the agreement?
What remedy applies if promised service levels are missed?

7. What happens when the contract ends?

This subject is easy to overlook during a sales process.

The board should understand the exit process before the equipment is installed.

Five priority questions

Who owns the cameras, poles, mounts, recordings, and plate records?
Can the HOA export its information before the contract ends?
When and how will the vendor delete the HOA's information and backups?
Who removes vendor-owned equipment and restores the property?
Can any purchased hardware work with another system after the contract ends?

Ask whether the vendor will confirm deletion in writing.

Also ask how much time the HOA will have to download or transfer information before access is removed.

Go deeper when needed

What file format will exports use?
Is there a fee for exporting information?
Does the system stop working immediately when the license ends?
Who repairs holes or damage caused by removal?
Can the vendor keep de-identified or aggregated information?
What happens if the vendor is acquired or stops supporting the product?

Ask about a pilot when there is real uncertainty

A pilot can be useful when the board needs to test:

Camera placement
Nighttime performance
Plate-reading results
Search usefulness
Manager workload
Resident response
Alert procedures
Connectivity

A pilot should have:

A defined length
A limited number of locations
Written access and retention rules
Clear success measures
A known cost
No hidden long-term commitment
A process for deleting pilot information
A defined decision date

A pilot should answer specific questions. It should not simply turn into a contract because the equipment is already installed.

Ask for relevant references

Request one or two customer references from communities with a similar:

Property type
Number of homes
Number of entrances
Camera count
Management structure
Use case

Ask each reference:

Did installation match the original proposal?
Were there unexpected costs?
Does the system perform well at night?
How much manager time does it require?
Would the community choose the same system again?

Vendor-selected references are likely to be satisfied customers, but their operating experience can still reveal useful details.

Warning signs

Pause and investigate further if a vendor:

Promises that the system will prevent or solve crime
Will not test the actual property
Avoids discussing failed reads or unclear images
Cannot explain what information is collected
Cannot demonstrate user permissions and audit logs
Gives vague answers about law-enforcement access
Calls the system private without explaining sharing settings
Will not provide an itemized quote
Leaves installation responsibilities unclear
Keeps important promises out of the written agreement
Pressures the board to sign before counsel reviews the contract
Cannot explain what happens when the contract ends
Says policies can be developed after installation

A good vendor should be able to explain limitations as clearly as features.

A simple vendor scorecard

Score each category from 1 to 5.

Category	Vendor 1	Vendor 2	Vendor 3
Fit with the community's problem
Site design and coverage
Daytime and nighttime performance
Search and alert usefulness
Privacy and access controls
Installation plan
Maintenance and support
Five-year total cost
Contract flexibility
Data export and deletion
References
Overall clarity

Add notes beside each score.

A high total should not outweigh a serious concern involving privacy, performance, cost, or contract terms.

The 15-question shortlist

For an initial vendor meeting, these are the questions to prioritize:

What specific problem is your design intended to address?
Why have you selected these camera locations?
What will each camera capture, and what will it miss?
What performance should we expect here during the day and at night?
Can you show us failed or incorrect results as well as successful ones?
What information will the system collect?
What can users search for later?
How long will information be retained?
Who can access the system?
Can outside agencies or other customers search our information?
What will the HOA need to provide for installation?
Who handles failures, maintenance, and replacement?
What is the total cost over five years?
What happens to the equipment and information when the contract ends?
Can you provide these answers in writing?

These questions are enough for a useful first conversation. The longer sections in this guide can be used when reviewing the final proposal and contract.

Sources and further reading

Government technical resource: Department of Homeland Security, License Plate Reader Systems Market Survey Report
Government policy resource: Bureau of Justice Assistance, License Plate Reader Policy Development Template
Government cybersecurity resource: NIST, IoT Device Cybersecurity Guidance
Government procurement resource: CISA, Internet of Things Acquisition Guidance
Government procurement example: Ravalli County camera project request for proposals
Government procurement example: Town of Oakland cloud security camera request for proposals
Vendor planning resource: Axis total cost of ownership guidance
Vendor technical resource: Axis license plate capture guidance

FAQ

How many questions should we ask during the first vendor meeting?: Start with the 15-question shortlist. Use the more detailed questions when the board is comparing final proposals or reviewing a contract.
How many vendors should the HOA speak with?: Three written proposals often provide a useful comparison. The appropriate number may depend on the project, purchasing rules, and available providers.
Should every vendor receive the same questions?: Yes. Give every vendor the same description of the community's problem and ask the same priority questions. This makes the answers easier to compare.
Should the board require a site visit?: For a permanent system, a site assessment is usually important. Camera performance depends on placement, lighting, distance, vehicle speed, power, connectivity, and the property layout.
Can we rely on a vendor's accuracy percentage?: Treat it as one piece of information. Ask how it was measured and request testing at the property. Performance can change with angle, lighting, speed, weather, and plate condition.
Should all promises appear in the contract?: Important promises about features, installation, pricing, support, privacy, retention, access, and performance should appear in the agreement or another binding document.
Is a pilot always necessary?: No. A pilot is most useful when the board needs to test uncertain locations, performance, workload, resident response, or operating procedures.

Prepare the board proposal

Once the board understands the system, costs, operating rules, and vendor responsibilities, it can organize the decision into a short proposal that residents and directors can understand.

Read How to Present an ALPR Proposal to Your HOA Board

Related guides

This guide is operational guidance and is not legal advice. Consult association counsel for advice specific to your community.