Structure
How cohorts are organized
A cohort forms around a specific site, a defined scope, and faculty-guided review points.
Students are not asked to float in the abstract. They work toward documented outputs and a formal handoff.
Student Cohorts
Student cohorts translate classroom learning into site-based professional practice.
Students join BEAM Architecture to work on buildings and redevelopment questions that require documentation, coordination, technical judgment, and public responsibility.
Participation
Who should apply
Architecture students are a natural fit, but BEAM is designed to include students from preservation, planning, real estate, fabrication, landscape, accessibility, and related fields.
Interdisciplinary collaboration is part of the model because real buildings demand it.
Learning
What students gain
Students gain practical experience through real community projects rather than speculative exercises alone.
They learn how to document conditions, synthesize evidence, communicate with partners, and frame phased next steps.
- Field documentation and analytical methods
- Team coordination and public accountability
- Exposure to preservation, access, and implementation logic
- A clearer pipeline from education into professional practice
Responsibility
What the work demands
BEAM expects seriousness. Sites are not props for student experience; they are partners with real needs and constraints.
That means reliability, careful observation, responsive communication, and work that can stand up to review.
Continue Exploring
Review the rest of the BEAM Architecture framework.
About BEAM Architecture
Mission, model, and why a university-linked practice matters.
Current Pilot: Central UMC
Current pilot site testing documentation, planning, and phased implementation.
Faculty Partnerships
Advising, sponsorship, course integration, and research collaboration paths.
Project Types
Architecture, preservation, adaptive reuse, fabrication, access, and strategy.