Documenting design evolution with timeline boards

Architecture students are often asked to explain why a final proposal looks the way it does, yet a jury usually sees only the resolved building. A timeline board series restores the reasoning behind it. Each board can expose a stage of concept development, comparison and testing, making the evolution of a design visible rather than presenting the finished work as an isolated object.

The method is especially useful for NAGOYA Archi Fes, where final-year projects meet professional jurors, educators and visitors from the wider community. Rather than squeezing the whole process onto one oversized wall, students can use several boards as a chronological record: brief and site, early propositions, design development, testing and final resolution. Visitors can enter at any board, while the sequence still preserves cause and effect.

For Australian students, the content must also speak to local conditions. A project tested in Brisbane’s humid climate needs different performance evidence from one in cooler, changeable Melbourne, while a coastal Sydney site raises salt and UV exposure that are not equally important inland. Studios can strengthen that account with familiar market options such as spotted gum where supply allows, recycled brick and reclaimed timber. These references make technical decisions feel grounded rather than imported from an overseas precedent.

How to document the evolution of your design through a series of timeline boards is therefore less about drawing more and more about deciding what belongs. The boards should show what changed, why it changed and what the team learned. Used well, they become both a design argument and a practical portfolio asset for interviews, competitions and future calls for proposals.

Start with a narrative, not a diary

Begin with the project’s central proposition, not the date of the first sketch. Write a one-sentence design question that the sequence must answer, then identify the evidence needed to answer it credibly. This gives every board a job and prevents the familiar problem of boards becoming a scrapbook of attractive but unrelated images.

A workable narrative often moves through four movements: framing the brief and site, testing competing ideas, refining one proposition and showing final integration. These are editorial phases, not claims that design happened in a straight line. State where the work overlapped, reversed or skipped ahead; that candour gives a jury a clearer account of iteration than a falsely tidy chronology.

Design the sequence for two audiences at once. Jurors need evidence of rigour, including precedents, constraints and evaluation criteria. Other visitors need a shorter route through the same story, with plain captions and a legible hierarchy of drawings. A board that makes the reasoning clear to a non-specialist often communicates professional judgement more effectively than a dense technical display.

Turn project phases into visible milestones

Give each board a stable title and an explicit moment in the process. “Site and brief”, “First propositions”, “Prototype testing” and “Final resolution” are useful labels, while dates or version numbers anchor them in time. A header can also record the responsible team member, the decision under consideration and the scale of the work, so the board remains understandable when separated from the exhibition wall.

Milestones should mark meaningful changes rather than routine production. A useful test is whether the board shows a fork in the road: a different spatial arrangement, a revised material strategy, a response to code or community feedback, or a prototype that disproved an assumption. If nothing changed, the material may belong in a process archive or the project portfolio instead of the public sequence.

Early boards should preserve enough of the original brief to make later choices traceable. Include site analysis, user needs and project limits that were known at the outset, then show how those conditions affected each move. For students travelling between studios in cities such as Perth, Adelaide or Melbourne, record the source and date of field observations; precise evidence prevents a local site condition from becoming an anonymous claim.

Select evidence that reveals change

Not every sketch deserves equal space. Select material that reveals a transformation: the option that clarified circulation, the section that corrected daylight, the mock-up that tested a junction, or the comparison that rejected an expensive finish. Prioritise evidence with a clear relationship to the design question, and crop ruthlessly so the board communicates rather than merely contains.

Pair images when change is easier to understand than explanation. Place two plans at the same scale, a model beside its measured drawing, or a photographed mock-up beside the relevant detail. Use arrows sparingly to identify the consequential difference. Colour can distinguish retained and removed elements, but captions must carry the meaning for visitors with low vision or for reproductions that print without colour.

Annotations should record decisions, not describe what is already visible. Instead of “moved stair”, write “shifted stair to free a 1.8 m clear route from the entrance, then widened the landing after accessibility testing”. Keep rejected options when they demonstrate a useful comparison, and explain the criteria used to reject them. A decision log linking each major change to a reason turns separate images into evidence of reflective design practice.

Build a working board checklist

A compact checklist prevents the series from losing coherence during production. Collect evidence as the project develops rather than searching through old files immediately before the exhibition.

Evidence worth collecting

• Dated sketches and plans with selected alternatives marked
• Physical models, mock-ups and material tests photographed from consistent views
• Site photographs tied to analysis of access, light, climate and context
• Captions naming the decision, responsible collaborator and resulting next step

The second pass checks clarity rather than content. Each board should work at a glance, in print and for someone who encounters it outside the exhibition.

Checks before finalising

• Can a visitor identify the issue, move and outcome in under a minute?
• Does every image have a caption that explains why it matters?
• Are dates, scales, north arrows and legends present and consistent?
• Are file names, credits and permissions recorded for the archive?

Make each board legible in a public exhibition

Treat the boards as a small publication rather than a collection of pinned sheets. Establish a grid, a limited type hierarchy and a consistent margin before placing content. Give each board one dominant image, supporting evidence in a predictable position and a short explanatory panel. This visual discipline is familiar from white-easel pin-ups in many Australian architecture studios, but it becomes more useful when refined for a formal juried exhibition.

Check legibility at standing and seated viewing distances, using a printed A1 or A2 proof before committing to large-format output. Diagrams need enough contrast and line weight to survive fluorescent gallery lighting, while model photographs need tonal separation from captions. Provide a digital or printed viewing guide that identifies the reading order, yet allow the physical boards to remain self-contained.

At a public exhibition, even a well-prepared project benefits from conversations around the display. These conference field notes capture how informal exchanges can reveal which explanations resonate and where visitors need more context. Treat such comments as questions to investigate, not as reasons to rewrite history, and adjust the live presentation without erasing the documented sequence.

Use critique to test the story

Test the boards before the jury with people outside the studio. Ask a classmate to narrate the project after viewing the sequence, then note where the explanation becomes uncertain. This audience test is more revealing than asking whether the board is “good”. A family member, recent graduate or neighbouring practice may identify a missing explanation about use, maintenance or cost that the team no longer notices.

External comparison can sharpen the design argument. The NAGOYA Archi Fes discussion of visiting other schools’ reviews explains why seeing another school’s final review can expose assumptions about presentation and critique. Compare how each project frames its brief, not merely how polished it looks, and borrow the method of evidence rather than another studio’s graphic style.

Record feedback in a structured way: observation, interpretation, proposed change, owner and due date. Some comments will contradict each other, so explain how the team weighed them against the brief, codes, resources and intended users. This is also where the series can acknowledge uncertainty. A clearly labelled open question may be more credible to a jury than presenting every stage as a predetermined success.

Preserve the record and carry it forward

After the exhibition, preserve both the boards and the logic behind them. Digitise each board at print resolution, export its source files and keep the exhibition photographs. Store a brief index with the project title, studio, year, team names and board sequence. NAGOYA Archi Fes past editions and resource material provide a useful model for how an event archive can keep student work available to future audiences and prospective exhibitors.

Use the same material to strengthen a portfolio and future tender or competition entry. A condensed selection can sit beside final drawings, while the full board set demonstrates process under different drawing conventions and budgets. Remove confidential site information, personal data and uncredited photography, and check usage permissions. Clear version names prevent a later team from accidentally rebuilding the project from an obsolete file.

The series is complete when it lets another person follow the project’s reasoning without the team narrating every transition. A final test is to archive the current board set, ask a peer to read it cold and note any unexplained break in the chronology. Create a shared folder called Timeline_Boards, place the brief, dated iterations, selected tests and decision log in it, and schedule a thirty-minute board audit before the next studio review.