Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Rfp Peabody topic
No spam. Unsubscribe anytime.
Concord subcommittee narrows RFP scope, asks consultants to cost Peabody and other consolidation options
Summary
The subcommittee agreed Feb. 5 to include Peabody in a consultant RFP to get independent cost estimates to bring candidate buildings up to code and, where feasible, rough renovation estimates. Members chose Paul's space-bucket spreadsheet as the RFP starting point and set internal deadlines for the report to reach the Feb. 20 packet.
Get email alerts on the Rfp Peabody topic
No spam. Unsubscribe anytime.
Mary, the acting chair of the Land Use Working Group’s municipal office consolidation subcommittee, told members at their Feb. 5 meeting that the group’s next step is an RFP asking consultants to verify cost assumptions in the draft report and to provide firmer estimates for bringing candidate buildings up to code. The committee agreed the RFP should give consultants the committee’s space-requirement buckets and building blueprints so firms can map uses and cost the code upgrades needed for each use.
Paul, who compiled the subcommittee’s space spreadsheet, said that document — which lists program and staff space building-by-building and totals roughly 47,000–48,000 square feet plus two ~7,500-square-foot playgrounds — is the best starting point for the RFP. “Giving them these buckets of space, I think, is what we need,” Paul said, and members agreed the phase-1 deliverable should be conceptual rather than a full detailed space plan.
The committee discussed whether the RFP should ask only for code-upgrade costs or also for renovation estimates. Mary said the subcommittee already has renovation assumptions from a consultant (Judith) in its model but needs an independent assessment of code-related costs. Members agreed it is acceptable to include renovation costing in the RFP if doing so does not materially increase price or delay delivery; the consultants can indicate whether they can provide both code and renovation figures with the same scope and fee.
On Peabody, members stressed two points: some in the community view Peabody skeptically, and Peabody’s value is already embedded in the committee’s financial model. Carrie noted community concerns and recommended limited, targeted due diligence so the public can see independent evidence on Peabody’s renovation cost. Mary summarized the committee’s view: even if Peabody is unlikely to be the consolidation site, it should be included in the RFP as a costing exercise to verify the model. The subcommittee formally agreed to include Peabody in the RFP to obtain firmer cost estimates.
The group also agreed that one member should be available for informal, preliminary conversations with local architects to peer-review scope and reduce translation issues before issuing the RFP; Paul was nominated and accepted. The committee asked staff to attach the group’s space buckets and the available building blueprints to the RFP and to ask consultants to identify which assumptions would require more detailed follow-up in a phase 2 study.
The RFP decision is intended to refine the subcommittee’s financial model and give the larger land use working group independent evidence about renovation and code-upgrade costs before the committee’s Feb. 20 presentation.

