Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Pilot Reporting Student Yield topic
No spam. Unsubscribe anytime.
Council hears competing views on PILOT reporting and pupil‑yield data collection
Summary
Council members and stakeholders debated CB45, which would require DHCD to report student yields from pilot (PILOT) housing projects; housing advocates warned of privacy and administrative burdens and urged broader data collection across all new developments, while supporters said targeted reporting is needed to inform council decisions about pilot agreements.
Council Bill 45, introduced June 15, seeks to add student‑yield reporting to the Department of Housing and Community Development’s annual report for pilot (payment‑in‑lieu‑of‑taxes) housing projects. Proponents argued the extra data would help policymakers understand how pilot projects affect school enrollment; opponents cautioned the proposed mechanism would impose privacy and administrative burdens and recommended the Howard County Public School System (HCPSS) as a better data source.
The issue in brief: Council members said prior pilot approvals have leaned on projections, not post‑occupancy enrollment data. Supporters of CB45 said tracking student yields from pilot projects would create an evidence base for future decisions. Jackie Yang of the Housing Affordability Coalition asked whether the bill’s focus on pilots, rather than all new or redeveloped housing, would miss the larger picture. She and others suggested HCPSS already holds the enrollment data and could provide anonymized counts more efficiently than DHCD.
Housing providers weigh in: Jennifer Leonard, policy director for Enterprise Community Development, opposed CB45 as written. She urged a countywide approach to data collection — including market‑rate and single‑family development — and said research shows school‑aged child counts in affordable housing are not necessarily higher than in single‑family homes. Enterprise also recommended HCPSS as the appropriate source for pupil‑yield analysis because it maintains student addresses and enrollment records.
Supporters’ rationale: Brent Loveless and other public speakers said pilot projects sometimes receive large public incentives and the council needs post‑occupancy data to compare projections against outcomes and to understand impacts on school capacity. Council members and advocates discussed privacy protections, the mechanics of data sharing and whether the proposed reporting could be redesigned to rely on school system analyses such as a pupil‑yield study.
What’s next: The council asked questions about administrative burden and data sources and signaled the topic may require further work‑session discussion and technical fixes before any ordinance vote.
Ending: No vote was taken; witnesses urged either expanding the bill’s scope or designating HCPSS as the reporting partner to avoid duplicative burdens and protect student privacy.
