Academic writing

Architecture Draft Too Vague or Too Dry? Balance Visual and Technical Writing

A practical revision framework for architecture students: connect design intention, spatial experience, and technical detail; keep terminology consistent; and use AI-assisted drafting as a starting point for clearer, more credible academic writing.

When architecture students ask me to fix an AI-assisted draft, the same problem appears again and again: one version sounds like a glossy brochure, while the other reads like a copied product sheet. Your first move is to pair every design claim with one visual cue and one technical detail. Make a simple three-column table: design intention, what the reader can see or experience, and the specification that makes it possible. Before: “The library feels calm.” After: “The reading room uses indirect north light, acoustic ceiling panels, and a repeated desk module to support quiet, individual study.” That pattern keeps your writing grounded without losing the spatial idea. If you cannot fill one column, that is usually the sign that the paragraph needs more evidence or a narrower claim.

Start visual description from a clear viewpoint, not from a pile of adjectives. Tell the reader where the body is, what changes in scale, light, or material, and why that change matters. Then connect it to a technical requirement such as circulation width, daylight control, or accessibility. Before: “The atrium is stunning and welcoming.” After: “From the main entry, the atrium narrows toward the stair, using a lower ceiling and a brighter floor finish to guide visitors; the stair width supports peak class changeover.” This gives tutors a sequence they can test against your drawings, instead of asking them to trust your taste. A clear sequence also helps you avoid the common habit of describing the building as if it were floating outside real use.

Technical specifications should never sit in your paragraph like a copied table. Each spec needs a design reason, and each design reason needs a material consequence. Use a “because” bridge: you chose the system, material, or dimension because it supports the spatial goal. Before: “The façade uses brick, insulation, and triple glazing.” After: “The brick façade and deep reveals reduce visual busyness on the street side, while triple glazing protects the interior study zone from traffic noise.” The sentence still names technical items, but they now serve the architectural argument rather than filling space. When you write this way, even simple materials become part of the design story, not just items in a schedule.

AI drafts often mix terms that sound similar but mean different things in architecture. Pick one term for each element and keep it consistent: if you call it a brise-soleil in section, do not switch to “sun shade,” “facade screen,” and “external blind” in the same report unless you are distinguishing components. Do the same with units and references. If you mention glazing ratio, ceiling height, or acoustic performance, state the reference once and use it in the same format. Consistency makes your writing easier to assess and makes your design decisions look deliberate. A short glossary at the start of a longer report can save your reader from guessing and keep the discussion precise.

Revise your AI-assisted text in three passes instead of asking it to “sound more academic.” First, delete vague intensifiers such as very, stunning, unique, and beautiful unless you can prove them with a drawing, detail, or citation. Second, insert project-specific evidence: plan reference, section marker, material, joint, structural member, or environmental strategy. Third, check sentence rhythm and register so the paragraph sounds like your own academic voice. A tool like EasyDue can help you reword stiff sentences, but you should supply the architectural evidence and final judgment. If a sentence sounds impressive but says nothing about your specific project, replace it with a smaller, verifiable observation.

Before submitting, run a balance check. For every visual claim, ask: which drawing, photo, model view, or detail supports it? For every technical specification, ask: which design intention does it explain? If a paragraph has only imagery, add performance; if it has only performance, add spatial effect. Then read the section aloud and see whether it sounds like a student who understands the project, not like a catalogue. This is also where academic integrity matters: keep your own design reasoning, cite sources properly, and use revision tools to clarify thought rather than replace it. Over time, this habit trains you to write with more control and to use AI drafts as raw material, not final thinking.