Mixed-use buildings pack residential units, retail shops, offices, and sometimes civic spaces into a single structure. That sounds straightforward until you start programming one. Every occupancy type brings its own code requirements, circulation demands, structural loads, and user expectations. Ground-floor retail needs high ceilings, generous glazing, and direct street access. Upper-floor residences need acoustic separation, secure entries, and private outdoor space. Office tenants want column-free floor plates and freight elevator access. The architect's job during programming is to sort out which functions go where, how they connect (or stay apart), and whether the building code even allows the combination being proposed.

The ARE tests your ability to analyze these competing demands and make evaluative judgments about spatial organization. You need to understand the difference between vertical mixed use (stacking different functions on different floors) and horizontal mixed use (placing them side by side). You need to know how the IBC handles mixed occupancies through separated and nonseparated approaches. And you need to recognize when a proposed program creates conflicts that require design trade-offs rather than simple rule application.

Zoning codes increasingly encourage or mandate mixed-use development, especially near transit. That policy push means architects encounter these programming challenges on virtually every urban project. Getting the spatial relationships right at the programming stage prevents expensive redesigns later.