Monthly Action Plan

05 Monthly Action Plan

This calendar focuses on the highest‑leverage steps remaining in your senior fall timeline. The emphasis is on documenting your academic rigor, packaging your cybersecurity work clearly, and integrating those materials into your application before Early Action and Regular Decision deadlines. Where relevant, this calendar references other sections (Academic Profile Analysis, Creative Projects, Essay Strategy, and Application Execution) for execution details.

Month Primary Focus Action Steps & Target Outcomes
Month 1 Academic context + application setup
  • Compile a concise academic rigor summary listing your highest‑level math, computer science, and physics courses. Pair this with transcript context for applications and counselor materials (see Academic Profile Analysis).
  • Begin outlining cybersecurity writeups by identifying bug bounty findings or technical discoveries you plan to document. Create a structure for clear explanations and responsible disclosure timelines (see Creative Projects).
  • Set up application portals for Georgia Tech, University of Maryland, and Purdue; confirm Early Action policies and create a master deadline tracker.
Month 2 Technical writing + EA preparation
  • Draft the first technical blog post or documentation piece explaining a vulnerability discovery or bug bounty case, including methodology and disclosure steps (see Creative Projects).
  • Refine the academic rigor summary and confirm transcript presentation with your school counselor so that course context is clear to admissions readers.
  • Complete and review Early Action application components for Georgia Tech and Purdue if applying early; confirm submission readiness.
Month 3 Open‑source project launch
  • Begin building an open‑source cybersecurity tool. Establish a GitHub repository with a clear README, documentation structure, and usage explanation (see Creative Projects).
  • Publish or finalize at least one cybersecurity writeup explaining your technical process and lessons learned from vulnerability analysis.
  • Ensure the activity description for cybersecurity work is drafted for applications, capturing scope, tools used, and technical depth (see Application Execution).
Month 4 Documentation + visibility
  • Expand documentation for your cybersecurity tool and push meaningful commits to GitHub so the repository clearly demonstrates functionality and purpose.
  • Publish additional bug bounty or security analysis writeups if available, emphasizing technical clarity and responsible disclosure timelines.
  • Prepare concise portfolio links (GitHub, blog posts, documentation) that can be referenced in your activities list or additional information section.
Month 5 Project refinement
  • Continue improving the open‑source cybersecurity tool with stable functionality and clearer documentation for outside users.
  • Review your cybersecurity writeups to ensure explanations are understandable to a technically literate but non‑specialist reader (important for admissions staff).
  • Confirm that portfolio links and project summaries are ready to integrate into application materials.
Month 6 Application integration
  • Integrate your projects, writeups, and coursework evidence into the activities list and application materials (see Essay Strategy and Application Execution).
  • Ensure that cybersecurity work is described with clear technical impact rather than only listing participation.
  • Finalize Regular Decision application timelines and confirm remaining requirements for each school.
Month 7 Essay alignment
  • Revise essays so they connect your cybersecurity exploration, technical curiosity, and academic preparation (see Essay Strategy).
  • Reference relevant projects, bug bounty work, and coursework evidence where appropriate.
  • Double‑check that your activities list, essays, and supplemental materials all reinforce the same technical narrative.
Month 8 Final application polish
  • Conduct a final pass through all applications to ensure cybersecurity projects, GitHub links, and technical documentation are correctly referenced.
  • Verify that your academic rigor summary and transcript context are accurately represented across materials.
  • Submit remaining applications and confirm that recommendation letters and transcripts have been received.

Throughout these months, keep your focus on clear presentation rather than adding entirely new commitments. The committee emphasized that your strongest leverage this cycle will come from documenting your cybersecurity work clearly, demonstrating technical depth through writing and open‑source code, and making sure admissions readers can easily understand the level of rigor in your academic preparation.

Testing Strategy →