Board approves visitor-management purchase after debate about license scanning and privacy; rollout to wait for procedures

The Berkeley Heights Board of Education voted to approve procurement of a visitor-management system intended to log visitors, print badges and run checks against child-welfare databases, but the vote followed extended public discussion about privacy, data retention and rollout procedures.

Jeremy (district technology staff) described the system’s features: it can capture a visitor photo for badge printing, record first name, last name and date of birth, and in some cases read the last four digits of a driver’s license to differentiate similar names. "It collects from the license the name, the date of birth, and the last four digits of the license number," Jeremy said, adding that the camera image will be stored briefly for badge printing.

Several board members raised privacy, equity and legal concerns. Board member Aditi Akiri asked whether the software requires scanning a license or if staff can manually enter a visitor’s information for those who decline. Akiri said she was worried about storing unique identifiers and asked how long data would be retained. Jeremy and other staff said manual entry is possible but less efficient, and that many districts use similar systems for safety and custody checks.

Board member Dr. Tom Forager urged the group to clarify the tangible safety benefit and lifecycle costs, and raised questions about whether the district is legally permitted to store scanned driver-license information. "We have to understand where the data sits, how long it is stored, and who has access to it," another board member said. Members with experience running visitor systems said the primary purposes are emergency accountability and safety flags for custody or background concerns.

The administration said the district had procured the system through a cooperative purchase and that hardware/software components are in hand; it asked the board to authorize completion of implementation steps. The board approved the purchase but stipulated the system will not be rolled out until the administration develops procedures and a communications plan, the technology committee vets those procedures, and the board is satisfied with privacy protections and exceptions (for example, manual entry for visitors who do not want their license retained).

In related technology discussion, the finance committee also briefed the board on an expected licensing/service cost and the need to coordinate with PTOs and building administrators for messaging. The board directed administration to produce implementation procedures, clarify any ongoing license or hosting fees, and return to the technology committee for review prior to public deployment.

Next steps: administration will draft operational procedures, data-retention policy and public communications; the technology committee will vet those materials and make recommendations before any campus-wide rollout.