Documenting Your Design Process for an Online Exhibition Archive

A graduation project is rarely understood through its final drawings alone. The decisions behind the work—the abandoned schemes, material tests, site observations and conversations—show how an architectural idea developed. An online exhibition archive can preserve that journey and help future students, jurors and visitors read the project with greater depth.

For architecture students preparing work for a public digital platform, documentation is both a design task and a communication task. The archive must be clear enough for someone unfamiliar with the site to follow, while still retaining the uncertainty and experimentation that make a process meaningful. A carefully edited record can turn a collection of files into a coherent project narrative.

This matters especially when viewers are accessing the exhibition from different places and devices. Someone in Melbourne may view the project on a phone during a tram journey, while a tutor in Brisbane may study drawings on a large monitor. Images need to load efficiently, captions need to carry useful information, and the sequence should remain legible without a presenter standing beside the work.

An effective archive also respects practical obligations. Australian students should consider copyright ownership, privacy, image permissions and accessibility when publishing photographs, interviews or scanned material. The result should feel generous and open, while making a precise record of who made each contribution and when.

Define The Story Before Collecting Files

Begin by identifying the central question of the project. It might concern housing density, public space, climate adaptation, construction systems or the relationship between memory and place. This question should guide the archive, but it should not become a slogan repeated under every image. Instead, use it to decide which stages of development are essential to show.

A useful process record usually includes the brief, site reading, research references, early propositions, testing, feedback, revision and final resolution. These stages do not need equal space. If a failed model changed the direction of the project, it deserves more attention than a routine software export. The aim is to reveal cause and effect: what was discovered, what was challenged and what changed as a result.

Create a simple inventory before uploading anything. Give each item a working title, date, format, scale and short description. Note whether it is an original drawing, a photograph of a physical model, a digital render, a diagram or a quotation from research. This prevents the archive from becoming a miscellaneous folder and makes later editing faster.

Students in Sydney or Adelaide may have accumulated material across university servers, personal laptops, cloud storage and studio pin-up photographs. Gather these sources into one temporary project directory, then preserve the original files separately from the edited web versions. Keeping both prevents accidental loss of high-resolution material when images are resized for online use.

Select Evidence That Shows Decisions

A strong digital portfolio does not need every sketch. It needs representative evidence. Choose drawings that show a change in thinking: a plan where circulation was reorganised, a section that clarified structure, or a diagram that exposed an environmental problem. A sequence of three related studies can often communicate development better than twelve nearly identical images.

Physical models are particularly valuable because they reveal qualities that renders may conceal. Photograph them in consistent light, from a useful height and against a quiet background. Include one wider image that explains the whole model and several close views that show joints, openings, landscape or material experiments. A ruler, human figure or familiar object can help communicate scale, but use it consistently.

For Australian audiences, climate and orientation often deserve visible attention. If the project responds to harsh western sun in Perth, prevailing winds in Hobart or summer heat in regional New South Wales, document the testing that supports those claims. Sun studies, shadow diagrams, cross-ventilation sketches and material samples can make environmental intentions more credible than a sentence describing them.

Captions should answer the questions an absent presenter would normally receive. State what the viewer is seeing, when it was made and why it matters. “Iteration 04, courtyard study, cardboard and tracing paper, March 2025” is more useful than “model development”. If a drawing is not to scale, say so. If an image has been cropped, explain enough for the viewer to interpret it accurately.

Build A Consistent Digital Record

Before publishing, establish a file naming system that works for both humans and machines. A structure such as projectname_stage_date_itemnumber is practical, while spaces, unexplained abbreviations and labels such as final-final2 create confusion. Use dates consistently, preferably in year-month-day order, and retain a spreadsheet or text file describing the archive’s contents.

Export drawings at a resolution that preserves line quality without creating unnecessarily large downloads. Vector PDFs are often appropriate for plans and sections, while compressed JPEG or WebP files work well for photographs and renders. Check every export at desktop and mobile sizes. Fine line weights that look clear on a studio monitor may disappear on a smaller screen.

Accessibility should be treated as part of design communication rather than an afterthought. Add alternative text to meaningful images, use descriptive headings, maintain strong colour contrast and avoid placing essential information only inside a diagram. A screen-reader user should be able to understand the project’s main argument even if some visual material cannot be fully accessed.

This is also a good point to review the platform’s technical requirements. An archive may have limits on file size, aspect ratio, embedded fonts or video duration. Confirm whether animated material is supported and whether downloadable drawings need a watermark. When the requirements are unclear, students can contact the organisers before spending time preparing files in the wrong format.

Protect Rights, Privacy And Context

Architecture students frequently use photographs, maps, precedent images, product data and quotations. Ownership is not automatically transferred simply because material appears in a university presentation. Keep a record of the source and permission status of every borrowed image. Where permission is unavailable, replace the image with an original diagram, a properly licensed alternative or a concise written reference.

Australian copyright law gives creators rights over original artistic and architectural works, but educational use and public online publication are separate situations. A drawing made by a student is generally different from a photograph taken by someone else of that drawing. If a classmate, photographer or collaborator contributed material, agree on how it may be displayed and credited before the archive goes live.

Privacy deserves equal care. Do not publish identifiable faces, personal contact details, private emails, student numbers or informal studio conversations without permission. If documenting community consultation, remove unnecessary identifying information and explain the purpose of the record. The Australian Privacy Act and related university policies may apply, particularly when a project includes interviews, surveys or sensitive community data.

Site research can also expose cultural and ethical concerns. Images or maps connected to Aboriginal and Torres Strait Islander communities should be handled respectfully, with attention to provenance, permission and appropriate terminology. A project that references Country should identify its location accurately and avoid treating cultural knowledge as decorative content. Context strengthens the archive; careless borrowing weakens it.

Edit For A Visitor Who Was Not There

Organise the archive as a guided path rather than a storage cabinet. A viewer should be able to move from the project premise to evidence, testing and outcome without guessing what comes next. A short opening statement can establish the site, programme and design question, followed by a sequence of visual chapters. Use consistent labels such as “Site”, “Research”, “Iterations”, “Resolution” and “Reflection” if they help navigation.

Keep the written material concise, but do not remove useful uncertainty. A sentence explaining that a structural study failed because the span was unrealistic can be more revealing than polished language about innovation. Visitors are interested in judgement: why one option was rejected, why another was retained and what the student learned through making.

Before submission, ask someone outside the project to navigate the archive without explanation. Observe where they pause, what they misunderstand and which images they skip. A friend studying in another discipline can identify jargon, while a practising architect may notice missing scale information or inconsistent drawings. Test on a phone connected through ordinary mobile data, not only a fast campus network or home NBN connection.

An online exhibition archive should also remain useful after the event. Include the project title, author, institution, year, software or fabrication methods where relevant, and a short statement of the final outcome. If the work develops later, preserve the original exhibition record and add a clearly dated update rather than silently replacing it. This creates a reliable history for alumni, educators, researchers and future exhibitors.

Practical Checks Before Publication

• Confirm that the project title, author name, institution and year are consistent across every page and file.
• Select process images that demonstrate decisions, revisions and experiments rather than simply increasing the image count.
• Write captions with stage, date, medium, scale and purpose where that information helps interpretation.
• Compress digital files, test mobile loading and inspect drawings for missing lines, unreadable labels or accidental cropping.
• Add alternative text, descriptive links, sufficient colour contrast and a logical reading order for accessibility.
• Record permissions and credits for photographs, borrowed references, interviews, maps, fonts and collaborative work.
• Ask an unfamiliar viewer to navigate the archive and note every point where context or instructions are missing.

The most valuable process archive is selective, honest and easy to read. It shows how an architectural proposal moved through observation, speculation, testing and revision, while preserving enough detail for another person to study the work later. Good documentation does not compete with the design; it makes the design’s reasoning visible.

Set aside one uninterrupted session to create the inventory, rename the working files and mark each item as essential, supporting or unnecessary. That first sorting pass provides the concrete foundation for the finished online archive.