How to present an ALPR proposal to your HOA board

1. State the decision first

Begin with the exact decision the board needs to make.

For example:

Approve a 90-day pilot of two Automated License Plate Reader cameras at the community's vehicle entrances, subject to the attached usage policy and a total cost not to exceed $8,000.

Or:

Authorize management to obtain three site-specific camera proposals and return to the board with a recommendation. No equipment purchase is being approved at this meeting.

The board may be deciding whether to:

• Research possible systems
• Approve a vendor
• Approve a pilot
• Adopt operating rules
• Approve a budget

Avoid presenting a general discussion about “improving safety” when the board is expected to take a specific action.

The decision preview

At the beginning of the presentation, summarize:

This can fit on one slide or one page.

2. Explain the problem and the proposed system

Start with the community's actual experience.

Use information the association can support, such as:

• Recent incident reports
• Gate or property damage records
• Police or insurance reports
• Areas where existing coverage was not useful
• Patterns involving vehicles or particular locations

Keep personal details out of the presentation.

A simple explanation might say:

Over the past 12 months, management received seven reports of vehicle break-ins and two reports of gate damage. Existing cameras show general activity in the parking area but do not provide reliable plate images at the main entrance.

Set the boundaries

Explain what the project is intended to address.

For example:

These boundaries help directors understand the purpose before they debate the product.

Explain what will be collected

Describe the proposed system in ordinary language.

For video cameras:

The cameras would record activity in selected common areas. Authorized users could review footage after a reported incident.

For ALPR:

The cameras would photograph vehicles passing the community entrance and attempt to convert each license plate into searchable letters and numbers. Each record would include a vehicle image, time, and camera location.

For a combined system:

The ALPR would create searchable vehicle records at the entrance. The video camera would show activity within the parking area.

State whether the proposal includes:

• Still images or recorded video
• License plate and vehicle details
• Audio or facial recognition
• Automatic alerts
• Outside access

The proposal should clearly state that facial recognition is prohibited unless a later board vote, resident notice, and legal review approve a change.

Show the scope map

Include a simple property map showing:

• Camera locations
• Direction of view
• Areas covered
• Areas specifically excluded
• Entrances that remain uncovered

Do not rely on a general vendor coverage diagram. The board should understand what every camera is expected to do.

3. Present the trust commitments

The board should review the main rules at the same time it reviews the equipment.

These rules should be clear enough to fit on one slide.

Five trust commitments

1. Purpose limitation. The system will be used only for documented safety and security purposes.
2. Limited retention. Routine records will be deleted automatically after the approved period, such as 30 days.
3. Restricted access. Access will be limited to named roles. Residents and board members will not be allowed to browse records casually.
4. Logged use. Searches, views, and sharing will be recorded and reviewed on a regular schedule.
5. Controlled sharing. Law-enforcement and outside access will follow the specific process approved by the board.

The policy should be adopted before the system begins collecting information.

Keep the access model simple

A clear access model might look like this:

The board should make a separate decision about ongoing law-enforcement access. Sharing one record after a specific incident is different from allowing an agency to search the system directly.

Explain resident transparency

Residents should know:

• Why the system is being considered
• What information it collects
• How long information is kept
• Who can access it
• How to ask a question or report an incident

The pilot deck recommends signage at relevant entrances or common areas and a simple online page explaining the system and its rules.

If the vendor supports a resident Safe List or another exclusion feature, explain how it works and what tradeoffs it creates. Do not promise that a feature provides more privacy than it actually does.

Describe the incident process

Residents should not need to know the camera system to report an incident.

A simple workflow is:

1. The resident provides the approximate time, location, and type of incident.
2. Management acknowledges the request within the stated period, such as 48 hours.
3. An authorized user checks whether relevant information exists.
4. Any useful record is preserved and shared only under the policy.
5. The request and result are documented.

The download checklist includes the full governance steps for configuring retention, users, logging, signage, resident notice, and the incident workflow.

4. Describe the pilot and the full cost

A pilot should answer specific questions before the HOA makes a longer commitment.

Five questions for the pilot

1. Did the cameras cover the intended locations?
2. Was the information clear and useful?
3. Did the access and incident process work?
4. How much staff or manager time was required?
5. Is there enough value to continue?

The pilot should have a defined length and a second board vote.

A typical period might be 60 to 90 days, although installation delays and a low number of incidents may require a longer review period.

Show the full cost

Present the cost in a simple table.

Also show the approximate cost per home per month. This can make the budget easier for residents and directors to understand.

Include any likely additional costs, such as moving a camera, replacing damaged equipment, extending retention, or completing electrical work.

Define the evaluation plan

The board does not need dozens of performance measures.

Use five:

• System availability
• Number of valid incident reviews
• Usefulness of the information found
• Resident questions or complaints
• Actual cost and management workload

The pilot report should explain what the community learned, even when no major incident occurred.

5. Put the motion and next steps in writing

The final slide or page should contain the proposed motion.

It should match the actual scope of the project.

Sample motion

Move to approve a [60/90]-day pilot of [number and type of cameras] at the locations shown in the attached scope map, at a total cost not to exceed $[amount].

The pilot will operate under the attached usage policy. Records will be retained for [number] days. Access will be limited to [roles]. Law-enforcement access will be handled [case by case or according to the approved arrangement].

Management will provide resident notice and publish the approved policy before activation. Management will return to the board after the pilot with a report covering system availability, usage, cost, resident feedback, and policy compliance.

Continued use after the pilot will require a second board vote.

Have association counsel adapt the motion to the association's governing documents and applicable law.

The five things to approve

Before ending the presentation, confirm that the motion addresses:

• The rules
• The pilot scope
• The budget
• The evaluation plan
• The second decision date

If one of these is missing, the board may approve a project without agreeing on how it will operate.

Use the download pack to prepare the meeting

The HOA Safety Playbook download pack includes:

• A board presentation deck
• A pilot checklist
• An example implementation timeline
• Governance and access steps
• A second-vote structure

Use the article to understand the process. Use the deck and checklist to prepare the actual board packet and pilot.

Board presentation checklist

Before placing the proposal on the agenda, confirm that:

• The requested decision is specific.
• The scope and exclusions are shown on a map.
• The five trust commitments are included.
• Pilot cost and evaluation measures are clear.
• The motion includes a second board vote.

Sources and further reading

• HOA Safety Playbook resource: Community Safety Tech Pilot board deck
• HOA Safety Playbook resource: HOA Safety Leads Pilot Checklist
• Related HOA Safety Playbook guide: Camera Retention and Access Policies
• Related HOA Safety Playbook guide: How to Discuss Cameras and Privacy With Residents
• Related HOA Safety Playbook guide: Questions to Ask a Camera or ALPR Vendor

FAQ

Should the vendor present to the board?

The vendor can demonstrate the product and answer technical questions. Management or the board committee should present the community's recommendation and proposed rules.

Does the board need to approve the policy before the pilot?

Yes. Access, retention, sharing, and prohibited uses should be settled before the system begins collecting information.

Should every director have access to the system?

Usually, no. The board provides oversight. Operational access should be limited to a small number of trained users.

What if the board is not ready to select a vendor?

Ask for a narrower motion authorizing site assessments, proposals, resident feedback, or legal review.

Does a pilot need a second board vote?

Yes. The board should review the results and make a deliberate decision about continuing, changing, or ending the system.