Use this guide to connect architectural fundamentals with the decisions assessed by the Architect Registration Examination (ARE) 5.0 in the United States. Each concept explains a useful distinction, calculation, or decision, then applies it through an original example and a mistake to avoid. Numerical examples use stated assumptions; project requirements must come from the governing documents.
Firm Practice and Project Management
1. Professional judgment and the standard of care
Professional care concerns the competence and diligence appropriate to the circumstances. It differs from promising a flawless outcome. Assess an architect's decision using the information available, the agreed services, and the need for appropriate specialist input; applicable law and contract language establish the actual obligations.
Worked example: An unfamiliar facade system prompts the architect to obtain specialist analysis before recommending it. That demonstrates informed judgment without guaranteeing that every future defect is impossible.
Mistake to avoid: Treating an owner's desired result as an automatic professional warranty.
Source reference: ARE Overview: Architect Registration Examination | NCARB
2. Scope and responsibility allocation
A useful scope identifies deliverables, assumptions, exclusions, decision makers, and responsibility for interfaces. A responsibility matrix should distinguish producing information from coordinating or approving it. Coordination cannot succeed when two parties each assume the other will resolve the same issue.
Worked example: The structural consultant designs rooftop equipment supports; the mechanical consultant supplies equipment loads; the architect coordinates their locations. Naming all three tasks exposes the information handoff.
Mistake to avoid: Writing 'coordinate consultants' without identifying inputs, outputs, or responsibility boundaries.
Source reference: ARE Overview: Architect Registration Examination | NCARB
3. Project delivery and contractor selection
Project delivery describes how design and construction responsibilities are organized. Contractor selection describes how a contractor is chosen. They interact but are separate decisions. Compare alternatives through owner involvement, timing, communication paths, and allocation of design and construction responsibilities rather than assuming one approach always performs best.
Worked example: An owner can select a contractor through negotiated qualifications while retaining separate design and construction contracts. Negotiation alone does not create a design-build arrangement.
Mistake to avoid: Confusing a competitive bidding method with the project's contractual delivery structure.
Source reference: ARE Overview: Architect Registration Examination | NCARB
4. Staff utilization
Utilization measures the share of working time assigned to direct project work. With a consistent definition, divide direct project hours by total working hours. Higher utilization can improve revenue capacity, but staffing decisions must also allow for supervision, business development, training, and other necessary indirect work.
Worked example: A staff member records 30 direct project hours during a 40-hour week. Utilization is 30 divided by 40, or 75%.
Mistake to avoid: Assuming every indirect hour is waste or comparing ratios with different denominators.
Source reference: ARE Overview: Architect Registration Examination | NCARB
5. Net multiplier and break-even multiplier
The net multiplier compares net service revenue with direct labor cost. A break-even multiplier includes direct labor and allocated overhead, expressed relative to direct labor. Define revenue and cost categories consistently before comparing them; consultant pass-through amounts can distort the result if included inconsistently.
Worked example: Direct labor of $100,000 and overhead of $140,000 produce a 2.4 break-even multiplier. Net service revenue of $270,000 produces a 2.7 net multiplier and $30,000 remaining before other applicable charges.
Mistake to avoid: Equating a revenue multiplier with a profit percentage.
Source reference: ARE Overview: Architect Registration Examination | NCARB
6. Fee allocation and labor budgets
A project fee must support the services promised, including direct labor, consultants, overhead, and the intended financial return. Translate the labor allocation into hours using appropriate staff cost assumptions, then distribute those hours across tasks. A fee percentage alone does not show whether the work is adequately staffed.
Worked example: A phase has a $24,000 direct labor allowance. At an assumed average direct labor cost of $60 per hour, it supports 400 hours.
Mistake to avoid: Dividing the entire project fee by a wage rate while ignoring other costs.
Source reference: ARE Overview: Architect Registration Examination | NCARB
7. Critical paths and schedule float
A critical path is a longest-duration dependency chain controlling the earliest project finish. Float is the time an activity can move without delaying the relevant milestone under the stated network assumptions. Several paths can be critical, and changes can make a previously noncritical path controlling.
Worked example: After a three-day common task, parallel branches take five and seven days. A two-day final task gives a twelve-day project duration; the shorter branch has two days of float.
Mistake to avoid: Adding parallel task durations as though every activity occurs sequentially.
Source reference: ARE Overview: Architect Registration Examination | NCARB
8. Risk records and controlled changes
A risk record identifies an uncertainty, its possible consequences, an owner, and a response. Change control addresses an actual proposed departure from the agreed scope or baseline. Evaluate effects on fee, schedule, consultants, and deliverables before documenting the authorized adjustment through the applicable process.
Worked example: A possible utility relocation belongs in the risk record. When the owner approves relocating the building instead, that decision triggers a documented scope and schedule review.
Mistake to avoid: Treating an emerging risk as authorization to perform additional services.
Source reference: ARE Overview: Architect Registration Examination | NCARB
Programming and Site Analysis
9. Performance requirements and design solutions
Programming identifies what a project must accomplish before committing to how it will accomplish it. Distinguish a performance requirement from a preferred physical solution. This preserves alternatives and makes evaluation more objective, especially when users describe familiar layouts rather than the underlying operational need.
Worked example: A library asks for a glass meeting room. Further discussion reveals the requirement is supervision from the service desk; visibility could also be achieved through location and controlled interior glazing.
Mistake to avoid: Accepting the first requested form as the only valid solution.
Source reference: Project Planning & Design
10. Net area and gross area
Net programmed area accounts for identified usable spaces; gross building area also includes circulation, walls, support areas, and other components according to the chosen measurement convention. State the convention and distinguish an efficiency ratio from a grossing multiplier before calculating the building's approximate size.
Worked example: A program totals 18,000 square feet net. At an assumed net-to-gross efficiency of 75%, gross area is 18,000 divided by 0.75, or 24,000 square feet.
Mistake to avoid: Multiplying net area by 0.75 when estimating a larger gross area.
Source reference: Project Planning & Design
11. Adjacency and separation requirements
An adjacency diagram expresses relationships rather than final geometry. Distinguish required proximity, convenient proximity, and necessary separation. Evaluate relationships through movement, supervision, noise, security, and service access; two spaces can need operational proximity while still requiring an acoustic or access buffer.
Worked example: A school music room needs convenient access to the performance hall but separation from quiet reading areas. A storage zone between the music room and library can satisfy both relationships.
Mistake to avoid: Interpreting every desired relationship as a shared wall.
Source reference: Project Planning & Design
12. Buildable area and site constraints
The parcel boundary does not define the usable building footprint. Overlay setbacks, easements, access needs, utilities, environmental constraints, and other applicable restrictions. Distinguish a physical obstacle from a documented limitation on use, and verify the terms governing each restricted area.
Worked example: A visually open strip contains a utility easement. A schematic equipment location there remains unresolved until the easement terms and utility access needs are checked.
Mistake to avoid: Assuming land is buildable because it appears vacant on a site plan.
Source reference: Project Planning & Design
13. Contours and slope calculations
Contours connect points of equal elevation. Closely spaced contours generally indicate steeper terrain when the interval and drawing scale remain constant. Calculate percent slope as vertical change divided by horizontal distance, multiplied by 100; use horizontal run rather than the sloped surface length.
Worked example: A path rises 6 feet over a 150-foot horizontal run. Its average slope is 6 divided by 150 times 100, or 4%. Local segments still require separate evaluation.
Mistake to avoid: Assuming an acceptable average slope proves every segment satisfies applicable requirements.
Source reference: Project Planning & Design
14. Climate analysis and orientation
Orientation decisions should respond to seasonal sun, prevailing winds, temperature, humidity, surrounding obstructions, and the building's uses. A climate strategy beneficial in one season can impose costs in another. Evaluate the intended operating periods rather than applying a universal preference for one facade direction.
Worked example: A classroom used through summer needs analysis of afternoon solar gain on west-facing glazing, even if that orientation offers an attractive winter view.
Mistake to avoid: Choosing orientation from a single seasonal condition or compass direction alone.
Source reference: Project Planning & Design
15. Geotechnical findings and settlement
Soil bearing resistance and settlement describe different concerns. A soil may resist a load without a bearing failure yet deform enough to damage finishes or disrupt structural performance. Interpret geotechnical findings with groundwater, variability, adjacent construction, and foundation alternatives through the responsible specialists.
Worked example: Two building wings cross different soil conditions. Differential settlement may govern their coordination even when preliminary bearing resistance appears adequate under both wings.
Mistake to avoid: Treating one allowable bearing value as proof that settlement and groundwater issues are resolved.
Source reference: ARE Overview: Architect Registration Examination | NCARB
16. Runoff volume and downstream effects
Impervious surfaces generally reduce infiltration and increase runoff. A simplified volume estimate multiplies rainfall depth, contributing area, and an assumed runoff fraction, using consistent units. This estimates volume rather than peak flow and does not replace hydrologic analysis or locally required stormwater design procedures.
Worked example: One inch of rainfall over 12,000 square feet, with an assumed runoff fraction of 0.8, gives 1,000 cubic feet multiplied by 0.8, or 800 cubic feet.
Mistake to avoid: Using a runoff-volume calculation to size conveyance without analyzing flow rates.
Source reference: ARE Overview: Architect Registration Examination | NCARB
Architectural Planning and Design
17. Massing and enclosure area
For comparable building volumes, compact forms generally expose less enclosure area than elongated or highly articulated forms. Enclosure area influences heat transfer, material quantity, and maintenance, but compactness must be balanced with daylight, program, site conditions, and useful outdoor relationships.
Worked example: Two one-story options each enclose 10,000 square feet. A 100-by-100-foot plan has a 400-foot perimeter; a 50-by-200-foot plan has a 500-foot perimeter, increasing wall area at equal height.
Mistake to avoid: Calling a compact form optimal without evaluating its interior spaces.
Source reference: Project Planning & Design
18. Circulation hierarchy and wayfinding
Circulation should make primary destinations legible while distinguishing public, staff, and service movement where the program requires it. Evaluate actual routes, intersections, sightlines, and decision points. A simple-looking plan can still create confusing choices or undesirable conflicts between different users.
Worked example: A clinic places its reception desk in view of the entrance and routes deliveries through a separate service connection, reducing uncertainty and intersections with waiting patients.
Mistake to avoid: Relying on signs to compensate for an unnecessarily confusing circulation layout.
Source reference: Project Planning & Design
19. Structural grids and spatial modules
A structural grid should reconcile economical spans with room dimensions, circulation, facade modules, and service distribution. Establishing a grid is an integration decision, not merely a geometric exercise. Compare how repeated modules accommodate normal spaces and how exceptional spaces affect framing and coordination.
Worked example: An office grid accommodates repeated work areas, but a large assembly room needs clear space. Testing that exception early may avoid a late transfer structure.
Mistake to avoid: Selecting column spacing before checking important rooms and vertical service locations.
Source reference: Project Planning & Design
20. Daylight quantity and visual comfort
Daylight availability does not automatically produce useful visual conditions. Evaluate distribution, direct sunlight, glare, contrast, and the tasks performed in the space. Glazing location and shading can matter as much as glazing area, while electric lighting must support changing daylight conditions.
Worked example: A workstation facing an unshaded bright window may experience glare despite abundant daylight. Reorientation and appropriate shading can improve comfort without simply enlarging the opening.
Mistake to avoid: Using total window area as the sole measure of daylight quality.
Source reference: Project Planning & Design
21. Solar geometry and shading
Shading effectiveness depends on solar altitude, azimuth, orientation, and the time of year. Horizontal overhangs are generally better suited to higher-angle sun; low-angle sun often requires other strategies. Evaluate the desired seasonal balance and local solar geometry rather than copying a detail from another facade.
Worked example: An overhang that shades a window at summer noon may leave it exposed to low late-afternoon sun. The design therefore needs a separate assessment of afternoon conditions.
Mistake to avoid: Assuming one overhang depth controls sunlight equally on every orientation.
Source reference: Project Planning & Design
22. Sound isolation and room absorption
Sound isolation limits transmission between spaces; absorption reduces reflected sound within a space. They solve different problems. Isolation depends on the complete transmission path, including doors, penetrations, and flanking routes, while absorption influences reverberation and speech clarity inside the room.
Worked example: Adding acoustic ceiling panels reduces echoes in a meeting room, but conversation still escapes through a poorly sealed door. The door path needs separate evaluation.
Mistake to avoid: Expecting absorptive finishes to provide the same function as a sound-isolating enclosure.
Source reference: ARE Overview: Architect Registration Examination | NCARB
23. Life-cycle cost comparisons
Life-cycle comparisons include initial cost, operation, maintenance, replacement, and relevant residual value over a consistent analysis period. Discount future amounts consistently when performing present-value analysis. A lower purchase price can produce higher total cost, but assumptions about service life and operating conditions must be explicit.
Worked example: Option B costs $12,000 more initially but saves an assumed $2,000 annually. Its undiscounted simple payback is six years; that alone does not establish the better life-cycle choice.
Mistake to avoid: Treating simple payback as a complete life-cycle analysis.
Source reference: Project Planning & Design
24. Comparing alternatives with weighted criteria
A decision matrix makes priorities explicit by assigning weights and consistent scores to alternatives. First eliminate options that violate mandatory constraints; then compare acceptable options. Weighted scoring supports discussion but cannot turn a prohibited or functionally impossible design into a valid choice.
Worked example: With weights of 60% for function and 40% for cost, an option scoring 8 and 6 earns 7.2. Another scoring 7 and 8 earns 7.4, assuming higher scores are better.
Mistake to avoid: Allowing a high aesthetic score to offset failure of a mandatory requirement.
Source reference: Project Planning & Design
Building Systems and Structural Principles
25. Continuous structural load paths
A load path traces forces from their point of application through connected structural elements to the ground. Gravity and lateral loads may follow different paths. Evaluate connections and transitions as well as individual members; a strong element is insufficient when its supporting connection or next receiving element is unresolved.
Worked example: Roof loads pass through joists, girders, columns, and foundations. Moving a column at one floor requires a deliberate transfer rather than simply deleting the support.
Mistake to avoid: Checking members individually while overlooking discontinuities between them.
Source reference: ARE Overview: Architect Registration Examination | NCARB
26. Strength and serviceability
Strength addresses resistance to failure; serviceability addresses behavior such as deflection, vibration, and cracking during use. A member can satisfy a strength check yet perform poorly for finishes or occupants. Longer spans generally increase deflection significantly, so structural depth and stiffness must be considered during planning.
Worked example: A floor framing option supports the anticipated loads but produces excessive vibration for sensitive equipment. Revising stiffness or the framing arrangement addresses a different issue from ultimate strength.
Mistake to avoid: Assuming adequate load capacity guarantees acceptable everyday performance.
Source reference: ARE Overview: Architect Registration Examination | NCARB
27. Tributary areas and gravity loads
Tributary area assigns the portion of a distributed load carried by a structural element, based on the framing arrangement. Multiply area by load intensity using consistent units. This is a load-accounting step; it does not by itself establish member size or satisfy all required load combinations.
Worked example: A beam supporting a 120-square-foot tributary area under an assumed uniform load of 90 pounds per square foot receives 10,800 pounds from that area.
Mistake to avoid: Using the entire floor area for every beam or omitting framing direction.
Source reference: ARE Overview: Architect Registration Examination | NCARB
28. Lateral resistance and torsion
Lateral systems resist wind and seismic effects through elements such as frames, braces, walls, and diaphragms. When lateral stiffness is distributed unevenly, the building can twist as well as translate. Architectural planning should therefore consider system location and continuity, not only the amount of resisting material.
Worked example: Concentrating stiff walls along one edge of an otherwise open plan creates a potential torsional concern that the structural engineer must evaluate.
Mistake to avoid: Assuming any arrangement of the same wall area has equivalent lateral behavior.
Source reference: ARE Overview: Architect Registration Examination | NCARB
29. Foundation selection and ground conditions
Foundation selection depends on loads, soil behavior, groundwater, settlement tolerance, adjacent structures, and construction constraints. Shallow and deep systems distribute loads differently and require different investigations. Architectural coordination should preserve the specialist's assumptions and account for foundation geometry, excavation implications, and surrounding conditions.
Worked example: A heavy addition beside an existing building requires evaluation of both new support conditions and effects on the existing foundation, even if a shallow system appears economical.
Mistake to avoid: Choosing foundation type solely from the building's number of stories.
Source reference: ARE Overview: Architect Registration Examination | NCARB
30. Thermal resistance and parallel heat paths
For an ideal series heat path, thermal resistances add and thermal transmittance is their reciprocal. Real assemblies also contain parallel paths through framing and other bridges, so adding insulation ratings alone can overstate performance. Evaluate the complete assembly rather than the insulation product in isolation.
Worked example: An idealized path with total R-value 20 has U-value 0.05 in corresponding units. Conductive framing paths can increase the assembly's effective U-value.
Mistake to avoid: Reporting cavity insulation's R-value as the performance of the entire wall.
Source reference: ARE Overview: Architect Registration Examination | NCARB
31. Water, air, and vapor control
Bulk water drainage, air control, and vapor diffusion control address different transport mechanisms. A material may perform more than one function, but each function needs continuity and suitable placement. Vapor-control decisions depend on climate and assembly behavior; a universal placement rule can create moisture problems.
Worked example: A wall has a vapor-resistant layer but an interrupted air barrier at a floor edge. Moist air can still enter through that discontinuity and affect concealed surfaces.
Mistake to avoid: Assuming a vapor retarder automatically provides complete air and rain control.
Source reference: ARE Overview: Architect Registration Examination | NCARB
32. Surface temperature and condensation
Condensation can occur when a surface falls below the dew point of adjacent air. Risk depends on temperature, humidity, air movement, and thermal bridges. Increasing insulation, improving continuity, and controlling indoor moisture address different contributors; the appropriate response depends on diagnosing the actual assembly.
Worked example: Indoor air has an assumed dew point of 52°F. An interior window-frame surface at 48°F presents condensation potential, even if the room's air temperature is comfortable.
Mistake to avoid: Diagnosing condensation from room temperature alone without considering humidity or surface temperature.
Source reference: ARE Overview: Architect Registration Examination | NCARB
33. Sensible loads, latent loads, and ventilation
Sensible loads change air temperature; latent loads involve moisture. Ventilation introduces outdoor air and can affect both. A cooling strategy must account for humidity and required air quality as well as temperature, especially where outdoor air is humid or occupancy varies substantially.
Worked example: A crowded meeting room remains cool but humid. Lowering the thermostat alone may not resolve moisture control; the mechanical system's latent performance and operating conditions require review.
Mistake to avoid: Treating cooling capacity, moisture removal, and outdoor-air delivery as interchangeable measures.
Source reference: ARE Overview: Architect Registration Examination | NCARB
34. HVAC zoning and system fit
Thermal zones should reflect differing exposure, occupancy, schedules, and internal loads. Spaces with conflicting conditions may need independent control even when adjacent. System selection must also consider distribution space, maintenance, acoustics, efficiency, and operational needs rather than relying on one favored equipment type.
Worked example: A sunny perimeter office and a continuously occupied interior server room have different load patterns. One thermostat for both is unlikely to represent their needs well.
Mistake to avoid: Grouping spaces into one zone merely because they share a floor.
Source reference: Project Planning & Design
35. Water supply and drainage coordination
Water supply must deliver suitable pressure and flow; sanitary drainage generally depends on gravity, venting, and appropriate routing. These systems have different spatial demands. Early coordination of wet areas, shafts, and service connections reduces conflicts, but slopes, capacities, and required arrangements must follow the applicable design criteria.
Worked example: Stacking restrooms can shorten vertical plumbing routes, yet a transfer level may still interrupt the drainage path and require additional coordination.
Mistake to avoid: Assuming a short supply route proves the drainage and vent systems will also fit.
Source reference: ARE Overview: Architect Registration Examination | NCARB
36. Electrical demand and continuity of service
Connected load is the sum of equipment ratings; anticipated demand considers how loads operate together under justified assumptions. Real power and apparent power also differ when power factor is below one. Critical functions require a separate assessment of continuity needs and applicable requirements, not merely a larger normal supply.
Worked example: A hypothetical 36-kilowatt load at power factor 0.9 represents 40 kilovolt-amperes. That calculation alone does not establish service sizing or backup requirements.
Mistake to avoid: Treating connected load, demand, and standby capacity as the same quantity.
Source reference: ARE Overview: Architect Registration Examination | NCARB
Codes, Accessibility, and Environmental Health
37. Identifying applicable requirements
A project may be subject to several regulatory documents with different purposes and authority. Establish which requirements apply, including adopted editions and amendments, before comparing provisions. Apparent conflicts need interpretation through the appropriate authority; simply choosing the larger number does not resolve every conflict.
Worked example: A zoning setback and a fire-separation requirement both affect building placement. The design must satisfy their applicable conditions because the provisions address different concerns.
Mistake to avoid: Applying a blanket 'most restrictive always wins' rule without checking applicability and authority.
Source reference: Project Planning & Design
38. Use, occupancy, and zoning classifications
Zoning use categories and building-code occupancy classifications serve different purposes and may use different names. Classify the actual activities under each applicable framework. Mixed uses and accessory spaces require careful analysis rather than assuming the project's marketing description determines all classifications.
Worked example: A building advertised as a community center contains offices, a large gathering room, and storage. Each framework must be checked against those actual activities.
Mistake to avoid: Carrying a zoning label directly into the building-code analysis without examining definitions.
Source reference: Project Planning & Design
39. Area, height, and construction strategy
Permitted area and height depend on the applicable code's combination of occupancy, construction type, protection features, and other qualifying conditions. Develop these decisions together. A change in program or structural material can alter the viable strategy, so numerical limits must come from the governing provisions.
Worked example: Expanding an assembly function may change the code analysis enough to require reevaluating construction and separation options rather than merely enlarging the floor plan.
Mistake to avoid: Using an allowable area remembered from a different occupancy or code edition.
Source reference: Project Planning & Design
40. Occupant-load calculations
Occupant load relates a space's use and applicable area convention to a prescribed factor or other governing method. Read whether the factor uses net or gross area and follow the stated rounding requirements. Design headcount and code-calculated occupant load may differ and must be reconciled under applicable provisions.
Worked example: For a hypothetical exercise requiring 20 net square feet per occupant and upward rounding, a 1,250-square-foot net room yields 62.5, rounded to 63 occupants.
Mistake to avoid: Using gross area when the stated factor requires net area.
Source reference: Project Planning & Design
41. The complete means-of-egress path
Evaluate egress as a continuous route, including exit access, exits, and exit discharge as defined by the applicable code. Capacity, arrangement, travel, protection, and discharge conditions interact. A sufficient number of doors does not establish that routes are independent, usable, or continuous to the required destination.
Worked example: Two room doors lead into the same dead-end corridor. Counting them as two doors does not resolve the downstream arrangement.
Mistake to avoid: Checking exit quantity while ignoring the route beyond each door.
Source reference: Project Planning & Design
42. Fire-resistance continuity and penetrations
A fire-resistance strategy depends on complete assemblies and their interfaces. Openings, penetrations, joints, and concealed transitions can undermine separation if their required protection is unresolved. Coordinate compatible tested or otherwise approved systems for the actual conditions rather than assuming any fire-labeled product suits every application.
Worked example: A service pipe crosses a rated wall. Its material, size, surrounding assembly, and opening conditions must match an appropriate protection system.
Mistake to avoid: Treating the wall's rating as proof that every opening through it is adequately protected.
Source reference: ARE Overview: Architect Registration Examination | NCARB
43. Continuous accessible routes
Accessibility depends on connected usability from arrival through entrances, circulation, destinations, and relevant facilities. Evaluate route geometry, level changes, doors, maneuvering spaces, and controls together using the applicable requirements. One accessible feature cannot compensate for an interruption elsewhere in the route.
Worked example: A restroom layout provides appropriate clearances, but a stepped corridor is its only approach. The route remains unresolved despite the room's compliant internal arrangement.
Mistake to avoid: Checking individual rooms without tracing how users reach and operate them.
Source reference: ARE Overview: Architect Registration Examination | NCARB
44. Indoor environmental health and source control
Indoor air quality depends on pollutant sources, moisture, ventilation, filtration, and operation. Source control addresses contamination before relying on dilution. Material emissions, outdoor-air intake locations, and maintenance access require coordinated consideration; ventilation cannot reliably compensate for every persistent source or moisture problem.
Worked example: A proposed outdoor-air intake faces a vehicle loading area. Relocating the intake may address exposure more directly than increasing airflow through the same contaminated location.
Mistake to avoid: Assuming more ventilation always corrects poor source placement.
Source reference: ARE Overview: Architect Registration Examination | NCARB
Documentation and Interdisciplinary Coordination
45. Drawing scale and graphic measurement
Scale expresses the relationship between a drawing and the represented object. Use stated dimensions for coordination; graphic measurement is vulnerable to printing, resizing, and reproduction errors. When interpreting an undimensioned feature for an exercise, confirm the applicable view scale and distinguish approximation from an established dimension.
Worked example: At one-quarter inch equals one foot, a three-inch drawn length represents twelve feet, provided the drawing has not been resized.
Mistake to avoid: Measuring a reduced print with the original scale and treating the result as authoritative.
Source reference: ARE Overview: Architect Registration Examination | NCARB
46. Datums and dimension control
A datum provides a common reference for locating work. Coordinated grids, elevations, and dimension conventions reduce ambiguity between disciplines. Dimension chains should establish intended control without creating inconsistent duplicate requirements; finish faces, structural faces, and centerlines are different reference points.
Worked example: An equipment clearance is measured from a finished wall, while structural dimensions locate the concrete face. The finish thickness must be included when coordinating available space.
Mistake to avoid: Assuming dimensions to different reference surfaces describe the same usable clearance.
Source reference: ARE Overview: Architect Registration Examination | NCARB
47. Drawings and specifications as coordinated information
Drawings primarily communicate geometry, location, and relationships; specifications describe materials, quality, performance, and other requirements. Their information must agree. Document precedence, where relevant, comes from the applicable contract rather than a universal rule that one format always overrides the other.
Worked example: A drawing shows a glazed partition while the specification describes an opaque assembly. Resolve the discrepancy rather than expecting the contractor to infer the intended requirement.
Mistake to avoid: Assuming a conflict is harmless because one document is more detailed.
Source reference: ARE Overview: Architect Registration Examination | NCARB
48. Details as continuity checks
A construction detail should explain how systems meet and continue across a junction. Trace water drainage, air control, insulation, structure, and movement accommodation through the interface. Repeating a familiar detail is insufficient when materials, geometry, exposure, or structural conditions change.
Worked example: At a roof-to-wall transition, the wall air-control layer must connect to the roof strategy while drainage follows a separate continuous route.
Mistake to avoid: Drawing each assembly correctly in isolation while leaving the junction unresolved.
Source reference: ARE Overview: Architect Registration Examination | NCARB
49. Clash detection and service access
Coordination must address physical collisions, installation space, operating clearances, and future access. A model with no intersecting objects can still describe an unmaintainable building. Resolve conflicts through the responsible disciplines while preserving structural, environmental, and functional requirements.
Worked example: A valve fits above a ceiling without touching a beam, but no access panel or working space is available. The arrangement still requires revision.
Mistake to avoid: Equating a clash-free model with complete interdisciplinary coordination.
Source reference: ARE Overview: Architect Registration Examination | NCARB
50. Estimates, quantities, and uncertainty
An estimate combines quantities, unit costs, scope assumptions, and allowances appropriate to design maturity. Keep known work distinct from uncertainty provisions and avoid counting the same item twice. An estimate becomes more useful when its inclusions, exclusions, and basis are visible.
Worked example: A hypothetical 2,400-square-foot finish at $18 per square foot totals $43,200. An explicitly assumed 10% design allowance adds $4,320, producing $47,520 for that exercise.
Mistake to avoid: Presenting an allowance percentage as a universal requirement or guaranteed final cost.
Source reference: Project Planning & Design
51. Revisions and document consistency
A revision changes information that may appear in several documents. Track its scope, issue status, and related effects across drawings, schedules, specifications, and consultant information. Clear version control helps recipients distinguish the current requirement from superseded information without relying on informal memory.
Worked example: Changing a door's fire-protection requirement prompts review of the plan tag, door schedule, hardware coordination, and specification rather than revising only one note.
Mistake to avoid: Updating the primary drawing while leaving contradictory information elsewhere in the set.
Source reference: ARE Overview: Architect Registration Examination | NCARB
52. Addenda, alternates, and comparable proposals
Pre-award clarifications and revisions should reach the appropriate participants through the established procurement process. Alternates describe defined scope changes for pricing. Compare proposals on an equivalent basis, including acknowledged revisions, exclusions, and alternate treatment, before drawing conclusions from the lowest stated total.
Worked example: A $980,000 proposal excludes a required $40,000 item, while a $1,005,000 proposal includes it. Their stated totals do not represent equivalent scope.
Mistake to avoid: Ranking proposals without reconciling exclusions and acknowledged document changes.
Source reference: ARE Overview: Architect Registration Examination | NCARB
Construction and Building Evaluation
53. Submittal review and delegated responsibilities
Submittals communicate proposed products, fabrication information, or other required details. Review them for the purpose established by the contract and compare them with design requirements. Identify disclosed deviations and interfaces while preserving the responsibilities assigned to contractors, fabricators, and design professionals.
Worked example: A curtain-wall submittal proposes a different mullion depth that affects interior clearance. The interface requires evaluation even if the product otherwise appears consistent with the specified system.
Mistake to avoid: Assuming a reviewed submittal automatically resolves every deviation or construction responsibility.
Source reference: ARE Overview: Architect Registration Examination | NCARB
54. Requests for information and authorized changes
A request for information seeks clarification; it is not inherently approval to alter cost, time, or scope. Determine whether a response explains existing requirements or changes them. When a change is involved, follow the applicable authorization process and assess consequences before work proceeds on that basis.
Worked example: Clarifying a dimension confirms existing intent. Moving the wall to satisfy a new owner preference may require a separately authorized change.
Mistake to avoid: Treating every clarification response as authorization for additional compensation or revised work.
Source reference: ARE Overview: Architect Registration Examination | NCARB
55. Site observations and factual reporting
Construction observations provide information about visible work within the agreed services; their scope differs from continuous inspection. Reports should separate observed facts, apparent discrepancies, requested action, and unresolved questions. Avoid asserting concealed conditions or assigning causes that the available observations do not establish.
Worked example: A report records staining near a window after rain and requests investigation. It does not declare a concealed flashing defect before that condition is verified.
Mistake to avoid: Turning a limited observation into a claim that all work has been comprehensively checked.
Source reference: ARE Overview: Architect Registration Examination | NCARB
56. Substitution equivalence
A proposed substitution must be evaluated against all relevant criteria, including performance, compatibility, dimensions, durability, appearance, maintenance, and coordination effects. A single matching attribute does not establish equivalence. Review the proposal through the process and responsibilities established for the project.
Worked example: An alternate window has similar thermal performance but different anchorage and sightlines. Those differences still require assessment before acceptance.
Mistake to avoid: Accepting a product because one published rating matches while ignoring its assembly interfaces.
Source reference: ARE Overview: Architect Registration Examination | NCARB
57. Change pricing and schedule consequences
Evaluate a change through added work, deleted work, justified cost components, and its effect on the construction sequence. Cost and time are separate questions. A small material change can affect a critical activity, while an expensive addition may fit within available schedule flexibility.
Worked example: Added work of $8,000 less a $3,000 deletion gives a $5,000 net direct change before any applicable contractual adjustments. Its delivery delay still needs independent evaluation.
Mistake to avoid: Assuming the size of a cost change determines its schedule impact.
Source reference: ARE Overview: Architect Registration Examination | NCARB
58. Progress payments and cumulative accounting
A progress-payment evaluation compares claimed completion with the contract's payment basis, supporting information, and observed progress. Keep cumulative earned value, retained amounts, and prior payments distinct. Treatment of stored materials and other payment conditions must follow the applicable agreement.
Worked example: With $120,000 cumulative earned value, an expressly assumed 10% retainage, and $70,000 previously paid, the current amount is $120,000 minus $12,000 minus $70,000, or $38,000.
Mistake to avoid: Applying retainage again to amounts already withheld without reconciling cumulative totals.
Source reference: ARE Overview: Architect Registration Examination | NCARB
59. Substantial completion and remaining work
Substantial completion concerns readiness for the intended use under the contract's definition; it is distinct from final completion. Remaining-work lists document unresolved items but do not make unsafe or unusable conditions acceptable. Occupancy permissions and contract milestones also require separate consideration.
Worked example: Minor paint touch-ups may remain while intended use is possible. An unresolved essential access or life-safety condition may prevent the same conclusion despite a short remaining-work list.
Mistake to avoid: Determining readiness from the number of unfinished items rather than their significance.
Source reference: ARE Overview: Architect Registration Examination | NCARB
60. Commissioning and post-occupancy evaluation
Commissioning verifies and documents whether systems perform against established requirements through defined processes. Post-occupancy evaluation examines actual use and performance after occupancy. Both benefit from explicit criteria, but neither should be reduced to collecting equipment manuals or assuming occupant satisfaction proves technical performance.
Worked example: Functional testing reveals conflicting heating and cooling commands. Later occupant feedback identifies an uncomfortable afternoon zone, prompting comparison with measured operation and the original requirements.
Mistake to avoid: Treating document delivery or equipment startup as evidence that integrated performance has been verified.
Source reference: ARE Overview: Architect Registration Examination | NCARB
Sources
Exam identity verified:
Browse all study guides