Architecture and design are visual professions, but they run on words. A project is won or lost in a pitch, shaped in a brief, argued over in a review, and recorded in writing that has to survive years of revisions and a contractor who reads it literally. If English is your second language, none of that is about your talent at the drawing board — it’s about whether the people paying for the building understand exactly what you mean. The reassuring part is that the English architects and designers actually need is a narrow, learnable set of skills, not the whole language.
The brief: get it right before you draw a line
Everything starts with the brief, and a brief is really a translation problem. The client describes what they want in the loose language of hopes — “something light and modern, but warm” — and your job is to turn that into questions precise enough to design from. That means probing without sounding like an interrogation: “When you say warm, are you thinking materials, or the way the light falls?” and “What’s the one thing this space has to do that the current one doesn’t?” Then write the brief back to them in plain, confirmable sentences — “You need three bedrooms, a home office that can close off, and a kitchen that opens to the garden” — so any misunderstanding surfaces now, on paper, rather than on site.
Talking a client through a drawing
A plan that’s obvious to you is a maze to a client. Presenting a design in English is the skill of narrating space: walking someone through a drawing as if you were walking them through the finished building. Lead with the experience, not the geometry — “you come in here, and the ceiling lifts as you move towards the light” — and keep the technical vocabulary (elevation, section, massing, circulation) for the moments it genuinely helps rather than to sound expert. The phrases that carry a review are the ones that frame a choice: “The reason we pulled the staircase to this wall is…”, “The trade-off here is a little less storage for a lot more daylight.” When a client can repeat back why you did something, you’ve communicated.
Handling feedback you can actually use
Design reviews are where confident English pays off, because vague feedback is expensive. When a client says “I’m not sure about the front,” your task is to convert that into something designable: “Is it the proportions, the material, or the colour?” Learn the language of disagreeing politely too — “I’d push back gently on that, and here’s why” — because an architect who nods along to every comment ends up building a committee’s compromise. And master the confirmed next step: “So the two changes are the window size and the cladding — I’ll have revised drawings to you by Thursday.” Ambiguity at the end of a meeting has a habit of becoming a dispute three weeks later.
Writing that holds up on site
Your drawings leave the office with notes, specifications and emails attached, and those are read by people who were never in the room. Here, precision beats elegance every time. A specification that says “high-quality finish” invites an argument; one that names the product, the standard and the tolerance does not. Emails to contractors and consultants should be short, numbered where there are several points, and unmistakable about who does what by when. This is ordinary workplace English done carefully, and it’s exactly the ground our workplace English programme covers — the writing and speaking that professional work really turns on, practised on your own live projects rather than textbook scenarios.
You can be the most gifted designer in the room and still watch the commission go to someone who simply explained their idea more clearly. The language of briefs, reviews and specifications is learnable, and sharpening it is one of the highest-return things a non-native architect or designer can do for a career built on persuading people to trust a drawing. If you’d like to work on the English your projects depend on, take a look at our courses — we’ll build the sessions around the conversations and documents you face every week.
