Committee sets July distribution, Aug. 14 public meeting for harbor plan draft

Members of a local committee met on June 10 to finalize logistics for releasing a draft harbor plan and to schedule public review. They agreed to send the draft to entities listed as “responsible” or “participating” by July 14, ask for responses by Aug. 1, and hold a hybrid public meeting at 5 p.m. Aug. 14. Staff said they will post a public draft and provide an online comment form for those who cannot attend.

The committee’s work focuses on recommendations for harbor operations, shellfish and eelgrass considerations, and related outreach. Kim (staff member) told the group she would circulate an updated draft and cover materials and said, “I just sent that,” referring to a corrected version of the document. Jeff (committee member) recommended using the same Google form the group used for the eelgrass management plan so online comments feed to the project team. Jack (staff member) reported an extension had already been filed with the state coastal program: “We did just file for an extension, so we’re we’re good on that front.”

Why it matters: the draft identifies parties the plan asks to carry out or help with recommendations and gathers public and stakeholder input before the select board and a formal state review. Committee members emphasized getting input from both named stakeholders and the general public while avoiding needless repeat rounds of review.

Discussion highlights - Responsible vs. participating parties: Committee members debated whether to immediately designate some entities as “responsible” (expected to carry tasks) and others as “participating” (supporting roles). Jeff agreed to help sort the list so each organization would see which recommendations apply to it. Kim said the circulated draft now includes a single combined list and that she would update it to show the two labels before distribution. - Distribution and deadlines: The group settled on sending the draft to listed entities on July 14 and requesting written responses by Aug. 1 to give stakeholders time over the busy summer period. Several members cautioned that departments’ capital submittals and summer schedules could delay responses; one member suggested allowing up to three weeks. - Public meeting format and timing: The committee selected Aug. 14 at 5 p.m. for a hybrid public meeting (in-person with a remote option). Members said microphones will be provided, comments will be recorded, and staff will prepare a one-page flyer and a short summary for responsible parties so they can focus on the recommendations that concern them. - Online comment collection: Jeff proposed repurposing the Google form used for the eelgrass plan to collect comments electronically; the committee agreed this is the simplest way to gather and route feedback. - Appendix, photos and posting: Kim said the plan will include an appendix with background material and that photos may be updated before posting. Committee members said posting a public draft while concurrently soliciting stakeholder feedback is acceptable so long as the team can fold comments into the final version. - Technical and enforcement topics: Committee members discussed operational matters such as dye tablets, pump-out records and enforcement in the harbor. One member noted the harbor master’s office runs the pump-out program and recordkeeping. Another argued for more enforcement and education for visiting vessels: “We just need to enforce it, and we need to be more diligent about it.”

Next steps and timeline Staff will distribute the updated draft by July 14, provide a short summary keyed to each responsible or participating entity, accept committee comments by July 9 (internal review), and request stakeholder responses by Aug. 1. The committee tentatively set its next meeting for Aug. 4 to review feedback and prepare a final draft for the select board. After local approval the plan will enter the state review process, which committee members said normally includes a 30-day public comment period.

Formal actions At the meeting’s close a motion to adjourn was made and seconded and carried by voice vote; members recorded as voting “Aye” included Steve Linebach, Phil, Rachel Freeman and Dave (last name not specified).