Unitized Curtain Wall Engineering Responsibility: Design-Assist, Delegated Design, BIM and Shop Drawings
Why Engineering Labels Need a Responsibility Register
Terms such as design-assist, delegated design, engineering support, BIM coordination, and shop drawings are common in unitized curtain wall procurement. They can also be interpreted differently from one project to another. One project may use design-assist for early technical coordination; another may define a delegated-design package with specific inputs, calculations, reviews, and professional appointments.
Neither label, by itself, transfers every design, legal, or professional responsibility to a supplier, contractor, or specialist subcontractor.
A clear engineering scope records more than a company name. It identifies the required input and criteria, the document or model to be produced, the project-assigned role that develops it, the internal check, the submission route, the review role, the affected interfaces, the revision process, and the project-defined record location.
This article is a planning guide for facade contractors, specialist subcontractors, procurement and project managers, estimators, technical coordinators, and design managers. It does not provide structural or facade design, calculations, connection details, method statements, legal advice, professional-signature advice, approval decisions, or code-compliance conclusions.
Direct Answer: What Should a Unitized Curtain Wall Engineering Scope State?
For each technical item, the scope or responsibility register should state:
- Input and criteria: project documents, design intent, requirements, references, assumptions, and missing information.
- Deliverable: calculation package, model, shop drawing, fabrication drawing, installation drawing, schedule, response log, or record document.
- Preparer/developer: the party or role assigned by project documents to develop the item.
- Internal checker: the person or team assigned to perform the defined internal check.
- Submitter/coordinator: the party assigned to control submission and document-register updates.
- Reviewer: the project-defined recipient or reviewing role.
- Interface owner: the project-assigned role responsible for coordinating an affected interface.
- Revision route: how comments, changes, responses, resubmissions, and superseded versions are recorded.
- Status: quotation scope status and workflow/project status, kept as separate fields.
- Record holder: the party or system designated by project documents to retain the record.
These are planning fields, not a universal contract form. The contract, specification, professional appointments, BIM information requirements, project procedures, and applicable jurisdiction define the final allocation. “Preparer,” “interface owner,” and “record holder” describe project-assigned roles; they are not universal legal responsibility conclusions.
Design-Assist Versus Delegated Design
Design-assist as a defined service scope
Design-assist may describe specialist input during design development, system selection, detailing, coordination, constructability review, material planning, or technical-submittal preparation. Break the term into specific outputs rather than treating it as an undefined promise of engineering support.
- design information already issued;
- criteria and design intent to be used;
- technical options or coordination input requested;
- drawings, schedules, calculations, samples, or models to be produced;
- limits of design and detail development;
- interfaces requiring input from other project-assigned roles;
- internal checking and submission route; and
- record or handoff required after assistance.
Design-assist does not automatically mean the supplier owns the design, prepares every calculation, or assumes every professional responsibility.
Delegated design as a defined package
Delegated design may involve a defined package of technical deliverables prepared by a contractor, specialist, supplier, fabricator, or appointed professional. Identify the delegated items, inputs, criteria, limits, interfaces, checking, submission, review, professional appointments, revisions, and records.
- exact systems, components, details, or documents covered;
- criteria and approved references used as inputs;
- calculations or analysis required by project documents;
- assigned preparer and internal checker;
- submission and review route;
- interfaces that remain with others;
- change-control and revision process; and
- final record requirements.
A delegated-design label does not automatically transfer every design, legal, or professional responsibility to one party. The contract, specification, appointment, responsibility matrix, and qualified professionals must define the actual scope.
Inputs, Criteria, Calculations, and Technical Interfaces
Inputs and criteria
A project-specific engineering register may identify employer or contract requirements; architectural design intent and approved references; project geometry and panel/system information; structural support and interface information; performance criteria; materials, glass/infill, and finish basis; movement and tolerance assumptions; applicable fire, waterproofing, thermal, or acoustic criteria; BIM information and exchange requirements; professional appointments and review routes; and unresolved input, responsibility, and change-control fields.
These are input categories to assign and review, not design instructions. Qualified project professionals must define the applicable criteria and confirm which documents govern.
Calculations and analysis fields
The quotation or register should state whether the scope includes or excludes a calculation or analysis package; defined inputs, assumptions, and criteria; system or detail development; connection or interface analysis where required; component or material data; calculation format and submission record; internal checking; professional review or certification where required; comments, responses, revisions, and resubmission; and final records.
This article does not perform or validate calculations. A submitted or signed calculation does not automatically establish project approval, code compliance, or acceptance.
Technical interfaces as routing prompts
These names are routing prompts only. This article does not design, calculate, install, test, or approve the interfaces. It asks which project-assigned role provides the input, prepares the document, checks it, coordinates the response, and records the decision.
BIM Purpose, Information Requirements, and Model Exchange
A BIM requirement should describe why the model is needed and what information must be exchanged. buildingSMART materials support questions about information requirements, delivery formats, stakeholder exchanges, openBIM concepts, and issue management. They do not create a universal BIM execution plan, platform mandate, or model-ownership rule.
Model purpose and information requirements
- model purpose and intended use;
- information requirements and level of information need;
- required geometric and non-geometric data;
- model elements, attributes, classifications, and naming;
- authoring role and source information;
- exchange format and frequency;
- coordination and issue-management process;
- permissions and read-only/edit rights;
- update responsibility and change control;
- validation or checking requirements; and
- record/as-built model status.
Do not claim that a BIM model is automatically accurate, legally controlling, approved, code-compliant, or the final record model. Model control, permissions, intellectual-property terms, updates, and record status must be defined by project information requirements and contract documents.
Authoring, exchange, and coordination
Identify which project-assigned role authors the facade model, supplies reference models, coordinates interfaces, manages exchanges, and updates the model after comments or design changes. State the exchange method, file format, model version, issue reference, and required response log.
A common data environment or issue platform may be used, but this article does not mandate one. The project should define the platform, permissions, naming, version control, and record route.
Updates, permissions, and record status
Ask who can edit, comment, submit for the next workflow step, archive, or issue the model. Keep permissions separate from professional approval or legal ownership. Define what happens when a model exchange conflicts with drawings, schedules, specifications, or an approved project instruction.
buildingSMART describes BCF as an openBIM standard for communicating model-based issues across BIM applications, including comments, assignments, references, documents, and statuses. A BCF issue marked closed, or a model exchange marked final, does not automatically mean design approval, code compliance, site acceptance, or contract completion.
Shop Drawings, Fabrication Drawings, and Installation Drawings
The names of drawing types can vary between contracts and companies. Project documents should define their purpose, required content, assigned preparer, checker, submission route, revision control, and record status.
Shop drawings
May coordinate project-specific system layouts, interfaces, dimensions, materials, panel schedules, and construction information. State expected views, details, schedules, revision fields, and coordination references.
Review does not automatically equal design approval, code compliance, professional acceptance, or an instruction to fabricate unless the project process defines those meanings.
Fabrication drawings
May convey production-specific part or assembly references, labels, tolerances, material basis, factory operations, and release fields. Identify developer, checker, submitter, review route, relationship to the approved shop/detail basis, and retained record.
A “final” label alone does not establish approval. The project-defined review and release route controls its meaning.
Installation drawings
May provide field-oriented information for locations, sequence, connections or interfaces, access coordination, and installation activities. Identify preparer, checker, submitter, site reviewer, revision route, and record holder.
This article does not provide installation methods or approve field details. Site execution must follow project documents and qualified professional review.
Panel, material, and record schedules
Panel and material schedules are controlled tables, not substitutes for drawings or design review. Define who prepares, checks, submits, revises, and records schedules containing marks, locations, types, materials, quantities, revisions, and document references.
Define what “record” or “as-built” means, which reviewed changes must be incorporated, who compiles the package, who checks and submits it, and where the final record is stored. A model or drawing does not automatically become the legal or controlling record because it is labeled “as-built.”
Submittal Preparation, Review Comments, and Revision Routes
- Define inputs and criteria. Identify project documents, design criteria, model/drawing requirements, interfaces, and missing information.
- Allocate preparation and checking. Name the preparer/developer, internal checker, submitter, reviewer, and record holder.
- Prepare and internally check. Record version, assumptions, references, coordination checks, and open issues.
- Submit through the controlled route. Use the project-defined register, recipient, format, and submission status.
- Record comments and responses. Link each comment to the document/model version, responder, response, and required action.
- Revise and resubmit. Record revision reason, affected interfaces, response status, and remaining open item.
- Update the register and records. Maintain current document, comment, response, and version history.
- Handoff final records. Confirm record/as-built models, drawings, schedules, and response-log requirements.
Shared fields for both planning tools
The Engineering Responsibility Register and Technical Document Deliverable Matrix use the same planning vocabulary. The first starts with a technical item and assigns project-defined roles, interfaces, revisions, and records. The second starts with a document or model and defines its purpose, inputs, preparation/checking/submission route, review route, status fields, and final-record requirement.
Both tools must be completed from the contract, specification, BIM requirements, professional appointments, and project procedures. Neither tool assigns legal responsibility or professional appointment by itself.
Status Taxonomy for Scope, Workflow, and Roles
Quotation scope states
IncludedOptionalExcludedSubject to ConfirmationOpen QuestionWorkflow and project states
Open / Submitted / ReturnedRevised / ReviewedProfessional reviewResponsibility to assignRecord / Final recordRole fields
To assignPreparer to assignInterface owner to assignRecord holder to assignRole-field values are not workflow statuses. Approval and acceptance fields must be defined separately by project documents. A workflow status is not automatically approval, acceptance, code compliance, professional sign-off, or legal responsibility.
Engineering Responsibility Register
| Technical item | Required input / criteria | Project-assigned preparer / developer | Internal checker | Submitter | Project-defined reviewer / status | Revision / record holder | Interface / open issue |
|---|---|---|---|---|---|---|---|
| Design criteria and inputs | Project criteria, requirements, approved references | To assign | To assign | To assign | Project-defined review | Record holder to assign | Missing input |
| Calculations / analysis | Defined data, assumptions, criteria, format | To assign | Qualified checker to assign | To assign | Professional review where required | Project record route | Criteria gap |
| System / detail development | Approved system basis and interfaces | To assign | To assign | To assign | Comment/review route | Revision control | Interface gap |
| BIM model / exchange | Information requirements, purpose, format, coordination rules | Model author to assign | BIM/design checker to assign | To assign | Model review/status | Project-defined model/record status | Model interface |
| Shop drawings | Approved inputs, schedules, details, materials, dimensions | To assign | To assign | To assign | Review/comment status | Drawing register holder to assign | Detail gap |
| Fabrication drawings | Production inputs, labels, tolerances, factory requirements | Fabricator/preparer to assign | To assign | To assign | Project/factory route | Factory/archive record to assign | Production interface |
| Installation drawings | Approved details, sequence, field interfaces | Installer/preparer to assign | To assign | To assign | Site/project route | Site record holder to assign | Access/sequence gap |
| Panel/material schedules | Marks, materials, quantities, revisions | To assign | To assign | To assign | Schedule review | Schedule holder to assign | Data mismatch |
| Submittal register / response log | Required documents, dates, recipients, formats | Coordinator to assign | Internal review | To assign | Submitted/returned/revised/reviewed | Register holder to assign | Missing requirement |
| Review responses | Comments, responses, change references | Response owner to assign | To assign | Coordinator to assign | Project-defined status | Response log holder to assign | Unresolved comment |
| Record / as-built documents | Final revisions and record requirements | To assign | To assign | To assign | Project-defined record status | Record holder to assign | Handover gap |
This register is a planning tool. It does not itself assign legal responsibility, professional appointment, approval, or code compliance.
Technical Document Deliverable Matrix
| Deliverable | Purpose | Inputs | Prepare / check / submit | Review route | Revision / status fields | Final record requirement |
|---|---|---|---|---|---|---|
| Design criteria/input register | Define project basis and open inputs | Employer, contract, project criteria | To assign | Project-defined review | Version, open, confirmed | Source record |
| Calculations/analysis package | Document project-defined analysis | Criteria, materials, interfaces, project data | To assign | Professional review where required | Revision, comment, status | Final package if required |
| BIM model/exchange | Coordinate information and interfaces | BIM requirements and model inputs | Author/checker to assign | Model coordination route | Exchange, version, status | Record model if required |
| Shop drawings | Coordinate project-specific technical information | Approved inputs, details, materials, schedules | Preparer/checker/submitter to assign | Submittal route | Revision, comment, status | Record drawing if required |
| Fabrication drawings | Convey production-specific information | Approved shop/detail/material basis | Fabricator/checker to assign | Factory/project route | Revision, release, status | Factory/archive record |
| Installation drawings | Coordinate project-defined field information | Approved details and sequence inputs | Installer/checker to assign | Site/project route | Revision, comment, status | Site record if required |
| Panel/material schedules | Link marks, materials, quantities, documents | Panel IDs, material basis, revisions | To assign | Schedule review route | Version, status | Handover schedule if required |
| Submittal register/response log | Track documents, comments, responses | Requirements and review comments | Coordinator to assign | Controlled workflow | Open, submitted, returned, revised, reviewed | Final register |
| Record/as-built package | Preserve project-defined final information | Reviewed changes and records | To assign | Project-defined route | Record status | Handover destination |
The matrix must be adapted to the contract, project specification, BIM information requirements, and professional appointments. It does not itself assign legal responsibility, professional appointment, approval, or code compliance.
Engineering and Interface Clarification Questions
- Which design inputs and criteria are issued by the project team, and which must be developed or confirmed by the facade package team?
- Is the requested service design-assist, delegated design, technical coordination, fabrication support, or another defined scope?
- Which calculations or analyses are included, and who prepares, checks, submits, and reviews them?
- Which party develops system or detail information, and what are the limits of that development?
- Who authors, checks, exchanges, coordinates, updates, and stores the BIM model?
- What model purpose, information requirements, file format, exchange frequency, permissions, and record status apply?
- Who prepares shop, fabrication, and installation drawings and panel/material schedules?
- What internal checking is required before submission, and how is it recorded?
- Who receives, reviews, comments on, responds to, and tracks each submittal or issue?
- Which issue/comment platform or register is required, and who can change each status?
- How are revisions, resubmissions, technical queries, and design changes recorded?
- Which structure, waterproofing, fire-stopping, doors, louvers, shading, adjacent-facade, logistics, and installation interfaces require assigned roles?
- Which final models, record/as-built drawings, schedules, and response logs are required?
- Which items remain Subject to Confirmation, Open Question, Professional review, or Responsibility to assign?
FAQ: Engineering Responsibility and Technical Documents
What is design-assist for a unitized curtain wall?
Design-assist is a project-defined service scope that may include technical input, coordination, system information, detailing, document preparation, or other stated deliverables. Define inputs, limits, interfaces, checking, submission, review route, and records.
What is delegated design in curtain wall procurement?
Delegated design is a project-defined package of technical deliverables and responsibilities. Project documents should state what is delegated, which inputs and criteria apply, which interfaces remain with others, who prepares and checks the work, and what review and professional process is required.
Who prepares unitized curtain wall calculations?
Name the project-assigned role in the responsibility register and project documents. Identify required inputs, criteria, preparer, checker, submitter, reviewer, revision route, and record holder. This article does not perform or approve calculations.
Who is responsible for curtain wall shop drawings?
Responsibility depends on project scope and appointment. Identify the assigned preparer, internal checker, submitter, reviewer, interfaces, revision route, and record holder rather than relying on a general industry label.
What is the difference between shop and fabrication drawings?
Shop drawings generally coordinate project-specific technical information, while fabrication drawings may convey production-specific information. Exact definitions, content, review route, and status should be set by project documents and the deliverable matrix.
What should a curtain wall BIM responsibility matrix include?
State model purpose, information requirements, authoring, inputs, exchange format and frequency, coordination, permissions, checking, update responsibility, issue management, record status, and assigned roles. Model control and ownership are defined by BIM requirements and contract documents.
Does shop drawing review mean design approval?
Not automatically. A review comment, “no comments,” reviewed status, closed issue, or final label is a workflow record unless project documents give it a separate defined approval or acceptance meaning.
How should curtain wall submittal comments and revisions be recorded?
Link each comment to the document or model version, assigned responder, response, affected interface, revised version, resubmission date, status, remaining action, and record holder. Use the project-defined register or issue-management process.
Conclusion and Project-Specific CTA
A unitized curtain wall engineering scope is clearer when every technical item has a defined input, criteria, deliverable, project-assigned preparer, checker, submitter, reviewer, interface, revision route, status, and record holder.
- Define the category. Describe design-assist, delegated design, technical coordination, fabrication support, or another project-specific service without assuming a universal transfer of responsibility.
- List inputs and criteria. Identify project documents, design requirements, interfaces, BIM information requirements, and missing information.
- Allocate deliverables. Separate calculations, BIM, shop drawings, fabrication drawings, installation drawings, schedules, submittals, response logs, and record documents.
- Control the review route. Assign preparation, internal checking, submission, comments, responses, revisions, resubmissions, status updates, and record handoff.
- Name interface roles. Record who supplies, develops, checks, reviews, and records decisions for technical interfaces.
- Obtain project-specific review. Keep workflow statuses separate from approval, acceptance, code compliance, professional sign-off, and legal responsibility.
Share the project responsibility matrix, design criteria, BIM requirements, drawing register, submittal procedure, review route, revision rules, interface schedule, record-document requirements, and professional appointments for a project-specific unitized curtain wall engineering-scope review.
FOWALL’s public pages describe categories such as engineering design, calculations, shop drawings, material schedules, BIM coordination, installation planning, and quality-control documentation. Any service availability, scope, fee, technical responsibility, document format, or project deliverable must be confirmed for the specific project. This article does not provide engineering design, approval, code-compliance, professional-signature, performance, or supplier-capability conclusions.
