How to write a personal statement

1What admissions readers look for

An admissions reader may give your statement ten minutes, often less, with a stack of other files waiting. In that time they are trying to answer three questions: what has this person actually done, what do they want to do next, and why does this program sit between the two?

Most statements answer none of them clearly. They open with a passion anyone could claim and praise the program in words that would fit any school.

The statements that stand out do something simpler. They show one piece of real evidence early, let it explain the goal, and name what the program adds. The rest of this guide shows how.

The three questions

What have you done? Not what you are like. Readers cannot check adjectives, and every applicant uses the same ones: passionate, motivated, hardworking, detail-oriented. They can believe a thing you did. A shift you ran, a problem you traced, a project you finished, a mistake you fixed. Your statement is where that evidence gets its meaning, because your résumé can only list it.

What do you want to do next? A direction concrete enough to picture. “Make a difference in healthcare” does not tell the reader what you will work on. “Design the scheduling systems clinics use to track patients” does, and it lets them judge whether their program can get you there.

Why this program? The bridge between the first two answers. Readers want to know that you understand what they offer, that you need it, and that you will make use of it. Often the people reading are the faculty you would study with, and they are asking a practical question: can this person do the work here, and will they add something to it?

What readers are not looking for

They are not looking for your life story. A statement that starts in childhood spends its best words on the years that matter least. They are not looking for your résumé in sentences, either: a list of roles with “I learned a lot” after each one tells them nothing the résumé did not. And they are not looking for a dramatic hook, a famous quotation or a definition from the dictionary. Those openings delay the evidence the reader came for.

Nor are they looking for perfection. A statement does not need to be brilliant to be strong. It needs to be clear, true and specific, so that by the end the reader can say in one sentence who you are and why you belong in their program.

A test to keep in mind

Read any sentence of your draft and ask whether it could appear in someone else’s statement. If it could, it is not yet doing its job. The first sentence of Maya’s first draft fails at once:

The sentence after it passes, because no one else has her two years at that desk:

2Find your story

Most applicants start writing too early. They open a blank document and try to sound like an applicant. The statement that comes out is made of the phrases applicants use, because that is what the writer was reaching for. Start somewhere else: with what you have done.

Make an inventory

On paper, list everything you have done that took real effort over the last few years. Jobs and internships, research, volunteering, projects, a course that changed your mind, a problem you could not leave alone. Do not judge the list yet. Small things belong on it. Maya almost left off her Saturday shifts at the clinic because they were “just volunteering”. They became the center of her statement.

Then, for each item, answer four questions in a line or two:

1. What exactly did I do? Not the team, not the role: you.
2. What changed because I did it?
3. What did it teach me that I could not have learned another way?
4. Does it point toward what I want to study next?

Write the answers fast and plainly. Specifics matter more than polish. “I registered about sixty patients a shift” is worth more than a paragraph about dedication.

Where strong stories hide

Some patterns turn up again and again in the stories that work:

• A problem that kept coming back. Something that went wrong more than once, in more than one place, until you looked closer.
• A moment you changed your mind. About a field, a method, or what you were good at.
• Work you would do without being asked. The thing you kept doing after the assignment ended.
• Two experiences that turn out to be one. Two parts of your life that look unrelated until you notice they share a question.

Maya’s story is the last kind. At Northline Logistics she traced a recurring scheduling failure to inconsistent intake codes and rebuilt the validation step. At the clinic she watched appointments go missing for what looked like the same reason. On her résumé these are two separate lines. Together they explain why a logistics analyst wants to study health informatics.

How to tell a strong story from a weak one

A strong story is specific: it has names, numbers and outcomes. You acted in it, rather than watched. It connects to what you want to do next, and it is yours, in the sense that no other applicant could tell it. A weak story is general, passive or borrowed: the patient who inspired you, the book that changed your life, the trip that opened your eyes. Those can be true and still be weak, because they describe what happened to you rather than what you did.

If you are stuck, work through the question bank. Each card asks for one thing a reader wants to know, and your answers will become the raw material for the next chapter.

3Choose one and commit

By now you will have several candidate stories, and each will seem worth telling. The hardest decision in the whole statement is to choose one to carry it, and to let the others support that one rather than compete with it.

Maya’s candidates

When Maya wrote her goals on sticky notes, three directions stood out:

• Healthcare and analytics. True, but too broad. Half the applicants to her programs could say it.
• Designing clinical data systems. A stronger direction, and one her experience points toward.
• Fixing scheduling and intake workflow problems. The same failure she saw at Eastside and at Northline. This became her anchor.

She did not drop the other two. They are inside the anchor: fixing intake problems is clinical data work, and clinical data work is healthcare analytics. The anchor is simply the version specific enough to prove.

How to choose

Pick the story that does the most of these at once:

1. Your record can prove it. A reader could check every claim against your résumé, transcripts or recommendations.
2. It explains your goal. Someone who heard the story could guess what you want to study.
3. It points at what the program offers. It leaves a gap that this program, specifically, can fill.

When two stories tie, choose the more specific one. A small, exact story is more convincing than a large, vague one.

Commit

Once you have chosen, commit. Do not hedge with three passions in the first paragraph to keep your options open. A reader who finishes your statement should be able to say what it was about in one sentence, and they can only do that if it was about one thing.

Committing means leaving things out. A good experience that does not serve your anchor belongs on your résumé, not in your statement. This is the part most applicants resist, and the part that most improves their writing.

Stay inside what is true

Choose a story your record supports as it is, not as you wish it were. Do not stretch a small role into a leading one, invent an epiphany, or claim an interest in a professor’s work you have not read. Readers are experienced at noticing, and an exaggeration they catch undoes every true thing around it.

If you are applying to several programs, you do not need a new story for each. The anchor usually stays the same. What changes is the program paragraph, because each program fills your gap in its own way.

4Give it a shape

A chosen story still needs an order. Readers move through your statement once, quickly, so the shape has to make each idea arrive when they are ready for it.

A shape that works for most statements

1. The evidence. Open with what you did: a scene, a fact, a problem. Not a quotation, not a definition, not a passion.
2. What it revealed. The question or problem the evidence uncovered, and why it mattered to you.
3. How you pursued it. What you have done since: the other experiences, now arranged as proof of one direction rather than as a list.
4. The gap. What you cannot yet do. Honest, specific, and the reason you need a degree at all.
5. The program. What this program offers that fills the gap: courses, methods, labs, people, practical work. Specific to them.
6. The goal. What you will do with it, concrete enough to picture.

This is a shape, not a template. Maya’s two drafts use it differently. The first follows her path in order, from the clinic desk to Northline to the program. The second opens with the pattern itself, “the same scheduling failure has found me three times”, and tells the three stories as evidence for it. Both work, because both put the evidence first and let the goal grow out of it.

Proportion

Spend most of your words on evidence and what it revealed, because that is the part only you can write. The program paragraph usually needs a fifth to a quarter of the statement. The goal can be short; a concrete goal does not need much explaining. If your opening paragraph is about wanting something and your evidence arrives on page two, the proportions are upside down.

Length

Follow the program’s limit exactly, whether it is in words, characters or pages, and treat it as a ceiling, not a target. Where no limit is given, many statements run to one or two pages; check what the program’s own guidance suggests. A statement that is shorter and sharper almost always beats one that is longer and looser.

One job per paragraph

Give each paragraph a single job from the shape above, and let its first sentence say what that job is. Then join paragraphs with reasons, not with “additionally” and “furthermore”. Words like because, so and which is why carry your logic from one paragraph to the next, and they force you to notice when there is no logic to carry.

5Write the draft

With a story and a shape, the draft is mostly a matter of saying plainly what happened. Write the whole thing quickly, badly if necessary, and fix it afterward. Leave the opening sentence for last. It is easier to write once you know what it is opening.

Show it, then say it

Every claim about yourself needs something you did behind it. Compare two ways of saying the same thing:

Use numbers where they matter: sixty patients a shift, forty dispatchers, three months of tracking. Use names where they help: the clinic, the company, the course. Explain technical terms once, in plain words, because not every reader is in your field.

Voice

Write in the first person, in active sentences, in the language you would use to explain your work to a thoughtful colleague. Be confident without being grand. You do not need to call your work groundbreaking; describe it accurately and let the reader decide. Do not apologize for yourself, and do not perform humility either.

If something in your record needs explaining, such as a gap, a weak semester or a change of field, address it briefly and factually: what happened, and what has changed since. One or two sentences are usually enough. Then return to your story.

The program paragraph

This is the paragraph applicants most often write last and worst. Research the program properly: its courses, its methods, its labs and clinics, the faculty whose work connects to yours. Then connect each thing you name to the gap you described. A list of professors’ names with no reason attached reads as flattery. One course or one lab, tied to a specific thing you need to learn, reads as a plan.

If you do not yet know a program well enough to be specific, say what you need and why this kind of program provides it, and keep researching. Never invent specifics. A wrong course title or a professor who has left is worse than no name at all.

The ending

End by returning to your anchor and looking forward: what you will do with what the program teaches you. You do not need to summarize the statement, and you do not need to thank the committee for its time. Maya’s draft ends by bringing both halves of her story back to where it began: the clinic taught her who pays when a record is wrong, Northline taught her how to find out why, and she wants to bring both back to the desk where she started.

Help with drafting

Whoever or whatever helps you draft, whether a mentor, a friend or a writing tool, the facts and the voice have to be yours. Every claim must be true and something you can talk about in an interview. Check each program’s policy on outside help, including AI tools, and follow it.

6Check it before you send it

Finish the draft, then leave it alone for at least a day. You cannot see what is on the page while you still remember what you meant to write.

Five tests

1. Read it aloud, start to finish. You will hear the sentences that are too long, the words you repeat and the places where the logic skips a step.
2. The swap test. Imagine another applicant’s name at the top. If a paragraph would still work, it is not yet specific enough.
3. The school test. Replace the program’s name with a competitor’s. Your program paragraph should break. If it still reads fine, it is praise, not fit.
4. The evidence test. Underline every claim about yourself. Next to each, note the thing you did that proves it. Cut or prove the rest.
5. The one-sentence test. Give it to someone who does not know your plans and ask them to tell you, in one sentence, what it is about. If their sentence is not yours, the statement is not yet clear.

Cut

Most drafts improve by losing a tenth of their words. Cut sentences that repeat your résumé without explaining it, sentences that announce what you are about to say, and adjectives that a reader cannot check. Keep anything that only you could have written.

The details that cost you

Before you submit, check the things readers notice for the wrong reasons: the right school’s name in every place it appears, the program’s exact prompt answered in full, the limit and the requested format, and names of courses and faculty spelled correctly and still current. The checklist covers all of it, and you can print it.

When to stop

No statement is ever perfect, and you can revise one forever. Stop when it is clear, true and specific: when a reader would finish it knowing what you have done, what you want to do, and why this program belongs between the two. That is what the reader came to find out.