Who
A full-time high school student with a permanent U.S. address, applying alone or with one teammate.
Counselor intelligence brief
MIT THINK Scholars Program
A practical guide for high school students who have a serious STEM project idea, need funding and mentorship to execute it, and want to turn an early-stage proposal into a credible application-season artifact.
Updated June 3, 2026. The 2025-26 cycle had already closed and finalists had been announced. Treat date-specific guidance here as a next-cycle watch item until THINK posts fall 2026 instructions.
Decision brief
MIT THINK in five answers
What
A proposal-stage STEM program run by MIT undergraduates. Finalists receive weekly mentorship and up to $1,000 to execute the project.
When
Develop the idea through summer and fall, then verify the new cycle when instructions post. The prior cycle closed January 1.
How
Use the proposal to define the problem, map current work, specify a testable solution, and prove feasibility with a budget, timeline, risks, and success criteria.
Why
THINK helps a student turn an early idea into a semester-scale build or study, with funding and technical guidance aimed at a measurable spring result.
1. What it is
THINK is a science, research, and innovation program run by MIT undergraduates. Students apply with a project proposal before the work is finished. Finalists then receive mentoring and modest funding to carry the project through the spring.
The college-application value comes from the proposal judgment: the student has found a real problem, read enough background to understand the field, and designed a semester-scale project that can be tested, built, or measured.
Proposal length
10 pages
THINK describes a proposal limit of up to 10 pages before references, cover pages, and figures.
Finalist support
$1,000
Finalists can receive up to $1,000 in project funding, plus weekly mentorship.
2025-26 deadline
Jan. 1
The 2025-26 cycle listed January 1, 2026 as the application deadline. Verify the next cycle in fall 2026.
2. Eligibility first
THINK is worth a December push only if the student clears the basic rules and the project can realistically fit the program's mentorship-and-funding model.
Quick THINK fit check
No data leaves your browser.
Green-light path
- Confirm the current cycle's official eligibility rules before drafting.
- Write the proposal as a concrete procedure, budget, timeline, and validation plan.
- Name the specific technical decision where mentorship would help.
- Keep the project small enough to produce evidence by spring.
Common trap
Students often pitch a full platform, cure, or national deployment. THINK is stronger when the proposal describes one feasible proof of concept with a clear first experiment, build, dataset, or prototype.
3. Proposal fit
The proposal has to feel novel, useful, and executable. A strong THINK idea explains what exists, what remains unsolved, what the student will do, and how progress will be measured.
Strong THINK fit
- A device, algorithm, experiment, app, material, or engineering process with a clear build path.
- The student has read enough current work to identify a real gap.
- The plan has a week-by-week procedure and a measurable result.
- Funding and mentoring would remove a specific blocker.
Needs shaping
- The idea is interesting but too broad for one semester.
- The proposal names a technology without explaining the problem it solves.
- The validation plan is vague: "test accuracy," "survey users," or "see if it works."
- The budget lists parts but skips access, safety, data, or failure modes.
Weak THINK fit
- A finished science-fair project looking for a prize after the fact.
- A literature review, policy essay, or business plan with no technical execution.
- A huge project that depends on lab, dataset, or regulatory access the student cannot realistically get.
- A generic AI app where novelty lives in the wrapper instead of the method or use case.
4. Proposal spine
Build the application around four proof points. Each one should make the project feel easier to execute, not larger.
01
Problem
A specific need, constraint, or scientific question with enough background for an MIT undergraduate reader to care.
02
Current work
A short map of existing methods, products, papers, or prototypes, with a clear explanation of the remaining gap.
03
Solution
The proposed project, written as a buildable or testable plan instead of a broad promise.
04
Logistics
Budget, materials, data access, weekly execution plan, risks, safety, mentor needs, and success criteria.
5. Examples to study
THINK is proposal-first, so the useful examples are finalist project descriptions, full-results posts, and presentation traces that show how a funded idea became a completed artifact.
Official finalists archive
THINK publishes finalists and full results by cycle. Students should read these first to see the level of specificity expected before funding and mentorship.
Project before polish
A THINK example is usually a proposal-stage research or engineering plan, not a finished science-fair poster. Study how the idea names a build path and a measurable spring result.
Mentorship need
Strong finalists make the mentor role legible: a technical decision, method choice, or validation blocker where MIT undergraduate support can change the outcome.
Presentation trail
Past THINK presentation videos are useful for seeing how finalists explain the finished work after the mentored spring build.
6. Submission roadmap
June to August
Problem search
Find a problem that can be studied, built, or tested within one semester and about $1,000. Start with the bottleneck, user, dataset, organism, device, or environment.
September
Background read
Read current literature, comparable products, open-source methods, and safety constraints. The student should know what exists and where the gap sits.
October
Project design
Turn the idea into inputs, procedure, validation metric, budget, week-by-week timeline, and a fallback if the first method fails.
November
Draft
Draft once applications open. Keep figures, tables, budget notes, and citations close to the procedure so the plan feels executable.
December
Counselor review
Review novelty, feasibility, and fit. Trim broad ambition, add experimental detail, and make the mentoring need specific.
January
Submit
Submit before the posted deadline. For 2025-26, THINK listed January 1, 2026 as the deadline.
7. Common pitfalls
Most weak proposals fail before the technical idea gets a fair read.
Scale drift
The student proposes a platform, cure, national deployment, or full product instead of a semester-scale proof of concept.
Novelty fog
The proposal says the idea is new but never names the closest existing work or the exact improvement.
Method gap
The application has motivation and goals, then skips materials, data, steps, tests, and constraints.
Mentorship vagueness
"I want MIT guidance" is too broad. Stronger proposals explain what technical decision a mentor could help resolve.
8. Resources
Use official THINK materials at the moment of submission. The THINK resources PDF endpoint returned a 502 during this build, so confirm the PDF link again before a student starts drafting.