Skip to main content
AREConstruction & Evaluation

Post-Occupancy Evaluation: User Surveys, Occupant Satisfaction, Space Utilization, and Lessons Learned Documentation

How architects evaluate building performance after occupancy through structured post-occupancy evaluations (POEs), including user survey methodology, occupant satisfaction measurement, space utilization analysis, lessons learned documentation, and the integration of POE findings into future design decisions and recommissioning programs.

2 min read330 words

Evaluating Buildings Through the Eyes of Their Occupants

Post-occupancy evaluation (POE) is the systematic process of assessing how well a completed building performs for the people who actually use it. Unlike commissioning, which tests whether systems operate according to design specifications, POE measures whether the building delivers the outcomes the owner and occupants expected: comfort, productivity, functionality, and satisfaction.

POE serves two distinct purposes. First, it identifies performance issues in the current building that can be addressed through maintenance adjustments, recommissioning, or renovation. Second, it generates lessons learned that improve future design decisions across the firm's portfolio. Both purposes require structured data collection rather than anecdotal feedback.

User surveys are the primary POE instrument. Well-designed surveys measure occupant satisfaction across multiple dimensions: thermal comfort, lighting quality, acoustic privacy, indoor air quality, spatial adequacy, wayfinding clarity, and amenity access. The survey methodology matters as much as the questions themselves. Anonymous surveys with standardized scales produce data that can be benchmarked against peer buildings and tracked over time.

Space utilization analysis examines whether spaces are used as the designers intended. Conference rooms may sit empty while corridors overflow with impromptu meetings. Individual offices may house collaborative teams, while open workstations may be used primarily for private phone calls. These usage patterns reveal misalignments between design assumptions and actual behavior that inform future programming.

Lessons learned documentation captures both positive outcomes and deficiencies in a format that transfers knowledge across projects. Effective lessons learned sessions identify technical strengths and weaknesses with specific recommendations for improvement on future projects. The documentation should be distributed broadly within the organization, not just to the project team, so that the institutional knowledge persists beyond the individuals who generated it.

Recommissioning provides the mechanism for acting on POE findings. Systems that have drifted from their original performance specifications, or that never performed as intended, can be returned to proper operation through systematic evaluation and adjustment. GSA recommends considering recommissioning when periodic reviews such as POEs suggest it, typically every three to five years after initial occupancy.

Want to track your progress and access more study tools?

Create a free account