Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Contracts Procurement topic
No spam. Unsubscribe anytime.
Finance committee approves most contracts, defers several and seeks clarity on Gilbane subcontractor requirements
Summary
The committee approved a tie-bar motion to pass the bulk of vendor contracts but excluded several items for further review; board members asked for explanations of why the Gilbane general contractor requested subcontractor financials and requested policy changes to boost Detroit-headquartered contractor participation.
The finance committee combined and approved most contract items on the meeting agenda but pulled several for separate review and sought follow-up on procurement language the board said may disadvantage Detroit-headquartered subcontractors.
The vote matters because decisions about contractor requirements and subcontractor vetting affect local small and minority-owned firms’ ability to participate in large district capital projects.
The committee adopted a tie-bar motion to approve contract items 5.01 through 5.21 with exceptions; members amended the motion to exclude items 5.09, 5.13, 5.17 and 5.18 pending further information. During discussion board members asked why Gilbane, a general contractor on district projects, had requested audited financial statements and organizational charts from prospective subcontractors. One board member (Deborah) said such requirements can unintentionally bar smaller Detroit-headquartered firms and asked staff to explain the rationale and propose policy changes.
Staff described possible reasons the general contractor requested detailed financial information (bonding/capacity checks to secure subcontract performance), and said the district’s owner’s representative (client Moran RealPoint) helps coordinate vendors and pricing. Board members pressed for a written explanation from Gilbane and asked policy committee referral to consider procurement language that would give weighted value to Detroit-headquartered companies and avoid redundant documentation when firms are already certified by state or city programs.
Separately, the committee approved specific contracts that had been pulled for individual votes. For example, contracts for fencing repairs and a roof replacement at Moses Field (items 5.09 and 5.18 were discussed and processed separately) were explained and approved for moving forward; paving and other grouped contracts also advanced.
Committee members asked staff to return with documentation explaining why financial disclosures were requested, and to present options for procurement language that would encourage local participation without exposing the district or prime contractors to undue risk. The committee did not change procurement policy in this meeting but asked for a policy-level follow-up and vendor-sourcing analysis.
