Grants for AI in Education 2026: Win Part of $400,000 from the Stanford Create+AI Challenge

Captured cycle: This page is retained for historical guidance. Confirm whether the program has reopened before planning an application.

Grants for AI in Education 2026: Win Part of $400,000 from the Stanford Create+AI Challenge

Stanford Accelerator for Learning and Google.org launched the Create+AI Challenge 2026 to fund projects that use AI to support learning, teaching, and career pathways without replacing people. The program is designed around a human-centred principle: AI should reduce low-value friction and expand agency, not automate away relationships.

The short version is this: this was a strong opportunity with real money and ecosystem access if you had a team aligned to an AI-for-learning idea, and it was targeted at teams that could show educational value, equity thinking, and practical execution. The application window is now closed, but understanding the structure is still useful for two reasons. First, people still ask whether it was a good match for them. Second, the same criteria and standards matter for future Stanford and comparable education innovation programs.

At a glance

What this opportunity is trying to fund

This is not a broad “build anything with AI” grant. The page itself is explicit that winners should address human-centred outcomes: better teaching interactions, stronger learner participation, and real support for career pathways. That is a narrower and more evaluative target than many edtech grant calls.

Across all three tracks, the underlying idea is the same: if AI is used, it should help a person perform better, understand better, or participate more meaningfully. Programs that frame AI as a replacement for teachers, counsellors, or mentors are a poorer fit in this design.

The funding is also paired with non-monetary support. In practice, that matters because many education projects fail after funding because teams run out of research design, ethical guidance, or real-world testing pathways. The listed outcomes include mentorship, workshop-like design support, and visibility at Stanford’s AI+Education Summit in February.

Who should consider this (and who should not)

You should consider this if all of these are true:

• You have a concrete problem in education, teaching, workforce development, or learner support that AI can augment.
• Your team already has or can recruit at least one Stanford-affiliated member (student, scholar, staff, or alum) when that requirement applies.
• You can define what “success” looks like in measurable terms and are willing to measure it.
• Your project involves real classroom, workforce, or community settings, not only a theoretical concept.
• You are prepared for a review process that rewards clarity, learning science alignment, and fairness over flashy branding.

You should probably skip this one if:

• You are building a pure automation product and do not plan to keep a human in the loop.
• You cannot define a measurable learning, participation, or outcomes metric.
• You have no team members with Stanford-affiliation pathway in the required format.
• You are looking for a vague “pay us now, we will figure it out” grant and are not ready to design next-step pilots.

If you are uncertain, use the next section as your readiness filter.

Readiness check before you spend time

1) Is your use case truly human-augmentation?

Examples that tend to fit:

• AI helps teachers spend less time on repetitive grading admin, while preserving instructional judgment.
• AI gives learners with disabilities accessible ways to participate and express understanding.
• AI helps mentors scale meaningful career guidance with guardrails.

Examples that likely do not fit:

• AI auto-generates final educational content with no teacher oversight.
• A product that mainly replaces existing human support roles.
• A prototype without clear educational benefit beyond curiosity.

2) Can you measure impact in a way that a reviewer can verify?

The scorecard mentions measurement, and Stanford’s listed criteria also emphasize feasibility. A credible plan at minimum should explain:

• what you will measure,
• who you will measure it with,
• and how you will collect the signal ethically.

For example, participation lift, confidence scores, mastery changes, attendance pattern changes, mentor follow-through rates, or pilot retention may be acceptable if definitions and timeframe are realistic.

3) Can you support fairness and accessibility?

This is a serious filter. Even if not listed as a separate checkbox everywhere, fairness work is part of the stated review framework. You should avoid generic statements like “we support equity” and instead explain actual actions:

• multilingual support,
• accessibility modes,
• diverse user testing,
• bias checks or prompt evaluation methods,
• policies for human review when AI outputs are uncertain.

4) Does the team have execution capacity for what you request?

A large award can be tempting, but judges evaluate feasibility. If you request significant funds without pilot capacity, data access, or clear milestones, you usually lose points. It is better to show a realistic path with clearly staged outputs than a grand blueprint.

Tracks and how they differ in practice

The official page lists three tracks:

• Augment Teaching: AI to support teachers, especially around student relationships and practical workflows.
• Augment Learning: AI to improve learner participation, including support for students with disabilities or learning differences.
• Augment Career Opportunities: AI for skill-building, mentorship, and pathways to meaningful work.

When choosing a track, don’t do it based on your favorite buzzword. Do it based on where your evidence will be strongest. If your prototype depends on teacher behavior change and professional development, pick Teaching even if there is a clear learner benefit. If your strongest outcome is confidence and participation among learners, pick Learning. If your product is strongest for portfolios, apprenticeships, project readiness, or mentorship loops, pick Career Opportunities.

What the program offers (beyond money)

The official page and associated Stanford posts describe several non-financial supports:

• Mentorship from Stanford community members across disciplines.
• Workshop-style interactions on learning science and teacher co-design.
• Visibility at the AI+Education Summit.
• Potential invitation to continue development in a summer cohort.

For practical applicants, this matters because these channels can open partnerships you may not be able to build independently, especially in schools, nonprofit networks, and research environments.

Eligibility: what is clear and what you still need to verify

The program page itself does not expose full detailed intake rules beyond broad categories. However, multiple official-era sources and legacy copies of the call consistently describe additional constraints:

• Team composition should include at least one Stanford affiliate.
• Applications were intended to be global in spirit, with international team members allowed.
• Applicants were generally expected to be adults.
• Stanford affiliates needed to align with internal policy if joining as employees.

Because the official form is now closed and no longer exposes full intake fields, treat these as historical requirements for the 2026 call rather than current live guidance.

If you use this framework for future rounds, confirm any requirements from the live page before spending application time.

Application process and current status

As of the redirected Stanford-linked Google Form endpoint, the call is explicitly closed and no longer accepting submissions. The page states:

The application closed January 12, 2026 (12:00 PM/noon PST). For any questions, contact Sarahi Espinoza Salamanca at [email protected].

That means you cannot currently apply to this exact round. If you are still in active planning mode, the most practical response is:

1. Use this as a model for your own internal proposal quality checks.
2. Keep the project structure ready in case Stanford publishes a similar round.
3. Reach out to the listed contact only for archival clarification if you are trying to verify specific interpretation details.

For teams who keep hearing “applications are closed” and feeling disappointed, this is a good moment to pause and convert your draft into a reusable package: problem brief, evidence plan, budget map, and short demo. Those components stay useful across accelerators.

What a strong proposal would need to include

Even without current submission mechanics, reviewers still score in the same broad patterns: innovation, impact, fairness, learning science grounding, measurement, and feasibility.

To prepare in a way that transferably passes these criteria:

• Start with one explicit problem statement in one sentence.
• Explain who is affected and why now.
• State how your solution augments human work, not replaces it.
• Describe the intervention in practical terms: what happens in week one, month one, and month three.
• Define at least two outcomes and one method of measurement.
• Describe risks and mitigations (data handling, staff time, inequitable effects, deployment constraints).
• Show budget alignment with outcomes: every requested dollar should move one measurable outcome forward.

For teams, this is where people often fail: they spend too much energy on technology description and too little on context, workflow integration, and evidence collection.

Practical application preparation (historical guidance for future rounds)

Because the 2026 form is closed, what you can still do is prepare using a robust application template that mirrors likely expectations.

Step 1: Clarify your story

Draft a short narrative that covers three lines:

• Who is the user?
• What human burden exists today?
• How does AI change that burden?

Reviewers usually read fast, so this should be intelligible to someone outside your subfield.

Step 2: Make the outcome measurable

Create a tiny scorecard of outcomes and metrics before your technical plan:

• target group,
• target effect,
• baseline method,
• endpoint at 4–12 weeks,
• what success looks like.

Use conservative numbers and explain what would constitute failure. That builds credibility.

Step 3: Build an ethical and inclusion layer into the design

Include a dedicated section for fairness and access:

• who might be harmed by over-automation,
• what control options users have,
• how non-English and differently-abled users are supported,
• what your review and error-handling loops look like.

Step 4: Design an implementation plan that fits your resources

A review panel may accept that your idea is compelling but not likely if implementation is not realistic. Include staffing assumptions, pilot setting assumptions, and clear dependencies (data access, partner schools, legal approvals).

Step 5: Prepare concise supporting materials

For historical versions of this round, many submitters used concise documents and short video explanations. Even when specific format changes later, the principle holds: a small set of well-structured artifacts helps judges assess whether you can execute.

Timeline model for deciding readiness

Even though this call is closed, this timeline is still useful for planning your next application.

• 6 to 8 weeks before a target deadline: align team and choose one track.
• 4 to 5 weeks before: finalize problem, user journey, and outcomes.
• 3 weeks before: produce draft deck/brief and run external review.
• 2 weeks before: film, record, and tighten visuals.
• 1 week before: verify all links, permissions, and team confirmation.
• 3 days before: final internal review and fallback edits.

In this challenge style, technical polish helps, but strategic clarity matters more than aesthetic perfection.

Common mistakes that weaken submissions

• Submitting a broad idea with no operational setting.
• Ignoring equity and inclusion details until the end.
• Confusing AI capability with educational impact.
• Designing around tool novelty rather than measurable outcomes.
• Underestimating teacher/workforce context and time constraints.
• Letting one technical founder dominate a team narrative without clear school or learner perspective.

Each of these is avoidable with structured planning. The reviewer can usually see through buzzwords quickly.

FAQ

Is this call still open?

No. The official form endpoint shows the application closed, with closure time and date in 2026.

Can international teams apply?

Historical materials for this round indicated international team members were allowed, with legal and sanctions considerations. Because intake details are tied to a closed call, verify current terms for any future round.

Do non-Stanford teams have any pathway in?

The available criteria repeatedly required at least one Stanford-affiliated team member. Teams without that connection were therefore not aligned for this specific challenge round.

What was the value beyond cash?

Mentorship, workshop exposure, and summit visibility were part of the program structure. The official program page also mentions potential continuation opportunities in a summer 2026 cohort.

What should I do now if my idea fits?

Do not discard it. Turn your draft into a reusable applicant package:

• one-page problem statement,
• user outcome metrics,
• safety and inclusion notes,
• simple budget mapping.

Keep it ready for the next similar round or a sister program with similar criteria.

Official links and follow-up actions

• Create+AI Challenge official page
• Application page (closed)

If you want to move fast on a real submission cycle, use this page as your baseline and keep these three documents ready: a one-page outcome brief, a practical implementation plan, and a budget tied to measurable milestones.