PAQE common mistakes
PAQE · Understand the traps and how to avoid them.
Starting the design vignette by drawing walls and rooms before writing down the program areas, adjacency requirements, and net-to-gross assumptions, then discovering mid-solution that the required square footage will not fit inside the given footprint.
Candidates carry over a studio habit of sketching parti diagrams first and treating the program table as a reference to check later, but the vignette is scored on whether every programmed space exists at the required size and adjacency, so late discovery forces wholesale redrawing under time pressure.
What to do instead
Spend the first five minutes building a bubble diagram with numbered areas and a running total, convert to a grossing factor for circulation and structure, and confirm the total fits the site or floor plate before drawing a single wall. Recheck the running total after every zoning decision.
Treating the site plan as a graphic composition and ignoring the setback, height, floor-area-ratio, and parking calculations that the zoning envelope actually imposes, so a beautifully massed scheme violates the buildable envelope.
Candidates underweight the arithmetic portion of site analysis and assume the drawn site boundary equals the buildable area, forgetting that setbacks, easements, and required open space shrink the envelope before massing begins.
What to do instead
Compute the buildable envelope numerically first: lot area minus required setbacks, maximum footprint from coverage limits, maximum gross area from FAR, and maximum height from the district standard. Draw that envelope as a wireframe and keep all massing inside it.
Designing massing and floor-to-floor heights without coordinating them against the structural bay, the mechanical zone, and the ceiling plenum, producing a section where ducts, beams, and ceilings collide.
Candidates plan in plan view and defer section thinking, so structural depth and mechanical distribution are discovered after the plan is fixed and cannot be accommodated without moving walls or dropping ceilings below code minimums.
What to do instead
Establish a typical bay and a typical wall section early: structural depth plus mechanical zone plus ceiling zone plus finished floor-to-floor. Test the section against the massing before committing to plan geometry, and carry that section through every subsequent decision.
Selecting a structural system or spanning concept that is incompatible with the program's column-free requirements or the site's soil and seismic conditions, then patching it with transfer beams that blow the budget and the ceiling height.
Candidates treat structure as a downstream engineering task and pick systems by familiarity rather than by span, load, and lateral-force demand, missing that long spans, poor soils, and high seismic categories drive system choice from the first sketch.
What to do instead
For each major space, state the required clear span and load, then match it to a system with a known economic range. Check soil and seismic parameters from the given data before choosing lateral systems, and avoid transfer structures unless the program truly demands them.
Specifying envelope assemblies and glazing ratios by appearance or by copied detail without checking condensation potential, thermal bridging, air barrier continuity, or the water-shedding layering of the wall.
Candidates memorize wall section drawings as images rather than as performance logic, so they cannot tell whether a proposed assembly keeps the dew point on the right side, maintains a continuous air barrier, or drains water out rather than in.
What to do instead
For every proposed assembly, trace four continuous control layers - water, air, thermal, vapor - and confirm each is uninterrupted at penetrations and transitions. Check the vapor profile against the climate zone and verify glazing ratios against the energy code allowance.
Laying out egress paths by eye, ending a corridor at a dead end, spacing exits too close together, or sizing the stair width from the floor population without applying the correct occupant load factor and egress width per occupant.
Candidates rely on remembered rules of thumb instead of the actual occupant load calculation and forget that travel distance, common path, dead-end length, exit separation, and capacity are separate checks that all must pass simultaneously.
What to do instead
Compute occupant load by use and area first, then check each egress criterion explicitly and sequentially: exit access travel distance, common path, dead-end limit, remoteness of exits, capacity of the narrowest element, and door swing. Mark each check off on the plan as it is verified.
Treating accessibility as a final cleanup pass, adding a ramp or an accessible stall after the plan is set, which then fails slope, landing, clear-floor, or reach-range requirements because there is no room left to satisfy them.
Candidates see accessibility as a checklist applied at the end rather than a spatial driver, and they underestimate how much continuous clear width, turning space, and vertical circulation geometry the standards actually consume.
What to do instead
Draw the accessible route as a continuous path from the arrival point through every required destination at the start of planning, and dimension clear widths, turning spaces, ramp runs and landings, and reach ranges as you go. Verify each element against the specific technical requirement rather than a general impression.
Writing specifications and assembly descriptions that are either proprietary sole-source language without justification or so vague that they cannot be enforced, and failing to distinguish prescriptive from performance requirements.
Candidates confuse a materials list with a specification and do not understand the master-format organization, the substitution and equal clauses, or where performance criteria belong versus named products, so the document neither protects the owner nor guides the contractor.
What to do instead
Organize by master-format divisions, state scope and submittal requirements explicitly, and choose deliberately between proprietary, descriptive, performance, and reference standards. For each assembly, name the control layers and their performance criteria so the requirement is measurable.
Confusing the phases of project delivery - issuing design development documents as if they were construction documents, or failing to track which decisions are still open at each phase - and mismanaging the submittal and RFI process during construction.
Candidates learn phase names without the deliverables, approval gates, and level of completeness attached to each, so they cannot reason about what the architect owes at each stage or how change orders and shop drawing review actually flow.
What to do instead
Build a phase matrix: deliverable, level of detail, owner approval, and cost estimate type for schematic design, design development, construction documents, bidding, and construction administration. For each submittal or RFI, state who acts, what the architect's review means, and what it does not mean.
Answering professional-practice and ethics items from personal opinion or business instinct rather than from the standard of care, the architect's contractual obligations, and the conflict-of-interest and licensure rules that govern the situation.
Candidates prepare almost entirely on technical content and treat practice questions as common sense, missing that the correct answer usually turns on a specific duty - to the public health, safety, and welfare, to the client under the agreement, or to the jurisdiction under licensure law.
What to do instead
For every practice scenario, identify the duty owed, to whom, and under what instrument (contract, statute, or code of ethics) before evaluating options. Memorize the standard of care definition, typical scope and compensation structures, and the rules on sealing drawings, conflicts of interest, and unauthorized practice.