How to Clarify Assumptions and Exclusions in a Curtain Wall Quote
Unclear Quote Language Needs a Record, Not a Guess
A returned curtain wall quotation may contain phrases such as "by others," "excluded," "allowance," "subject to design," "as required," "alternative," or "provisional." These phrases can be useful commercial qualifications, but they are not always clear enough to identify the affected scope, responsible party, documentary basis, or next action.
The practical response is not to guess what the supplier intended. Use this workflow:
- 01Identify
- 02Classify
- 03Ask
- 04Assign
- 05Document
- 06Update
- 07Review
Capture the exact wording and reference, classify it as a working review category, link it to the affected scope or interface, ask a neutral written question, assign responsibility, record the response and status, update the applicable quotation or project record, and route specialist questions to the right professional team.
This article uses practical working distinctions rather than universal legal definitions. The quotation, specification, contract, procurement rules, jurisdiction, and project professionals control the applicable meaning and documentary effect. Written clarification can improve traceability, but it is not automatically a contract amendment, legal acceptance, or guarantee that every risk is eliminated.
This article assumes that a quotation has already been returned. It focuses on written clarification and register management, not on preparing the full RFQ, explaining the anatomy of a complete quotation, comparing multiple bids, reviewing delivery terms in depth, or presenting a broad quotation-risk taxonomy.
Working Distinctions for Ambiguous Quote Language
Use the following as practical review categories only:
| Term | Practical review meaning | What to ask for |
|---|---|---|
| Assumption | A condition used because information is missing, uncertain, or not finalized | The information assumed, affected scope, responsible party, and what must be confirmed |
| Exclusion | Work, material, service, or responsibility stated as outside the quoted scope | The exact excluded item, interface, named party, and documents needed to assign or price it |
| Qualification | A condition, limitation, deviation, or dependency attached to the offer | The trigger, limitation, deliverable, review path, and quotation status |
| Allowance | A provisional amount, quantity, or basis for an incompletely defined item | Basis, quantity/unit, inclusions, exclusions, limits, and reconciliation method |
| Provisional item | A placeholder that remains subject to definition or reconciliation under the project process | Definition trigger, responsible party, evidence, and update mechanism |
| Alternative/substitution | A proposed basis different from the stated or base requirement | Base/option status, product information, technical review, approval path, and affected scope |
| Work by others | An allocation phrase that should name the other party and interface | Supply, coordination, installation, testing, protection, replacement, and handover responsibilities |
These categories may be defined differently by project documents, contracts, procurement rules, or jurisdictions. Do not treat a category label alone as proof of legal effect, supplier intent, technical equivalence, or a fixed commercial result.
Working classification, workflow status, and formal outcomes
These three layers should not be mixed:
- Working classifications: Assumption, Exclusion, Qualification, Allowance, Provisional Item, Alternative/Substitution, and Work by Others describe what kind of wording is being reviewed. They are practical categories, not universal legal definitions.
- Workflow statuses: Open, Clarification requested, Evidence received, Assigned, and Closed track progress in a working register. Open does not mean accepted scope.
- Formal clarification outcomes: Clarify before comparison, Document before contract review, Requires project-professional review, and Not resolved / carry forward describe the issue's next routing step. They do not judge a supplier or determine contract effect.
Step 1: Capture the Exact Wording and Reference
Start with the quotation as written rather than a paraphrase. Record:
- quotation number, revision, issue date, and validity
- exact sentence, table cell, qualification, or line item
- page, section, schedule, or line reference
- drawing, specification, panel schedule, addendum, email, meeting record, or other source
- affected material, engineering, testing, factory, logistics, installation, replacement, or handover scope
- affected interface or work-by-others area
- current status and owner; and
- whether cost, programme, testing, logistics, or installation effect is To be confirmed.
This record prevents paraphrase drift. It is a documentation practice, not a legal conclusion.
Example capture format
| Capture field | Example entry |
|---|---|
| Quotation basis | Quote Q-___, revision ___, dated ___ |
| Exact wording | "Subject to site conditions" |
| Reference | Page ___, line ___, drawing/specification ___ |
| Affected scope | Access, unloading, installation, adjustment, or another interface |
| Classification | Qualification / Open Question |
| Responsible party | Supplier / buyer / installer / design team / other named party |
| Cost/programme effect | To be confirmed |
| Next action | Ask for the trigger, boundary, owner, and written response |
Step 2: Link the Wording to Affected Scope and Responsibility
A phrase is easier to clarify when it is linked to the actual work it affects. Check whether the wording concerns:
- system configuration, profiles, reinforcement, glass, infill, finishes, gaskets, sealants, anchors, or hardware
- design-assist, delegated design, calculations, shop drawings, fabrication drawings, BIM, or revisions
- mockups, testing, reports, QA/QC, traceability, corrective work, or handover
- factory assembly, factory glazing, sealing, inspection, labeling, storage, release, rework, or replacement
- packaging, transport, customs, insurance, unloading, storage, lifting, delivery, or site access
- installation labor, supervision, training, site adjustment, re-delivery, or handover; and
- work by others, adjacent systems, non-unitized areas, openings, corners, transitions, or interfaces.
Then identify who may be responsible for supply, coordination, installation, testing, protection, replacement, acceptance, and documentation. Do not infer fault from a responsibility gap. The aim is to make the allocation visible and reviewable.
FOWALL, YKK AP, Yuanda, and Hydro public pages describe product, service, document, factory, or installation categories in their own published scope. They can provide useful clarification prompts, but they do not define the scope of a specific quotation or decide technical equivalence.
Step 3: Ask Neutral, Specific Clarification Questions
Neutral questions make it easier to obtain a usable response without assuming concealment, bad faith, legal entitlement, automatic contract effect, or a guaranteed cost or programme result.
Use questions such as:
- "Please confirm whether this item is included in the base quotation, optional, excluded, or subject to confirmation."
- "Please identify the document, drawing, schedule, line item, or assumption used for this qualification."
- "Please identify the responsible party for supply, coordination, installation, testing, protection, replacement, and handover."
- "If this item is excluded, please identify the affected interface and the information required to price or assign it."
- "Please state whether the proposed alternative is part of the base offer or a separately priced option, and provide supporting technical information."
- "Please state the allowance or provisional basis, quantity/unit, inclusions, exclusions, and reconciliation method."
- "Please identify any effect on scope, cost, programme, testing, logistics, or installation as a field to be confirmed."
- "Please confirm how this response will be reflected in the revised quotation, clarification register, addendum, or other applicable project document."
A question should point to the exact wording and ask for a defined response. Avoid broad prompts such as "Please clarify everything" or accusatory wording such as "Why did you hide this item?"
Step 4: Record Alternatives, Allowances, Provisional Items, and Qualifications
Do not combine unresolved categories in one lump-sum line. Record the base offer and each qualification separately.
Alternatives and substitutions
A proposed alternative should be identified separately from the base requirement. Ask for:
- base/option status
- product, system, or material information
- affected drawings, schedules, interfaces, and samples
- technical review and approval path
- testing, QA/QC, maintenance, or handover implications to be confirmed; and
- any cost or programme effect as To be confirmed unless supported by project-specific written information.
Do not assume that an alternative is equivalent to the base offer. Request supporting information and project review.
Allowances and provisional items
An allowance or provisional item should state its basis, quantity or unit, inclusions, exclusions, limits, reconciliation method, trigger for update, and responsible party. It should not be silently treated as a complete fixed scope.
Ask:
- What information defines the allowance?
- Which materials, labor, engineering, testing, logistics, or installation activities are included?
- Which items are excluded or assigned to others?
- What quantity, unit, limit, or assumption applies?
- How and when will the item be reconciled or updated?
- Which cost, programme, testing, logistics, or installation fields remain To be confirmed?
Qualifications and deviations
For "subject to design," "subject to approval," "subject to site conditions," "as required," or similar wording, identify the trigger, limitation, deliverable, responsible party, review path, and quotation status. Do not convert a qualification into a legal reservation or supplier fault without project-specific professional review.
Step 5: Confirm Cost and Programme Fields Without Inventing Values
Ambiguous wording may affect scope or commercial review, but the effect cannot be inferred safely from the phrase alone. Use explicit fields:
| Review field | Safe entry before evidence is available |
|---|---|
| Scope effect | To be confirmed |
| Cost effect | To be confirmed |
| Programme effect | To be confirmed |
| Testing/QA effect | To be confirmed |
| Logistics/delivery effect | To be confirmed |
| Installation/handover effect | To be confirmed |
| Responsible reviewer | Named supplier, buyer, design, procurement, contract, testing, tax, customs, logistics, installation, or other professional team |
| Evidence required | Written response, revised quotation, addendum, drawing, schedule, product data, test document, or other applicable record |
Ask the supplier or project team to state the effect and its basis. Do not invent a cost increase, saving, delay, loss, dispute, performance result, or contract outcome.
Step 6: Obtain Written Confirmation and Update the Project Record
Use a controlled sequence:
- Capture the exact wording and reference.
- Identify the affected scope, document, interface, and responsible party.
- Ask a neutral written question.
- Record the response without paraphrasing away qualifications.
- Mark unsupported cost, programme, testing, logistics, or installation effects as To be confirmed.
- Obtain the applicable revised quotation, addendum, clarification record, or other project document.
- Route specialist matters to procurement, contract, design, testing, tax, customs, logistics, installation, or other professionals.
- Close, carry forward, or escalate the item according to the project process.
FAR Subpart 14.2 provides a U.S. federal example of structured solicitation sections for prices, specifications, packaging/marking, inspection/acceptance, delivery/performance, administration, documents, explanations, and amendments. This supports controlled records as a documentation principle in that context; it is not a universal private-sector or international process.
A written clarification is not automatically a contract amendment or legal acceptance. The applicable procurement and contract teams must determine how it should be incorporated.
Assumptions and Exclusions Register
Use a register to preserve wording, ownership, status, and next action.
| ID | Exact quote wording | Reference | Affected scope/interface | Classification | Supplier response | Responsible party | Status | Cost/programme field | Written record/next action |
|---|---|---|---|---|---|---|---|---|---|
| A-01 | "By others" | Quote line/detail | Supply, coordination, or installation | Exclusion/work by others | To be confirmed | Buyer/supplier/design team | Open | To be confirmed | Request boundary and owner |
| A-02 | "Allowance" | Commercial schedule | Material or provisional scope | Allowance | To be confirmed | Supplier/procurement team | Open | To be confirmed | Request basis and reconciliation |
| A-03 | "Subject to design" | Qualification | Engineering or technical deliverable | Qualification | To be confirmed | Supplier/design team | Open | To be confirmed | Request responsibility and deliverables |
| A-04 | Proposed substitution | Alternative schedule | Product, performance, or approval scope | Alternative | To be confirmed | Supplier/design team | Open | To be confirmed | Request separate base/option information |
| A-05 | Unrecorded verbal answer | Meeting/email note | Any affected scope | Open Question | To be confirmed | Buyer/supplier | Open | To be confirmed | Obtain dated written confirmation |
These are workflow fields, not legal acceptance, contract conclusions, or guarantees.
Clarification Register and Responsibility Handoff
The Assumptions and Exclusions Register identifies uncertain quote language. The Clarification Register tracks the questions, responses, revised documents, and handoffs that follow.
| Question ID | Quote/reference | Neutral question | Supplier response | Affected scope | Responsible party | Status | Revised quote/addendum/document | Next action |
|---|---|---|---|---|---|---|---|---|
| Q-01 | Quote page/line | Is the item included, optional, excluded, or subject to confirmation? | To be recorded | Scope boundary | Supplier/buyer | Open | To be confirmed | Update scope status |
| Q-02 | Drawing/specification | Which document or assumption supports the qualification? | To be recorded | Technical basis | Supplier/design team | Open | To be confirmed | Verify document |
| Q-03 | Interface detail | Who supplies, coordinates, installs, tests, protects, replaces, and hands over the item? | To be recorded | Responsibility | Named parties | Open | To be confirmed | Update responsibility record |
| Q-04 | Alternative/allowance | Is the item base, option, allowance, or provisional? What is its basis? | To be recorded | Commercial/technical scope | Supplier/procurement/design | Open | To be confirmed | Request separate line |
| Q-05 | Verbal clarification | Can the response be confirmed in a dated written record? | To be recorded | Any affected scope | Buyer/supplier | Open | To be confirmed | Attach to quotation record |
Route issues to the team that can review them:
- Supplier: quotation basis, product information, scope status, assumptions, alternatives, and revised commercial response.
- Buyer/procurement: quotation records, bidder communications, deadlines, distribution, and comparison status.
- Design/project professionals: configuration, interfaces, design responsibility, technical equivalence, testing, fire, structure, and acceptance.
- Contract/procurement team: documentary process, commercial terms, qualifications, revisions, and applicable contract review.
- Trade/tax/customs/insurance professionals: delivery, importer/broker, taxes, duties, insurance, and local charges where relevant.
- Logistics/installation/site team: packaging, unloading, storage, lifting, access, floor release, installation, adjustment, replacement, and handover.
Conditional Clarification Outcomes
Use these statuses to classify the issue and next action, not the supplier or legal effect.
| Status | Use when | Evidence expected | Next action |
|---|---|---|---|
| Clarify before comparison | The wording may affect whether the quotation shares the same scope or basis as another offer. | Exact wording, reference, neutral question, and affected line/scope. | Obtain a written response and update the comparison record. |
| Document before contract review | The response affects assumptions, exclusions, qualifications, alternatives, allowances, responsibilities, or commercial conditions. | Dated response, responsible party, affected document, and quotation revision. | Record it in the register and route it for procurement/contract review. |
| Requires project-professional review | The issue concerns design, structure, testing, code, tax, customs, contract, installation, acceptance, or another specialist matter. | Configuration/project-specific evidence and professional input. | Escalate; do not resolve it through generic wording. |
| Not resolved / carry forward | The response is incomplete or the project team has not accepted the basis for the next step. | Open question, owner, due item, and follow-up record. | Keep it visible and do not silently treat it as confirmed scope. |
These statuses classify the issue and next action, not a supplier, contract, or legal outcome.
Common Clarification Mistakes to Avoid
- Guessing what "by others," "excluded," "allowance," or "subject to design" means.
- Replacing the exact quotation wording with an untraceable paraphrase.
- Asking an accusatory question that assumes concealment or bad faith.
- Failing to name the affected scope, interface, or responsible party.
- Treating an alternative as equivalent to the base offer without supporting information or review.
- Treating an allowance or provisional item as complete fixed scope.
- Leaving cost, programme, testing, logistics, or installation effects blank instead of recording To be confirmed.
- Relying on an unrecorded call or meeting statement as the only scope evidence.
- Treating written clarification as automatically changing the contract or quotation.
- Using a clarification register as a substitute for design, testing, tax, customs, insurance, contract, installation, or acceptance review.
- Rebuilding the full RFQ, quotation anatomy, delivery tutorial, or multi-bid matrix instead of focusing on the ambiguous wording.
- Promising that written clarification eliminates every risk.
FAQ: Assumptions and Exclusions Clarification Questions
How should I clarify assumptions in a curtain wall quote?
Record the exact assumption, quotation reference, affected scope, responsible party, and any cost or programme field as To be confirmed. Ask the supplier to state the basis, required information, and how the answer will appear in the applicable revised quotation or project record.
What is the difference between a curtain wall exclusion and a qualification?
As a practical review distinction, an exclusion identifies work stated as outside the quoted scope, while a qualification states a condition, limitation, deviation, or dependency attached to the offer. Project documents, contracts, procurement rules, and jurisdictions may use different definitions.
How do I ask a supplier to confirm a curtain wall quote exclusion?
Use neutral wording: "Please identify the affected item and interface, confirm whether it is excluded from the base quotation, and identify the responsible party and information required to assign or price it." Record the response and status.
What should an assumptions and exclusions register include?
Include the ID, exact quote wording, reference, affected scope/interface, classification, supplier response, responsible party, status, cost or programme field, written record, and next action. Keep unsupported effects as To be confirmed.
How should alternatives and allowances be recorded in a curtain wall quote?
Separate them from the base offer. Record the product or scope basis, quantity/unit, inclusions, exclusions, limits, supporting information, approval or review path, reconciliation method, responsible party, and any unresolved cost, programme, testing, logistics, or installation field.
How do I document a curtain wall quotation clarification?
Record the question, exact quote reference, date, sender, recipients, response, affected scope, responsible party, status, revised quotation/addendum/project document, and next action. Follow the project's applicable procurement and contract process.
Who should review a curtain wall quote responsibility gap?
The supplier and buyer should clarify the quotation basis, while design, testing, installation, logistics, tax, customs, insurance, procurement, contract, or other professionals review issues within their domains. The right reviewer depends on the project documents and question.
Can written clarification change the scope of a quotation?
It may inform a revised quotation or project record, but the applicable procurement and contract teams must determine its documentary effect. Do not assume that an email or clarification automatically changes a contract or confirms technical acceptance.
Conclusion and Project-Specific Clarification CTA
Clarifying assumptions and exclusions is a traceability workflow:
- Identify the exact wording and reference.
- Classify it as a working review category without assigning universal legal meaning.
- Ask a neutral, specific question.
- Assign the affected scope and responsible party.
- Document the response, evidence, and status.
- Update the applicable quotation, addendum, clarification register, or project record.
- Review specialist matters with the appropriate project and professional teams.
Reviewing an ambiguous curtain wall quotation? Share the quotation revision, assumptions, exclusions, qualifications, alternatives, allowances, scope schedule, responsibility gaps, and open questions for a project-specific clarification review and register before the project's next authorized procurement or contract step.
FOWALL's public pages describe product, engineering, planning, manufacturing, logistics, and installation-support categories. Any service availability, scope, fee, technical responsibility, delivery content, or project outcome must be confirmed for the specific project. This article is not legal or contract interpretation, engineering approval, tax/customs/insurance advice, or a guarantee that written clarification eliminates all risk.
