- Reading time: 3 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 852 words
- File format: Text
Why do you want to study this course or subject?
The thing that made me want to study automation was watching a bottle-filling line on a school trip to a drinks factory and realising that almost nothing on it was clever on its own. A sensor knew whether a bottle was there. A pneumatic arm pushed. A controller decided the order. The intelligence was in how those simple parts had been arranged, and in the decisions someone had made about what to do when a bottle fell over. I spent the rest of the visit asking the engineer what happened during a fault, and she explained that most of her work was not making the line run but making it recover. That has stayed with me more than anything about the machinery itself. Automation engineering appeals to me because it sits between electronics, mechanics and programming rather than inside any one of them. I enjoy the moment in a problem where you have to decide which discipline is actually causing the trouble: whether a jerky movement is a mechanical tolerance, a noisy signal or a badly tuned control loop. I would like to work on manufacturing and materials-handling systems eventually, and I am particularly interested in control theory, industrial sensing and the safety reasoning behind machinery, because those are the parts I can only partly teach myself at home. Studying at degree level would give me the mathematics to design behaviour rather than adjust it by trial and error.
How have your qualifications and studies helped you to prepare?
My A levels in Maths, Physics and Design and Technology have been a good preparation, partly because they disagree with each other in useful ways. Physics gives me idealised systems; DT gives me components with tolerances, friction and parts that arrive slightly bent. Learning to move between the two has been the most valuable thing about the combination. In Maths I have found mechanics and the work on differentiation most relevant, since rates of change are what a controller actually responds to, and trigonometry has come up constantly in working out arm geometry. Physics has covered circuits, fields and oscillations, and studying damped oscillation made me understand why a system that reacts too strongly can end up worse than one that reacts slowly, which is the same idea I later met as overshoot. For my DT coursework I designed and built a small conveyor that sorts plastic parts by height using a photoelectric sensor and a servo-driven diverter arm, controlled by a microcontroller. Writing the specification taught me to be honest about requirements: my first version worked only if parts were fed one at a time, so I added a spacing gate and rewrote the logic as a set of states rather than a long sequence of ifs. Outside lessons I have been working through an introductory electronics book on operational amplifiers and reading about PID control online. I do not claim to have mastered it, but I can now explain why my conveyor arm hunted around its target position, which I could not do when I built it.
What else have you done to prepare outside of education, and why are these experiences useful?
For the past two years I have helped at a model engineering and robotics club that meets on Saturday mornings in a scout hall. I started as a member and now run the beginners' table, teaching eleven and twelve year olds to solder and to wire a motor driver without shorting it. Explaining current limiting to someone who has never held a multimeter has forced me to understand it properly myself, and I have learned to ask what a child has actually built rather than what they meant to build. Last spring I rebuilt the club's line-following robot, which had been unreliable for years, by replacing the sensor mounting with a rigid printed bracket and adjusting the threshold in software; it now completes the course consistently and is used for demonstrations. That is a small thing, but it is the first repair I made that other people rely on. I also work Saturdays and some school holidays at a hardware shop, mainly on tills and the returns desk. Customer-facing work has taught me to listen to a fault description carefully, because people rarely describe what happened in the order it happened, and to separate what a customer observed from what they concluded. I have become the person colleagues send over when a returned power tool needs checking, since I can usually tell a worn brush from a damaged cable. Away from engineering I swim with a club twice a week and have taken on the job of keeping the lane-timing spreadsheet, which is duller than it sounds but has made me tidier about recording data. Together these commitments have taught me to work steadily, to keep notes I can return to, and to be patient with systems that are almost working.
This example has 4,572 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.
Why this example works — strengths and ways to improve
This is a specific, coherent statement whose strongest moments connect ordinary evidence to real engineering ideas: fault recovery, overshoot, state-based logic and diagnosis. Your reflection is usually genuine rather than claimed. The main problem is length: the note gives 4,572 characters, above the 4,000 limit, so you need selective cutting, especially in the third answer, rather than any additions.
Subject motivation
most of her work was not making the line run but making it recover
You turn a common school trip into a precise insight about automation as arrangement and recovery, not machinery alone. The later point about deciding which discipline causes a fault shows you understand the subject's interdisciplinary nature. The closing line about designing behaviour gives a clear academic reason for study.
Academic preparation
studying damped oscillation made me understand why a system that reacts too strongly
You link A level content to control concepts convincingly, showing understanding rather than just listing topics. The Physics and DT contrast is perceptive. The trigonometry and differentiation links are thinner; one well-developed example like damping does more than several brief mentions, which also helps with length.
Evidence and reflection
rewrote the logic as a set of states rather than a long sequence of ifs
The conveyor project is your best evidence: you state a limitation, the fix and a change in approach. Explaining why the arm hunted around its target shows learning over time. This is real reflection, and you avoid overclaiming by admitting you have not mastered PID control.
Relevant experience
separate what a customer observed from what they concluded
You draw transferable diagnostic thinking from an ordinary job, and the club robot repair shows practical reliability work. The swimming spreadsheet and the general closing summary add less. Your teaching and repair examples already demonstrate patience and note-keeping, so these are natural candidates for cutting.
Credibility and voice
That is a small thing, but it is the first repair
Your voice is modest and age-appropriate; claims are scaled to a school student, and being sent returned tools sounds plausible rather than professional. Phrases like 'partly teach myself at home' feel personal. Keep this restraint, and avoid generic summaries such as 'work steadily', which weaken an otherwise distinctive tone.
Structure and format
Each answer clearly exceeds 350 characters and avoids duplicating evidence or naming universities. However, at 4,572 characters the total is over the 4,000 limit. Aim for roughly 3,500 to 4,000 by trimming weaker material. The third answer and the final sentences of answers one and three offer the easiest cuts.
What you’ve done well
- The bottle-line opening gives a specific, intellectually interesting reason for choosing automation rather than a generic passion claim.
- The conveyor coursework shows design iteration, honest limitations and later understanding through PID reading.
- Club and shop experiences are reflected on selectively for teaching, diagnosis and reliability skills.
How this draft could improve
- Cut about 600 characters to meet the 4,000 limit. Start with the swimming paragraph and the closing summary of answer three.
- Trim the Maths topic list to the strongest links so the damping and conveyor examples carry the academic answer.
- Make the final sentence of answer one shorter so your motivation ends crisply.