October 28, 2026
Dear Councilmembers,
As you know, DC Action convenes the DC Out-of-School Time Coalition and we are writing to flag important oversight and grant-making transparency concerns our coalition has raised regarding the FY27 grant awards from Learn24 Office that has led to funding reductions or eliminations for many afterschool and year-round programs that youth rely on. For students, grant challenges have meant fewer available seats for high-quality afterschool programming. For families, it has meant fewer affordable, supervised places for their kids, likely creating disruptions to parents’ work schedules. And for OST providers, it has meant programmatic disruptions, staff reductions, and uncertainty about their long-term viability.
The good news we see coming out of this year’s grant cycle is that funding demand far exceeds funding available, suggesting the sector is ready to serve potentially twice as many youth! In total, OST providers requested $52.2 million, while only $25.7 million was available. The $25.7 million will fund 120 grants to 103 organizations aspiring to serve roughly 15,000 youth. However, insufficient funding meant the OST Office had to deny funding to 80 of 200 eligible applications (40%), including eliminating funding for 25 organizations funded in the last grant cycle.
How Learn24 grants work
Learn24 is the Office of Out-of-School Time (OST) Grants and Youth Outcomes within the Office of the Deputy Mayor for Education. It awards competitive grants to nonprofits (community-based organizations and charter schools) that run afterschool and summer programs for DC students in grades K–12. Grants run on a three-year cycle, and FY27 is the first year of the new cycle.
The grant-making process works in four steps:
- Initial Scoring. Three independent reviewers score each grant application against a rubric. If any one score is 10 or more points from the average, a fourth reviewer is brought in and the outlier score is dropped; the remaining three scores are then re-averaged.
- Prior performance. For returning grantees, the previous year’s performance review is factored into their final score.
- Priority points. Applicants can earn bonus points for meeting District priorities, such as serving middle schoolers or operating more days than required. These proposed grant application commitments then become conditions of the award.
- Award levels. Scores are converted to dollars using fixed cutoffs. In most competitions, a program scoring below 100% of baseline points receives no funding. In the largest competition, Year-Round OST (100 applicants), scores from 100% to 110% earned 70% of the grant amount requested, and scores of 111% or higher earned 85% of grant dollars requested.
Challenges Identified with the FY27 Grant-Making Cycle:
In late August, just after FY27 grant awards were announced, DC Action began to hear anecdotes from OST Coalition partners about challenges and inconsistencies with the grant process prompting us to create an anonymous survey for OST providers. Then, in early September, the Deputy Mayor for Education’s office hosted virtual office hours to respond to grant concerns. More than 80 providers joined that call and over 20 providers filled out our survey speaking to the same patterns:
-
- Rigid but inconsistent scoring put funding at risk:
- Scoring Discrepancies: Numerous OST providers have reported initial reviewer scores 20 and even 50 points apart for the same application, raising a concern over the grants management team’s consistency of application of the scoring rubric. DC Action has requested but not received a list or count of instances where grant applications met the threshold for a fourth reviewer.
- Structural bias against returning programs: Because last year’s grant performance review counts toward the score of a returning grantee’s application (when a provider is applying to the same grant competition, just new cycle), scoring for returning programs had an additional scoring threshold to meet that new grant competition applicants did not. For example, a prior-grantee rated “Performing” (one step below “High Performing”) could fall below a scoring cutoff when applying for that same grant competition, even when an identical application was submitted and well-scored for a different grant competition, a competition the OST provider had not been funded through previously and was therefore considered a new applicant. This means that returning grantees who have come to count on public funding to serve District youth may have been unfairly – and likely unintentionally – locked out of funding. According to the OST Office, 30% of returning grantees had a rating of “Performing” – a review indicating a program is successfully achieving its grant requirements – putting at least this proportion of returning grantees at risk of funding losses and disruption of services for youth.
- Rigid but inconsistent scoring put funding at risk:
- Poorly-structured funding caps created harm:
-
-
- Grant caps: In past years, programs scoring above 100% typically received their full funding request, while those scoring below 100% would receive partial funding. This year, in Learn24’s largest grant competitions, no applicant was eligible for full funding. The maximum award was 85% of the requested amount, and most awardees received just 70%. In practice, this meant returning grantees could maintain level funding only by requesting an enhancement to expand their operations, but those proposed enhancements were then expected to be fulfilled regardless of the final award amount. Grantees that applied for level funding to serve roughly the same number of youth as in previous cycles lost out on priority points, which left many underfunded or defunded, forcing cuts to OST opportunities (due to closed programs, reduced sites, fewer seats, etc.) for students Districtwide just weeks before the start of the new school year.
- Too Rigid: This year, programs required an averaged score of 100% to receive funding, meaning a score that was a fraction under that benchmark could lead to funding elimination, abruptly destabilizing an OST program’s operations. See Higher Achievement example below.
- Inconsistent application of grant caps: The 85% and 70% cap on grant awards were tied to application score ranges but some grantees reported receiving awards below the stated cap for their score range, raising additional concerns over the Learn24 grants management team’s consistency of application of the scoring and funding rubrics.
-
- Poor communication from the OST Office exacerbated challenges:
-
-
- Key changes were not clearly or proactively communicated: Notably, the OST Office did not tell OST grant applicants that new funding caps would be applied to the FY27 grant cycle until after awards were announced. This meant programs applying to maintain their service levels had no time before the new school year to plan for funding losses (receiving just 85% or 70% of an award that, in the past, would have earned them 100% of their request). Programs who applied to expand their services were also left scrambling when they received awards far below what it would take to actually increase their capacity or dosage (see FRESHFARM example below). Awardees had just 48 hours – mere days before the start of the new school year – to decide whether to accept their award, knowing it was insufficient, and to then figure out how to make that insufficient funding stretch far enough to comply with their grant proposal.
-
- Delayed follow up: Many providers reported that they could not obtain a clear breakdown of their application scores or priority points and had challenges understanding how the scoring rubric was applied, particularly the rubric for factoring in past performance of returning applicants. For applicants who submitted appeals, resolution took weeks, with school-year programming already underway.
Example: Higher Achievement
Higher Achievement runs academic and mentoring programs for middle schoolers. It has been a Learn24 grantee for more than 10 years and served over 100 students with Learn24 funds last year. In the initial scoring phase, its three reviewers scored it above the funding cutoff on average. When its prior-year review score of “Performing” was factored in, their overall score dropped to just below the funding threshold. Even though “Performing” is a solid review score, that half-point difference put more than $200,000 at risk. Higher Achievement appealed, and parents, mentors, and community members sent a letter and petition to the Chairman and Council. The appeal partly succeeded and Higher Achievement received $175,000 annually for the 3-year FY27 cycle, but a funding gap remains.
| Higher Achievement FY27 Grant Applicant Scores | Score |
| Reviewer 1 | 101.7% |
| Reviewer 2 | 108.3% |
| Reviewer 3 | 96.3% |
| Average of reviewers | 102.1% |
| Final score (after FY26 review was factored in) | 99.5% |
| Funding cutoff | 100% |
Example: FRESHFARM FoodPrints
FRESHFARM runs FoodPrints, a food and garden education program in DC public schools. ITs FY27 grant application scored 110%, so it received 70% of its request; in dollars, this was about $80,000 less than the funding they requested. It had earned a priority point for proposing to run programming four days a week instead of the required three, but this plan depended on full grant funding to scale operations by hiring an additional staff person.
With a smaller award, FRESHFARM requested returning to three days of programming, instead of four days of programming, which was the enhancement they’d proposed in their application and that helped them earn priority points. The OST Office responded that the proposed services that had earned priority points needed to be executed and suggested the FoodPrints program keep four days of services but reduce the number of 6-week series the program would run during the school year; this schedule would have been much harder for FRESHFARM FoodPrints to staff and ultimately would have provided less programming for students.
After weeks of review by the OST office, FRESHFARM’s second appeal was approved to operate three days of programming per week plus offer extra weeks during the school year and summer. In effect, the program earned a priority point for a commitment that its smaller award made impossible to keep – creating a choice of forgoing the funding altogether or overextending the organization’s budget to fill funding gaps and comply with the grant requirements.
FRESHFARM’s appeal experience also highlights a need for greater shared understanding of grantees’ experiences on the ground. Had grant funding caps and priority point impacts on expected grant compliance (dosage, participation levels, populations to be served, etc) been communicated to applicants in advance, surprises and implementation challenges like this may have been avoided.
Data DC Action has requested from the OST Office
We have requested and received the number of FY27 grant applicants, the number of unfunded organizations from FY27 application cycle, the number of youth that FY26 grantees proposed to serve, and funding level data (requested and received) on the 120 funded grants for FY27. Much of this data is (or was) public on the Learn24 website.
To date, we have requested but not received:
- The list of names of organizations not renewed for funding in FY27
- The number of grant applications that met the threshold for requiring a fourth scoring review
- Which OST programs earned points for proposing to serve middle school students
- Service level data on all 200 applicants (anonymized), including seats proposed to be operated by Ward and by “priority site;” this data is imperative for understanding if this year’s grant process changes created any disparate impact on already underserved Wards or sites.
What we’re asking of the Council:
- Request the full data. Ask the OST Office to make public all data DC Action has requested including anonymized data on all OST applicants’ (both FY27 grant awardees and unfunded grant hopefuls) including proposed seats they planned operate in FY27, the proposed seat count by Ward, count by priority site, count by age/grade, and which grantees or grant application received priority points for planning to serve middle school students. This data is necessary for the Council and public to be able to analyze through a racial and geographic equity lens which students lost and gained access to publicly-funded OST programming as a result of changes implemented this grant cycle.
- Exercise strong oversight. We urge the Council to press the Learn24 Office for greater transparency in grantmaking by making it standard practice to share back each applicant’s scoring breakdown and priority point awards so providers can strengthen future applications. The Council should also exercise its oversight role by pressing the Office to conduct a comparison of similarly situated OST offices in other jurisdictions to identify best-practices that help those offices run grant competitions that remain rigorous while being fairer and more consistent, transparent, and predictable for providers. Additionally, going forward, the Council should require Learn24 to publish award rules, including any funding caps, before applications are due; this may require legislative action (similar legislative requirements intended to improve how the Office can act as a true partner with OST providers are included in the Universal OST Act).
- Plan for FY28. Use this year’s $26.5 million in unmet funding demand to gauge and grow OST funding ahead of the roughly $12 million funding cliff facing the OST Office in the FY28 budget. And remember: when funding is insufficient to meet demand, it is even more imperative that a more fair and transparent grant process be executed.
Thank you for your commitment to the District’s young people. We would welcome the chance to brief your office in greater detail. Please contact Joanna Blotner, Director of Government Affairs, at jblotner@dckids.org if you are interested in discussing these concerns, data needs, or solutions further with members of DC Action’s staff or with any of our OST Coalition partners providing youth development programming in your community.
Sincerely,
The OST Team at DC Action
Jorge Membreño
Youth Advocacy Director
Njeri Jenkins
OST Policy Analyst
Joanna Blotner
Government Affairs Director
Rachel Metz
Data Manager