- Reading time: 3 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 874 words
- File format: Text
Why do you want to study this course or subject?
The bakery where I work on Saturdays packs iced buns by hand. Six people stand along a bench, and the bottleneck is always the person applying lids, because the lids stick together in cold weather. Nobody had planned it that way; the line had simply grown. I started timing how long a tray took to move from icing to crate, and noticed the whole bench waited whenever the lid person reached for a new sleeve. Suggesting they pre-split sleeves during quiet minutes cut the waiting a little, and my supervisor kept it. That small change made me realise manufacturing is not only about machines, but about how work, people and materials are arranged in time. I want to study manufacturing systems engineering because the interesting problems sit between the mechanical detail and the whole system: how a machine's cycle time, a layout, a maintenance schedule and a batch size interact. Reading The Goal by Eliyahu Goldratt gave me language for what I had seen with the lids, particularly the idea that improving a non-bottleneck station can leave total output unchanged. I also want the engineering underneath it. In Design and Technology I have worked with tolerances, jigs and material selection, and I enjoy that a well-designed fixture can remove an entire class of defects rather than inspecting for them afterwards. A degree that combines mechanics, materials, automation, quality methods and operations modelling is exactly the range I am looking for, and I would like eventually to work in production engineering for manufacturers making physical goods in the UK.
How have your qualifications and studies helped you to prepare?
My A levels in Maths, Physics and Design and Technology have given me complementary habits of thinking. Maths is where I am strongest: mechanics modules involving resolving forces and the statistics work on sampling and normal distributions both feel directly relevant, since quality control depends on understanding variation rather than treating every out-of-spec part as a separate incident. Physics has trained me to estimate before calculating, which helped when I was working out whether a stepper motor could drive a small conveyor I sketched. Design and Technology has been the most practical preparation. For my coursework I designed a wall-mounted storage unit for the college's hand tools, and the useful part was not the finished object but the iterations: my first version used dowelled joints that were slow to assemble and easy to misalign, so I redesigned around a simple locating rebate that made assembly almost self-aligning. Writing up why that change reduced assembly time and error taught me more about design for manufacture than reading about it did. I also took part in a school STEM club where we built and raced CO2-powered model cars, which involved repeatable machining of small parts and realising how much our finishing times varied between team members. Alongside lessons I have read around the subject, including sections of Toyota Production System by Taiichi Ohno, and found the emphasis on making problems visible rather than hiding them behind buffer stock genuinely surprising. I keep a notebook of production ideas I notice in ordinary places, from supermarket self-checkouts to the queueing system at our local pharmacy.
What else have you done to prepare outside of education, and why are these experiences useful?
My sixth form has one 3D printer shared by about forty students, and prints were often failing or being reprinted because nobody knew whose job was running. With my teacher's permission I took on managing it. I built a paper booking sheet with slot lengths estimated from the slicer, added a simple label on each print, and started logging failures with their cause. Over a term the log showed that most failures were first-layer adhesion problems concentrated on one corner of the bed, which led to levelling it properly and cleaning the surface between prints as standard. Reprints dropped noticeably and, more importantly, people could see when their print would be ready. Keeping that log taught me that data collected badly is worse than none, because my early entries just said "failed".
I also ran a small stall at two school fairs making pin badges with a hand press. I costed the blanks, worked out how many designs to pre-cut, and discovered that cutting circles was far slower than pressing them, so the second time I pre-cut everything the night before and the queue moved properly. Profits went to the school's netball kit fund.
My Saturday bakery job has given me a realistic view of shift work, hygiene rules and how people respond to changes they were not consulted about. Twice a week I collect my younger cousins from school and cook for them, which means my week runs to a fixed timetable and I plan coursework around it. I play in a local netball team as centre, where reading the whole court rather than the ball is the same instinct I want to apply to production systems: watching the flow, not just the nearest machine.
This example has 4,872 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, well-observed statement whose bakery, storage unit and 3D printer examples show genuine systems thinking at a believable school level. Its main problem is length: at 4,872 characters it exceeds the 4,000 limit, so you need selective cutting rather than new material. A few weaker items and a forced netball link dilute the stronger evidence.
Subject motivation
manufacturing is not only about machines, but about how work, people and materials are arranged
Your motivation grows convincingly from the lid bottleneck you timed, and the Goldratt link shows you used reading to name what you observed. Explaining the space between mechanical detail and whole systems shows you understand what distinguishes this subject from general mechanical engineering.
Academic preparation
quality control depends on understanding variation rather than treating every out-of-spec part
You connect statistics to quality control rather than just listing modules, which shows real understanding. The storage unit iteration is excellent design-for-manufacture evidence. The stepper motor estimate and CO2 cars are thinner; either develop one or cut it to save space.
Evidence and reflection
data collected badly is worse than none, because my early entries just said "failed"
This is genuine reflection: you admit an early mistake and draw a lesson that matters for manufacturing data. Similar honesty appears in the rebate redesign. The notebook of production ideas is asserted without any example of what you noticed, so it reads as generic.
Relevant experience
most failures were first-layer adhesion problems concentrated on one corner of the bed
The 3D printer project is your strongest outside evidence: a real problem, a system you built, data and a measurable outcome. The badge stall usefully echoes bottleneck thinking. Mentioning the bakery again in answer three repeats evidence already used for motivation.
Credibility and voice
cut the waiting a little, and my supervisor kept it
Your modest phrasing makes the claims believable and avoids sounding like a qualified engineer. The voice is personal and precise throughout. The netball comparison to production flow feels forced, and stating that Ohno was "genuinely surprising" needs a sentence on why it challenged your assumptions.
Structure and format
This example has 4,872 characters across the three answers.
Each answer comfortably exceeds 350 characters, but the total is roughly 870 over the 4,000 limit. The UK production career goal suits multiple choices. Cutting duplicated bakery material, the CO2 cars, the cousins detail and netball would bring it within range without losing core evidence.
What you’ve done well
- The bakery bottleneck and 3D printer log give concrete, ordinary examples that demonstrate systems thinking rather than claiming it.
- Reading by Goldratt and Ohno is linked to your own observations instead of being listed for prestige.
How this draft could improve
- Cut about 900 characters by removing the CO2 cars, the repeated bakery paragraph, and the netball analogy, keeping the printer, storage unit and lid examples.
- Replace the general notebook claim with one specific observation, or remove it.
- Add one sentence explaining what in Ohno surprised you and how it changed your view of buffer stock.