NSF 26-017: Empowering and Educating Children to Thrive in a Digital Era

NSF 26-017: Empowering and Educating Children to Thrive in a Digital Era

The NSF 26-017 page is a Dear Colleague Letter (DCL), published by NSF’s Technology, Innovation and Partnerships (TIP), that invites proposals to support children’s safety, privacy, digital literacy, and well-being through advanced technologies, including AI, across both formal and informal education settings. On the NSF page, this is framed as an active funding opportunity and explicitly connected to at least two named NSF programs. In this sense, it is not a single stand-alone competition with one application form or one award amount. It is a policy signal and a routing mechanism into existing NSF solicitations.

For applicants, this is not a drawback. It can be a stronger path if your project is interdisciplinary and you already know that your idea may need both research rigor and implementation support.

If your team has a robust idea but not a single perfect home program yet, this DCL matters because it can help you identify which active NSF streams are most aligned and then route your concept correctly.

Key details at a glance

What this opportunity actually is

A DCL is not the same as a full solicitation with one fixed mechanism. It gives program offices a common framing and tells applicants which ongoing NSF programs and themes they should target. The current DCL states that NSF is open to proposals that use advanced technologies, including AI, to support children in the digital age.

The language emphasizes:

• evidence-based strategies and tools,
• safe and innovative technology use,
• support for parents/caregivers and community stakeholders,
• strengthening digital literacy,
• ensuring children can participate safely in online and AI-enabled environments.

The document is explicit that proposals must still satisfy the rules of the relevant underlying program: eligibility, deadlines, budgets, submission systems, and criteria. In practice, the DCL acts like a high-level strategy memo plus eligibility filter; it does not replace individual program instructions.

If you are expecting one central grant portal and one amount, you will likely be disappointed. If you are ready to map to sub-programs and build a program-specific submission, this can be a major leverage point.

Why this is useful for 2026/2027 planning

This DCL is still inside the target cycle and was marked active with a 2026 publication date. The practical value is this:

1. It broadens how you can justify child-focused digital interventions to NSF.
2. It gives a common language around AI, privacy, and child welfare that appears in multiple education, innovation, and workforce-related solicitations.
3. It encourages cross-sector partnership (education systems, nonprofits, families, technology teams) rather than one-off technical grant writing.

For 2026–2027 preparation, the key advantage is sequencing. Many NSF programs associated with this DCL have different deadlines and funding shapes. That can allow teams to decide whether they are submission-ready for their strongest path this cycle or whether they should submit later with a stronger evidence base.

Who this fits best

Strong fit profiles

This DCL is best for teams where the problem is not purely technical and not purely educational. It is strongest when:

• there is a clear child-focused outcome (learning, safety, psychological well-being, or inclusion),
• the team has or can build non-academic partnerships,
• AI or digital systems are part of the solution but are not the only deliverable,
• the proposal can be adapted to existing NSF program requirements.

Typical strong candidates include:

• schools and districts piloting AI-assisted learning support,
• nonprofits focused on online safety, youth protection, and digital citizenship,
• researchers studying children’s development in technology-rich contexts,
• curriculum or platform designers addressing digital literacy,
• public-interest organizations connecting families, educators, and community institutions.

Weak fit profiles

• pure software MVP grants without educational outcomes,
• projects aimed only at adults with no child outcomes,
• teams that only have a concept and no implementer partner,
• applicants who prefer a single no-fuss application with one budget and one due date.

Eligibility logic in practice

Because this is a DCL, eligibility is inherited from the program you submit to.

The official page does not provide a single consolidated eligibility table for all possible paths. Instead, NSF explicitly tells applicants to submit through the linked opportunities and follow their rules. The practical rule is:

1. Pick a program route first (at least one of the listed programs),
2. confirm your organizational and eligibility status against that route,
3. match your concept to that program’s funding mechanism.

NSF also instructs teams to include this title prefix: Empowering Children to Thrive DCL:. You should use that exact prefix for submissions that are clearly routed under this DCL framing.

How to apply: practical sequence

The single largest mistake is treating NSF 26-017 as one submission. The better approach is a two-step planning workflow:

Step 1: identify the correct child-focused NSF lane

The DCL lists two programs at the time this was captured:

• NSF Fostering Interdisciplinary Networks to Develop Emergent and Responsive Solutions Foundry (FINDERS FOUNDRY), and
• TechAccess: AI-Ready America.

Each route has different award style, deadlines, and scoring expectations. Your first task is to decide which route fits your project stage.

A quick decision rule:

• Choose a solutions design route if your proposal is about co-designing interventions with educators, families, and communities.
• Choose an AI-ready route if your primary contribution is scaling AI literacy, planning and adoption infrastructure, and broad coordination around AI readiness.

Step 2: verify the linked solicitation requirements

For the chosen route, copy and answer:

• who can apply (institutional/individual status),
• budget limits,
• proposal components,
• due dates,
• submission method (Research.gov/Grants.gov/other approved route),
• any required partner composition.

Step 3: align concept and evidence with the route

A DCL submission should not read like a generic digital transformation pitch. It should explicitly map:

• problem statement to child outcomes,
• digital intervention to measurable learning or well-being impact,
• implementation partners to real deployment context,
• safety and privacy safeguards to concrete workflows.

Preparation strategy: what to build before submission

Since the DCL has no single deadline, you should build in a rolling preparation cycle across the deadlines of your chosen routes.

Build a partner map first

The strongest applications are not solo academic papers. At minimum, list:

• educational partner (school, afterschool, nonprofit, youth-serving organization),
• technical lead,
• researcher or evaluator,
• child-facing implementation support (counselor, youth worker, community lead).

NSF language around child well-being often rewards practical delivery architecture over one-directional platform demos. Your partner map should show who owns curriculum adaptation, consent handling, communications, and outcomes review.

Convert problem statements into measurable outcomes

Write outcomes in observable terms:

• reduction in unsafe online interactions,
• increased verified digital literacy assessment scores,
• improved reporting confidence among students and caregivers,
• measurable teacher adoption outcomes,
• family outreach completion rates.

Avoid generic goals like “improve child safety online.” Use baseline and target language the evaluator can score quickly.

Prepare legal and ethics scaffolding early

Child-focused digital projects attract reviewer attention on privacy, safeguards, and data governance. Include:

• data minimization principles,
• age-appropriate consent and assent assumptions,
• reporting and escalation paths for potential harm,
• moderation and grievance workflow.

These details are not always the only thing scored, but they are one of the fastest ways to demonstrate seriousness.

Prepare your application for the selected route, not for a broad DCL ideal

If you try to write one proposal for both underlying programs, you create a generic and weak application. Instead:

• tailor structure and claims to the submission route,
• align budget lines to that route’s format,
• use route-specific milestones,
• place DCL framing in the intro only where it directly supports reviewer interpretation.

What many good applicants get wrong

1) Applying as if this were one funding pot

That is the top error. A DCL does not replace the funding details of a solicitation. Treat it as a framework and route to linked opportunities.

2) Ignoring submission timing

If you delay until the last route deadline and only then attempt to align eligibility requirements, many applications fail for simple mismatch reasons. Build backward from route deadlines once identified.

3) Overpromising AI without child-centered controls

NSF’s child well-being framing is not a permission slip for unconstrained AI pilots. Strong proposals show where AI helps and where human oversight remains explicit.

4) Underinvesting in implementation pathway

“Need and novelty” is not enough. Reviewers expect practical deployment logic: who trains, who maintains, who supports families, and who tracks outcomes after launch.

5) Weak stakeholder participation

If your application sounds like a school-only or vendor-only project, it may not satisfy the broader spirit of this DCL. Show educators and community stakeholders as active, not decorative.

Expected review logic (how teams are likely to be judged)

NSF generally evaluates fit by how well the proposal aligns to stated goals and by proposal quality against the target solicitation’s review criteria. For this DCL context, likely high-scoring themes are:

• clear evidence of child benefit,
• practical and safe digital intervention design,
• measurable outputs tied to learning and well-being,
• meaningful collaboration with education/community stakeholders,
• realistic budget and timeline consistency with route-specific rules.

Because this is a cross-program invitation, the review logic can vary. The DCL itself does not create a single scoring rubric; the linked solicitations do.

Timeline thinking for teams in 2026/2027

A useful planning approach is to run your effort against a sequence:

1. Month 0–1: choose route and map to linked program requirements.
2. Month 1–2: refine problem framing and collect partner confirmations.
3. Month 2–3: draft core concept, ethics, and outcomes sections.
4. Month 3–4: finalize budget and partner commitments.
5. Month 4–5: internal review, then submit at least three business days before the official deadline of the selected route.

Because the DCL is active and the underlying funding mechanisms have their own schedules, this cadence keeps your team aligned without assuming one common deadline.

Step-by-step application checklist

Use this checklist before you click submit:

• Confirm the correct NSF route from the DCL list,
• Verify route-specific eligibility and accepted applicant types,
• Confirm title prefix requirement,
• Confirm budget constraints and required sections,
• Confirm internal approvals and institutional authorizations,
• Attach only required documents and formats,
• Add child safety and data governance section,
• Define who owns outcomes reporting,
• Add a short evidence appendix (pilot results, previous collaborations, evaluation plans),
• Validate that all links and registration details are final,
• Submit via the specified NSF portal for that solicitation.

Frequently asked questions (application-centered)

Is NSF 26-017 itself a grant with one amount?

No. This DCL identifies a funding direction and points to specific program solicitations where the actual award rules, amounts, and deadlines are defined.

Do I have to work on both listed programs?

No. The page presents participating programs as pathways. You can apply to the one best aligned with your concept and readiness.

What should I include in the proposal title?

The DCL asks applicants to use the prefix Empowering Children to Thrive DCL: as a proposal title convention.

What if my idea changes after reading linked programs?

That is possible and expected. The most important adjustment is to preserve alignment with the selected route’s scope, eligibility, and outcomes.

Does this help if I’m not AI-first?

Yes. The DCL encourages broad technology-enabled interventions for child well-being and education. AI can be part of it, not the only path.

Where do I find amounts and exact deadlines?

On each linked NSF program’s solicitation page. The DCL itself references the programs and states proposals must meet each corresponding solicitation’s requirements.

What to do next in the next 14 days

If you want to use this now, do this:

1. Read the two linked program pages carefully and choose one route.
2. Draft a one-paragraph problem-to-impact statement for children and families.
3. Confirm your submission deadline and portal.
4. Add title prefix and partner commitments.
5. Set an internal submission deadline one week before the official date.

This is a small amount of process work that can prevent most avoidable application failures.

Official links

• NSF DCL page (official): https://www.nsf.gov/funding/opportunities/dcl-empowering-educating-children-thrive-digital-era
• Linked program context from NSF page: NSF FINDERS FOUNDRY
• Linked program context from NSF page: TechAccess: AI-Ready America

The most reliable interpretation is simple: this DCL is strong strategically, but it is only your starting map. Your real application must be route-specific.