AB 1746 directs California counties to inform CalWORKs applicants and recipients about paid childcare and to provide a specific childcare request form (CCP‑7 or successor) at enrollment and at several later contact points. The bill requires counties to verify that childcare is needed for participation in a program activity and to confirm childcare is authorized and secured before forcing participation in mandatory activities.
The bill sets concrete operational rules: what must appear on the CCP‑7, a 10 working‑day county decision window on requests, a 30‑day rule for requesting reimbursement to secure retroactive payments, bilingual notice requirements, and a route for the Department to update forms and issue an all‑county letter while regulations are pending. For county administrators, providers, and compliance officers, AB 1746 creates clear procedural timelines and new front‑line duties that will affect intake, case management, and IT workflows.
At a Glance
What It Does
Requires counties to provide a CalWORKs childcare request form (CCP‑7) at application and several subsequent events, verify childcare necessity and authorization before requiring participation in mandatory program activities, and decide CCP‑7 requests within 10 working days. It also limits retroactive payment eligibility to requests submitted within 30 days of the first day services were provided.
Who It Affects
County welfare departments (intake, eligibility, caseworkers, IT/SAWS teams), CalWORKs applicants and recipients with childcare needs, childcare providers and contractors who may verify care, and local childcare resource and referral programs named on the form.
Why It Matters
The bill removes an administrative gray area by standardizing notice and request procedures and imposing deadlines that could speed access to childcare or, if poorly implemented, create new chokepoints. It also shifts operational workload to counties and their IT systems while codifying a 30‑day reimbursement window that is decisive for recipients seeking retroactive payment.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 1746 makes the CCP‑7 (CalWORKs childcare request form) a routine part of CalWORKs intake and case contacts. Counties must give the form when someone applies for benefits and again at specific subsequent events — for example, on approval, with eligibility certificates, on semiannual reports, and when welfare‑to‑work plans are signed or assigned.
The bill also instructs counties to provide the form at orientation and whenever a participant reports new or increased participation or income, where automation permits.
The form must tell people that paid childcare exists to enable employment or welfare‑to‑work participation; provide the local childcare resource and referral program’s contact; describe available help finding a provider; require recipients to notify the county when they need childcare; and spell out the rule that recipients must request a subsidy within 30 days of the first day services are received from each provider to receive full reimbursement. The bill also requires counties to explain retroactive payment rules on the form.On the operational side, counties must verify whether childcare is needed for a participant to attend a program activity and ensure childcare authorization and that care has been secured before requiring participation in mandatory activities.
That verification can be established by the participant, the childcare contractor, or the provider. After a CCP‑7 is submitted, counties have 10 working days to approve or deny it.
The department must update CalWORKs notices and forms, translate them under the Dymally‑Alatorre Act, and may issue an all‑county letter to implement these changes while formal regulations are written.
The Five Things You Need to Know
Counties must give the CCP‑7 childcare request form at application, at approval, with annual certificates of eligibility, on semiannual reports, when signing original or amended welfare‑to‑work plans, and on welfare‑to‑work appointment notices.
The CCP‑7 must state recipients must request a childcare subsidy within 30 days from the first day services are received from each provider to be fully reimbursed; requests outside that window risk denial of retroactive payment.
A county must approve or deny a submitted CCP‑7 within 10 working days.
Counties must verify that childcare is needed and that services are authorized and secured before requiring a participant to join any mandatory program activity; verification may come from the participant, a childcare contractor, or the childcare provider.
The Department of Social Services must modify notices and may implement the bill’s changes by all‑county letter pending formal rulemaking; forms must comply with the Dymally‑Alatorre bilingual translation requirements.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Informing participants and verifying childcare before mandatory activities
This subsection requires counties to tell applicants and recipients about childcare availability when they enroll and whenever a participant expresses a need. Crucially, it obligates counties to verify whether childcare is necessary for a participant to engage in a program activity and to confirm both authorization and that care is secured before requiring attendance in any mandatory activity. Practically, caseworkers must pause enforcement of attendance requirements until verification is recorded; the bill allows the participant, the childcare contractor, or the provider to supply verification, which reduces sole reliance on county field checks but raises questions about documentation standards.
When to provide the CCP‑7 and what it must say
The bill lists specific triggers when the CCP‑7 (or successor) must be given: application, benefit approval, annual certificates of eligibility, semiannual reports, original/amended welfare‑to‑work plans, and welfare‑to‑work appointment notices. The form must inform recipients that paid childcare exists to support employment and program participation, give local childcare resource/referral contact information, explain assistance finding providers, require prompt notification of need, spell out the 30‑day request rule for full reimbursement, and summarize retroactive payment rules. This standardized content creates a single reference point for recipients and county staff, reducing variation in client messaging across counties.
Ten‑working‑day county decision deadline
Counties must approve or deny a CCP‑7 within 10 working days of receipt. That deadline creates a hard processing target and will affect eligibility workflows: caseworkers may need triage procedures for urgent requests, and counties must track business‑day deadlines. The statute does not add an explicit appeals timeline here, so denial handling will follow existing CalWORKs administrative appeal procedures unless the department issues additional guidance.
Additional timing, automation caveat, and expanded notice events
The statute ties some notice obligations to the Statewide Automated Welfare System (SAWS), saying the form will also be provided at orientation and when assigned to activities or when reporting new/increased participation or earned income, commencing either January 1, 2021, or when SAWS can automate the change — whichever is later. That language makes certain distribution requirements contingent on county IT capabilities and triggers coordination between counties, SAWS consortia, and the department.
Bilingual requirements and signed acknowledgment
The written notice must comply with the Dymally‑Alatorre Bilingual Services Act, so counties must provide translated forms where required. The bill also requires asking applicants and recipients to sign a copy acknowledging receipt; the signed form must be retained in the client file with a copy provided to the client. This creates a discrete recordkeeping duty for counties and an audit trail for whether recipients were informed.
Retroactive payment limits, departmental form updates, and interim implementation
The statute limits retroactive payments by refusing to pay for Education Code Section 8351 childcare services more than 30 days prior to a recipient’s initial request for payment if the recipient received the written notice form. The department must work with counties to modify notices and forms to include the new content, make them available at additional touchpoints where feasible, and develop implementing regulations. Until regulations are adopted, the department may use an all‑county letter or similar directive to effect the changes immediately.
This bill is one of many.
Codify tracks hundreds of bills on Social Services across all five countries.
Explore Social Services in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- CalWORKs recipients with childcare needs — The CCP‑7 and verification requirement reduce ambiguity about how to request subsidies and create a documented path to secure childcare before being required to attend program activities.
- Childcare providers and contractors — Clearer notification and a 10‑day county decision window can shorten payment timelines and reduce uncertainty when a provider is asked to accept a CalWORKs family.
- Local childcare resource and referral programs — The statute explicitly requires their contact information on the form, potentially increasing referrals and demand for their placement services.
Who Bears the Cost
- County welfare departments — New intake, verification, recordkeeping, translation, and processing demands (including meeting the 10‑working‑day deadline) will increase staff time and require updates to local procedures.
- SAWS consortia and county IT teams — The automation contingency and expanded distribution triggers will likely require programming, testing, and deployment work to insert the CCP‑7 into workflows and client notices.
- Department of Social Services — The department must revise forms, provide guidance, and may need to manage all‑county letters and subsequent rulemaking, which consumes regulatory and stakeholder coordination resources.
Key Issues
The Core Tension
The bill balances two legitimate goals—protecting program integrity and controlling retroactive liability versus removing childcare barriers to participation—but the operational rules (verification flexibility, a 10‑working‑day decision window, and a 30‑day reimbursement deadline) can push outcomes in opposite directions: they either enable timely access to care or, if poorly implemented, create new administrative chokepoints that keep participants from meeting program requirements.
The bill addresses an important barrier to participation—lack of childcare—by formalizing notice and request procedures, but it leaves several operational ambiguities that could undermine its intent. First, ‘‘verification that childcare has been secured’’ is broad: allowing verification from a participant, a contractor, or a provider reduces friction, but the statute does not prescribe acceptable evidence or documentation standards.
Counties will need to decide whether a provider’s verbal confirmation, a signed statement, or proof of payment suffices, and those choices will materially affect how fast participants can be cleared for activities.
Second, the 10‑working‑day approval timeline improves predictability but can also create a de facto pause before participants can begin activities if counties wait to approve childcare. The law does not require provisional authorizations or prioritization for urgent cases.
Third, the 30‑day reimbursement rule protects against unlimited retroactive liability but risks financially penalizing recipients who do not immediately know the rule or who face delays in submitting requests — a common reality for low‑income families. Finally, the automation clause ties several distribution requirements to SAWS capability and includes a 2021 date; that creates implementation variance across counties and exposes the program to inconsistencies depending on local IT schedules.
The department’s authority to use an all‑county letter speeds rollout but also risks uneven local practices until formal regulations clarify open questions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.