Common Specification Coordination Issues That Should Be Resolved Before Tender

Drawings and specifications must describe the same work

An architectural specification is not an isolated document. It forms part of a coordinated set of construction documents alongside drawings, schedules and other consultants' requirements. A final review before tender should identify material descriptions, assembly configurations, performance requirements and locations that do not agree. Where design decisions remain outstanding, the responsible consultant should resolve them rather than leaving bidders to interpret competing instructions.

1. Conflicting material and product requirements

A door schedule may identify one assembly while a specification section describes another. A finish schedule may use a designation that is absent from the technical section, or the section may prescribe a performance characteristic that has not been coordinated with the selected product. Confirm that designations, material types, ratings, finishes, dimensions and performance criteria describe a consistent requirement. Product names can help communicate design intent, but they should not replace the necessary technical criteria or the project's approach to acceptable alternatives.

2. Requirements placed in the wrong section

Section titles and numbers should help users find the requirements applicable to the work. When a specialized assembly is described under an unrelated section, contractors may overlook it or apply inconsistent requirements. Review section scope, related requirements, schedules and references to confirm that each assembly is addressed in the appropriate location. A correction should resolve the conflict rather than merely duplicate the requirement elsewhere.

3. Division 01 and contract coordination

Division 01 establishes administrative and procedural requirements that affect technical work, including submittals, quality assurance, testing, temporary facilities, project constraints and closeout. Its requirements should reflect the selected construction contract, procurement approach and owner conditions. Generic provisions carried forward from an unrelated project can create conflicts over responsibilities, approvals, review periods and deliverables.

4. Interfaces and delegated design responsibilities

Some assemblies rely on design or engineering carried out by a specialty supplier or contractor. Specifications should establish the required performance, applicable design criteria, submittals, professional authentication where required and interfaces with adjacent construction. Delegated design does not remove the need for the project design team to define the intended outcome and coordinate the surrounding work. Consultant review of submittals should be described consistently with the contract and professional responsibilities.

5. Unresolved decisions at the tender milestone

A final review should distinguish confirmed requirements from incomplete selections, missing details and open consultant questions. Particular attention is warranted where a decision affects price, sequencing, procurement, testing or the work of multiple trades. Clear documentation before tender can reduce avoidable ambiguity, although it cannot eliminate all requests for information, changes or construction risks.

A practical pre-tender review

Before issue, compare the drawing index and schedules against the specification table of contents; review key assemblies and product designations; verify applicable reference standards; confirm Division 01 aligns with the contract; and resolve cross-discipline interfaces and outstanding design decisions. The purpose is not simply to produce a complete-looking project manual. It is to communicate coordinated requirements that bidders can understand and price.

SPECDOCX provides architectural specification development, document coordination and technical review support for design teams. Explore document coordination services or discuss your project requirements.