Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Cip Submission Form topic
No spam. Unsubscribe anytime.
Litchfield CIP committee recommends clearer submission form, asks for engineering estimates and funding fields
Summary
At a meeting, the Litchfield Capital Improvement Program committee reviewed its capital-project submission form and recommended relabeling date fields, adding funding-source and lease-term fields, and requiring attached, dated engineering or contractor estimates to reduce later rework.
The Litchfield Capital Improvement Program (CIP) committee reviewed and proposed revisions to its capital-project submission form, emphasizing clearer date fields and more consistent cost documentation.
Committee members said the top-row date labels — currently phrased as "year first scheduled" and "year needed" — cause confusion and proposed replacing them with a single "year requested" field and a checkbox or short explanation for prior submissions. One committee member advised, "Year requested is all we really need on that one," arguing departments should indicate when they want the project on the plan rather than leaving multiple ambiguous date fields.
The committee also recommended adding explicit prompts for funding source (grant, bond, department funds) and for whether engineering or professional cost estimates are attached. Members urged that any attached quotes include a date so the committee can identify outdated estimates later: "Get the date of the quote, the last time it was updated, and go from there," one participant said.
Other suggested changes included adding a place to list lease terms when projects are lease-related, converting some open-text boxes into checklists or dropdowns to improve consistency, and reducing the overall length of the form so applicants provide the most relevant information up front. Members discussed automating parts of the form (for example, auto-populating today's date or providing department dropdowns) but noted the town may lack the technical resources to implement a full digital workflow immediately.
Committee members agreed the narrative justification section should remain as the place for fuller explanations (compulsory vs. voluntary work, life-safety concerns, urgency), while the form itself should prompt for the specific follow-up information the committee uses during its review. They asked a volunteer to review the previous year’s minutes to extract the questions staff typically ask so those items can be added to the form as prompts.
Procedural notes: the committee approved the May 4 minutes by voice vote with three in favor and one abstention (one member said they were not at the May 4 meeting). Chair Pete Stone postponed adoption of the bylaws until fuller participation at the next meeting. The committee cited presentation dates to be finalized (members referenced an August 24 presentation slot and school presentations on September 14) and planned to circulate refined form language to departments before the August meeting. The meeting was adjourned by voice vote.
