13.2 Presentation Techniques & Design Communication
Key Takeaways
- The conventional reading sequence of a presented design — concept first, then plans, sections, and elevations, then the perspective or rendering last — remains testable knowledge even though no board is submitted under the current OMR format
- A perspective or rendering communicates spatial experience and material intent, but only dimensioned orthographic drawings can prove a design actually meets area, code, and clearance requirements
- Standard sheet annotations — scale notation, north arrow, project title, and sheet number — are required graphic-knowledge recall items regardless of how strong the design itself is
- The conventional evaluation order — clarity of concept, completeness of required drawings, then legibility — is the sequence OMR items use to judge described presentation scenarios
Presentation Techniques & Design Communication
Quick Answer: Since PRBoA Resolution No. 14, Series of 2009 reformatted the Architectural Design and Site Planning subject into a non-drafting, OMR-scored exam, no presentation board is physically submitted or read by jurors. What the exam now tests is the candidate's grasp of design-communication principles — composition and hierarchy, the complementary roles of perspective and orthographic drawings, labeling, and how a presented solution is conventionally read — through situational multiple-choice items that describe a presentation scenario and ask which choice communicates most effectively or which omission creates a specific problem.
A presentation board is not a random collection of drawings; it is a communication tool with its own logic, and that logic is what the OMR items probe. Even though no board is produced on exam day, an architect must still know how a solution is organized, hierarchical, and legible, because items describe boards and ask the candidate to judge them.
Composition and Hierarchy on the Board
A presentation board should read the way a well-structured argument reads: main idea first, supporting evidence after. In practice this means:
- The concept or parti — the single organizing idea behind the design (for example, a courtyard scheme responding to cross-ventilation, or a linear plan following a site's long axis) — should be visible at a glance, often through a small diagram, not buried among the technical drawings.
- Drawings should be arranged in a logical viewing sequence: site development plan first (establishing context), then floor plans, then sections and elevations, then the perspective or rendering last, so a reader's eye moves through the project the way the designer thought through it.
- Scale of importance on the sheet should match scale of importance in the design: the primary floor plan or key section should occupy more visual weight than a minor detail.
- Consistent margins, alignment, and spacing (a grid) keep the board from feeling cluttered, which matters because a cluttered board slows comprehension and invites the reader to miss a required drawing.
An OMR item may describe a board whose concept is buried among details, or whose drawings are ordered out of sequence, and ask the candidate to identify the communication flaw.
Perspective and Rendering Alongside Orthographic Drawings
A perspective view or rendering shows what a floor plan or elevation cannot: the lived spatial experience of a space, the interplay of light and shadow, and the perceived quality of materials and proportion. It is often the first thing a reader looks at because it communicates design intent immediately and emotionally.
However, a perspective can never substitute for orthographic drawings. Only a dimensioned floor plan can prove a room meets a required area; only a section can prove a stair or ramp meets code; only an elevation can prove a facade's height and fenestration pattern. The strongest presentations pair both: the perspective sells the idea, and the plans, sections, and elevations prove the idea actually works. A board that shows only a beautiful rendering with an incomplete or missing plan set fails its communication purpose, because completeness of the required drawings is judged independently from graphic polish — exactly the principle an OMR item tests when it asks why a perspective-only presentation is deficient.
Labeling and Annotation Practices
Every sheet, regardless of how strong the design is, needs a minimum set of annotations to be read correctly:
| Element | Purpose |
|---|---|
| Project title and sheet/plate number | Identifies what the reader is looking at and where it fits in the full submission |
| Scale notation | Lets the reader verify dimensions and area claims |
| North arrow | Establishes orientation for climate-responsive and code-related judgments |
| Room or space labels | Confirms the program has actually been addressed, space by space |
| Key dimensions | Demonstrates the design meets area, setback, and clearance requirements |
| Legend for symbols/materials | Removes ambiguity when non-standard symbols or hatches are used |
Missing even one of these on a given sheet forces the reader to guess at information that should have been stated outright. An OMR item may list a sheet's annotations and ask which required one is missing — a candidate who knows this baseline set answers confidently.
Common Presentation Pitfalls
Even technically competent designs suffer from preventable presentation errors. Overcrowding a single sheet with too many drawings at inconsistent scales makes every drawing harder to read at once; leaving large blank, unused space on one sheet while cramming another is a sign of poor sheet planning rather than a stylistic choice. Inconsistent north-arrow orientation across sheets in the same submission, for example orienting the site plan one way and a floor plan another, forces the reader to mentally re-orient the project sheet by sheet, which slows comprehension and invites misreading. Inventing a non-standard symbol or hatch pattern without including it in a legend leaves the reader guessing at what a mark on the page is supposed to represent; when in doubt, a candidate should use the conventional symbol covered earlier in this chapter rather than a shorthand that only makes sense to the person who drew it.
How a Presented Design Solution Is Conventionally Read
Examiners evaluating a presented design solution typically look for three things, roughly in this order:
- Clarity of concept — can the design's central idea be identified within the first few seconds of looking at the board?
- Completeness of required drawings — are the site development plan, floor plans, sections, elevations, and any other requested deliverable all present and consistent with each other?
- Legibility under time pressure — is the line work clean enough, and the labeling clear enough, that the drawings can be read and judged quickly and confidently?
A design that scores well on all three criteria communicates efficiently: a reader should never have to hunt for information or guess at intent. Under the current OMR format, this evaluation sequence is itself testable knowledge — an item may ask which of two boards communicates more effectively, or which omission most undermines legibility — so a candidate must know the sequence even though no board is submitted.
Why should a perspective or rendering never replace orthographic drawings (plans, sections, elevations) in a presented architectural design solution?
Which of the following is NOT one of the minimum annotations every standard architectural sheet should carry?
In what order is a presented design solution conventionally evaluated?
Under the current, PRBoA Resolution No. 14 (Series of 2009) format of the Architectural Design and Site Planning subject, how is a candidate's grasp of design-communication principles most likely assessed?