- Reading time: 3 minutes
- Price: Free download
- Published: 16th September 2026
- Word count: 626 words
- File format: Text
Personal statement example
My interest in digital preservation began with a practical frustration. For my undergraduate dissertation on interwar allotment societies in the south Wales valleys, I relied on a local newspaper run that had been digitised by a council-funded project around 2008. Roughly a third of the issues I needed were listed in the index but would not open: the viewer required a plug-in that no longer existed, and the files behind it were in a format nobody at the library could identify. I eventually read those issues on microfilm, which worked perfectly well after fifty years. That contrast stayed with me. The analogue surrogate had needed no intervention; the digital one had failed within a decade because nobody had planned for the software around it to disappear.
Since graduating I have worked as a library assistant at a further education college, two and a half days a week. Much of the job is circulation, shelving and helping students who have left an essay draft on a college computer they can no longer log into. That last problem comes up more than people expect, and it has taught me that loss is usually undramatic. Nothing is destroyed; it simply becomes unreachable because an account lapsed, a system was replaced, or the person who knew where things were kept moved on. I also maintain the small local studies shelf and a shared drive of past exam papers, which has given me a modest view of how quickly informal arrangements become de facto archives. The drive has no naming convention, three files called "final", and no record of who created what. I have begun tidying it with my line manager's agreement, and drafting a simple file-naming guide, which has made me appreciate how much preservation work is documentation and negotiation rather than technology.
To build technical confidence I have taught myself the basics of Python, mainly to write scripts that walk a folder tree and report file extensions, sizes and duplicate checksums. I have used DROID on a sample of my own material and was surprised how many files it could not identify with certainty. Reading the Digital Preservation Coalition's Digital Preservation Handbook helped me understand why that matters and gave me vocabulary for concepts I had only half-grasped, particularly the distinction between bit-level preservation and keeping something meaningfully usable. I am interested in how institutions decide where on that spectrum a collection sits when resources are finite, and in the significant properties problem: deciding what about a file actually has to survive.
I volunteer with a community oral history group recording memories of a closed brickworks. Interviews are captured on a borrowed recorder, and until recently the only copies lived on the interviewer's laptop. I proposed a basic routine of uncompressed masters, a listening copy, two storage locations and a spreadsheet of consents and speaker details. Persuading volunteers that metadata is worth the effort was harder than setting up the folders, and it has made me realistic about the human side of this work. Alongside this I help my aunt with shopping and hospital appointments each week, which has taught me to plan carefully around fixed commitments and to be honest about what I can take on.
I want formal grounding in the areas I have only approached from outside: repository standards and the OAIS model, appraisal and selection for born-digital material, web archiving, and the legal and ethical questions around personal data in collections. My longer-term aim is to work in a local authority or university archive service, where digital collections are growing without matching capacity and where someone willing to write dull documentation is genuinely useful. Postgraduate study is the sensible next step, and I am ready to commit to it.
Why this example works — strengths and ways to improve
This is a grounded, credible statement for a taught postgraduate course in digital preservation. Your motivation comes from a real research problem, and your library and oral history work show practical understanding of preservation as documentation and negotiation. The main gaps are limited reflection on what your Python and DROID work taught you, a caring paragraph that is not linked to the subject, and a flat conclusion.
Subject motivation
the digital one had failed within a decade
Your opening is persuasive because the motivation comes from a dissertation obstacle, not a vague passion. Setting microfilm that still worked beside digitised files that were inaccessible explains why preservation planning matters. The contrast is concise and gives the rest of the statement a clear problem to explore.
Academic preparation
the distinction between bit-level preservation and keeping something meaningfully usable
You show independent reading and name real concepts, including significant properties, at a suitable level for a taught master's. You say little about what your history degree gave you in methods, such as source criticism or provenance. That transferable preparation could make the conversion feel more deliberate.
Evidence and reflection
loss is usually undramatic
This is real reflection. You turn routine login problems into an insight about lapsed accounts and lost knowledge, so you are interpreting the experience rather than claiming a generic skill. The technical paragraph is weaker. You say DROID surprised you but not what you did with uncertain identifications.
Relevant experience
three files called "final", and no record of who created what
These ordinary examples work well. The shared drive and the oral history routine show modest, plausible responsibility, with suitable caveats such as having your manager's agreement. Saying that persuading volunteers was harder than setting up folders shows you understand the human side of preservation.
Credibility and voice
someone willing to write dull documentation is genuinely useful
Your voice is honest and dry, and you avoid exaggerating your authority. Your claims match your stage. The paragraph about your aunt is sincere, but its connection to planning feels added on. You could show that self-management through your work commitments, or decide the statement does not need it.
Structure and format
Postgraduate study is the sensible next step, and I am ready to commit to it.
The paragraphs move logically from problem, to work, to technical skills, to volunteering, to aims. Your prose is economical throughout. The final sentence is generic and weaker than everything before it. Ending with the specific problem you want to be equipped to solve would be stronger.
What you’ve done well
- You open with a concrete research failure that sets up the whole statement without melodrama.
- You treat ordinary library and volunteer tasks as evidence and draw clear insights about documentation and human factors.
- Your technical claims are modest and accurate, which supports your credibility.
How this draft could improve
- After naming DROID and your checksum scripts, explain what you concluded or changed as a result, not only that you were surprised.
- Either connect the caring commitment clearly to your readiness for study or remove it, so it does not read as an add-on.
- Replace the closing sentence with a specific link between the topics you want to study and the archive work you plan to do. For a real application, tailor this to the actual programme.