Advisory subcommittee refines subcommittee charter and RFP draft for redevelopment; flags deed limits, outreach, and timing concerns

The Town of Concord advisory subcommittee spent the bulk of its meeting refining the subcommittee charter and an initial draft request for proposals (RFP) to guide redevelopment of several town parcels, including the former prison site.

Members agreed on several immediate edits to the charter: remove references to RFQs (the process will use an RFP), replace the phrase "master planning" with "scenario planning" or "concept development planning," and merge Linda's fuller objective language with other key responsibilities. One member cautioned against using the word "development," saying it can give the public the impression a decision has already been made; the group agreed to use "concept land‑use scenarios." Peter (committee member) urged the RFP and consultant work to surface "big ideas"—such as a life‑science center, a clean‑energy hub or university research uses—while emphasizing that themes should emerge from community input and consultant analysis, not be prescribed by the subcommittee.

Timing and procurement: members debated the draft timeline for issuing the RFP and receiving proposals. The timeline under discussion included issuing the RFP on Dec. 3, a site walk/survey milestone in mid‑December, and a proposal receipt date later in December or mid‑January; members noted the schedule, as written, was confusing. Scott (committee member) warned two weeks is typically too short for prime consultants and subconsultants to assemble proposals, and other members suggested a more conservative month‑long response window given the December/January holiday period. Dan (committee member) agreed to add a "prepare RFP" milestone and to clarify the RFP schedule before circulation to the group.

Scope and procurement language: Scott presented a draft RFP that breaks the work into phases—discovery, public engagement, visioning and concept planning, draft zoning ordinance and mapping, and final zoning ordinance amendments—and asked whether consultants should propose phase‑specific fees or a total price. Members agreed procurement and legal counsel should review required contract language and guidance about budget disclosure; several members recommended asking for hourly rates and attachments (GIS, maps) and advised the RFP include a short paragraph of historical/contextual background (to be provided by town staff or linked documents) rather than reprinting all prior materials.

Community outreach and roles: the group discussed whether the visioning consultant should perform community outreach or collaborate with a communications hire the town plans to engage. The consensus was to require collaboration: the RFP should specify coordination with the communications team and allow for hand‑off or shared work. Shannon (committee member) and other members will bring a paragraph from the RFP draft to a community‑outreach subcommittee meeting this week for feedback.

Deed restrictions and feasibility: Linda (committee member) raised concerns about Junction Village, noting deed constraints require a defined percentage of affordable housing and that the deed restriction could materially affect economic‑feasibility scenarios. Peter and others said the RFP should require consultants to account for deed restrictions in feasibility analyses and to include market/economic analysis (Scott requested adding that task to the draft).

Budget and comparables: Dan shared a comparable project example—a 10–12 acre downtown San Diego site—where consultants spent more than $300,000 to reach an advanced product and retained consultants at about $35,000 per month in a later phase. Members flagged that the subcommittee needs procurement officer input about whether to disclose a budget amount or use a "not to exceed" structure.

What happens next: Dan will update the timeline and incorporate agreed edits to the charter and RFP; Scott will incorporate comments into his draft and circulate it for member feedback by the weekend. The subcommittee plans additional review with town staff and procurement counsel before issuing the RFP.

Representative quotes from the meeting: Peter said the RFP should help produce "big ideas" for the site but not preselect a theme; another participant urged avoiding use of the word "development." Dan summarized the administrative approach: the group will draft a first RFP iteration, have town staff draft a short historical paragraph, and provide the group two rounds of review before issuing the RFP.

(Reporting based solely on the subcommittee meeting transcript.)