Edinburgh Personal Statement vs Skills Box
Decide what belongs in Edinburgh’s personal statement and separate skills field, with two worked allocation cases and checks for useful overlap.
Edinburgh Personal Statement vs Skills Box
Use Edinburgh’s personal statement to explain your academic direction and course choice. Put relevant experience or training that will not fit there in the separate skills field. Repeat an experience only when each mention does a different useful job.
The difficult decision is usually not whether an internship counts as experience. It is whether the application needs its dates and methods, the reason it changed your study plans, or both in different places.
Our UK masters personal statement examples show a complete statement and its compression. Here, the task is allocating your own material between Edinburgh’s two fields before drafting either one.
What Edinburgh actually says about the separate field
Edinburgh’s current instructions, checked September 16, 2026, allow relevant experience or training in the separate Relevant knowledge/training skills section if statement space runs out. The personal statement is limited to 3,500 characters, approximately 500 words. Check the degree’s own requirements too.
That instruction does not turn the second field into another unrestricted personal statement. Nor does it publish a universal rule requiring bullets, banning overlap or assigning a second 3,500-character allowance. Follow the instructions and counter in your application form; do not assume the two fields have equal limits.
Our recommendation is to build a factual inventory first, then decide what each field needs from it. Writing two complete narratives and removing duplicate sentences afterward often leaves both versions weaker.
Start with an evidence ledger, not two drafts
For each potentially relevant experience, write down four things: what happened, what you personally did, what it demonstrates, and why it matters for this course. Keep these as working notes. They are not a third document to submit.
A useful allocation might look like this:
| Material in your notes | Likely job in the skills field | Possible job in the statement |
|---|---|---|
| A substantial project | Methods used, individual responsibilities, relevant training | An intellectual problem that explains the next step |
| Employment | Relevant tasks and level of responsibility | Why further study is needed after that experience |
| A specialist course | Actual subject, provider and completion status | Evidence supporting a specific academic interest |
| An award | Brief recognition linked to relevant work | Only if the underlying work advances the argument |
| Planned training | Clearly identified future activity, if relevant to the prompt | A bounded plan, never evidence of an acquired skill |
This is an editorial tool, not Edinburgh’s marking scheme. Sometimes a concise statement can contain all the relevant preparation without using the additional field. Sometimes the skills section deserves several short entries. The useful amount depends on your evidence and the form’s instructions, not a duty to make both boxes look equally full.
Test each proposed entry against a simple question: would removing it leave the reader with a materially less accurate account of my preparation? If the answer is no, it may be a résumé detail you do not need to repeat.
A recent graduate: one thesis, two different jobs
Consider a constructed example of an applicant whose final-year project examined how people navigate an unfamiliar online service. They designed a small usability study, recruited participants through their department and compared two interface versions. Their main interest is now research methods for evaluating digital systems.
A weak allocation gives both fields the same miniature project story: the title, participant count, software, result and desire to learn more. That consumes space twice while leaving the reader to infer why this particular degree follows.
A more useful allocation separates the evidence from its interpretation. The skills entry could record the applicant’s role and methods:
Final-year project: designed a usability task sequence, conducted moderated sessions and coded recurring navigation errors. Responsible for study materials and analysis; recruitment procedures were agreed with the project supervisor.
The statement could use that experience to explain a learning need:
Comparing the two interfaces showed me how strongly the task design shaped the findings. I now want more rigorous training in evaluating whether a study measures the behaviour it claims to capture.
These are original illustrations of allocation, not text to copy or a complete Edinburgh submission. A real applicant would use their own facts and connect the learning need to verified features of the selected programme.
The overlap is the project itself. The repeated material is not doing the same work: one passage makes preparation legible; the other explains an academic decision. Removing every shared reference would make the documents harder to understand, not more sophisticated.
If the applicant also received a project prize, ask what the award adds. A brief mention alongside the project may be enough. A second paragraph about winning it is unlikely to explain more than the work already demonstrates.
An experienced engineer: choose preparation, not chronology
Now consider a second constructed case: a software engineer with six years across maintenance, product development and team coordination, applying for a computing masters. Their CV already records employers and dates.
The temptation is to turn the skills field into a shorter CV, listing every language, framework and promotion. That creates breadth without telling the reader which experience matters for advanced study.
We would select two or three relevant capabilities and attach evidence to each. For example, the applicant might identify responsibility for diagnosing concurrency failures, designing repeatable tests and documenting a system migration. The record should make clear whether they designed the approach, implemented an assigned component or supervised others doing the work.
The statement then needs a different answer: why is a degree the right next step? Perhaps repeated reliability problems exposed a gap between practical debugging and the formal methods needed to reason about complex systems. That is a possible educational argument if it is true and the programme offers relevant study. Years employed alone do not supply it.
Suppose the applicant completed a short statistics course but has only registered for a second one. The ledger should distinguish these statuses before prose makes them sound alike. Completed coursework can support a claim about preparation; registration can support only a claim about an intended activity. Neither should become an unqualified declaration of expertise.
This selection also protects useful space for the course choice. If the statement is still mostly a career timeline, the problem is not necessarily an insufficient character limit. Too many facts may be doing the work of a missing explanation.
Should the skills field use bullets or paragraphs?
Use the format that makes the relevant evidence easiest to understand within the actual form. Edinburgh’s public instruction does not settle this choice for every application.
Short labeled entries are useful when the reader needs to distinguish several kinds of preparation. A compact paragraph can work when several methods belong to one experience and separating them would obscure your role. Neither format improves vague content by itself.
Compare “Python, analysis, leadership” with an account identifying the analysis you performed and the decisions you owned. The latter gives each skill a basis. You do not need to attach a dramatic achievement to every entry; accurately bounded routine work can be relevant preparation.
Before submission, paste into the form and inspect the result. If bullets disappear, use short labels or sentences that remain intelligible without formatting. Keep the information understandable as plain text rather than relying on indentation to explain which details belong together.
When another box is the wrong destination
A specifically named skills field has a different purpose from a generic optional box. Our guide to graduate additional information explains why extra space is not automatically an invitation to submit another essay. Moving irrelevant material out of the statement does not make it relevant elsewhere.
The arrangement also does not transfer unchanged to every university. UCL’s Data Science and Machine Learning maths note belongs at the beginning of that programme’s statement. An applicant using the same academic records for both destinations still has to follow two different document instructions.
Check the pair of Edinburgh fields together for inconsistent dates, changing project responsibilities and claims that become stronger in the shorter version. Compression should remove detail, not change what happened. Then read the statement alone: can you still understand the academic direction without searching the skills field for its missing explanation?
Finish with your own account
Edinburgh suggests asking a friend to proofread, while warning that copying, asking someone else to write the statement or using AI apps “could be considered fraud.” Those statements appear on the linked university page; the availability of another service does not establish permission under its rules.
The UK taught-masters statement rubric describes the main statement’s academic and educational case. The graduate statement review route concerns that statement, not a separate skills-field assessment or validation of your qualifications. Read the institution’s current assistance instructions when deciding how to work on an application.
More graduate application articles cover adjacent document decisions. For this one, the final test is practical: each field should add information or reasoning that helps the reader understand the same truthful account of your preparation.
Get SOP Feedback
See how your statement of purpose scores on an application-specific rubric.