A portfolio is not an admissions object with a required project count. It is an evidence system for work the student owns and can explain: dates, role, question, new contribution, methods, student-authored code, data provenance, results, limitations, iterations, verification, artifacts, and mentor disclosure. Students may begin without programming experience, but they must understand and explain the tools and code used in the final work.
No university-wide project count, duration, or competition record is implied. Last reviewed: July 11, 2026.
A portfolio records what a student built, the role they played, the evidence behind the result, and what they learned. Whether it may be submitted in an application depends on the university and route, but a well-documented process also supports learning, interviews, collaboration, and project handoff.
A good portfolio isn't a list of finished results. It has to tell a story—the motivation behind finding the problem, the trial and error of solving it, the reasons behind technical choices, and how you grew through the project. At CIT, we build out the way to systematically design and document this whole process together with you.
For each substantial project, record the title and dates, exact student role, question, coursework anchor, new contribution, methods and tools, student-authored code or work, data provenance, results, limitations, iterations, verification, report/demo/repository, and mentor support. One project may create several artifacts; those artifacts are not automatically separate activities.
Source: aimi.stanford.edu · inspiritai.com · veritasai.com
No university publishes a universal project count, duration, or competition formula. The useful standard is whether the student can explain their exact role and verify the work truthfully.
| Evidence item | Document | Verify | Reporting rule |
|---|---|---|---|
| Question and new contribution | Summary and log | Sources and requirements | Separate from assessed work |
| Student-authored code, demo, or report | Artifact | Version and authorship | Check privacy and permissions |
| Student role and mentor support | Role record | School, team, mentor | Do not overstate |
| Data, methods, results, and limitations | Reproducibility | Baselines and tests | Include failures |
| Official result or verification | Link evidence | Official record | Check route before use |
| Projects and artifacts | No fixed count | Ownership and continuity | Do not split one activity artificially |
An AI portfolio isn't just for students aiming at a CS major. Students aiming for medicine/life sciences, humanities/social sciences, business, or the arts can also stand out in admissions with an original project that applies AI tools to their own area of interest. The table below lays out project directions and key AI technologies by major.
| Target major/field | AI-fusion project direction | Key tools & technologies |
|---|---|---|
| Life sciences/medicine (Pre-med) | Medical image classification, drug-molecule property prediction, public-health data visualization | Google Teachable Machine, Python (pandas), Kaggle datasets |
| Humanities/social sciences | Sentiment analysis of historical texts, social-media opinion analysis, AI ethics policy research reports | Hugging Face sentiment classification, ChatGPT API, public data portals |
| Business/economics | Automated consumer-review classification, financial-data prediction models, startup pitch-deck automation | Scikit-learn, Tableau, Google Colab (no-code flow) |
| Arts/design | Generative-AI art projects, music-emotion classification, digital-media accessibility tools | Stable Diffusion, Magenta (Google), p5.js + ML5.js |
| Environment/earth sciences | Satellite-image-based deforestation detection, climate-data visualization, carbon-emissions prediction | Google Earth Engine, NASA open data, Python visualization |
CIT matches mentors across the fields above. Students may begin without programming experience, then learn the coding required for the chosen project. They must understand and explain every tool, AI output, line of code, and analysis used in the final work. See the full AI program curriculum →
Using the same curriculum as our in-person classes in Apgujeong, we run 1:1 online sessions with dedicated mentors for the life sciences, humanities, business, and arts. Korean students living in Singapore, Hong Kong, or the U.S. East Coast, as well as families who find it hard to travel within Seoul, can receive the same level of portfolio guidance.
CIT helps map the student's interests, intended major, prior learning, available time, and assessed-work boundary. The student chooses the independent question and remains responsible for every project decision.
Students carry out a real project—implementing an AI model, building an app, analyzing data, and more. Alongside technical mentoring, the development process is documented systematically, and the trial-and-error and improvement process is treated as an important part of the portfolio.
Students write their own project report, GitHub README, and presentation materials. CIT teaches structure and gives permitted feedback on clarity, reproducibility, and whether the student's exact role, methods, results, limitations, and support are disclosed.
We organize the project log, code, data provenance, demo, report, and verification. If an admissions route permits the material, students describe their exact role, dates, outcome, and mentor support truthfully.
U.S. and U.K. applications: A route may allow a student to describe the project in activities, additional information, or an interview. The description must state the student's exact role, dates, outcome, limitations, and mentor support. GitHub links, apps, and competition results are not universal requirements. See the full EC strategy →
Korean university routes: Whether a portfolio, outside competition, award, or repository may be submitted—and whether school verification is required—depends on the university, admission year, and route. The current official guide takes priority.
School activity: A project may become a school-approved club, service, or research presentation when appropriate. Records must reflect the student's real role and verified outcome.
There is no required project count. Start with one substantial project the student owns and can explain, then document the question, role, data, methods, results, limitations, and verification. The study guides below are learning resources; assessed coursework is not copied into a new project.
A portfolio records a problem the student found, the solution process, a working result, the exact student role, data provenance, iterations, limitations, verification, and mentor support. There is no required project count, and multiple artifacts from one project are not automatically separate activities.
Students may begin without programming experience. The coding required depends on the project, and students must understand and explain every tool, AI output, line of code, and analysis used in the final work. CIT offers 1:1 mentoring across life sciences, humanities, business, and the arts.
Record the project title and dates, the student's exact role, question, coursework anchor, new contribution, methods and tools, student-authored code or work, data provenance, results, limitations, iterations, verification, artifacts, and mentor support. No university publishes a universal portfolio formula.
There is no required project count or fixed duration. One sustained project may produce a report, poster, demo, repository, presentation, and award, but those artifacts are not automatically separate activities. Prioritize student ownership, relevance, truthful verification, and the ability to explain every decision.
Timing depends on the student's prerequisites, current coursework, examination and assignment deadlines, and intended output. Younger students can build foundations and explore; older students should extend one strong existing area narrowly. Academic performance and required schoolwork come first.
Of course. Competition results are just one element of a portfolio. A project where you found and solved a problem on your own, work you kept developing over time, and your role in a team project can carry even greater value.
Student-owned coding and AI work may provide evidence of interests, technical skill, and initiative. GitHub, apps, and competition records are not universal requirements. If a route permits the material, describe the student's exact role, dates, outcome, limitations, and mentor support truthfully.
Yes. We coach students on setting up a GitHub profile, writing READMEs, documenting projects, and managing their commit history. Especially when applying to U.S. universities, a GitHub link becomes an important piece of evidence of technical ability.
Timing depends on the state of the existing work, code and data permissions, new validation required, and the academic calendar. We plan in relative weeks after diagnosis and reduce or pause work around mocks, examinations, and required coursework.
Yes. CIT runs 1:1 online sessions using the same curriculum as our in-person classes in Apgujeong. For students pursuing non-CS majors in particular, we match you remotely with a dedicated mentor in the life sciences, humanities, business, or arts. Korean students living in Singapore, Hong Kong, and the U.S. East Coast are already taking part. For details, see the online class guide page.
Not sure how to get started on a portfolio? In a free consultation, we'll walk you through a portfolio strategy tailored to the student's current level and goals.
References (Sources)
ACADEMIC → INDEPENDENT EXTENSION → VERIFIABLE EC
Protect grades and required school submissions first. Then branch into a new, student-owned question and document evidence that the applicable route permits.
Course knowledge + new question + new evidence + student ownership + verification = defensible EC
CIT helps students extend what they have learned into new work. We do not duplicate assessed submissions, write school coursework for students, or present old work as a new competition project. The student must make the decisions, create the work, and be able to explain every part.
CIT does not duplicate assessed submissions, write student coursework, or guarantee awards, international selection, or admission.