Raising IELTS from 6.0 to 7.5 in four months for a UK work visa
Lukas needed an overall IELTS 7.0 for a UK skilled-worker visa and had already missed it once at 6.0. A targeted, exam-specific plan took him to 7.5 on his next attempt.
Background
Lukas is a senior software engineer who'd been offered a role in London. The visa required an overall IELTS 7.0. He sat the test cold, scored 6.0, and assumed he just needed 'more English'. In fact his English was strong for his field — what he lacked was exam technique and two specific weak bands.
The challenge
His reading and listening were already near 7. Writing (5.5) and speaking (6.0) were dragging the overall down. With a visa deadline, he couldn't afford a broad, slow course — he needed to lift two bands fast without wasting time on the two that were already fine.
What we did together
- A diagnostic mock placed every band precisely, so we spent his time only where it moved the score: Writing Task 2 structure and Speaking Part 3 development.
- Weekly timed writing under real conditions, each script marked against the official IELTS descriptors with the exact band and what was capping it.
- Speaking practice focused on extending answers and signposting — the difference between a 6 and a 7 in Part 3.
- Two full timed mock exams in the final fortnight to build stamina and remove surprises on test day.
The results
- Overall 7.5 on his first attempt after the programme — comfortably above the 7.0 he needed.
- Writing rose from 5.5 to 7.0; speaking from 6.0 to 7.5.
- Secured the UK skilled-worker visa and relocated to London.
- Reported the test 'felt predictable' — exactly the goal of exam-specific preparation.
I'd have wasted months 'improving my English' in general. The marked mock tests showed me it was two bands and two techniques. Fixing those was fast once I could see them.
— Lukas, Software engineer, Berlin
Start free, or see how our courses are built around goals exactly like these.
Case study shared with the learner's permission; some details changed to protect privacy. See our editorial policy.