For partners / Architects & engineers
Architects and engineers: when to bring construction questions into design
Use the design-partner page to identify field constraints, equipment interfaces and decisions worth resolving before drawings are issued.
THE KEY POINT
Ask for construction input while a design decision can still change; record who owns the design response.
Start with a question the contractor can investigate
The Architects & Engineers page is useful when a design depends on existing conditions, access or the sequence of installation. Instead of asking whether a design is generally buildable, identify the detail that needs review: a route through an occupied ceiling, equipment replacement clearance or a connection to an existing system.
Share the current drawing issue and explain the decision it supports. Early sketches can be enough for a planning conversation if their status is clear. Mark dimensions and system information that have not been verified rather than allowing a preliminary drawing to look like a complete field survey.
Resolve the interfaces before they disappear into the walls
Equipment can have several owners in the design process. A room layout may belong to the architect, power requirements to the electrical design and controls to a specialist. Record who confirms each interface and which product information is still outstanding.
For example, a display location needs more than an outline on an elevation. Backing, power, signal routes, ventilation and service access may all matter. This is an illustrative coordination example, not a design specification. The useful deliverable is a list of answered and open questions tied to that location.
Distinguish a field observation from a design instruction
A contractor can describe a site condition or propose an installation sequence without taking over the designer’s responsibilities. When an observation requires a design change, use the project’s written question-and-response process. Record the affected drawing, issue date, requested clarification and approved response.
Do not rely on a markup that has circulated informally without establishing whether it is approved for construction. Keep superseded details accessible as history but make the current instruction easy to identify. An unresolved question should remain visibly unresolved in the coordination record.
Turn the discussion into a handoff
Before finalizing the next package, list decisions that affect pricing, procurement and inspections. Assign an owner and needed date to each. Confirm what must be field-verified and what can be established from drawings or manufacturer information.
Use the partner page’s stage checklist to prepare the next conversation with YKCA. It supports collaboration around constructability and trade interfaces; it does not establish a design contract, engineering approval or acceptance of every proposed method. Project-specific responsibilities should stay with the agreed team and documents.
Keep the next steps clear
| Step | What to record | Why it helps |
|---|---|---|
| Identify | Existing condition | Locate the constraint |
| Coordinate | Trade interfaces | Resolve the shared detail |
| Document | Design response | Keep revisions aligned |
BEFORE THE NEXT STEP
Your checklist
A useful question
When should a design team involve a contractor?
When existing conditions, access, trade interfaces or installation sequencing could change a design decision. Share the current drawing issue and a focused question while alternatives can still be considered.
PUT THE GUIDE TO WORK
Page & sources
This guide helps you prepare for a conversation with YKCA. Reviewed October 3, 2026. Check current project terms and official instructions when making a decision.
CONTINUE WITH THE NEXT DECISION
Related Company guides
Ready to use what you have learned?
Open Architects & engineers