Every architectural project runs on people. The right team, assembled at the right time, with clearly defined roles, is what separates a smooth project from one that hemorrhages time and money.

Your project team isn't just the architects in your office. It's a layered structure of in-house staff, outside consultants contracted directly by you, and subconsultants who work under your umbrella but bring specialized expertise you don't carry. Each category comes with different levels of control, different liability exposure, and different contractual relationships.

Here's what catches candidates off guard: team composition isn't static. The people you need during schematic design are not the same people you need during construction administration. Structural engineers ramp up during design development. Commissioning agents enter during construction documents. The project manager stays constant, but the support cast rotates based on phase demands.

For the ARE, you need to understand three things about project teams. First, the distinctions between staff, consultants, and subconsultants, and why those distinctions matter for liability and management. Second, how team roles shift across project phases. Third, how delivery methods like IPD completely reshape traditional team hierarchies.

This topic connects directly to NCARB Competency 13: organizing and coordinating an interdisciplinary project team. Getting team composition right isn't just good management. It's a core professional skill that licensing boards expect you to demonstrate.