Monthly Action Plan

05 Monthly Action Plan

Month Priority Actions & Target Outcomes
May (Junior Spring)
  • Document technical ownership. Create a working document describing your role in any robotics, research, or engineering work you have participated in. Clarify what code you wrote, what systems you designed, and what problems you solved so future applications reflect precise authorship.
  • Define your core technical project. Select one substantial CS project to expand over the next several months (see Creative Projects section). Write a short scope plan: problem, users, technical stack, and what a public release would look like.
  • Survey Washington competitions. Review the timeline for events such as the Congressional App Challenge or regional science fairs and decide whether your project could be adapted into a competition submission.
June (Start of Summer)
  • Begin full project build phase. Establish a GitHub repository, define the architecture, and begin the first functional prototype. Aim to complete the core system structure this month.
  • Organize research and technical artifacts. If you have prior robotics or research involvement, gather code samples, documentation, papers, or presentations that demonstrate your contribution for future portfolio use.
  • Prepare for public documentation. Start writing a README and technical overview explaining the problem your project solves and how it works. This will later support adoption and application materials.
July (Deep Build Period)
  • Expand the project into a meaningful system. Implement major features and ensure the project demonstrates clear technical depth (algorithms, systems design, or engineering complexity depending on your focus).
  • Create early visibility. Publish development progress on GitHub with clear commits and version history so outside reviewers can see your technical ownership and iteration.
  • Test with initial users. Share the project with a small group of developers, classmates, or mentors and gather feedback that can guide improvements.
August (Public Release Preparation)
  • Release Version 1 publicly. Push a stable release of your project to GitHub with documentation, installation instructions, and examples. The goal is a project someone outside your school could realistically try.
  • Begin external visibility. Share the project within relevant developer communities (online forums, student groups, or technical communities) to start building adoption and feedback.
  • Start early application groundwork. Draft a résumé-style activity list describing your academic work and technical experiences in clear language for recommenders and future applications.
September (Senior Application Ramp‑Up)
  • Strengthen adoption and collaboration. Continue promoting and improving your project based on feedback. Track usage, forks, or contributions on GitHub to demonstrate external engagement.
  • Confirm recommendation letter writers. Ask two academic teachers and one mentor who can speak about your technical thinking or problem‑solving. Provide them with your activity summary.
  • Outline personal and supplemental essays. Develop story ideas emphasizing how you approach technical challenges and intellectual ownership (see §06 Essay Strategy).
October (Early Application Month)
  • Draft and refine essays. Write full drafts of your main personal statement and early‑school supplements. Focus on showing how you build and think as a computer scientist (see §06 Essay Strategy).
  • Package your project professionally. Add diagrams, documentation, and a technical explanation page so admissions readers can quickly understand the project’s purpose and complexity.
  • Prepare Early Action / Early Decision submissions. If applying early to any target schools, finalize essays and verify all materials before the deadline.
November (Early Deadlines & Iteration)
  • Submit early applications. Ensure all Early Action or Early Decision materials are submitted and confirmed by each institution’s deadline.
  • Continue project development. Release improvements or new features based on community feedback to demonstrate ongoing engagement with the project.
  • Begin regular decision essay refinement. Adapt and improve essays for remaining applications using feedback from teachers or mentors.
December (Regular Decision Finalization)
  • Finalize all remaining applications. Complete and submit Regular Decision applications to Stanford, MIT, Georgia Tech, and any additional schools on your list.
  • Update project documentation. Publish a year‑end update or new release summarizing improvements, adoption, or technical milestones achieved since the initial launch.
  • Confirm recommendation and transcript delivery. Double‑check that your school has submitted all required materials and that each application portal shows a complete file.

This timeline focuses your junior‑to‑senior transition on four phases the committee highlighted: clarifying your technical contributions, building a substantial project, demonstrating real‑world adoption, and translating that work effectively into recommendations and essays. Each month builds toward the summer‑to‑fall window when selective computer science programs form their strongest impressions of applicants.

Major Specific Prep →