The Project Folder That Holds Up Under Jury Questions
A graduation project is judged through a short, intense exchange. A juror may notice one drawing, ask where the structural idea came from, and then move quickly to questions about users, cost, climate or construction. In that moment, your spoken explanation matters, but the folder behind the project can keep your answer accurate, calm and connected to the evidence.
For an architecture student preparing an exhibition such as NAGOYA Archi Fes, the folder is more than a storage place for PDFs. It is a compact record of decisions: what changed, what was tested, what failed, and why the final proposal looks the way it does. Organised well, it helps you retrieve the right diagram or reference before a vague answer turns into a lost opportunity.
Treat The Folder As A Second Presentation
A jury rarely experiences a project in the same order as its maker. Visitors might first see the hero perspective, while a professional juror starts with the site plan or asks about circulation. A well-structured project folder lets you move between those entry points without searching through filenames such as “final_final2_reallyfinal.pdf”.
Think of the folder as an invisible companion to the exhibition board. It should reveal the project’s argument in layers: the problem, the research, the design response, the technical logic and the unresolved questions. When these layers are easy to locate, you can answer with a drawing rather than relying on memory.
This is especially useful in a crowded exhibition environment. A juror may have just reviewed several housing, civic or landscape schemes, so your ability to locate a specific section or environmental diagram gives the conversation shape. Clear access to evidence makes the work feel considered before you have explained every detail.
Build A Traceable Design Story
The strongest folders preserve the path from first observation to final proposal. Early site photographs, mapping studies, precedent notes and discarded options can explain the reasoning behind a decision that otherwise looks arbitrary. Keep these materials, but edit them so they support the story rather than bury it.
Use a consistent naming system based on project stage and content. For example, “03_Site_Climate_WindStudy” is more useful than “wind stuff”, while “07_Sections_Resolved” immediately tells you what is inside. Dates can help with version control, but they should not replace meaningful descriptions. A folder that sorts logically is easier to use when your attention is divided by a live critique.
Every major claim should have a corresponding piece of evidence. If you say the courtyard improves cross-ventilation, keep the wind diagram, section and relevant modelling output close together. If you describe a low-cost construction strategy, place the material palette, wall build-up and cost assumption in the same evidence group.
A short project index can make this relationship visible. List the main design questions, then note the drawing or file that answers each one. This turns the folder into a quick reference system rather than an archive you hope to navigate under pressure.
Organise Around Likely Jury Questions
Jurors tend to test the links between intention and consequence. They may ask why the building is located in a particular part of the site, how a public space is managed after hours, or whether a striking form can be built with the proposed materials. The folder should anticipate these lines of enquiry without becoming a script.
Group information by question as well as by drawing type. A section called “How the building performs” could contain daylight studies, thermal assumptions, façade details and a brief note on seasonal behaviour. “How people use it” might hold circulation diagrams, accessibility decisions, programme testing and a sequence of user scenarios.
A Practical Folder Checklist
Use the following groups to prepare the core project record:
- A one-page project summary with the central proposition, site and programme
- Site research covering climate, movement, context, users and relevant constraints
- Process material showing tested alternatives and the reasons for key changes
- Coordinated plans, sections, elevations, details and three-dimensional views
- Technical evidence for structure, materials, services, access and environmental performance
Prepare a second set of files for questions that often appear after the main presentation:
- A concise response to the project’s biggest design risk
- One diagram explaining the relationship between concept and construction
- A short list of assumptions about budget, staging, maintenance and planning
- Before-and-after comparisons showing how testing altered the proposal
- A backup image set that can clarify details without interrupting the conversation
The aim is not to guess every possible question. It is to make the important relationships visible. If a juror challenges the feasibility of a cantilever, you should be able to show the structural diagram, not scroll through every export from your modelling software.
Make The Digital Copy Jury-Proof
Digital organisation matters when files are shared with tutors, uploaded for exhibition records or opened on a different computer. Keep a presentation PDF, a compressed viewing copy and a source archive. The presentation version should open quickly and display clearly at normal zoom, while the source archive can retain larger drawings, models and calculations.
Check links, fonts, image resolution and file permissions before the jury day. A beautifully composed board loses value if a missing font changes the labels or a cloud link asks for an account no one can access. Export key diagrams as stable PDF pages and keep a local copy on your laptop or USB drive.
A useful folder has a “Start Here” file that explains its structure in a few lines. Include the project title, your name, the latest revision date and the location of the main presentation PDF. This is practical for a supervisor reviewing dozens of projects, and it also gives you an immediate orientation when nerves make familiar material feel strangely distant.
Keep a separate “jury backup” with only the material you are likely to need. It might contain ten to fifteen labelled pages rather than hundreds of working files. The goal is quick retrieval: type a keyword, open a page and point to the relevant evidence within seconds.
The presentation itself still needs to work visually. Advice on crowded exhibition hall conditions is useful here because a folder cannot compensate for illegible boards, weak hierarchy or a project that is difficult to read from a distance. Your digital record and physical display should tell the same story.
Add Local And Professional Realities
Australian students can test their folder against the questions heard in local practice. A project set in Melbourne might need to explain winter daylight, overheating in west-facing rooms and how a proposal responds to a dense inner-urban block. A scheme for Brisbane may need a convincing account of shade, heavy rain, cross-ventilation and outdoor circulation rather than a generic sustainability statement.
The market context matters too. Graduate roles in Sydney, Melbourne, Perth and Brisbane often involve quick coordination between architects, consultants, builders and clients. A portfolio or interview folder that shows clear decisions, revision history and technical understanding can communicate workplace readiness more convincingly than a collection of polished renders.
Use local language accurately. An Australian jury may refer to a “crit”, a “pin-up”, a “DA pathway”, a “builder’s price” or a “site walk” in the same conversation. You do not need to imitate office slang, but you should be comfortable explaining how the project would move from a student proposal towards planning, documentation and construction.
Australian conditions also reward specific evidence. If your project is near Adelaide, discuss water use and heat; if it is near Hobart, consider cold weather, material durability and seasonal comfort. A proposal beside Sydney Harbour or Federation Square should address public access, maintenance and civic visibility, not simply borrow the visual language of a famous place.
These details should sharpen the design argument rather than turn the folder into a compliance report. Explain what the context changes: the section, the threshold, the material choice, the operating cost or the pattern of occupation. Jurors remember consequences more readily than broad claims.
Rehearse Retrieval As Well As Speaking
Many students practise a two-minute speech and stop there. Jury preparation should include a retrieval rehearsal: someone names a drawing or challenges an assumption, and you locate the evidence without losing the thread of your answer. This exercise exposes confusing filenames, missing diagrams and explanations that depend too heavily on memorised wording.
Ask a studio peer to play different kinds of juror. One can focus on social value, another on construction, and another on whether the drawings support the claims. Give each person access to the same folder and notice where they hesitate. Their hesitation may reveal a structural problem in the archive, even if the design itself is sound.
When answering, lead with the decision, then show the evidence, then acknowledge the limit. For example: “The courtyard is positioned here to draw cooler air through the shared rooms. This section shows the pressure difference and openings. The result still depends on seasonal conditions, so the mechanical system provides a supplementary mode.” That answer is precise without pretending that a student project has solved every variable.
A folder also protects you from overclaiming. If a simulation is preliminary, label it as preliminary. If a cost is based on an estimate rather than a quantity survey, state the assumption. Professional jurors generally respond better to a clear boundary around knowledge than to certainty that collapses under one follow-up question.
The wider purpose of the event is exchange between students, educators and practitioners. The NAGOYA Archi Fes community reflects that wider conversation, where a project can be viewed as an exhibition piece, a learning record and a possible starting point for future work. Your folder should support all three readings.
Separate Confidence From Performance
A well-organised project folder cannot replace design quality, and it will not make every difficult question comfortable. Its value is that it reduces avoidable friction. You do not need to remember the exact page number of a drainage strategy while also listening closely to a juror; you need a system that lets you find it.
Avoid filling the archive with every experiment simply to prove that work happened. A large volume of material can make your process look uncertain. Select the studies that explain a turning point, then add short captions: what was tested, what the result showed and what changed next.
Use visual consistency across file names, diagram labels and printed material. If the exhibition board calls a space the “shared workshop” but the plan labels it “community lab”, a juror may wonder whether the programme changed. Consistent terminology makes the project easier to discuss and helps you sound deliberate.
A short reflection can sit at the end of the folder. Record three decisions you would defend, two assumptions you would test further and one unresolved issue. This is more useful than a generic statement about learning. It gives you language for a question about weaknesses while demonstrating that you understand the project’s current limits.
Finish With A Clear Evidence Path
Before the jury, open the folder as if you were seeing it for the first time. Can you identify the main proposition in under a minute? Can you reach the site response, technical logic and key development studies without relying on memory? Can another person understand the file structure while you are speaking?
Make the first screen or page do useful work. Include a thumbnail of the primary board, a concise project statement and links or filenames for the major evidence groups. Keep the latest version clearly marked, archive older versions separately and remove duplicate exports that could cause confusion.
The best project folder creates a quiet form of confidence. It lets you listen to a juror’s question, decide which part of the project it touches, and respond with evidence that is close at hand. That control is valuable in Japan, Australia or any setting where a final presentation is also a professional encounter.
On the day before the jury, duplicate the final folder locally, open the “Start Here” file, and practise finding three pieces of evidence in under thirty seconds each.