Facade coordination: aligning geometry, structure and services
Admin · 22 October 2026
Illustrative image. Photo by Danist Soh on Unsplash. Unsplash License.
A façade package connects architectural intent with structure, building services, internal spaces and installation planning. A change in one area can affect several others even when the visible external arrangement appears unchanged. Coordination is therefore a sequence of information exchanges and decisions, rather than a single review of the finished elevation. The design manager’s task is to make those exchanges explicit and ensure that unresolved interfaces remain visible.
This article addresses coordination management, not the technical design of a façade. The relevant specialists must assess performance, connections and other technical requirements within their responsibilities. A useful project process makes sure those specialists receive the inputs they need and that their decisions are reflected in the information used by adjacent packages and the delivery team.
Agree the package boundaries
Identify what the façade package includes and where responsibility passes to another party. Review the scope against the architectural, structural and services appointments and the procurement arrangement. Broad descriptions can conceal work needed to define interfaces or integrate specialist proposals. Record gaps and resolve them through the appropriate commercial and technical processes before the team treats the allocation as settled.
Break significant interfaces into identifiable outputs. These might concern geometry, supporting information, openings or connections with internal finishes, depending on the project. Name the party producing each output, its contributors and the recipient. A generic instruction to coordinate with all trades does not explain what information another designer can expect or when it will be available.
Establish a shared geometric basis
Confirm the project reference information used by the relevant disciplines. The agreed grids, levels and spatial conventions should be controlled through the project’s information arrangements. Identify the revisions used for coordination and how changes are communicated. A detailed review can be undermined if participants are comparing models or drawings prepared from different reference information without realising it.
Where existing construction is involved, identify what has been measured and what remains an assumption. Ask the relevant specialists to define the survey information and verification needed for their work. A model can present uncertain geometry very precisely, so the record should preserve the distinction between observed conditions and a proposed or assumed position.
Map the structural information exchange
Identify the information the façade designer needs from the structural team and the information returned for assessment. The exact requirements depend on the system and project. Record the sequence, required dates and assumptions rather than inventing a generic technical checklist. The responsible designers should explain what must be stable before their work can proceed and what may remain provisional.
Review changes to equipment, geometry or package selection for effects on that exchange. A supplier substitution can alter the information needed by connected designers even when the architectural appearance remains similar. Make responsibility for reviewing the consequence explicit. Avoid relying on the assumption that someone else will notice the change in a later model federation or drawing issue.
Coordinate services and openings early
Ask the services team to identify façade interfaces that require a decision, with appropriate technical input on performance and location. These may affect external appearance, internal arrangements and specialist detailing. Link the decisions to the information programme. A late request for an opening can be more difficult to accommodate after the relevant production information has been released.
Consider a hypothetical office project where a services requirement changes the proposed position of an external opening. The team should assess the connected architectural and specialist design consequences rather than move a symbol on one drawing and assume coordination is complete. Record the agreed outcome and identify every affected output, including schedules and procurement information where relevant.
Include internal and operational interfaces
The internal relationship matters as well as the external view. Review the relevant connections with floors, ceilings, partitions and access arrangements through the responsible disciplines. Identify the information needed by fit-out designers and suppliers. Package boundaries should not leave them to infer dimensions or requirements from a presentation image that was not intended for that purpose.
Bring maintenance and operating requirements into the review at the appropriate time. Ask who will provide the relevant strategy and what input the client’s facilities team needs. The coordination process should make those questions visible without substituting for a competent technical assessment. Where the operating arrangement remains undecided, record the dependency and assign a decision owner.
Connect design releases to manufacture
Work with the supplier and procurement team to establish the information needed for each commitment. Tender pricing, material orders and fabrication may require different states of design readiness. Label those states clearly and avoid a single ambiguous milestone called design complete. The receiving team should know what it may do with the information released.
Record unresolved matters that remain at a release point, including the assumption allowing progress and the consequence if it changes. The relevant authorised parties must decide whether proceeding is appropriate. The coordination register should preserve that decision and its conditions, rather than showing the package as wholly complete while important dependencies remain open.
Use issue records that support decisions
Each coordination issue should identify the location, information reference, question and owner. State the evidence or revised output required to close it. Group related issues where they share a decision, but avoid closing many observations with a vague note that coordination has been agreed. Future users need to understand what was actually resolved.
Prioritise by consequence and the next affected commitment. A recently raised issue may be urgent if production is about to begin, while an older one may concern a later stage. Explain those priorities to participants. If the required answer cannot be obtained in time, assess the programme and procurement effect through the relevant project processes rather than repeatedly moving an action date.
Manage revisions across the full information set
Use the project’s controlled information process to identify current versions and permitted uses. The APM explanation of configuration management provides general context for maintaining a known current position and traceability between versions. In façade coordination, the practical concern is that all parties understand which information has been reviewed together.
When a decision changes, identify the related drawings, models, specifications and schedules that need updating. Confirm that the revised information reaches the people relying on it. A drawing issue is not sufficient if a supplier continues to work from an earlier schedule or an adjacent designer has not assessed the revised interface. Track the consequences as well as the original action.
Carry assumptions into delivery and handover
Transfer significant coordination decisions to the people managing manufacture and installation. Explain unusual boundaries, remaining information and conditions attached to approvals. Distinguish an explored option from the arrangement incorporated into the agreed scope. Personnel changes should not force the delivery team to reconstruct the design history from informal recollections.
Review the installed and final information through the project’s appropriate technical and quality processes. Keep consequential changes traceable and ensure handover records reflect the agreed completed arrangement. The measure of coordination is practical continuity: each team receives dependable inputs, knows its outstanding decisions and can understand how a change affects the connected work before that work proceeds.
Agree how incomplete inputs will be reported between coordination meetings. Waiting for the next formal review can leave a receiving designer working on an assumption that has already become doubtful. The author should identify the affected output and likely consequence, while the design manager coordinates the response with the relevant owners. This keeps the information programme responsive without creating an unofficial route for changing technical requirements or authorising production.
