Chubu Region Graduation Design Exhibition
Traditional wooden buildings with tiled roofs nestled among green trees and shrubs on a hillside, with stone steps leading upward in warm natural light
NAGOYA Archi Fes
Chubu Region Graduation Design Exhibition — Organized by Architecture Students

How to write a clear abstract for your architecture competition entry

An abstract is often the first piece of writing a juror reads about your project, and it carries more weight than students usually expect. In a juried exhibition, where dozens of entries compete for attention within a crowded catalogue and a tight review window, a well-crafted summary can be the difference between a project that gets discussed in depth and one that is skimmed past. The challenge is not really about saying less; it is about saying the right things, in the right order, with a clarity that survives translation, scanning, and tired eyes.

For students from Australian schools submitting to international platforms, the stakes are slightly different. Local programmes at institutions such as RMIT, the University of Melbourne, or the University of Sydney tend to emphasise critical writing and research-led design, which means an abstract that simply lists programme and site can feel thin next to entries that frame a clear position. Treating the abstract as a short piece of design writing, rather than a formal obligation, tends to produce stronger submissions and clearer jury conversations.

Know what the abstract is actually doing

An abstract for a graduation design exhibition is not a project description, and it is certainly not a personal statement. It is a compressed argument about why this project, in this place, with this strategy, matters. The reader needs to walk away with three things held in their head at once: what you designed, how you designed it, and why that approach is worth noticing. If any of those three is missing, the abstract feels incomplete, and the juror will have to work to fill in the gap themselves, which most will not do.

Think of the abstract as a stand-in for you when you cannot be in the room. A juror might read it on a train, on a phone, between meetings, or in the late afternoon of a long review day. Under those conditions, sentences that require context, jargon, or careful rereading lose their meaning. Writing for that reading experience is one of the most useful mental shifts a student can make before redrafting.

It is also worth respecting the format expectations of the competition. Some juried shows ask for 150 words, some for 300, some ask for a short paragraph plus a few keywords. Reading the brief twice, then once more the next morning, helps catch constraints that might have been skimmed over. If the brief asks for a single paragraph, do not submit three. If it asks for keywords, do not bury them inside prose. Format compliance is part of the mark.

Anchor your abstract in a single design argument

Every strong project has a core argument, and the abstract is where that argument becomes visible. Trying to capture every aspect of a building, from concept and site to structure and material, will compress everything into mush. Pick the line of thought that best represents the project's intellectual spine, and let everything else support it. A project about adaptive reuse in a coastal town might be framed through continuity; a project about housing on a flood-prone site might be framed through resilience; a project about community space in a suburban context might be framed through everyday ritual. The argument does not need to be philosophical, but it does need to be specific.

Australian students often find this step harder than expected because studio culture rewards breadth. A typical RMIT or Queensland final-year jury might appreciate projects that touch on culture, ecology, structure, and use. In the abstract, however, breadth becomes dilution. Choose one thread, hold it tightly, and let the rest of the design speak through drawings and models rather than through additional paragraphs. The abstract's job is to be sharp, not comprehensive.

A useful test is to ask whether you can state your argument in one sentence, without using the word "and". If the sentence needs several "and"s to hold together, it is probably trying to do too much. Stripping the argument back to a single claim forces clarity, and clarity is what jurors are really scanning for.

Build a simple three-part structure

Once the argument is clear, the structure of the abstract becomes easier to design. A reliable shape is three moves: open with the problem or context, introduce the design response, and close with the implication or outcome. This is not the only workable structure, but it is forgiving, predictable, and adaptable to almost any project type, from a civic library to a small infill house.

The opening should locate the project in a specific condition. This could be a physical site, a social gap, a regulatory tension, or a material question. Saying "this project addresses urban density" is generic; saying "this project addresses the gap between suburban back fences and the regional rail corridor in Melbourne's middle ring" gives the juror a place to stand. Concrete context is the cheapest way to make an abstract feel considered.

The middle should introduce the design response. This is where the core argument lives, supported by a short indication of method. A juror reading "through a series of mass-timber bays that step with the slope" gets more from the design than from "through innovative structural strategies". The middle should not list every move; it should describe the move that embodies your argument.

The closing should land somewhere. That could be a claim about use, an observation about material behaviour, a question left open, or a wider implication. Vague gestures toward "the future of architecture" tend to weaken strong projects. A precise closing sentence, even a quiet one, will feel more confident than a loud generalisation.

Choose words that show, not just tell

The language of an abstract sits in an awkward middle ground. Too informal and it reads as underprepared; too formal and it disappears into the kind of prose that sounds like every other submission. The goal is precision with personality. You want the reader to feel that a particular student, working on a particular site, made particular decisions.

Concrete verbs do heavy lifting here. "Carves", "stitches", "rotates", "anchors", "absorbs", and "echoes" can replace vague verbs like "explores" or "investigates" without sounding decorative. A short list of verbs you actually like, and that suit your project, will save you from leaning on the same two or three words throughout. Concrete nouns do the same work: "the rear laneway", "the existing trusses", "the Saturday market crowd" all carry more information than "the site" or "the community".

Reading the abstract aloud is one of the best editing tools available. If a sentence trips the tongue, it will probably trip the reader. Australian English tolerates shorter, more direct phrasing better than many students expect; a touch of plainness in an academic abstract reads as confidence rather than laziness.

Match the tone to the jury's expectations

Before writing the final version, it helps to spend time looking at past winners, archive entries, and any commentary the competition publishes. If the tone across successful abstracts is reflective, leaning into a personal position is reasonable; if the tone is technical, leaning into building performance and tectonic logic is reasonable. Tone mismatch is a quiet but persistent reason entries get passed over.

For competitions with an international jury, including NAGOYA Archi Fes, it is worth remembering that jurors will often read entries in translation as much as in English. Short sentences, common words, and minimal idioms travel well. An Australian reader might find "this project sits comfortably in its suburban context" pleasant, but a juror reading through translation may lose the nuance. A more concrete phrasing, such as "the building's edge aligns with the existing street setback", survives the trip.

If you want to understand exactly who will be reading your abstract and what they tend to look for, the jury selection panel page is a good place to start. Looking at the kinds of practices and academic backgrounds represented on the panel can help you decide whether to emphasise research, tectonics, social intent, or something else entirely.

Watch for the usual traps

Several recurring problems show up in competition abstracts. The first is the over-explained introduction: two or three sentences that describe architecture as a discipline before the project even appears. If your opening sentence could be deleted from any abstract in any year and still make sense, it is doing nothing. Start with the project.

A second trap is the metaphor stack. Students sometimes lean so heavily on poetic language that the project itself becomes hard to locate. A single, well-chosen metaphor can carry real weight, but four of them in 200 words feel evasive. When in doubt, replace the metaphor with the literal description.

A third trap is the silent site. If the abstract does not mention where the project sits, the project starts to feel as though it exists in a vacuum. Even a brief reference to the local climate, the urban grain, or the social condition of the site gives the reader something to picture. Many Australian projects sit on complicated sites, from bushfire-prone edges to flood-affected river corridors, and acknowledging that specificity early sets up the rest of the argument.

A fourth trap is the missing stake. Abstracts that simply describe a building without saying what the building does for someone, somewhere, tend to read as inert. The stake does not need to be grand. A clear sentence about who uses the space, what activity it supports, or what condition it changes is enough to anchor the project in a real outcome.

Polish through deliberate editing

The first draft of an abstract is rarely the right draft. Plan to write two or three versions, with real time between them. The first draft is for getting the argument down; the second is for tightening language; the third is for removing anything that is not earning its place. Each pass has a different job, and trying to do all three at once usually produces a muddled middle.

It helps to read the abstract against the brief as if you were the juror. Does the abstract answer the question the brief asked? Does it stay within the word count? Does it avoid introducing drawings, models, or references that are not part of the submission? These small checks catch most last-minute problems.

A useful final move is to print the abstract on paper, in the font and size of the actual submission, and read it in that form. On screen, abstracts often look tighter than they are. On paper, with line breaks and margins visible, the rhythm becomes clearer, and any sentence that feels long will announce itself. This is also the moment to catch typos that screen reading tends to hide.

Practical recommendations before you submit

A short checklist of habits to keep in mind as you prepare your final version:

  • Read the brief twice, with a gap of at least one sleep between readings, and underline every constraint before drafting.
  • Write your core argument in a single sentence, without using "and", and check that the abstract supports that sentence throughout.
  • Use one well-chosen metaphor at most, and let the rest of the writing be concrete and specific.
  • Replace vague verbs such as "explores" or "investigates" with verbs that describe what the design actually does.
  • Read the abstract aloud, and cut any sentence that does not survive being spoken.
  • Match the tone to past winning entries and to the composition of the jury rather than to your own preferred style.
  • Print the abstract in its final form before submitting, and read it once more on paper.

Once the abstract is settled, the next concrete step is to put the same core argument into the project's title, the panel text, and any spoken introduction you plan to use during the exhibition. When the abstract, the title, and the spoken framing all carry the same claim, the project reads as a single, coherent piece of work, and jurors, the public, and your own future portfolio readers will all benefit from that consistency.