Compare Plans Across Trades and Identify Conflicts

A. Finished-Package Specification

Deliverable set: one coordination matrix identifying every discipline-pair comparison required; one set of documented cross-discipline comparison findings with exact locations and source references; one conflict register with a unique identifier, classification, and full references for every issue found; and one RFI-style question list routed through the approved review and document-control process.

B. Deliverable Schedule (Component Schedule)

Component	Quantity	Source	Required Fields	Preparation / Purpose
Coordination matrix	1	Chapters 1–16 deliverables and current sheet register	Building area or system, sheets to compare, document types, comparison status	Defines the scope of every comparison performed in this chapter
Cross-discipline comparison findings	1 set	Direct comparison of current approved documents	Location, disciplines compared, observation, source references	Raw documented record of every match and mismatch found
Conflict register	1	Findings classified as conflicts, missing information, or ambiguity	Unique ID, location, description, source documents, revision, affected trades, consequence, required-by date, status	Controlled record used to route issues through document control
RFI-style question list	1	Conflict register entries requiring designer or owner clarification	Question text, references, field impact, required-by date, response, affected documents, downstream impacts	Neutral clarification requests ready for the approved review process

C. Source Material Takeoff

• Primary source: the current approved architectural, structural, civil, plumbing, mechanical, electrical, specialty, schedule, detail, and specification documents for the project, and the approved submittals affecting them.
• Supporting source: every deliverable produced in Chapters 1 through 16 for this project, including the sheet register, navigation map, and every discipline checklist.
• Reference tools: one straightedge, one engineer's or architect's scale, a consistent set of markup colors, and an overlay or digital comparison method if available.
• Recording medium: one coordination matrix template, one conflict-log template, and one RFI-log template capable of holding all fields listed in Section B.

D. Acceptance Standards

Check	Standard
Matrix completeness	Every building area or system named in the coordination matrix has a recorded comparison status of complete, in progress, or not applicable with a stated reason
Revision currency	Every document used in a comparison is confirmed as the current approved revision before the comparison is recorded
Conflict traceability	Every conflict register entry has a unique identifier, exact location, and complete source references for every document involved
Classification accuracy	Every entry is classified as missing information, direct conflict, coordination conflict, constructability concern, field discrepancy, scope ambiguity, or potential change
RFI neutrality	Every RFI-style question states the conflict and requested information without proposing an unauthorized design as the only acceptable answer
Closure control	No conflict register entry is marked closed until an approved response has been incorporated into the active field documents and checklists

E. Preparation — Confirm Documents and Build the Coordination Matrix

1. Confirm the current approved revision of every architectural, structural, civil, plumbing, mechanical, electrical, specialty, schedule, detail, specification, and approved submittal used. Check each against the Chapter 1 sheet register and revision summary before proceeding.
2. Create a coordination matrix listing the sheets and document types that must be compared for each building area. Organize the matrix by room, zone, or system so no area is left uncompared.
3. Select a consistent room-by-room, grid-by-grid, or system-by-system coordination route. Record the selected route on the Project and Document Identity Record and follow it without switching methods mid-chapter.

F. Architectural and Structural Coordination

1. Overlay or compare architectural and structural plans at a verified common scale or digital alignment. Confirm the alignment method before recording any finding.
2. Check grids, exterior dimensions, bearing walls, columns, beams, headers, openings, stairs, floor levels, roof geometry, and foundation supports. Work through the coordination matrix systematically rather than spot-checking.
3. Record every mismatch by exact location and source references. Cite the sheet number, detail number, and revision for every document involved in each mismatch.
4. Compare foundation penetrations, slab recesses, equipment pads, drains, and utilities with structural and architectural information. Note any penetration shown on one discipline's plan but absent from another's.

G. Systems Coordination

1. Compare plumbing fixtures and pipe routes with joists, beams, trusses, shear walls, footings, cabinets, ceilings, and access panels. Flag any route crossing a structural member without a documented penetration detail.
2. Compare HVAC equipment and ducts with framing, ceiling heights, soffits, roof penetrations, access, and service clearances. Confirm stated ceiling heights accommodate the documented duct and equipment dimensions.
3. Compare electrical panels, devices, fixtures, and controls with cabinets, mirrors, doors, windows, plumbing, structure, ceilings, and equipment. Identify devices that fall behind cabinetry, appliances, or other obstructions as documented.
4. Compare reflected ceiling plans with lighting, registers, fans, sprinklers, alarms, beams, soffits, access panels, and finish patterns. Identify overlapping or conflicting ceiling-mounted elements at the same location.
5. Compare cabinet and appliance drawings with electrical, plumbing, HVAC, wall backing, openings, and clearances. Confirm required utility connections fall within the documented cabinet or appliance envelope.

H. Envelope and Finish Coordination

1. Compare door and window schedules with plans, elevations, structural openings, flashing details, hardware, and finish thicknesses. Confirm rough-opening sources are consistent across all referencing documents.
2. Compare roof plans with structural framing, plumbing vents, HVAC exhausts, electrical equipment, solar or specialty components, and drainage. Identify penetrations shown on one discipline's roof information but missing from another's.
3. Compare exterior elevations with wall types, openings, MEP penetrations, grade, roof geometry, and material limits. Confirm elevation heights are consistent with the building and wall sections.
4. Compare wall sections and envelope details with structural support, opening products, roof transitions, and specifications. Identify any assembly layer named in one document but absent from a related detail.
5. Compare room finish schedules with plans, interior elevations, flooring transitions, cabinets, fixtures, and ceiling information. Confirm finish transitions are documented at every location where materials change.

I. Notes, Specifications, and Submittal Coordination

1. Compare general notes and specifications with discipline-specific details and schedules. Use the Chapter 16 specification summary as the comparison baseline.
2. Identify missing overall dimensions, incomplete dimension chains, ambiguous reference points, and field-verification notes without defined responsibility. Record each as missing information rather than estimating a value.
3. Identify broken detail references, unmatched tags, undefined abbreviations, inconsistent room names, and missing schedule entries. Cross-check against the Chapter 1 reference map.
4. Identify conflicts between approved submittals and construction drawings. Confirm the submittal's approval status and date before recording a conflict against it.
5. Identify code, permit, inspection, manufacturer, and delegated-design information requiring confirmation. Record the specific citation or requirement and the document in which it appears.

J. Conflict Register Construction

1. Classify each issue as missing information, direct conflict, coordination conflict, constructability concern, field discrepancy, scope ambiguity, or potential change. Use the classification key from the Reference Conventions table.
2. Assign a unique conflict number and record location, description, source documents, revision, affected trades, consequence, and required-by date. Populate one complete row per issue in the conflict-log template.
3. Attach clear annotated excerpts or overlays where authorized. Preserve original linework and text in any attached excerpt.
4. Do not solve a structural, life-safety, system, accessibility, waterproofing, or design conflict through an undocumented field choice. Record the issue and its consequence instead of a proposed fix.

K. RFI Drafting and Routing

1. Draft one neutral RFI-style question for each issue or logically related group. State the document references, the conflict or missing information, and the field impact.
2. State what information is needed rather than directing the designer toward an unapproved answer. Review each draft question to confirm it does not embed a preferred solution.
3. Identify work that must stop, may proceed elsewhere, or requires temporary protection pending response. Record this determination on the conflict register entry.
4. Route the conflict list through the approved review and document-control process. Submit the RFI-style question list using the project's stated procedure.
5. Update the register with responses, approvals, affected documents, and downstream impacts. Record the responder, date, and every document the response affects.
6. Close an item only after the approved response has been incorporated into active field documents and checklists. Do not mark an item closed based on a verbal or informal answer.