Information management personal statement example

Why do you want to study this course or subject?

Last spring my college library was moving its local history collection into a new room, and I volunteered to help. What I expected to be lifting boxes turned out to be two weeks of arguing gently with the librarian about how the pamphlets should be arranged: by parish, by date, or by the donor who gave them. Each option made different things findable and hid others. That trade-off is what pulled me towards information management. I had assumed organising information was a tidy, almost clerical task, and instead it was a series of decisions with consequences for whoever came looking next.

Studying History and Computer Science together has sharpened this. In History I depend on other people's descriptions of sources; if a catalogue entry is vague, whole documents effectively vanish. In Computer Science I build small databases and learn that a badly chosen field, or a date stored as free text, quietly ruins every query built on top of it. The two subjects meet in questions I find genuinely interesting: who gets to decide what a record is about, how metadata standards survive changes in technology, and what happens to material nobody thought worth describing at the time.

I want to study information management rather than history or computing alone because I am drawn to the practical middle ground: understanding users, collections and systems together. I am particularly interested in how public bodies manage records they are legally obliged to keep but rarely consult, and in the gap between what an organisation thinks it holds and what it actually holds.

How have your qualifications and studies helped you to prepare?

My A levels are History, Geography and Computer Science, and each contributes something I expect to use. History has taught me to read sources sceptically and to write clearly under time pressure; my coursework on nineteenth-century Leicester hosiery workers involved using census returns and trade directories, and I learnt quickly that the index to a collection shapes the argument you can make from it. Geography has given me practice with data: handling survey results, choosing sensible categories for responses, and presenting findings in a way that does not overstate what a small sample shows. Computer Science covers databases, data representation and file structures, which has demystified a lot of terminology I first met in library contexts, such as controlled vocabularies and unique identifiers.

For my Extended Project Qualification I investigated how small parish and community collections decide what to digitise. I read guidance published by the National Archives on collections care and digitisation planning, interviewed our college librarian and a volunteer from a local heritage group, and produced a short report comparing their priorities. The volunteers valued anything that attracted visitors; the librarian cared about condition and demand. Writing it taught me to structure a long piece of research independently, to keep a proper record of my sources, and to accept that a conclusion can be genuinely uncertain.

Alongside this I have been working through Everything Is Miscellaneous by David Weinberger, which argues that digital objects can sit in many categories at once. I find his optimism about tagging worth testing against the messier reality of inconsistent user-supplied labels, which I saw in my own project data.

What else have you done to prepare outside of education, and why are these experiences useful?

I work Saturdays and some holidays on the returns and information desk at a garden centre. It is not a library, but a surprising amount of it is information work. I handle returns without receipts, which means searching transaction records by date, card digits and vague descriptions of a plant; I have learnt how much easier that is when the original record was entered properly. Customers also arrive with half-remembered plant names, and my job is to ask the right questions to narrow it down: sun or shade, how tall, indoors or out. That is essentially a reference interview, and doing it twenty times a shift has made me much better at listening before answering.

At college I volunteer in the library for two lunchtimes a week, reshelving, checking spine labels against the catalogue and helping Year 12 students find their way around the Dewey numbers. Correcting misfiled stock has given me a practical feel for why classification consistency matters more than elegance. I also set up and maintain a shared spreadsheet for my friends' book swaps, with fields for who has which copy and when it is due back, which has been quietly useful and occasionally ignored.

Outside college I play in a local badminton club and take my turn organising the fixture list, which involves chasing people for availability and keeping one authoritative version of the schedule rather than five contradictory group chats. I am the sort of person who notices when a system is not working and would rather fix it than complain about it, and I would like to spend three years learning to do that properly, with theory behind it as well as instinct.

This example has 4,967 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.