Coordinating architectural and engineering design deliverables
Admin · 22 October 2026
Illustrative image. Photo by Daniel McCullough on Unsplash. Unsplash License.
Design coordination can fail even when every discipline issues its drawings on time. The architect may work from one equipment arrangement, the engineer from another, and the specialist supplier from a third. Each deliverable may be internally coherent while the combined information remains unsuitable for the decision the project needs to make. Coordinating deliverables therefore requires more than monitoring issue dates; it requires agreement about inputs, interfaces and the intended use of each output.
For design managers, the practical objective is to create a sequence in which the right information reaches the right people early enough for them to respond. That sequence should reflect procurement and construction needs without pretending that all disciplines can develop their work independently. A clear deliverables plan makes dependencies visible and gives the team a basis for resolving them before an issue becomes urgent.
Define the purpose of each deliverable
Start by asking what the receiving party needs to do with the information. A planning submission, cost review, tender enquiry and installation release require different levels of detail and assurance. Describe the intended use in the information schedule and align it with the project’s status conventions. The title of a drawing alone may not explain whether it contains enough coordinated information for the next activity.
Group deliverables around meaningful decisions or package releases where appropriate. This helps the team identify information that must be considered together. A single drawing may be ready to issue while an associated schedule is still unresolved. If the recipient needs both to proceed, reporting only the drawing’s completion can give a misleading impression of readiness. Track the completeness of the required information set as well as its individual parts.
Map the inputs between disciplines
For each important output, identify what the author needs from others. Record the source, required date and assumptions that apply if the input is provisional. The exercise should involve the people producing the work, because they can explain dependencies that may not appear in a high-level programme. Avoid assuming that a discipline can complete its design simply because its appointment has started.
Distinguish information needed to begin from information needed to finalise. Some work can progress using a clearly stated assumption, provided the consequences are understood and the assumption is reviewed at the right time. Other inputs may be essential before useful progress can occur. Making this distinction helps the design manager prioritise queries and prevents all outstanding information being described with the same level of urgency.
Agree a common spatial basis
Confirm the reference information that disciplines use for location, levels, grids and other shared spatial conventions. The relevant project procedures should establish how this information is controlled and changed. If a reference moves, identify the affected outputs and communicate the change through the agreed route. A coordination review is less effective when participants are unknowingly comparing information prepared on different bases.
Check existing building information carefully on refurbishment projects. Available records and surveys may have different coverage or confidence. Identify what has been verified and what remains uncertain, with appropriate specialist input on further investigation. Do not allow an assumed condition to become invisible simply because it has been modelled neatly. The design record should preserve the distinction between observed information and an interpretation awaiting confirmation.
Make interface reviews specific
Organise coordination reviews around interfaces that need decisions. Identify the parties, information and outcome required before the meeting. An agenda that merely asks each discipline for a progress update may miss the places where their work interacts. A focused review of a plant area, façade connection or circulation zone can produce clearer actions because the participants understand the question they are trying to resolve.
Consider a hypothetical service route through a structural zone. The team needs more than confirmation that the model objects do not overlap. It may need to resolve access, supporting arrangements, construction sequence and the requirements of connected systems. The relevant specialists should determine the technical solution. The coordination process ensures that the question is assigned, the necessary inputs are available and the agreed outcome reaches the affected deliverables.
Turn issues into accountable actions
Record each significant issue with a clear description, location and reference to the information reviewed. Assign an owner for the response and identify contributors where needed. State the decision or evidence required to close it. “Coordinate” is rarely a sufficient action because it does not tell the owner what outcome the team expects or how completion will be assessed.
Link the required response date to the affected release or procurement activity. Review overdue issues by consequence, not just age. A recently raised interface may require immediate attention if manufacture is about to begin, while an older query may concern a later stage. Explain these priorities to the team and adjust the programme where resolution cannot realistically occur within the assumed period.
Control revisions across the information set
Use the project’s agreed information management process to identify current revisions and permitted uses. Ensure the receiving team can locate the authoritative information without relying on informal copies. The APM overview of configuration management provides general context for controlling project information and its changes. In design coordination, the immediate concern is knowing exactly which information has been reviewed together.
When one deliverable changes, assess the connected outputs rather than treating the revision as isolated. A revised layout may affect schedules, details and specialist information even if their authors were not involved in the initial change. Record the required updates and confirm completion. Otherwise a newly issued drawing can coexist with an older schedule that still directs procurement or installation.
Include review and response time
A deliverables programme should allow for review, questions and revision where these are part of the agreed process. Issuing information on the date another party needs to act may leave no time to assess it. Agree realistic review periods with the relevant participants and identify the conditions on which they depend. A large or incomplete submission may require a different response from a focused, coordinated package.
Make the scope of each review clear. A client’s operational comment, a designer’s technical review and a supplier’s manufacturability check serve different purposes. Record who is reviewing what and avoid language that implies broader acceptance than intended. The applicable appointments and project procedures govern responsibilities; a coordination meeting should not casually redefine them through imprecise minutes.
Measure readiness rather than document volume
Progress reporting should explain whether the next decision has the information it needs. Counting issued documents can be useful for administration but may not reveal unresolved interfaces or incomplete inputs. Report the status of important releases, the issues preventing readiness and the actions required. This gives project leadership something it can influence rather than a percentage that conceals the cause of delay.
At each release, retain a concise record of the information considered, significant assumptions and outstanding matters. Where work proceeds with conditions, communicate those conditions to the receiving team through the appropriate process. The record should make it possible to understand why the release was considered suitable for its intended use and what further decisions remain.
Review the effectiveness of the process after major packages move into delivery. Ask which coordination issues appeared late and whether their inputs, ownership or review timing could have been clearer. Feed those lessons into the next package while the evidence is fresh. Good coordination is visible when disciplines can explain their dependencies, recipients understand the status of the information and changes reach every affected output before the work relies on them.
