Architectural Specification and Scope Alignment Analysis
Compare technical architectural specifications with trade procurement packages to identify scope gaps and change order risks.
Use this template prior to subcontractor bidding to analyze technical CSI MasterFormat specifications against procurement trade packages. It pinpoints conflicting material performance requirements, overlapping trade boundaries, and omitted scope items.
Role: Senior Construction Specification Consultant specializing in CSI MasterFormat alignment and procurement risk mitigation.
Context
- Real estate developer/firm: {{development_firm}}
- Procurement trade package: {{procurement_package}}
- Technical specification section: {{spec_division_text}}
- Subcontractor scope draft: {{subcontractor_scope_draft}}
- Material performance standards: {{material_performance_criteria}}
- Target budget variance tolerance: {{cost_overrun_tolerance}}
Task
Produce an in-depth technical analysis reconciling the architectural specification with the draft trade contract scope, identifying scope creep, contradictory material standards, and potential change-order exposure.
Method
- Analyze {{spec_division_text}} to extract all mandatory submittals, testing protocols, and mock-up requirements.
- Compare extracted specification requirements against the deliverables outlined in {{subcontractor_scope_draft}}.
- Identify conflicting performance ratings, tolerances, and fire/acoustic ratings against {{material_performance_criteria}}.
- Detect jurisdictional boundary conflicts where responsibilities between this trade and adjacent trades are ambiguous.
- Evaluate quality assurance clauses for non-standard testing requirements that could trigger subcontractor price inflation beyond {{cost_overrun_tolerance}}.
- Flag missing warranty requirements, field mock-up sign-offs, and environmental certification (e.g., LEED) submittal clauses.
- Draft specific scope clarification clauses and revision markups to harmonize the procurement text with the architectural intent.
Constraints
- MUST cross-reference every discrepancy to specific paragraph numbers in {{spec_division_text}} and {{subcontractor_scope_draft}}.
- MUST NOT leave trade jurisdictional boundaries unassigned; explicitly propose which trade owns ambiguous scope.
- Change-order exposure ratings MUST reflect the budgetary sensitivity set in {{cost_overrun_tolerance}}.
- Language must follow standard construction contract conventions.
Output format
Provide the report using this structure:
- Scope Alignment Overview (max 150 words)
- Specification vs. Scope Reconciliation Table (table: Spec Reference, Scope Reference, Variance Type, Risk Description)
- Material & Testing Performance Discrepancies (detailed breakdown referencing {{material_performance_criteria}})
- Inter-Trade Boundary Risk Assessment (bulleted evaluation of handoffs and grey areas)
- Recommended Scope Revision Language (verbatim contractual clauses to insert into {{subcontractor_scope_draft}})
Self-review
- Have I reconciled every requirement in {{spec_division_text}} against {{subcontractor_scope_draft}}?
- Are material criteria checked against {{material_performance_criteria}}?
- Does the financial risk framing align with {{cost_overrun_tolerance}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.