Technical Query Register for Window Projects: Owners, Deadlines and Dispositions

1. Define one register, one channel and one identity rule

Agree which matters belong in technical query/RFI, submittal comment, NCR, change request, site instruction, design decision, commercial notice or request for information. Terms vary by contract. Give each query a stable unique ID, project/discipline, originator, issue date, status and authoritative record location; do not recycle IDs after cancellation.

Define permitted submission/response channel, access, notification, attachments, version history, correction and audit trail. Chat and calls can support urgent coordination, but transfer any controlled question/response into the authorised system. Preserve original messages where the protocol requires them.

Deduplicate before issue. Search queries, drawing comments, submittals, meeting actions, changes and NCRs. Link related records, but do not bundle issues with different baseline, scope or decision authority. A parent/child relationship is clearer than one RFI containing five partially answered questions.

2. Separate facts, conflicts, assumptions, options and the decision requested

State facts with exact source quotations/references, opening marks, location, photographs/survey records and dates. Show the conflict side by side: drawing A revision, schedule B revision and physical condition C. Do not use a red-circle screenshot without its document identity and scale/context.

List assumptions separately and name their evidence status. A supplier may propose options with technical data, advantages, risks and dependencies, but label them proposals—not the expected answer. Avoid leading questions that hide a preferred unapproved substitution.

Ask one implementable question and state required authority. Explain affected decisions and potential schedule/cost/quality consequence neutrally, without claiming entitlement. Include the answer-needed date derived from the programme dependency and the last responsible decision point, not an arbitrary urgency label.

3. Assign owner, decision authority, contributors and due date separately

The query owner manages completeness and follow-up; the responder may provide technical analysis; the decision authority disposes within delegated scope; contributors review interfaces; document owners incorporate the answer. One person may hold several roles, but the register should not infer authority from seniority, attendance or email copying.

Route by subject: architect/design, façade, structural, glass, fire, acoustic, accessibility, hardware/system, contractor/site, compliance, commercial or another project role. When a decision crosses remits, identify coordinated dispositions or elevate under the authority matrix. A technical specialist cannot automatically direct contract scope or cost.

Track issue, acknowledgement, planned response and required answer dates under the project procedure. Escalate before the dependency becomes critical. Show overdue/open state and affected holds; do not close or approve by silence unless the executed contract explicitly creates that effect and authorised counsel confirms use.

4. Require a self-contained answer, disposition and impact assessment

A response repeats the query ID and baseline, directly answers each numbered question, states affected marks/scope, cites calculations/sketches or standards by controlled identity, lists conditions and exclusions, and names responder/authority/date. ‘As discussed’, ‘noted’ and an annotated screenshot without revision are not implementable dispositions.

Use project-defined dispositions such as answered/no change, design revision required, approved technical proposal within authority, rejected proposal, more information required, superseded/duplicate or another controlled state. Separate response status from query closure. An answer can be issued while documents and change consequences remain open.

Assess impact across drawings/schedules, system/BOM, glass, hardware, finish, compliance evidence, material commitments, machining/production, inspection/tests, packing, installation, cost and programme. Route any instruction, variation, notice, claim or entitlement through its separate contract process. The TQ/RFI record links that process but does not create its legal outcome.

5. Incorporate the answer, withdraw superseded sources and prove closure

Create an incorporation list for every affected drawing, schedule, specification, BIM object, BOM, work instruction, purchase order, inspection/test plan, method, label, packing list, change and as-built record. Name owner, target revision/status and verification. Meeting minutes or email should not remain the only production source.

Withdraw or visibly supersede obsolete copies in engineering, purchasing, supplier portals, workshop, QA, packing and site sets. Audit both directions: query to every revised output, and changed detail back to authorised query/change. Broken reverse traceability reveals informal decisions.

Close only when authorised disposition exists, separate consequences are routed, controlled sources are updated/issued, affected parties are notified, holds are released or restated and closure verification is recorded. Reopen on changed baseline, new evidence or failed implementation. Retain full history at handover.

FAQ

Continue the project review

Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.

Related buyer guides

• How to Run a Window Interface RFI Register Without Losing Decisions in Email
• Window Shop-Drawing Approval: What ‘Approved,’ ‘Approved as Noted’ and ‘Revise’ Should Control
• A Window Factory Quality-Control Checklist Buyers Can Actually Use