A personal project has value in a study abroad application when it solves a small, real problem, is used by or benefits people outside the family, and the student can explain what they decided at each step. Scale matters less than truth: a small app for the school library with twenty users usually weighs more than a "start-up fund" that exists only on a landing page.
Global Gate Pass mentors do not assign project topics to students. The mentor's job is to help the student find a problem from their own life, break the project into milestones achievable in spare time, keep the pace going, and teach them to record the process so they can tell it later in their essay. This article goes through that process, along with the signs that make a committee suspicious of a project.
How a personal project differs from a club
A club comes with a ready-made frame: a meeting schedule, someone in charge, activities that repeat every year. Students join and then rise into roles. A personal project has no frame. The student has to ask the question, make the plan, find collaborators and decide when to stop, all by themselves. Precisely because there is no frame, a project shows the committee an ability a club rarely shows: the ability to start something from nothing.
For the same reason, projects are the kind of activity easiest to fake. Admissions committees at American universities read thousands of "projects" every season, many of which sound alike: tutor-matching platforms, mini scholarship funds, mental health apps. They do not reject ideas for sounding familiar, but they read the details closely: who uses it, for how long, which part the student did themselves, where it failed.
So mentors judge a project by the length of the chain of real work behind it, not by its name. A project with a modest-sounding name and a long chain of work is always preferred over a project with a grand name that stopped after three months.
Five steps a mentor coaches a project through from the start
The process below is how mentors usually structure a personal project for a Grade 10 or 11 student with a few hours a week to spare. The length of each step varies by project; what does not change is that each step has a concrete output before moving on to the next.
- Find the problem, not yet the solution. The student lists the annoyances they or people they know face every week, then picks one where they can reach the people affected. Output: a one-sentence problem statement and the names of three people willing to talk.
- Ask before building. The student talks to those people to understand how they currently cope. Many projects change direction right at this step, and that is a good sign. Output: notes from the conversations.
- Build the smallest prototype. A form, a trial session, a rough mock-up. The goal is something others can use for a few weeks, not a finished product. Output: the prototype and its first few users.
- Measure and fix. The student records what users actually do, not just what they praise. Output: a list of changes and the reasons for them.
- Expand or close deliberately. The project can bring in more people, be handed over to a younger year group, or stop with a final summary. Output: a one-page project summary as material for the application.
These five steps sound simple, but most student projects skip steps two and four. Those are also the two steps that produce the best material for the essay, because they contain the moments when the student discovered they had been wrong.
Choosing the problem: small, close, and with real people
The question mentors use most at the first step is: who would notice a difference if this project succeeded, and can you meet that person next week? If the answer is "students across the country" or "people in disadvantaged areas" and the student has never met any of them, the problem is too far away.
Close problems are usually found at school, in the neighbourhood, in the family's work, or in a hobby the student has long been attached to. Illustrative examples: nobody at school knows which library books are available; a group of friends who play chess has nowhere to practise with players at their level; the family shop keeps records in a notebook and often gets its stock wrong. None of these sounds big, but each has real people, can be tested in a few weeks, and can be told in detail.
Mentors also filter out problems the student is not equipped to handle safely: health advice, psychological counselling for friends, cash fundraising with no organisation behind it. Such projects may come from kindness, but the risk to others and to the student outweighs any benefit to the application.
Weighty projects and projects that invite suspicion
The table below compares the two kinds of project committees often see. The examples in the table are hypothetical, to illustrate how projects are read, not projects of a specific student.
| Aspect | Weighty project | Project that invites suspicion |
|---|---|---|
| Claimed scale | Small and specific: "a book lookup app for the school library" | Large and vague: "an education platform for students nationwide" |
| Users | A specific named group, with a real user count the student counted themselves | Unclear who uses it, or only social media likes |
| The student's own part | Can describe each decision, each revision | Vague descriptions; the technical or organisational work done by adults |
| Time | Runs for many months, with slow periods and reasons for them | Built in one summer, then silence |
| Failure | Clearly explains what did not work and what was changed | No failures at all; everything was a "success" |
| Who can vouch for it | Teachers, users or a supervisor who know the project | Only parents or the company selling the programme |
A project does not need to meet every point in the left-hand column to have value. But if three or more points on the right apply, the mentor will advise narrowing the claims and focusing on the part the student genuinely did.
An illustrative case: from "an English learning app" to a word bank for one class
The following case is constructed for illustration and is not a specific student's application. A Grade 10 student who knows basic programming arrives at a session with the idea of building "an English learning app for Vietnamese students". The idea is not wrong, but the market already has a great many such apps, and the student cannot reach any specific user to ask.
The mentor suggests narrowing it down: among the people you see every week, who is learning English and struggling? The student remembers the free after-school class a friend's mother runs for children in their alley, where the Grade 3 and 4 pupils often forget vocabulary between lessons. After sitting in on two classes and asking the teacher, the student drops the app idea and makes a set of flashcards with audio that runs on the class's old phone, updated each week to match what the teacher is teaching.
The final product is much smaller than the original idea. But it has real users, a teacher who can follow it, revisions made because the children pressed the wrong thing or got bored, and a clear reason for the student to keep going throughout Grade 11. When writing the application, the very moment of giving up the big idea to make something small that works is the material worth telling, more than any download figures.
Keeping the pace while still doing schoolwork
Personal projects die most often in exam season. Students work enthusiastically over the summer, then in November they are busy with tests, the project stops for three months, and nobody reopens it. So mentors set a minimum pace rather than an ideal one: one or two hours a week during the school year, more during the holidays. A minimum pace keeps the project alive, and a project that survives several exam seasons is itself evidence of persistence.
In the monthly meeting, the mentor asks three questions: what did you get done this month, where did you get stuck, what will you do next month? The answers go into a project log that the student keeps. By Grade 12, this log is the source of material for writing the essay and activity descriptions, instead of having to remember everything from scratch.
Mentors also make clear to parents which parts they should not do for their child. Parents can connect the student with people they need to meet, drive them there, and give feedback when asked. Parents should not write code, contact partners, or present on their child's behalf. This line is not only about application ethics but because the student will have to tell the project in their essay themselves, and possibly in an interview too.
Telling the project in the application
A good project can appear in three places in the application: the description line in the activities list, a paragraph or the whole of the essay, and the supervisor's recommendation letter. The three should not repeat each other. The activity line states the role and results; the essay explains why the student did it and how they changed; the recommendation letter confirms it from an outsider's point of view.
A common mistake is using the essay to retell the whole project like a report. The committee has already read the work in the activities list; the essay should go into one specific moment, such as the first time the prototype was ignored by users and the student had to rethink from the beginning. Lâm Hà Phương, the mentor responsible for scholarship strategy and essay coaching for North American applications, usually starts from the project log to find moments like that.
Not every project needs to go into the essay. Some projects belong neatly in the activities list because the essay has a better story elsewhere. Families who would like a mentor to look at whether their child's project is worth developing further can book a free 60-minute first session through the form on the Contact page.
Frequently asked questions
Does a personal project have to relate to the intended major?
Not for US applications, where committees want to see the person more than the major. For UK applications or programmes that admit by subject, a project connected to the subject carries more weight. Mentors weigh this against each student's university list.
Can a group project be listed as a personal project?
Yes, if the student states their role in the group accurately. Committees do not mark down group work; they mark down one person taking credit for the whole group. State clearly what you initiated, which part you led and what the others did.
Should the project have its own website or social media page?
Only when the project needs one to run, for example for users to sign up. A landing page built just to "look professional" adds no value, and a beautiful page with thin content makes the committee more suspicious, not less.
Should a project that stopped midway be listed?
Yes, if the student worked on it long enough and learned something. A project that stopped for a clear reason, such as users no longer needing it, is an honest story. Just state the dates correctly and do not write as if the project were still running.
Does a personal project need written confirmation?
Most admissions systems do not require confirmation documents for each activity. Even so, it is good to have someone outside the family who knows the project well, such as a teacher or supervisor, who can mention it in a recommendation letter or answer if the university asks.
Do Global Gate Pass mentors do the project for the student?
No. Mentors help choose the problem, set milestones, keep the pace, give feedback and teach how to record the process. The doing, the contacting and the presenting belong to the student, because the student is the one who has to tell the project in the essay and interviews.