Frame Type Conflicts Between Door Schedules and Elevation Drawings and How to Catch Them Before Bid Day

Frame type conflicts are caught before bid day by reconciling each opening across the floor plan, door schedule, elevations, partition schedule, and Division 08 specifications simultaneously. The check must compare construction method, throat depth, pair status, rated assembly conditions, and hardware assignments, then record discrepancies in an RFI register. An opening count alone cannot show that the frame being priced matches the opening in the drawing.

Why frame type is the most conflict-prone field in a Division 8 document set

The frame type column is a reference. Its code points to a frame elevation or type detail, typically on or near the schedule sheet, that establishes what the opening requires. Welded or knocked down, masonry or drywall, and single or double rabbet describe distinct products. Substituting one in the field requires a change order.

The partition schedule adds another dependency to that reference. Stud information determines the required jamb depth, or throat size, so a frame designation must agree with the wall construction as well as the elevation. Hardware and fire-rating requirements further constrain the assembly. Frame type sits at the intersection of these documents because it must reconcile the opening’s drawn shape, its wall, and its specified performance.

How the structure of a construction document set makes frame type conflicts predictable

Construction documents distribute an opening’s requirements across sheets authored at different times by different disciplines. That structure makes discrepancies predictable without implying carelessness by the designers. A pair illustrates the problem directly. The elevation shows two leaves, while the schedule may not flag the opening as a pair. Reading that schedule alone can leave half the opening’s hardware out of the estimate.

P2C Construction Services describes a full check of floor plan tags against architectural door schedules and elevation details, with missing openings and frame size conflicts recorded in an RFI register. Its required document set also includes partition schedules for throat depths and Division 08 specifications. Each document supplies a different constraint on the opening. Omitting one leaves a category of conflict outside the review.

The schedule records the required assembly rating, while the elevation depicts sidelights, transoms, vision panels, and the physical frame condition. Added glazing or a changed profile can make the depicted assembly incompatible with the scheduled rating. The discrepancy appears when the required performance is compared with the drawn construction.

The four specific places where door schedules and elevation drawings most often disagree on frame type

The first check compares the construction method, whether welded or knocked down. A schedule code may point to welded construction while the elevation shows a narrow sidelight or unusual profile that needs knocked-down field assembly, or the reverse. The drawn condition must support the coded product. These alternatives have different prices and lead times. A welded frame ordered for a KD application cannot simply be field-converted and must instead be returned and replaced.

Throat depth is the second comparison, and it requires the partition schedule as well as the opening documents. The door schedule may specify a throat based on one wall condition while the partition schedule shows a different stud depth for that wall. The frame then does not fit the wall being built. The appropriate point to resolve that mismatch is before concrete is poured and frames are ordered, while correction remains a markup and before it requires a field modification.

Pair status and frame profile form the third comparison. An elevation may show two leaves while the schedule describes one or provides no pair indicator. That discrepancy calls the assigned profile, astragal provision, and coordinator prep into question. A single-rabbet or double-rabbet designation specified for the wrong condition produces a product mismatch.

Rated assembly compatibility is the fourth comparison. Fire door assemblies require matching labels for the leaf, frame, glazing, and hardware components consistent with the required rating, while smoke doors require “S” seals. A vision panel, sidelight, or transom changes the glazing and frame requirements. If the schedule predates that elevation condition, the documents can describe incompatible assemblies. A non-rated or incorrectly specified frame in a rated opening is a code violation and liability.

Why hardware set conflicts compound frame type errors and must be checked in the same pass

When the physical opening differs from the scheduled condition, its assigned hardware set may no longer serve that opening. A pair, rated opening, or special profile cannot be evaluated independently of its hardware requirements. Door usage also affects the assignment. The efficient review therefore compares the door and hardware schedules together rather than postponing hardware until the frame review is complete.

A hardware group number in the door schedule can differ from the number assigned to the same opening in Section 08 71 00. Both values must be surfaced so that the governing requirement can be determined. The schedule may reference a set number that does not appear anywhere in the hardware specification, leaving the opening counted but its hardware absent from the bid. Quantity reconciliation will not expose that omission because the count itself is correct.

What a systematic pre-bid frame type check actually looks like, document by document

The estimator should first establish that the complete document set is available. The required material includes floor plans, door schedule tables, elevation details, partition schedules, and Division 08 specification sections. A missing document prevents completion of the reconciliation. That gap should become an RFI before bid day, rather than an assumption about what the unavailable document would require.

The next step is to match every floor plan door tag to exactly one schedule entry. A plan tag without a schedule row identifies an opening that needs pricing but lacks the scheduled specification. Each unmatched tag should be logged immediately. This matching step precedes the elevation review because an opening without a schedule entry lacks the frame type reference needed for that comparison.

For each matched row, the estimator should then locate the referenced elevation and compare single or pair status, sidelights, transoms, vision panels, and the implied frame profile. A drawn condition absent from the scheduled frame type is a conflict. The record should identify the governing document where that is established or request architect clarification where it is not. Throat depth should then be checked against the partition schedule’s stud information to see whether the specified frame fits the wall as designed.

Hardware assignments follow that physical reconciliation within the same review pass. Every set number in the schedule must have a corresponding set in Section 08 71 00, and any frame discrepancy that changes the hardware requirement must be flagged. P2C logs fire labels and hardware set conflicts while confirming scope, before the takeoff quantities are final. Conflict logging is therefore an input to pricing. It is not a cleanup exercise after the quantities are settled.

The final check addresses every scheduled fire- or smoke-rated opening. Its depicted profile, glazing condition, and hardware set must be consistent with the required rating, including any elevation change that adds glazing without a corresponding label change. Those conflicts require resolution before the bid. The workflow’s output is an RFI register documenting each discrepancy, the document treated as governing, and the items still requiring architect clarification before the number is submitted.

Where institutional and owner-standard jobs make frame type conflicts harder to catch

The governing requirement may sit in an owner standard rather than the project specification, so the estimator must locate and read that standard before opening the door schedule. Some owner standards list hardware sets without finishes or describe their components in ways that are unclear. Others provide no numbered sets at all. In those cases, each opening’s usage must be matched to the appropriate component row.

Michigan State University’s project documentation for CP25028 and CP25054, both 2025–2026, directs the constructor to comply with MSU technical standards and standard details for materials and methods not specified within the project documents. The project specification is therefore not sufficient by itself. That requirement establishes a broader starting set of documents. It does not mean every owner applies the same standards or document hierarchy.

In Section 1/Division 08/Door Hardware (08 71 00), Cooper University Hospital’s Construction Project Design Standards add specifications for emergency release hardware and requirements for medical-grade door stop, and require full glass lites for medication room doors. These owner requirements introduce conditions that a project-specification-only review would not flag. The glass requirement also brings the opening’s glazing and rated assembly compatibility into the reconciliation.

Eastern Michigan University Construction Standards require a complete door and hardware schedule to be developed during design and submitted for review and approval before final construction documents are completed. The required reviewers are the EMU Project Manager and the EMU Lockshop. For the estimator, that reinforces the need to reconcile the project documents with the owner’s requirements rather than treat the schedule as a self-contained final instruction.

Why reading documents one at a time is the process failure that makes conflicts invisible until it is too late

The sequence establishes which relationship to check next, while the actual comparison requires the same opening’s information to be considered together. Reading the schedule, then the elevations, then the specification in isolation separates the requirements that expose the conflict. The weakness is that the estimator then has to remember a discrepancy while moving between documents.

Time pressure makes that weakness more consequential on complex jobs. A full day spent reconciling hardware sets against the schedule leaves less time for the elevation and partition checks. One review can displace another before bid day. Because those documents cover different conditions, checking the hardware cannot make up for skipping the throat-depth check.

Discovery after award also changes the consequence of the error. Custom frames, specialty glazing, and electrified hardware have lead times that can turn a missed conflict into a project schedule problem. When a misread set is found during bid review, it affects the bid amount. The same discrepancy found at submittal requires correction against a live construction schedule, and a frame type error may not be field-correctable within that timeline. Doors, frames, and hardware therefore need to be estimated as one system rather than separate scopes extracted from separate documents.

How can estimators reconcile door schedules with floor plans and specs simultaneously?

Simultaneous reconciliation compares each opening across the floor plan, schedule, elevations, partition schedule, and hardware specification in one review context. Its useful output is a count plus a conflict list. That distinction provides a concrete test for AI-assisted software. It must be able to cross-reference Division 8 document types as well as extract opening quantities or attach hardware prices.

When a tool prices counted openings without checking the hardware specification against the schedule, the estimator still has to check the sets by hand. The required comparisons include missing or conflicting set assignments, items marked out of scope, KD versus welded construction, frame profiles, and throat depths. Software helps when it shows those contradictions to the estimator without making them switch back and forth between separate documents.

Electrified hardware scope can involve whether a power supply belongs in Division 8 or Division 26 and whether a reader is owner-furnished and contractor-installed. These questions span four divisions and take institutional knowledge beyond what can be extracted from the documents. Pairs, rated openings, and special conditions also require closer human review, while early engagement with hardware manufacturers and consultants and the pre-installation coordination meeting remain essential safeguards against differences between documents and construction.

The estimator’s final responsibility is to turn the conflict list into a defensible bid. That requires recording unresolved requirements, identifying the governing basis used for pricing, and obtaining clarification rather than silently choosing between contradictory documents. Simultaneous reading supports that work but does not replace judgment. A conflict log backs the bid number and can protect scope when a change order is needed after award.