Specification coordination: reducing conflicting requirements
Admin · 22 October 2026
Illustrative image. Photo by Pedro Miranda on Unsplash. Unsplash License.
A specification can be carefully written within each discipline and still conflict with drawings, schedules or another package. The problem often becomes visible when a bidder asks which requirement to price or an installer finds two instructions for the same interface. Coordinating the specification means testing the information set as a whole before the project relies on it, rather than assuming that correct individual documents automatically form a coherent package.
For design and commercial teams, the practical objective is to identify inconsistencies, obtain decisions from the right people and issue a clear current basis. Technical and contractual questions need appropriate professional input. A coordinator should not resolve an apparent conflict by inventing a hierarchy or choosing the cheapest interpretation without authority.
Define the information set
Identify the documents that describe the relevant work and record their current revisions and purposes. Include schedules and details that bidders or suppliers need to interpret the specification. The coordination review should have a defined scope. A statement that the specification has been checked is difficult to understand if nobody can identify which related information was considered.
Keep the set aligned with the intended issue. A review based on an earlier plan can miss changes introduced in the current drawing package. Establish a controlled cut-off or other appropriate process for bringing information together. If a consequential document changes afterwards, assess whether the affected parts need another review.
Give requirements stable references
Use a consistent structure so users can connect an element on a drawing to its specification and schedule. The actual conventions should follow the project’s agreed information requirements. Avoid relying on informal product names that vary between disciplines. A stable reference makes queries and revisions more precise and helps the team locate the requirement being discussed.
Check that references resolve to the correct current content. A copied drawing note can point to a clause no longer present or a product type that has been renamed. These administrative details can create real ambiguity. Include them in the coordination process without confusing a reference check with technical assessment of the clause itself.
Examine repeated requirements
Identify where the same subject appears in several places. Repetition may be necessary for clarity, but it creates a maintenance responsibility when one version changes. Ask whether a controlled reference would work better under the project’s documents. The team should avoid casually deleting content without understanding its purpose or contractual treatment.
Where repeated requirements remain, compare their meaning and scope. Similar wording can hide a significant difference in location, performance or responsibility. The responsible designers should resolve the technical question, with commercial or legal advice where appropriate. Record the accepted outcome and update every affected source rather than closing the query after correcting only one clause.
Review package boundaries
Ask who designs, supplies, installs and verifies the work at significant interfaces. Separate specifications can each state by others while leaving the combined task unallocated. Bring the relevant package leads together around the actual interface. The purpose is a complete agreed scope, not merely a clean document for each individual organisation.
Consider a hypothetical fit-out where a wall-mounted item appears in the furniture schedule while the supporting provision is absent from the partition package. The products may each be fully described, yet the interface remains unresolved. A scope review identifies the missing contribution and routes it through the actual appointments and procurement documents.
Separate performance requirements from examples
Make clear whether a named product is mandatory, a reference example or part of an accepted proposal, according to the project’s arrangements. Ambiguous wording can lead bidders to price different assumptions about alternatives. The procurement and design teams should establish the permitted approach and the evidence required for review.
Where an alternative is proposed, assess the complete requirement and interfaces through the appropriate specialists. A general equivalent label does not explain which criteria have been considered. Keep the assessment associated with the accepted reference so later teams can distinguish the final selection from an option discussed during tender.
Check assumptions about existing work
Refurbishment specifications may rely on conditions described in surveys or existing records. Identify the relevant source and its limitations. Ask the responsible specialists what needs verification before the requirement can be finalised. A standard clause copied from another project can imply knowledge of the existing building that the team does not actually have.
Record unresolved assumptions and their decision dates. If the information will remain incomplete at tender, obtain appropriate advice on its treatment. The project should understand the resulting uncertainty rather than let a confident specification hide it. Clear assumptions help bidders ask useful questions and give the client a more realistic basis for commitment.
Use focused coordination reviews
Choose consequential interfaces and recurring problem areas for a structured review. Ask participants to bring the relevant documents and identify the decisions needed. A meeting that simply invites general comments can produce many observations without resolving the package. Focused questions make ownership and required evidence easier to establish.
Record issues with exact references, a clear description and an owner. State what response will close them and when the issued package needs the answer. A broad action to coordinate specification offers little help to the author. The review should create specific tasks that can be checked against the next information release.
Control tender clarifications
Questions from bidders can reveal conflicts that the pre-issue review missed. Use the project’s approved communication process and identify whether the answer explains or changes the requirement. If documents need revision, issue the accepted update through the appropriate route. Do not leave a substantive amendment solely in an informal message.
Keep the evaluation team informed of consequential changes and bidder qualifications. The comparison should reflect the actual basis offered, using the procurement rules applicable to the project. A clear clarification record helps establish which requirements bidders addressed and which departures still need review before award.
Reconcile the final accepted information
Before mobilisation, identify the specification and related documents forming the accepted scope through the actual contractual process. The delivery team needs a coherent current set rather than several tender versions and disconnected answers. Obtain the appropriate advice on incorporation and document relationships where required.
APM’s configuration-management overview provides general context for current versions and traceability. Applied here, the practical requirement is to keep accepted changes connected to the information people use. The project’s specific governance and contractual arrangements remain the basis for decisions.
Keep changes coordinated during construction
If a layout, system or product changes, identify the affected clauses and schedules as well as drawings. Assign responsibility for updates and confirm that the relevant parties receive them. A revised plan can create new contradictions if the supporting specification remains untouched. The coordination task continues after tender issue.
Preserve the decision history while making the current position clear. Record why a consequential requirement changed and what evidence supported the decision. This helps the handover team understand the installed selection and reduces reliance on personal recollection when a later question arises.
Use recurring conflicts as evidence
After the package, review which queries were repeated and why. The cause may concern copied clauses, unclear boundaries or late information rather than individual carelessness. Improve the reference material and review process accordingly. A useful lesson identifies the point where the conflict could have been resolved earlier.
Specification coordination succeeds when the project can connect a requirement to the work, its responsible parties and the current accepted information. That clarity supports better pricing, fewer ambiguous handovers and a more dependable record of what the client actually commissioned.
