Back to playbooks

Module: Childcare (Capacity + Stability + Real Schedules)

Purpose: reduce the monthly squeeze by making childcare easier to find, easier to keep, and closer to the hours families actually live by.

This module is designed to be runnable by normal people in small weekly sprints.

What is happening (1-2 sentences)

Childcare squeezes families, workers, and providers at the same time.

The visible pain is price and waitlists. The deeper problem is fragile capacity.

Why it is happening (mechanism, plain language)

Childcare slots are constrained by staffing ratios, provider stability, and schedule mismatch.

That means the bottleneck usually lives in one of three places:

A) licensing and opening new capacity
B) staffing and infant-room math
C) wraparound and nonstandard-hour access

If you do not know which one you are dealing with, you will ask for something too vague to move.

The capacity math (tiny version)

• ratios mean you cannot stretch infant care cheaply
• one worker leaving can shut a room
• if reimbursement and paperwork are unstable, capacity disappears right when families need it

What good looks like (principle)

A better childcare system has:

• more licensed slots where families actually need them
• infant care that providers can afford to offer
• subsidy rules that do not punish a raise or an extra shift
• pre-K and wraparound hours that match real work schedules
• less paperwork drag for providers

Childcare bottleneck triage

Pick one bottleneck for the sprint:

Bottleneck A: Licensing throughput

Run this when providers keep saying the process is slow, repetitive, or hard to navigate.

Bottleneck B: Staffing and retention fragility

Run this when rooms close because the staffing math is broken, especially for infants.

Bottleneck C: Schedule mismatch

Run this when care exists on paper but not at the hours families actually need.

Default plays (recommended)

Default Play A: Licensing timeline and provider help desk

Run this when capacity is stuck in the approval process.

One Ask (template): Publish childcare licensing timelines monthly, create a provider help desk, and cut median approval time by 20% within 6 months.

Minimum components:

• monthly licensing dashboard
• named help desk or navigator
• duplicate-form and duplicate-inspection review
• published service-level targets

Why it wins: It is measurable, operational, and easier to move locally than a giant funding ask.

Default Play B: Real-schedule access

Run this when the system assumes everyone works banker hours.

One Ask (template): Map evening, weekend, and gap-hour childcare capacity, then pilot wraparound support in one high-shift corridor or district.

Minimum components:

• hours-gap map
• partner list
• pilot location
• simple reporting on slot creation and usage

Why it wins: It makes the mismatch visible and creates a concrete implementation test.

Definition of Done (every module sprint)

At the end of any Childcare sprint, you should have:

1. One ask
2. One target map
3. One 1-page ask memo (250-400 words)
4. One 90-second testimony script
5. One scoreboard stub (3-5 metrics + data source)
6. One follow-up date
7. One public-record step if ignored

Target map (who can say yes)

Local targets

• licensing office lead or county regulator
• county human services
• school district early-learning or wraparound lead
• city or county executive budget staff
• local workforce or economic-development office

State targets

• state childcare licensing agency
• subsidy administration office
• legislative early childhood committee chair
• state education or human services agency

Implementation partners

• major shift employers
• nonprofit providers
• school districts
• provider associations and parent groups

Receipts stubs (what to gather before you argue)

You only need a few items to build shared reality.

Licensing / throughput:

• median licensing timeline if available
• steps in the licensing workflow
• provider complaints about duplicate forms or inspections

Capacity / staffing:

• infant-slot counts by area
• closure days or classroom shutdown patterns
• turnover or vacancy proxy

Schedule mismatch:

• map of evening, weekend, and gap-hour care
• major shift-employer clusters
• school wraparound availability

Escalation ladder (what to do when ignored)

Level 1 - direct ask

• email agency lead + elected sponsor with one-page memo

Level 2 - office hours

• ask who owns implementation and where the throughput or pilot language should live

Level 3 - public record

• testimony at county, school, or agency meeting

Level 4 - accountability move

• ask for workflow documentation, wait-time reporting, or budget detail

Level 5 - budget / rule change

• add capacity funding, navigator support, or reporting requirement

Scoreboard (choose 3-5 metrics)

Pick a small set that matches your play.

If running Play A (licensing throughput)

• median days from application to approval
• number of providers in queue
• duplicate-touch or duplicate-inspection count
• help-desk response time
• new slots opened

If running Play B (real-schedule access)

• evening and weekend slots by area
• wraparound participation
• pilot slot utilization
• closure days
• family wait time by hour type

If working staffing / infant fragility

• infant slots available
• provider turnover or vacancy proxy
• closure days
• subsidy processing time

60-minute Childcare Sprint (minimum viable)

If you only have an hour:

1. 10 min: pick licensing, staffing, or schedule mismatch
2. 10 min: build your target map
3. 20 min: write the one-page ask memo + scoreboard stub
4. 10 min: send two emails
5. 10 min: schedule follow-up + log

Done. Repeat next week.

One Ask examples (ready to use)

• “Publish childcare licensing timelines monthly and cut median approval time by 20% within 6 months.”
• “Create a provider help desk and report paperwork turnaround and provider satisfaction quarterly.”
• “Map evening and weekend childcare gaps and pilot wraparound support in one high-shift corridor.”
• “Create an infant-slot support fund and report how many stable infant openings it actually produces.”

Bridge language (calm, non-tribal)

• “Childcare is work infrastructure, family infrastructure, and kid infrastructure at the same time.”
• “If the schedule does not match real life, the slot is only half a solution.”
• “Infant care is where the math breaks first.”
• “The goal is fewer cliffs, fewer closures, and more usable hours.”

Weekly cadence (how to keep it small and real)

• Week 1: pick the bottleneck + send the ask
• Week 2: office hours or staff follow-up
• Week 3: public record step
• Week 4: follow-up for inclusion and reporting

Then repeat or pivot based on what moved.

Back to playbooks