In several districts I’ve reviewed this year, bilingual teachers get $3,000–$7,500 while ESL-certified teachers get $0–$500, even as policies mandate universal access to language services; what’s the local justification you’re hearing in 2024 contracts? If the work is legally required either way, we’re signaling that ESL expertise is optional — has anyone seen a district buck the trend?
In our 2024 talks, HR framed bilingual as “hard-to-fill” with built-in translation duty, while ESL was a baseline credential — like paying the interpreter and assuming the map reads itself. We countered by costing ACCESS/LPAC hours and won a tiered ESL stipend tied to caseload and compliance tasks; if parity’s a stretch, ask for a small “language access” stipend any ESL lead can claim. Has anyone gotten districts to tap Title III or state bilingual allotments to fund the ESL side?
What I’m hearing is finance leans on dedicated bilingual allotments (e.g., Texas’ BEA: https://tea.texas.gov/finance-and-grants/state-funding/state-funding-division/programs-and-initiatives/bilingual-education-allotment) while ESL gets pieced together from Title III/general funds, so stipends follow the money. Concrete ask: write CBA language for a two-tier ESL differential tied to caseload bands/WIDA service minutes plus a separate hourly pool for translation/parent outreach, so we stop treating ESL as “free” labor. Anyone have sample language that also caps unpaid translation time @Miriam_G?
We got a ‘Language Services Lead’ differential tied to concrete tasks — ACCESS scheduling, LPAC/ELPAC minutes, newcomer intake, family nights — so ESL-certified folks who do the lift see $1–2k even if the district won’t brand it an ESL stipend. Legal bought it as a compliance duty differential; @rclark82, seeing admins bite on that framing?