How to Write an SOP: A Step-by-Step Drafting Process With Examples
This is the working process for drafting a Statement of Purpose, written for students applying for a master's, PhD or undergraduate programme. It starts with a set of brainstorming questions, turns the answers into an outline, shows a before-and-after for each paragraph, and ends with revision passes and a plain position on AI tools and sample SOPs. If you first need to know what an SOP is or how it differs from a visa SOP, read our SOP guide before this one.
Step 1: Answer the brainstorming questions before writing a sentence
Most SOPs that read as generic were written straight into the final document. The writer had no material, so they filled the space with phrases. Spend your first session collecting facts instead. Open a blank document and answer these questions in rough notes, not polished sentences.
- Which two or three courses, projects or tasks taught you the most about this subject? What exactly did you do in each, and what did you produce?
- What problem, question or limitation did you run into that you could not solve with what you knew? This is usually the real reason you want the degree.
- What have you done on your own, beyond the syllabus: an online course, a side project, a competition, a paper you read closely, a tool you learned for work?
- If you have work experience, what did your job involve week to week, and what did you change or build there?
- What will you do in the two or three years after the programme? Name a type of role, sector or research area, not "a successful career".
- Which parts of this specific programme (modules, a lab, a thesis option, a placement) connect to your answers above?
- Is there anything in your record a reader will wonder about: a low semester, a backlog, a gap year, a change of field?
You will not use every answer; the point is to have more evidence than space, so drafting becomes choosing rather than inventing. If question 2 or 5 is hard to answer, sort that out first.
Step 2: Build the outline from evidence, not from headings
The usual SOP order (opening, background, experience, why this programme, goals, closing) is described in our SOP guide. What matters at the outline stage is that each paragraph is anchored to a specific piece of evidence from your notes. Write one line per paragraph: the point it makes and the fact that proves it.
2. Academic background: B.Tech ECE; signals and probability courses; final-year project on sensor noise filtering in Python.
3. Work: 14 months as a data analyst at a logistics firm in Pune; built the weekly route-delay report; tried a regression model that failed on seasonal data.
4. Self-study: completed a time-series course; rebuilt the model with seasonal features; still unsure how to validate it.
5. Why this programme: forecasting module, the applied project with an industry partner, a faculty group working on demand forecasting.
6. Goals: forecasting or supply-chain analytics role in India; longer term, lead an analytics team in logistics.
7. Closing: what I will bring to group projects; one line on readiness.
Read the outline back. Merge lines that make the same point, and cut any line that has a claim but no fact. The outline is the cheapest place to fix structure.
Step 3: Draft the opening and the academic background
The opening should put the reader inside the specific situation that led to this application, in two or three sentences. It is not the place for your whole life story or a general statement about the importance of your field.
Opening paragraph
Since childhood I have been fascinated by technology. In today's data-driven world, data science is transforming every industry, and I want to be a part of this revolution.
In my second month as a data analyst at a logistics company in Pune, I was asked why deliveries in two zones were late every Monday. I found the pattern in the data within a day, but the forecasting model I built to predict it failed as soon as the festival season began. That failure is the reason I am applying for this MSc.
The after version is specific to one person, sets up the rest of the SOP, and shows a gap the programme can fill. Nobody else could have written it.
The academic background paragraph is not a transcript in prose. Choose the two or three courses or projects that connect to the programme and say what you did in them. Mention your CGPA or percentage only if it adds something the transcript does not, such as a rising trend or a top rank in a relevant subject.
Academic background
I completed my B.Tech in Electronics and Communication Engineering from a reputed college with 8.1 CGPA. I scored 92% in 12th and 94% in 10th. I studied many subjects including signals, probability and programming.
My B.Tech in Electronics and Communication gave me more statistics than the name suggests. Signals and Systems taught me to think about noise and filtering, and Probability and Random Processes was the course where I first wrote simulations in Python. My final-year project applied a Kalman filter to noisy temperature-sensor readings; it was the first time I saw a model fail on real data and had to work out why.
The 10th and 12th marks are already in your application form. Space in the SOP is better spent on what the courses taught you.
Step 4: Draft the experience, programme and goals paragraphs
Project or work experience. Pick one or two pieces of work and describe them in enough detail that a specialist could picture them: the data, the method, the tool, what went right and what did not. Admitting a limitation is useful here, because it explains why you need further study.
Work experience
At my company I worked on various data analysis projects and gained valuable experience in tools like Python, SQL and Power BI, which enhanced my skills.
Over fourteen months I built and maintained the weekly route-delay report used by the operations team, pulling about 30,000 delivery records a week from SQL into Python. When I tried to move from reporting to prediction, a linear regression model performed well on the summer data and badly from October onwards. I added seasonal features after a short online course, which helped, but I still had no principled way to test whether the model would hold up next year.
Why this programme. This paragraph must name things that exist only in this programme: a module, a lab, a project structure, a faculty research area. Researching and writing it well is a topic of its own; see how to write the "why this university" section for a method and more examples. The short version: if you could swap in another university's name without changing a word, it is not finished.
Goals. State a realistic next step and a longer-term direction, both specific enough to be believable. Vague ambition ("become a leader in my field") is weaker than a modest plan with a reason behind it.
Goals
After completing my master's, I want to work in a top MNC and achieve great heights in my career, and contribute to society.
After the programme I want to work as a forecasting or supply-chain analyst, ideally with a logistics or e-commerce company in India, where demand swings around festivals are large and poorly modelled. In the longer term I would like to lead a small analytics team that owns forecasting end to end.
Step 5: Write a closing that ends the argument
The last paragraph should be short: three or four sentences that connect your preparation, the programme and your goal, and perhaps one thing you will contribute to the class. Do not summarise every paragraph, and do not ask the committee for a chance.
Closing
I hope the esteemed admission committee will consider my application favourably and give me an opportunity to study at your prestigious university. I assure you I will work hard and make you proud.
I am applying with a concrete problem I could not solve at work and a clear idea of which parts of this programme address it. In group projects I can bring fourteen months of handling messy operational data, which is usually the slowest part of any applied project. I would like to spend the next year learning to build forecasts I can defend.
Habits to remove before anyone else reads it
Many SOPs written by Indian applicants share a set of habits picked up from school essays, coaching samples and formal letters. None of them is wrong in itself, but together they make an SOP sound like hundreds of others. Search your draft for each one.
| Habit | Why it weakens the SOP | What to do instead |
|---|---|---|
| "Since childhood I have been fascinated by…" | Unprovable, and one of the most common openings readers see | Start at a specific, recent moment tied to the subject |
| A famous quotation (Kalam, Einstein, Jobs) | Uses your opening lines on someone else's words | Delete it; your own first sentence will do more |
| Restating 10th, 12th and CGPA marks | Already in the application; reads as filler | Mention a score only to show a trend or explain a dip |
| "Esteemed university", "prestigious institution" | Flattery says nothing about fit | Name the module, lab or project that drew you |
| "Respected Sir/Madam" or a letter format | An SOP is an essay, not an application letter | No salutation or signature unless the format asks for one |
| Ending with a request or a promise to "make you proud" | Sounds like a plea rather than a plan | End on what you will do in and after the programme |
One habit deserves its own note: explaining weaknesses at length. If you have a backlog, a weak semester or a gap, give it one or two factual sentences in the background paragraph, follow it with what changed, and move on. A full paragraph of justification draws more attention to it than the transcript does.
Step 6: Revise in separate passes, then get feedback
Trying to fix structure, wording and grammar in one read means you fix none of them properly. Leave the first draft for at least a day, then revise in passes.
- Structure pass. Write the one-line point of each paragraph in the margin. Does each line still match your outline? Does any paragraph make the same point as another?
- Evidence pass. Underline every claim about yourself ("strong analytical skills"). Each one needs a fact beside it, or it goes.
- Specificity pass. Read the programme paragraph and replace the university's name with a competitor's. If it still makes sense, it needs more specific detail.
- Length pass. Cut to the institution's limit. Cut repeated points and background that does not lead anywhere before you cut evidence.
- Language pass. Read the whole SOP aloud. Rewrite any sentence you stumble on, any passive sentence that hides who did the work ("a model was built"), and any word you would not use in conversation.
- Accuracy pass. Check the programme name, university name, module names and any faculty names against the official website. A wrong university name left over from another application is an easy mistake and a costly one.
For feedback, two readers are enough. One should know your field (a professor, a senior, a colleague) and can check that your technical descriptions are accurate. The other should not, and can tell you whether the argument makes sense to an outsider. Ask both a specific question, such as "What do you think I want to do after this degree?", rather than "Is it good?".
Using AI tools and sample SOPs honestly
Sample SOPs are useful for seeing how others structure the argument and how long each paragraph runs. They are not useful as text. Copying sentences, or lightly rewording a sample, puts you at risk on two fronts: the writing will not match your own record, and some universities and application systems check statements for similarity with other documents. Read a sample, close it, and write from your own notes.
AI writing tools raise the same problem in a different form. A tool can only work with what you give it, so a draft generated from a short prompt will contain the generic claims this article has been removing, and it may invent details. Some institutions now state a policy on AI use in application essays; read the instructions for each application and follow them. If AI use is allowed, the safer use is narrow: asking for grammar corrections or for feedback on clarity on a draft you have already written yourself, then checking every change.
Key takeaways
- Collect evidence first: answer the brainstorming questions in rough notes before drafting.
- Outline one line per paragraph, each anchored to a specific project, course or job.
- Open with a recent, specific moment, not childhood, a quotation or a statement about your field.
- Cut marks already in the application, flattery of the university and requests for a chance.
- Revise in separate passes for structure, evidence, specificity, length, language and accuracy.
- Use samples for structure only; follow each institution's stated policy on AI tools.
Put this into practice
- For definitions, standard structure and length norms, read our full SOP guide.
- Writing the programme-specific paragraph? See how to write the "why this university" section of an SOP.
- Many programmes also ask for a CV; the free Clean Professional template is a plain single-column layout that suits academic applications.
Frequently asked questions
Plan for one to three weeks of part-time work for the first application: a session or two for brainstorming and the outline, a few days for the first draft, and several revision passes with time away between them. Later applications are faster because the background and experience paragraphs carry over and only the programme-specific parts need fresh research.
Yes, if it explains a real decision and takes up little space, for example one or two sentences on why you chose a field. The SOP is mainly about your preparation and plans. If the prompt asks for a personal statement or a diversity statement, more personal content is expected there; check what each document is for.
Having someone else write it is presenting their work as yours, and many institutions ask you to confirm the statement is your own. It also tends to produce exactly the generic text that weakens applications. Feedback and proofreading from others are normal; authorship is not something to outsource.
About Ashish K.
Ashish K. writes and edits the articles on myperfectresumee, the resume and SOP builder run from Gujarat, India. His articles focus on the practical side of an application: how to word a resume bullet, what goes in a cover letter or a follow-up email, how to prepare for an interview and how to structure a Statement of Purpose. He is not a recruiter, careers counsellor or immigration adviser, and his articles say so where it matters.
See all articles by Ashish K. →
Last reviewed on .
How articles are written, checked and corrected is set out in our editorial policy. Spotted an error or something out of date? Tell us and we will review it.