Here is a professional SOP for Communication between Engineer and Architect.
SOP: Communication Between Engineer and Architect
1. Purpose
To establish a clear communication system between the Engineer and Architect so that design intent, technical requirements, site conditions, and construction execution are aligned, accurate, timely, and professional.
2. Objective
The objective of this SOP is to:
- reduce misunderstanding and design conflict
- improve coordination speed
- prevent rework on site
- protect quality, cost, and schedule
- create a professional record of decisions
3. Scope
This SOP applies to communication between:
- Architect
- Structural Engineer
- MEP Engineer
- Site Engineer
- Project Engineer
- Construction Manager
- General Contractor team
It covers communication during:
- concept design
- design development
- construction drawings
- shop drawing review
- material approval
- site execution
- design changes
- final handover
4. Definitions
Architect
Responsible for design concept, space
planning, building appearance, user function, and architectural
drawings/details.
Engineer
Responsible for technical systems and
construction feasibility, such as structural, MEP, civil, and site execution.
RFI
Request for Information. A formal question sent to
clarify drawings, specifications, dimensions, details, or site issues.
Submittal
Documents submitted for review, such as shop
drawings, material samples, method statements, and technical data.
NCR
Non-Conformance Report. A record of work that does
not comply with approved drawings/specifications.
5. Core Principles
Engineer–Architect communication must always be:
- clear
- factual
- respectful
- documented
- solution-oriented
- timely
6. Communication Rules
6.1 Use official communication channels
Main communication channels:
- formal meeting
- drawing markups
- RFI form
- site instruction
- approved messaging group for urgent coordination only
6.2 Avoid verbal-only decisions
Any important decision must be confirmed in writing.
6.3 One issue = one clear topic
Do not mix many unrelated technical problems in one message if it causes confusion.
6.4 Use drawing references
Always mention:
- drawing number
- revision number
- grid line
- level
- room/area
- detail reference
- date
6.5 Respect authority and responsibility
- Architect controls architectural intent and space/aesthetic decisions.
- Engineer controls structural safety, technical feasibility, system performance, and code compliance.
- If conflict happens, the issue must be escalated through the approved coordination process.
7. Roles and Responsibilities
7.1 Architect
- provide complete and coordinated architectural drawings
- clarify design intent
- review submittals related to finishes, layout, façade, and architectural details
- respond to RFIs on time
- attend coordination meetings
- issue revisions when required
7.2 Engineer
- review architectural drawings for technical feasibility
- identify clashes, risks, or constructability issues
- provide technical comments and calculations when needed
- coordinate with structural and MEP requirements
- support site team with execution clarification
- document discrepancies and request resolution
7.3 Site Engineer / Project Engineer
- raise site issues with proper evidence
- prepare RFI, sketches, photos, and measurements
- follow only approved drawings/instructions
- keep communication records
7.4 Project Manager / Construction Manager
- monitor response time
- resolve delays in coordination
- escalate unresolved issues
- ensure decisions are communicated to all relevant teams
8. Standard Communication Workflow
8.1 During design stage
- Architect issues design drawings.
- Engineer reviews for:
- dimensions
- structure interface
- MEP space
- buildability
- code compliance
8.2 During pre-construction stage
- Conduct coordination meeting.
- Review:
- drawings
- specifications
- material requirements
- site constraints
- clash points
8.3 During construction stage
- Site team identifies issue.
- Site Engineer checks latest approved drawing.
- If unclear, prepare RFI with:
- issue description
- location
- photos
- dimensions
- drawing reference
- proposed option if available
8.4 During design change stage
- Change request is raised.
- Architect reviews design impact.
- Engineer reviews technical and cost/schedule impact.
- PM approves coordination path.
- Revised drawing/instruction is issued.
- Old drawing is marked superseded.
- Site executes only updated approved document.
9. Communication Types
9.1 Daily coordination
Used for:
- small clarifications
- work sequence
- short updates
- urgent site conditions
Tools:
- site meeting
- approved chat group
- phone call followed by written summary
9.2 Formal technical clarification
Used for:
- dimension mismatch
- missing detail
- specification conflict
- structural/architectural clash
- finish alignment issue
Tools:
- RFI
- marked-up drawing
9.3 Design review meeting
Used for:
- major coordination issue
- façade review
- room layout changes
- structural impact on design
- material change approval
Tools:
- weekly coordination meeting
- meeting minutes
- action log
10. Response Time Standard
Recommended response times:
- urgent site issue affecting active work: within 2–4 hours initial response
- normal site clarification: within 24 hours
- technical RFI: within 2–3 working days
- major design revision: within 3–7 working days depending on complexity
If no response is received on time:
- follow up once
- escalate to Project Manager
- log delay in coordination register
11. Information Required in Every Technical Message
Every message should include:
- subject/title
- project name
- date
- sender name
- issue description
- exact location
- drawing number and revision
- attached photos or sketches
- requested action
- deadline if urgent
12. Meeting SOP
12.1 Before meeting
- prepare agenda
- collect questions
- review latest drawings
- prepare samples/photos if needed
12.2 During meeting
- discuss one issue at a time
- focus on facts, not emotion
- compare drawing vs site condition
- agree on responsible person
- agree on deadline
12.3 After meeting
- issue meeting minutes
- list action items
- assign responsible persons
- track close-out status
13. Drawing and Revision Control
- always use latest approved drawing
- mark old drawings as superseded
- do not build from verbal instruction alone
- all revisions must show revision number and date
- site team must be informed immediately when revision changes active work
14. Site Issue Escalation Procedure
When Engineer and Architect cannot agree:
- review contract drawings and specifications
- review codes and technical requirements
- compare design intent and site feasibility
- discuss in coordination meeting
- escalate to Project Manager / Design Manager
- issue final written decision
- distribute final instruction to all teams
15. Common Problems and Required Action
Problem 1: Dimension mismatch
Action:
- stop affected work
- verify with site measurement
- raise RFI
- request corrected detail
Problem 2: Architectural detail conflicts with structure
Action:
- engineer proposes feasible technical option
- architect reviews appearance/function impact
- final detail issued in revised drawing
Problem 3: Finish material not fitting actual site condition
Action:
- submit site photo, measurement, sample, and option
- architect confirms acceptable alternative
- record approval before installation
Problem 4: Verbal instruction given on site
Action:
- request written confirmation by email/message
- do not proceed on critical work until confirmed
Problem 5: Late reply causing delay
Action:
- follow up with urgency label
- escalate through PM
- record delay impact
16. Communication Behavior Standard
Engineer and Architect must:
- speak professionally
- avoid blame language
- discuss problem and solution
- respect expertise of each other
- listen before replying
- use evidence: drawings, photos, dimensions, calculations
Use this style:
- “Please clarify…”
- “Based on drawing A-203 revision 2…”
- “Site measurement shows…”
- “To avoid rework, we recommend…”
- “Please confirm approval before execution.”
Avoid this style:
- “Your drawing is wrong.”
- “This cannot work.”
- “Do it my way.”
- emotional or aggressive language
17. Required Records
The following records must be maintained:
- RFI log
- drawing revision log
- submittal log
- meeting minutes
- site instruction log
- email communication file
- approval register
- issue tracker
18. KPI for Engineer–Architect Communication
Suggested KPIs:
- RFI response time
- number of unresolved coordination issues
- number of reworks caused by communication failure
- percentage of drawings coordinated before site work
- meeting action close-out rate
- number of verbal instructions without written confirmation
19. Sample RFI Format
RFI No.:
Project:
Date:
From: Site Engineer / Project Engineer
To:
Architect / Design Team
Subject: Clarification for
architectural detail at Stair Lobby Level 2
Drawing Reference: A-204 Rev.03
Location:
Grid B-3, Level 2
Issue: Ceiling bulkhead height shown
conflicts with beam soffit level on structural drawing S-112.
Site Condition:
Actual beam depth reduces ceiling clearance.
Requested Clarification:
Please confirm revised ceiling detail/height.
Attachment:
Site photo, marked-up drawing, measured dimensions.
Required By:
[date]
20. Approval Matrix
- small architectural clarification: Architect
- technical structural feasibility: Structural Engineer
- MEP routing conflict: MEP Engineer + Architect
- site execution sequence: Construction team with technical confirmation
- major design change: Architect + Engineer + PM/Client approval as needed
21. Final Rule
No work should proceed when:
- drawing is unclear
- revision is not approved
- dimensions conflict
- technical risk is unresolved
- verbal instruction is not documented
22. Conclusion
Good communication between Engineer and Architect is not only about talking. It is about:
- correct information
- correct timing
- correct document
- correct responsibility
- correct record
When both sides communicate professionally, the project becomes smoother, faster, safer, and more profitable.
If you want, I can turn this into a clean HTML Smart-Book post for your Blogger style.