Drawings vs. Specs: A Pre-Issue Coordination Review

The set looks complete. The drawings are clean, the schedules are filled in, and the spec sections are attached. Then the bids come back with qualifications, or the framing crew calls with a question on day three. Somewhere in the package, the documents disagreed with each other.

This is one of the most common sources of field cost and pricing confusion: not missing information, but conflicting information. Plan notes say one thing. The finish schedule says another. The written spec says a third. Bidders price to the interpretation that protects them. Field crews ask questions that should have been answered before the set left the office.

A short coordination review before issue will not catch everything, but it will catch most of the contradictions that create problems at bid and in the field.

Why Conflicts Happen

Drawing sets are built in layers. Plan notes get added during design. Schedules get updated during documentation. Spec sections get attached or modified late. Each layer is usually managed by a different person, at a different time, sometimes in a different file.

The result is that the same item — a floor finish, a door hardware set, a ceiling height — can appear in three or four places in the set, and those places do not always agree.

No one intends the conflict. It is a coordination problem, not a competence problem. The fix is a structured comparison pass before the set goes out.

The Four Layers to Compare

Most conflicts in a drawing set live in the gaps between these four document layers:

Plan notes and keynotes. What is called out directly on the floor plans, elevations, and detail sheets. These are often the most current edits because they are easy to change in the drawing file.

Room finish schedules. The tabular record of floors, bases, walls, and ceilings by room. These are often updated less frequently than plan notes and can fall behind.

Material and finish legends. The graphic or coded key that ties finish abbreviations to actual products or specifications. If the legend is not current, every room that references it inherits the error.

Written specifications. The narrative sections that describe products, installation standards, and performance requirements. These are often the last thing updated and the first thing that conflicts with a late drawing change.

A fast coordination review compares these four layers against each other for the same items. It does not require reading every word of every spec section. It requires a targeted pass on the items most likely to conflict.

A Practical Pre-Issue Review Method

This review works best as a short checklist pass done after the drawing set is assembled but before it is issued for bid or permit.

Step one: Pull the finish schedule and open the floor plans side by side. For each room in the schedule, confirm that the floor, base, wall, and ceiling calls match what is noted on the plan. Look for rooms where the plan note was updated but the schedule was not, or where the schedule has a finish that no longer appears in the legend.

Step two: Check the finish legend against the spec sections. For each finish code in the legend, confirm that a corresponding spec section or product description exists. Flag any finish code that points to a product or standard that has been changed or removed.

Step three: Compare keynote callouts to the written specs. For any keynoted item that has a corresponding spec section, confirm that the keynote description and the spec description are consistent. Pay particular attention to items that were revised late in the documentation phase.

Step four: Check door, hardware, and fixture schedules against plan callouts. Schedules for doors, hardware sets, plumbing fixtures, and light fixtures are common conflict zones. Confirm that the schedule entries match the plan callouts and that both match the spec sections.

Step five: Flag conflicts, do not just note them. A conflict list that does not get resolved before issue is not useful. Each flagged item should have a clear resolution before the set goes out: which document controls, what the correct information is, and which other documents need to be updated to match.

What This Looks Like in Practice

Here is a typical example of how a conflict develops and where the review catches it.

A floor finish gets substituted late in the design phase. The designer updates the plan note and the keynote sheet. The room finish schedule does not get updated because it lives in a separate file. The written spec still references the original product.

When the set goes out, the plan says one finish, the schedule says another, and the spec describes a third. A flooring subcontractor pricing the job qualifies their number against the spec. The GC assumes the plan note controls. The owner expects what was shown in the design presentation. The discrepancy surfaces as an RFI on day one of flooring installation.

A step-two and step-three pass in the pre-issue review would have caught this in about ten minutes.

The Common Mistakes This Catches

Most pre-issue conflicts fall into a short list of recurring patterns:

• A finish was substituted late in design but only updated on the plan, not in the schedule or spec
• A room was renumbered or renamed and the schedule was not updated to match
• A hardware set was revised but the door schedule still references the old set number
• A spec section was carried over from a previous project and references products or standards that do not apply
• A keynote was added to the drawings but no corresponding spec section was written

None of these are unusual. They show up regularly in sets that were otherwise carefully produced. The issue is not carelessness. It is that drawing sets are assembled across time, and the coordination pass is the step that closes the gaps.

Before the Set Goes Out

The goal of this review is not a perfect set. It is a set where the documents agree with each other on the items that matter most for pricing and field execution.

Bidders who find conflicts will price for uncertainty. Field crews who find conflicts will generate RFIs. Both outcomes add time and cost that a short coordination pass could have prevented.

For remodelers and builder-side teams who regularly receive design packages, this kind of pre-issue review is also a useful lens for evaluating sets before accepting them into the bid process. A set with obvious internal conflicts is a set that will generate questions.

For design studios that want a more consistent production process, building this review into the standard issue checklist is one of the lower-effort improvements with a clear return. Creo's contractor production support is structured around exactly this kind of documentation coordination — helping teams catch the gaps before they become field problems.