A quick answer.
As much depth as you need.

Article 21 puts covered surveillance decisions before the public and makes the limits enforceable. The Town must explain proposed acquisitions, new uses and outside agreements before the Select Board decides. Residents get at least fourteen days to read the supporting materials. Approval requires written findings and a policy stating exactly what is allowed.

Article 22 limits what plate readers may keep. They may check lists of specific vehicles sought for documented reasons, such as a stolen vehicle or a vehicle associated with a missing person. A capture that matches no qualifying entry, a “nonmatch,” must be discarded immediately, within three minutes at most. State and federal law remain controlling.

Each article can stand alone. Together, they establish public oversight and specific limits on plate-reader records.

Residents should know what their tax dollars buy and what happens to information collected about them.

• 1. Information beyond the Town’s direct control. Article 21 requires ownership, access and contract protections for information that reveals identifiable activities over time. Article 22 ends standing network access to Town plate-reader records and requires individual review of ordinary outside police requests.
• 2. Records that become a picture of someone’s life. Article 21 gives linked information stronger protections. Article 22 requires immediate disposal of nonmatching plate captures, within three minutes at most, while allowing qualifying matches to be kept for their documented purpose and related investigation. Controlling preservation law still applies.
• 3. Uses that go beyond what the public approved. Covered acquisitions, new uses, locations and outside agreements need Select Board approval in an open meeting after at least fourteen days of public posting. Approval must weigh benefits, costs and alternatives, set the permitted uses, and rely on independently verifiable supplier claims.
• 4. Residents should not have to piece the account together themselves. Article 21 requires an inventory, annual reports, examination of access records by a qualified independent person, and complaint reporting. Residents gain a way to check which systems are used, what they cost, who accesses the information and whether the rules are followed.
• The result: useful tools with public limits. Article 21 makes oversight a continuing duty. Article 22 keeps plate-reader alerts focused on specifically sought vehicles. Both provide a route to court to enforce the rules.

A camera records a scene. Software can make those observations searchable, combine them with other records and reveal a person's routines. Residents deserve a say in how far that goes.

Residents should know what systems the Town has watching them. Article 21 requires an inventory of every covered system in use within 90 days after the bylaw takes effect and public approval for covered surveillance uses. Read what we know about the Town’s current systems.

Article 21 addresses control directly. Its strongest data protections apply to Aggregated Surveillance Information: information that can reveal an identifiable person’s movements, associations, habits or activities over time. Section 7.1 reserves sole ownership of that information and everything derived from it to the Town. An agreement cannot turn data derived from Town-collected events into someone else’s property. Section 7.9 keeps that information under Town control and limits outside processing to what is necessary to deliver an approved service, without the outside party retaining, copying or deriving data from it.

These standards support public safety with clear limits. Article 21’s stated purpose protects privacy while preserving the Town’s ability to obtain the operational capabilities its departments need. Article 22 permits plate-reader alerts for specifically sought vehicles and requires nonmatching images and data to be destroyed. Article 21 covers Town surveillance across departments, with its stated scope and exclusions, including the proposed school exclusion; Article 22 sets specific plate-reader rules. Both apply regardless of supplier. Residents should not have to start over with every new company or technology.

On September 25, the Police Department announced its decision to end the Flock relationship and stop using the system until the Massachusetts Legislature or the courts establish clearer guardrails. That decision does not itself establish local standards for future collection, retention or sharing. Both articles address technology and data practices regardless of supplier.

Article 21 requires public approval and continuing accountability for covered surveillance. Article 22 sets limits on plate-reader operation, retention and sharing. These protections belong in rules that apply beyond a single contract. Read why a bylaw matters.

Residents should not have to rebuild their privacy protections every time the Town changes vendors or wait for the next controversy to decide what is acceptable.

A by-law lets residents, through Town Meeting, set the standards future decisions must meet. Article 21 gives the Select Board flexibility to write and update implementing regulations within those standards. Article 22 puts its plate-reader limits in the by-law itself.

On September 15, the Town Manager reported restrictions on network access and supervisor-only use of the plate-reader tool. Those steps matter. The articles would make public approval and enforceable data protections continuing obligations through changes in vendors and leadership.

Any policy alternative should be judged on its actual safeguards, who can change them, and how residents can enforce them.

Within 180 days after the bylaw takes effect, the Town Manager or a named designee would also have to submit each covered system already in use for Select Board approval.

At least once a year, the Town would report publicly on how each covered system was used, who outside the Town received or accessed its data, what it cost, complaints and their outcomes, and any violations found in audits and the action taken. Those reports would appear in the Annual Town Report and be reviewed by the Select Board at a public hearing.

The published police policy described storage by Flock. In its May 15, 2026 response, Flock described computers serving multiple customers, with software controls separating their data. The Department’s September 25 announcement said it had decided to end the relationship and stop using the system; it did not state what would happen to stored data and derivatives.

Flock said it used less than 1% of data for model training, stripped identifying data from training images, and allowed customers to opt out. It also said data was deleted from applicable storage systems, including backups, using AWS deletion functions, while stating: “Data is not deleted from the model.” These are the company's dated descriptions, rather than an independent check of today's settings.

Privacy rules must cover what is made from information as well as the original records. For information revealing identifiable activities over time, Article 21 requires Town ownership and control, prohibits reuse for model training and requires documented deletion when retention ends, subject to controlling law and legal holds. Ending a vendor relationship and confirming what happened to the information are different tasks.

Ordinary Town computers and cybersecurity systems have express exclusions. Article 21 also lists routine Town databases, physical access controls, dispatch and other ordinary systems. Section 4.2 governs when an added surveillance use goes beyond the excluded purpose.

Under the proposed amendment, a building-security camera serving only that excluded purpose can record and overwrite footage on a fixed schedule without losing its exclusion. Added surveillance functions, such as linking or analyzing information, can bring those functions under Article 21. The distinction is between the ordinary job and the added surveillance use.

Added surveillance uses follow different rules. Linking records to track identifiable people or making vehicle movements searchable can bring a system within Article 21. Covered uses require approval; some practices, including facial recognition, are prohibited subject to the specified exceptions in Section 5(b).

Article 22 defines a plate-reader system to include a system that converts number plates in images into computer-readable or searchable data. It also includes systems that derive vehicle appearance or attribute data to identify, match or search for particular vehicles. Ordinary recording alone is excluded. A person’s use of software to read a plate in a specific image obtained while investigating a particular incident is also excluded. Read the plate-reader definition.

Police and Fire do not gain that exclusion merely by entering school property. Article 21 separately excludes ordinary dispatch and emergency operations within §4’s limits and permits specified emergency surveillance use under §6.3. Read the school-emergency and school-resource-officer explanation.

As printed, §3.3 respects authority granted by general law where a particular bylaw requirement conflicts with it. An entity claiming that protection must identify the legal authority, the provisions it says cannot apply and the extent of the conflict in writing. The School Committee has separate authority under state law, but §3.3 is not the same as excluding every school-capacity activity from the entire article.

Article 21 was never intended to reach the schools. Section 3.3 was intended to protect the School Committee’s authority under state law. At the request of the School Committee chair, writing on the Committee’s behalf, proposed Article 21 §3.4 makes the school exclusion explicit and removes the need for a written assertion under §3.3. The proposed clarification to Article 22 adds the same school exclusion. Read proposed Article 22 §3.4.

We support both articles with those express school clarifications. Town Meeting must act on them; the printed warrant does not already contain them. Article 22 remains a separate set of limits on Town-related plate-reader operation. Read what that means for schools and police.

If the Town operates a system, directs its use or enters an agreement involving it, the applicable requirements govern that activity. Your use of a camera remains distinct from what the Town may subsequently do with information it receives.

Information that can reveal identifiable people's movements or routines receives Article 21's strongest protections. The article calls it “Aggregated Surveillance Information.” The Town would own it and what is derived from it. Outside custody and access are restricted; shared data stores and model training are barred.

Retention must be limited to the shortest period consistent with the approved purpose. Deletion must be documented, including how backups and legal holds are handled. Contracts must require breach notice within a defined period of no more than seventy-two hours.

Article 22 ends standing or network-wide access to the Town’s plate-reader data. An outside police agency’s ordinary request must identify the information and purpose in writing before access. Town personnel must review it individually and determine that sharing serves the Town’s interests and complies with Massachusetts law. Requests, decisions and disclosures are recorded. Separate provisions preserve legal process served on the Town, legally required disclosures and specified prosecution uses.

Why this matters locally: the Town’s network audit export recorded 428,478 query records across 2,961 distinct organization names, including Tewksbury, with execution dates from February 1 through March 2, 2026. These were searches that included Tewksbury’s network, often alongside many other networks. The log does not establish that every search returned a Tewksbury image or targeted a local resident. It documents the scale of network access, not a count of successful local results. Read the network audit figures.

Article 21 also prohibits default enrollment in outside data networks. Information revealing identifiable activities over time requires legal process or an approved agreement; an agreement cannot grant blanket or network-wide access or waive Article 22’s stricter rules. The dated audit describes the earlier access pattern, not the system’s status after the September 25 announcement.

The published policy describes records of vehicle passages: plate information coupled with time, date and location, stored for thirty days with preservation for evidence and other legal requirements. Policy 424, Sections 424.2 and 424.8. On September 25, the Department announced its decision to end the Flock relationship and stop using the system. The announcement did not establish the timing of shutdown or deletion of existing records.

Article 22 would establish a lasting rule against accumulating nonmatching plate captures for later searches. Nonmatches must be discarded immediately, within three minutes at most. Qualifying matches may be retained for their documented reason and related investigation. State and federal preservation requirements remain controlling. The rule follows the technology, including a future supplier.

On systems and lists that meet its requirements, Article 22 also permits listed vehicles associated with a person subject to an outstanding warrant or who is endangered, and vehicles entered by an officer on a documented basis relevant and material to a particular criminal investigation.

The list must stay current and comparison must stop if its criteria no longer meet the standard. A qualifying match can generate an alert; officers must verify it before acting, and a match alone is insufficient grounds for a stop. Equipment must meet the article’s requirements, subject to its existing-contract provision. Read about NCIC, BOLOs, AMBER, Silver Alerts and partial plates.

If a crime is discovered Thursday, a nonmatching capture discarded Tuesday cannot be recovered for that investigation.

Keep records for a documented reason, rather than build a history of everyone’s travel. Article 22 permits retaining qualifying matches for their listed reason and related ongoing investigation. It requires other captures to be discarded, subject to controlling preservation law. We support that boundary.

Once a vehicle qualifies for a list, future detected matches can generate alerts, and qualifying matches may be retained for the listed reason and related investigation.

Even a one-day database records the travel of vehicles that matched no lookout list. Strict access controls reduce risks, but keeping that record still creates them:

• A record of ordinary travel. Where vehicles passed and when can reveal routines when observations are combined, including information about people who were not being sought.
• Exposure to misuse or a breach. Stored records remain available to someone who misuses authorized access or breaks into the system.
• Copies and later uses. If records are exported or shared, deleting the original does not remove those copies. Each use and copy needs enforceable controls.
• Ongoing responsibility and cost. The Town must secure the information, control access, examine search records and verify deletion. Those duties extend to retained nonmatches as well as qualifying matches.

A one-day database could help an investigation begun during that period. Article 22 chooses to limit what is kept: retain qualifying matches and discard nonmatches, subject to applicable law. Access restrictions on a stored record cannot provide the same protection as discarding it.

The limit draws inspiration from nearby New Hampshire, whose plate-reader law requires records to be purged within three minutes, with specified exceptions. It is an enacted example of a firm limit on retention. New Hampshire RSA 261:75-b, VIII.

Article 22 requires immediate discard, with three minutes as the maximum. Tewksbury's qualifying-match rules are its own, and controlling Massachusetts retention requirements still apply.

Article 22 would not require the Town to break a contract already in force when it takes effect.

On September 25, the Police Department announced it would stop using Flock. That was a separate decision. Article 22 would set the rules for whichever plate-reader system the Town uses.

Read what a supplier would need to demonstrate.

No. Ordinary recording alone is expressly excluded by the proposed definition. It reaches systems that turn number plates into computer-readable or searchable data, or derive vehicle attributes to identify, match or search for particular vehicles.

The amendment also protects a person's use of software to read a plate in a specific image obtained while investigating a particular incident. That activity does not constitute operating a plate-reader system. Broader plate-reading or vehicle-search functions remain subject to the definition.

Start with the function, not the location. Article 21 §4.1 excludes ordinary dispatch and emergency operations systems, subject to §4.2’s rules about added surveillance uses. The proposed school exclusion covers people acting for the schools in school capacities. A school resource officer performing police work does not receive that exclusion simply because the work takes place at a school.

When death or serious physical injury is at stake, Article 21 provides an emergency route. A department head or designee must believe in good faith that the danger requires the surveillance use. Use must end when the emergency no longer requires it, be reported to the Select Board in writing within seven days of starting, and not infringe lawful protected activity. Section 6.3 is not a general exception for every urgent request.

Article 22 still governs plate readers. It permits qualifying alerts, including vehicles associated with missing or endangered people. Urgent voluntary sharing with another police agency still requires a written request before access, individual Town review and the required lawful decision. Legal process, legally required disclosures and specified prosecution uses remain separately protected. Receiving school video and ongoing police access raise different questions: read the school-sharing answer. The Town would need emergency procedures that meet these requirements.

Implementation may require technical work, contract changes or changes to equipment. The cost will depend on the systems the Town uses and what changes they need to meet the requirements.

Residents would receive something concrete for that work: an inventory, public approval decisions, continuing reports and an independent examination of access records for all covered systems. Article 21 requires approval findings that weigh benefits, costs and alternatives, followed by annual reporting of each system's cost and funding source. Surveillance spending should be open to that scrutiny.

Article 21’s prohibitions apply when it takes effect. Article 21 requires the Town Manager or written designee to file an inventory of covered systems within 90 days after the bylaw takes effect and submit existing systems for approval within 180 days. If a system is not submitted on time, or is not approved within 180 days after submission, authority to continue using it expires and the Select Board must take up continued use at its next meeting. Existing contracts follow the protections described below.

After approval, a new purpose, manner or location of use requires further approval. Article 22 requires existing covered plate readers to conform to its configuration rules within 90 days after it takes effect or cease operation. Neither article requires breaching an existing agreement. Article 21 requires seeking a conforming amendment or lawful exit and reporting the result; Article 22 requires exit to the extent permitted by law and prohibits renewal of a nonconforming agreement.

The deadlines run from effectiveness, following the statutory Attorney General review and publication or posting process.

• Within 90 days: Article 21's inventory must be filed with the Select Board. Existing plate readers must meet Article 22's Section 3 or cease operation, subject to its existing-contract provision.
• Within 180 days: Article 21's implementing regulations are due after a public hearing, and existing covered systems must be submitted for approval.
• Within 180 days after submission: each existing system must obtain approval. Missed submission or approval deadlines end continued-use authority.
• Ongoing: covered acquisitions, new uses and outside agreements require advance approval. Public reports and independent examinations of access records occur annually.

Section 6 decisions occur in an open meeting after at least fourteen days of public posting. Article 21 separately requires hearings on regulations and annual reports. A delay in regulations does not excuse compliance.

The Town Manager or a designated official must arrange the annual independent examination. The Select Board must hold a public hearing before adopting implementing regulations.

The Town must establish lawful retention procedures. The Select Board’s regulations would set practical details, including report formats and approval procedures, and must follow the bylaw’s requirements.

Missing information must be disclosed and explained. If required access, query or disclosure records cannot be produced, Article 21 requires the Select Board to take up that system's continued operation at its next meeting. Residents would gain a public process for demanding answers and holding the Town to its standards.

The right to enforce the rules is deliberate. Article 21 §11.3 and Article 22 §7.1 state that any violation “constitutes an injury” and permit any person to bring an action in a court of competent jurisdiction. The listed remedies are an order to stop or correct unlawful conduct, a declaration of legal rights, or an order requiring performance of a legal duty. Courts decide whether the legal requirements for a particular action are met.

That provision can lead to litigation and defense costs even when the claimant is not seeking compensation. The articles themselves create no damages awards, attorney-fee awards or fines; other applicable law remains in force. The purpose is enforceable compliance: residents need a remedy when required protections are ignored.

Under the proposed amendments, the articles’ evidence exclusions apply to proceedings conducted by the Town, not state or federal criminal trials. They also permit evidence to establish or remedy a bylaw violation. Rules governing admissibility in court, discovery and preservation remain in force.

Deleting a nonmatching capture is a separate question from excluding evidence in court: a destroyed record cannot be retrieved later. Read the later-discovered-crime answer. Controlling retention, legal holds and discovery duties remain applicable. Qualifying matches kept for an ongoing investigation must be available to a criminal defendant under the applicable discovery and preservation rules.

Town Counsel discussed both articles in the draft warrant at the September 15 Select Board meeting. That public review preceded the proposed amendments. The amendments respond to the review and discussion by clarifying ordinary recording, plate-reader scope, Town proceedings and the school exclusions in both articles.

Counsel identified specific issues, including how Article 21’s approval process fits the Town Charter. Read the charter analysis. The September 15 discussion was neither an endorsement of the later amendments nor a ruling that the articles were invalid. Adopted town bylaws also undergo Attorney General review.

Examples include Amherst, Brookline and nearby New Hampshire:

• Amherst: a public approval framework for surveillance technology. Surveillance Oversight By-law, Section 3.59.
• Brookline: a face-surveillance ban with provisions allowing enforcement through the courts. Ban on Town Use of Face Surveillance.
• New Hampshire: a statutory three-minute purge limit, with specified exceptions. RSA 261:75-b, VIII.

Amendments may be offered within the article’s scope, subject to the Moderator’s ruling. The proposed amendments address ordinary recording under Article 21, the plate-reader definition and incident-reading exception under Article 22, “Town proceeding” in both articles, and the school exclusions in both articles.

The Select Board chair expressed an opinion about amendment scope on September 15. That was not a Moderator’s ruling on the later proposed amendments. We support both articles with those proposed amendments; they must be allowed and adopted through Town Meeting’s process. Read the printed-versus-proposed school distinction.

Town Meeting can put residents’ standards for surveillance into law. Article 21 requires public approval, written limits and continuing accountability for the surveillance systems it covers. Article 22 permits alerts for specifically sought vehicles while limiting the accumulation of ordinary travel records.

The proposed amendments respond to concerns about school authority, ordinary recording and the meaning of Town proceedings. We support adoption with those amendments. The decision is whether public approval, verifiable safeguards and enforceable limits should become lasting duties.

On September 15, the Select Board voted 4–0–1 to take no action on Article 21 and 4–1 on a motion not to adopt Article 22. Those votes preceded the proposed amendments described here. Town Meeting makes the decision on these bylaws. Read the distinction between the motions.

Article 21 makes the Town explain benefits, costs and alternatives before approval, then report publicly on use, sharing, costs and violations. That puts accountability into the rules for using surveillance. Read how the Town would implement the requirements.

Vendors change. Technology changes. Town leadership changes. Our safeguards should endure. Public decisions, checkable limits and a way to enforce them are worth making lasting requirements. Make the safeguards more than a promise: vote yes on both articles with the proposed amendments.

Article 21 defines its Town-related reach and includes a provision yielding where application conflicts with authority conferred by general law. That does not justify assuming either that every Housing Authority activity is covered or that the authority is automatically exempt.

The proposed school exclusion expressly names the School Committee and Public Schools; it should not be generalized to another entity. The appropriate question is which entity operates the technology, under what authority, and which specific provision would apply or conflict.

Article 22 §3.1(c) permits retention of the matching capture and alert record for the reason the vehicle was placed on the hot list and any related ongoing investigation. Retained investigative data must be available to a criminal defendant under applicable discovery and preservation rules. Section 6 requires each match, alert and access to a retained capture to be logged and individually attributed so responsibility can be traced.

A real match is not a general permission to build unrelated travel histories or share data through a standing network. The use, sharing and retention limitations still apply.

Article 21 §10.1 expressly includes refining exclusions within the stated categories, technology use policy and impact statement contents, approval procedures, infrastructure, retention and verification requirements for aggregated information, and report formats and schedules. Regulations require notice and a public hearing and must be filed with the Clerk.

They cannot create a new blanket exception that contradicts the bylaw, waive Article 22’s rules or override state law. The distinction is between setting the standard in a bylaw and specifying how to implement it. Delayed regulations do not suspend compliance.

Section 8 bars approving agreements whose incorporated terms can be modified by an outside party without new approval. The incorporated terms apply as of the approval date and must be attached to the agreement.

For systems holding Aggregated Surveillance Information, §7.8 requires data return on request and termination in an open, documented, non-proprietary format. Access to the Town’s own data cannot depend on renewal. Section 7.1 addresses ownership of derivatives and surviving licenses.

The obligations would become conditions on the Town’s agreements under Article 21. Existing agreements follow the transition rules: seek a conforming amendment or lawful exit, and report the result. Changing suppliers should not mean surrendering access to the Town’s own information.

In Commonwealth v. McCarthy, 484 Mass. 493 (2020), the Supreme Judicial Court concluded that the limited extent and use of four readers at the Cape Cod bridges did not invade the defendant’s protected expectation of privacy in the whole of his public movements. It also explained that enough cameras in enough locations could produce a constitutionally significant history.

The decision explains why a history assembled from many public sightings can raise a privacy issue. Article 22 makes a policy choice to limit that accumulation. McCarthy did not decide the constitutionality of Tewksbury’s deployment, set a three-minute rule or review these articles. Read the court opinion.

A series of observations may reveal routines, associations or visits that no single observation explains. A vehicle record is not proof of who was driving, and an inference can be wrong. The concern is what an identifiable record can reveal or be used to infer.

As a simple hypothetical, repeated sightings near a workplace and another location could suggest a routine. Article 21 gives information revealing identifiable activities over time additional controls. Article 22 limits the accumulation of nonmatching plate records. People should not have to do something wrong before their everyday movements deserve protection.

Article 21 §4.2 addresses how an otherwise excluded system is used or configured. Section 6.1(b) requires approval for a purpose, manner or location not previously approved. An update enabling new tracking or analysis can therefore bring a system under Article 21 or require new approval.

A routine security patch is not automatically a new surveillance use. The actual configuration and approved scope matter. The Town would need a process for detecting feature changes, reviewing them and preventing unapproved use. Section 5(f) also requires independent verifiability of vendor configuration claims.

Article 21 applies to people acting for or on behalf of covered Town entities, including contractors and volunteers. Purchase, lease, loan, grant, donation, pilot and free trial arrangements are included. A contractor’s system can therefore be covered even if the Town does not own it.

For a drone, ask what it collects, the purpose and location of the use, which exclusions apply, and what was approved. An incidental image during an approved use is not automatically a new use; repurposing the footage or adding tracking can present a different question. A drone is not automatically prohibited merely because its capabilities bring it within oversight.

Applicable information-handling duties must be written into the Town’s agreements. Specifications, training and contract administration put those duties into practice. Using a contractor or accepting free equipment does not avoid the rules.

A phone or other device can broadcast identifiers even when its user is not actively providing information to the Town. Article 21 §5(a) covers passive radio-network scanners, long-range Bluetooth scanning and other systems collecting identifiers for the purpose of identifying, counting or locating people or their devices. That is different from ordinary cybersecurity used solely for its excluded purpose.

“Passive, indiscriminate” also describes the broader concern in Article 21’s purpose. Its operative approval test is in §6.2: officials must assess the particular system as configured in its use policy. The article sets no numerical count of observations; regulations and written findings apply the standard. Ordinary building-security recording has the proposed §4.2 protection when used solely for its excluded purpose.

Proposed Article 21 §3.4 categorically excludes the School Committee, Public Schools and people acting for them in school capacities. School-capacity uses of campus video, safety software, school network monitoring and bus-location applications fall within that exclusion. Article 21’s employee-discipline provisions likewise would not apply to excluded school-capacity activity. No provision-by-provision assertion under §3.3 is required.

Other applicable law continues to govern school technology. A school resource officer’s role and activity matter: working on a campus does not by itself turn the officer’s police work or police systems into excluded school-capacity activity. Read how the rules apply to Police and Fire response at a school.

A school sharing a selected incident clip, a standing agreement for incident-specific transfers, and live or searchable access across systems raise different questions. The proposed school exclusion does not change student-record law or other rules governing what schools may disclose. Read Article 22’s school exclusion.

A Board-approved agreement and use policy can cover categories of lawful incident transfers without predicting each future incident. Staff can carry out transfers within that scope. Section 6.1(c) also covers oral agreements and has no general exception for unapproved one-off agreements, so the particular arrangement must fit the applicable approval rules.

Article 21 §7 adds duties when information can reveal identifiable activities over time. Article 22 §4 governs outward sharing of plate-reader data, not all ordinary school records. For Police and Fire responding to an emergency, read the separate emergency route.

The list must identify specific vehicles for individualized, documented reasons, including a stolen-vehicle report; association with a person subject to an outstanding warrant or who is missing or endangered; or an officer’s documented determination that the vehicle is relevant and material to a particular criminal investigation. Those criteria govern whether an NCIC, BOLO, AMBER or Silver Alert list qualifies.

The Town determines which lists are used and oversees them. Entries must be removed when their documented basis lapses. Section 3.3 requires a written determination that an outside list’s entry criteria meet §2.3, not separate Town certification of every entry. This is continuing oversight: comparison must stop if the list ceases to meet the standard. The Town records each list, its source, the determination and dates of use.

A label such as NCIC, BOLO, AMBER or Silver Alert does not by itself establish that every feed qualifies; its entry criteria must meet the rule. Receiving a qualifying list is also different from sharing Town captures outward, which follows §4. What about a partial plate? The text does not expressly resolve incomplete or wildcard entries. An entry must still identify a specific vehicle for an individualized, documented reason. Section 3.2 separately prohibits vehicle analytics beyond plate characters and issuing jurisdiction; a partial-plate scenario needs to be assessed against those requirements.

Before acting on an alert, an officer must visually confirm that the plate on the vehicle matches the capture and confirm that the hot-list entry remains current. These are safeguards against acting on a misread plate or stale entry.

A valid alert is information for an officer to assess, not automatic authority to stop a vehicle. Article 22 §5.1 requires both confirmation steps, and all other legal requirements for a stop still apply.

The emergency authority begins with the good-faith belief of a Town entity head or designee that danger of death or serious physical injury requires the use. The text requires a written report to the Select Board within seven days of commencement.

Implementation should assign responsibility for reassessing the emergency, stopping use and reporting. The article names the official who authorizes the use but does not separately assign that continuing assessment. Article 21’s emergency clause does not waive Article 22’s sharing rules.

Article 22 requires destruction that makes nonmatches unrecoverable. Its §6 logs matches, alerts and access to retained captures; it does not prescribe a standalone purge-testing protocol. Article 21 §5(f), if also adopted and applicable, requires independent verifiability of vendor claims about retention and other settings. Its §5(e) requires complete access records.

A practical verification plan could use controlled test captures, documented data flows and examination of storage, indexes, exports and backups. These are implementation options for checking whether deletion works.

Deletion would be an automated process. People must establish, test and periodically check that it works. Article 21’s verification requirement is one reason to support both articles.

Article 22 §7.2 preserves requirements of state and federal law. Section 3.1(c) expressly addresses discovery and preservation for retained investigative matches. Article 21 likewise preserves required retention in §7.7.

Implementation must identify the applicable record series, minimum retention periods and lawful disposal procedures, including for electronic records. The classification of a particular transient capture requires that legal assessment. The article does not authorize destroying a record that controlling law requires the Town to preserve.

New Hampshire demonstrates an enacted retention limit, but Massachusetts preservation requirements govern here. The linked Secretary of the Commonwealth guidance and the articles’ savings clauses explain that boundary.

The annual examination covers access, query and disclosure records for covered surveillance systems. Article 21 §9.2 refers to both §5(e) and §7.3, so this accountability is not limited to systems holding the special aggregated-information category. Excluded systems remain excluded.

The examiner must be qualified and independent of operating or supplying the system. The text allows a suitable person or firm; it does not automatically require an outside firm or make an existing financial auditor qualified for the work.

The Manager or written designee must ensure the examination happens and include the results in the annual report. Implementation must establish its scope, staffing or procurement and cost. Residents get the findings as part of the public report.

The proposals specify outcomes such as access records, verifiable settings, timely deletion and independent examination. They do not require a named security-event monitoring platform or brand.

The Town must assess whether existing tools and staff meet the duties and what additional tools or services are needed. The cost and staffing answer explains the work and the information still needed.

A supplier must demonstrate the whole requirement, including collection capabilities, matching, deletion, list management, outside access and usable records. Changing one retention setting or limiting who may search is not proof of compliance with the complete articles.

Article 21 §5(e) requires complete access, query and disclosure records, including non-Town users. Section 7.3 adds specified fields for systems holding aggregated information. Section 9.3 requires a public account of missing records and a Board discussion of continued operation.

Residents should set the standards, and suppliers should show how they meet them. A product demonstration must address the complete requirements; a price quote must include the work needed to comply. Vendor-neutral wording gives each supplier the same test without certifying an unexamined product.

The entity must identify the specific general-law authority, the bylaw provisions it says cannot apply and the extent of the conflict. That explanation appears in the annual report. The text requires documentation; it does not expressly authorize the Board to grant or deny the assertion.

The proposed school exclusion applies directly, without requiring a written assertion under §3.3.

The charter gives the Manager purchasing and administrative responsibilities. It also directs the Manager to administer bylaws and permits additional duties consistent with the office. Article 21 §6 establishes a public decision on permitted acquisitions, uses, locations and outside agreements. Existing covered systems also need approval. The Board sets the use policy; the text does not appoint it as the purchasing officer or contract signatory.

Our case is that Town Meeting can establish a defined privacy review alongside professional administration. Existing Tewksbury contract bylaws already place approval and lease conditions on purchasing. Those are useful local examples, although their conditions are not identical to Article 21’s substantive approval process.

Counsel’s earlier public discussion identified potential conflicts and also allowed for reading the provisions together harmoniously; it did not declare the articles unlawful.

Article 21 §6.2 requires findings on benefits and costs, civil rights, less costly or less intrusive alternatives, discriminatory or viewpoint-based deployment, disproportionate adverse effects and indiscriminate retention. Approval takes the form of a written use policy with defined limits.

Regulations can specify the submission format, impact statement, alternatives analysis and supporting evidence. They must implement the bylaw rather than waive its findings. The text does not require a particular expert or numeric formula. Whether expert assistance is needed depends on the proposed technology and evidence.

Local wetlands review illustrates how officials can make written findings about alternatives. Its standards and evidentiary burden are different. Article 21 supplies its own required findings; regulations provide the submission and review procedures for applying them.

Article 21 makes those limits binding: departments operate within approved purposes, locations, configurations and retention periods. Moving outside that approval can require a new Board decision. Public approval has real consequences, while professional staff carry out the work.

Local permitting and other bylaws offer examples of public standards administered by professionals. Our case is for the same division of responsibility here. The specific relationship between Article 21’s approval process and the charter is addressed in the charter answer.

Article 21 alone would not enact Article 22’s immediate-discard rule for nonmatches. Article 22 alone would not create Article 21’s broader public-approval, reporting and independent-verification framework.

Where both apply, approval under Article 21 cannot waive Article 22’s restrictions. Article 22 has its own definitions, enforcement and transition rules, so it can operate on its own. Read the two together for a particular system: the general oversight duties and the specific plate-reader limits reinforce one another.

Article 22 §2.2 includes images, plate characters, vehicle attributes, location and time, and derived data. Section 3.2 separately limits the kind of system that may be deployed, including analytics and audio restrictions.

Calling a record a “derivative” or “vehicle attribute” does not take it outside the handling rules. At the same time, the definition does not authorize a capability prohibited by §3.2. An integrated product must meet the limits as a whole, including the design and intended operation of the components that make up the system.

Requests and supporting submissions must be posted at least fourteen days before the Board acts in an open meeting. Approval requires written findings and a use policy. Section 9 requires a public annual report, an examination of access records and a hearing on the report.

The Manager or designated official must maintain a complaint process and publicly summarize complaints and outcomes. Regulations and annual reports require public hearings. Acquisition and use approvals occur in open meetings with advance posting; §6 does not separately guarantee a hearing or a speaking right at every approval meeting. Residents can use the required public materials to examine requests before the Board acts.

Residents can review posted requests, see the written reasons for decisions and use the required complaint process without organizing a new petition each time. Amending the bylaw itself or challenging a particular decision follows its own process.

The bylaw sets the standards. Under Article 21, the Select Board must adopt implementing regulations within 180 days after the bylaw takes effect, following public notice and a public hearing. That process provides a place to address technical details and how departments will meet the requirements.

Advice can improve procedures without replacing the protections in the bylaw. Residents can support the standards at Town Meeting and participate in the public process for implementing regulations.

The Police Department supplied records for the earlier Flock inquiry. In her September 14 letter, the School Committee chair thanked Mackey for reviewing both articles with her and proposed school-exclusion language. Town Counsel discussed the articles at the September 15 Select Board meeting.

The proposed clarifications address ordinary recording, plate-reader scope, evidence rules and school exclusions. Further operational work is needed to identify the Town’s covered systems, their costs and the changes needed to meet the requirements.

Residents can set the standards while technical and legal review continues. Article 21 assigns responsibility for inventory, approval, regulations and reporting. That gives implementation clear duties and makes the results accountable to the public.

Section 2.04.020 distinguishes official board routes from the right of an individual member or voter to submit an article under the General Laws process. A disagreement with a board majority does not, by itself, make that route unauthorized.

A petition brings the question to Town Meeting; it does not claim a board’s endorsement. The proposal’s substance and consultation record remain open to scrutiny. Residents have the right to consider and decide it through the petition process.

Signers and other voters can ask questions, assess the proposal and decide their position at Town Meeting. Amendments must remain within the permitted scope, subject to the Moderator’s ruling and Town Meeting action.

Article 21 provides technology oversight, while Article 22 sets plate-reader limits regardless of supplier. Residents can judge that scope and the proposed amendments when deciding how to vote.

Tewksbury’s warrant-posting bylaw expressly anticipates bylaw articles longer than three standard warrant pages, with a summary and access to the complete text. Existing substantive chapters also run to many pages.

A vehicle sought for an individualized, documented reason can be put on a qualifying list. Future detected matches can generate alerts and be retained for the listed reason and related investigation. The rules apply whether the relevant incident occurred here or elsewhere.

A new lookout entry cannot recreate a capture already discarded. Read the later-crime example. The case for this boundary is straightforward: the possibility of future usefulness should not make everyone’s ordinary travel a continuing police search record.

The relevant question is what a system does: ordinary recording, searchable plate conversion, vehicle-attribute analysis, biometric identification or another covered function. The proposed amendments explain those boundaries in the text. Procurement would require evaluation of equipment against the actual requirements.

Professional equipment can be used when its functions, configuration and approved use meet the rules.

Section 5(c) covers location histories, device identifiers and personal information about identifiable people where the Town could otherwise obtain it only through legal process issued on its application. This prevents purchases that bypass required legal process; it does not ban every ordinary data purchase.

Section 5(h) separately restricts searches of outside surveillance-data pools to specifically identified data under the stated agreement or legal-process conditions, with attributed, recorded purposes. Sharing nothing outward would not excuse bulk querying inward.

A summary count that cannot reveal an individual’s activities is different from person-level records with names removed. The latter can sometimes remain linkable through other information. The article uses that distinction in §2.5.

Its term “Aggregated Surveillance Information” means information revealing identifiable activities over time, not simply a harmless statistical total. Section 7.4 does not permit model training or shared stores merely because the output is labeled anonymized. Genuine non-identifying summaries remain publishable under the stated boundaries.

Section 7.9 requires that category to remain in Town custody and control. It permits outside processing only where strictly necessary for an approved service, transient and without outside retention, copying or derivation. Section 7.4 also prohibits shared or multi-tenant stores and common indexes for that information.

The Town must demonstrate that its storage and processing arrangements meets those requirements. Custody, control and handling determine compliance; a “cloud” or “local” label alone does not. Article 22 separately prohibits transmitting nonmatching captures to a person or system outside Town control.

Rules about custody, authorized sharing and retention are distinct from a statutory exemption from public access. Article 21 preserves controlling state and federal requirements. Its public reporting also serves a different purpose from releasing individual-level surveillance records.

For covered activity, violations must have consequences, which may include retraining, suspension or termination. The text requires due process and respect for collective bargaining agreements; it does not mandate automatic firing. Neither article itself creates fines, damages awards or attorney-fee awards.

For covered activity, both articles also provide court enforcement to require compliance. Read the injury clause, available remedies and litigation-cost explanation.

Amherst supplies an oversight example, Brookline a narrower face-surveillance ban and enforcement example, and New Hampshire an enacted retention limit. Tewksbury’s existing code supplies local comparisons for data rules, regulations, technical settings and oversight.

Article 21: the September 15 motion was to take no action, and the announced vote was 4–0–1. Article 22: the motion was clarified as not to adopt, with four votes for that motion and one against. Those are different actions; describing both as “no recommendation” would erase that distinction. These votes preceded the proposed amendments. Watch the September 15 Select Board meeting.