- Reading time: 3 minutes
- Price: Free download
- Published: 16th September 2026
- Word count: 623 words
- File format: Text
Personal statement example
My dissertation was meant to be about a strike at a local rope works in 1911. In practice, I spent as much time working out why I could find so little about it. The county archive's online catalogue described the relevant holdings as "miscellaneous papers, c.1905-1920" in a single line, while the digitised newspaper archive returned nothing useful until I searched for the owner's surname rather than the works. The material existed; the description did not lead me to it. When I eventually worked through the box in the searchroom, I found minute books that answered most of my questions. That gap between what a collection contains and what its description reveals is why I want to study information science formally.
My History degree gave me useful habits: reading finding aids closely, keeping a careful record of where things came from, and being sceptical about why some voices are easier to retrieve than others. It also gave me practice in working systematically through large amounts of unstructured material. What it did not give me was any grounding in how information systems are designed, how retrieval actually works, or how organisations decide what to keep. I have been filling in edges of that on my own, but I am conscious that I am working from guesswork and I would like proper theory and vocabulary behind what I do.
The most useful thing I have done since graduating is a small project with the community choir I sing with. Its sheet music lived in four plastic crates, and rehearsals often began with ten minutes of searching. I offered to sort it out. I started with a spreadsheet, then realised I was making decisions I had no basis for: whether to record the arranger, how to handle photocopies of unclear provenance, what to do with sets missing tenor parts. I read about Dublin Core and looked at how published music is described in library catalogues, then settled on a deliberately simple record: title, composer, arranger, voicing, number of copies, condition, and a note field. About 320 items are now listed, stored in an open-source collection management tool running on a spare laptop, with the crates relabelled to match. Two practical lessons stood out. First, consistency matters more than richness; my early records used three different forms of the same composer's name and were effectively unsearchable. Second, the people using a catalogue do not search the way the cataloguer expects, so our committee members search by the concert a piece was last sung at, which is now a field.
My job in council customer services has been unexpectedly relevant. I handle enquiries where residents describe a problem in their own words and I have to translate it into the categories our case system will accept. Poorly chosen categories send cases to the wrong team and add weeks of delay. It has made me think about classification as something with consequences for people, not just a filing convenience, and it has taught me to write clearly for readers who are tired and in a hurry.
I am particularly keen to study information retrieval, metadata standards and the organisation of digital collections, and to understand the ethical questions around data, access and long-term preservation. I have read some of David Weinberger's writing on how digital arrangement differs from physical arrangement, which was a helpful corrective to my instinct that everything should have one correct place. In the longer term I would like to work in a public or academic library service, or in a records role within local government, where description and access are the daily work rather than an afterthought. I am ready to move from improvising to being properly trained.
Why this example works — strengths and ways to improve
This is a focused, credible conversion-course statement. Your motivation grows from a concrete research problem, and the choir catalogue and council work supply ordinary but genuinely relevant evidence with real reflection. The main gaps are thin engagement with information science reading beyond one author, limited detail on technical skills, and an ending that restates readiness rather than showing it.
Subject motivation
the description did not lead me to it
Your opening works because the motivation emerges from a specific failure of retrieval you experienced, not a general love of libraries. The gap between collection contents and description is a real information science problem, and you name it precisely, so the reader understands why this subject rather than more history.
Academic preparation
reading finding aids closely, keeping a careful record of where things came from
You identify transferable History skills honestly and admit what the degree lacked, which suits a conversion course. However, the claim of filling in edges on your own stays vague; naming what you studied independently, beyond Dublin Core and Weinberger, would show more readiness for advanced study.
Evidence and reflection
consistency matters more than richness
This is your strongest reflective moment. Each lesson is anchored in a concrete consequence: three name forms made records unsearchable, and committee search habits produced a new field. You show learning from evidence rather than asserting skills, exactly what a reviewer wants to see.
Relevant experience
classification as something with consequences for people
Council customer services could easily read as filler, but you link it convincingly to classification and user needs through misrouted cases and delay. The choir project adds hands-on cataloguing. Briefly noting what the collection management tool required of you technically would strengthen this further.
Credibility and voice
I am conscious that I am working from guesswork
Your voice is modest, specific and plausible for a recent graduate; claims like about 320 items are proportionate. The honesty about limits builds trust. The single Weinberger reference feels slightly token, so saying what you disagreed with or would test would make engagement feel deeper.
Structure and format
I am ready to move from improvising to being properly trained.
Paragraphs progress logically from motivation to preparation, experience, interests and aims, with clear economical prose. The closing line is neat but restates rather than concludes; the interests paragraph also lists topics fairly generically. Tie your stated interests back to the archive or choir problems to close more strongly.
What you’ve done well
- The rope works archive anecdote turns a dissertation frustration into a precise, subject-specific motivation.
- The choir catalogue demonstrates practical metadata decisions and draws two concrete, earned lessons about consistency and user behaviour.
How this draft could improve
- Specify what you have read or practised independently so that self-directed preparation is evidenced, not just mentioned.
- Connect your listed interests in retrieval, metadata and preservation to the specific problems you encountered, rather than naming them as a general list.
- For a real application, tailor the final paragraph to the actual programme's focus and prompt, and replace the readiness line with a concrete forward-looking aim.