Guides · · Sebastian Correa
Window schedule vs. elevations: reconciling the mismatch
When the schedule and the drawings disagree: which wins, how to log it, when to RFI.

The schedule usually wins on attributes: size, glass, finish and hardware. The elevations win on quantity, location and how units are mulled. The floor plan decides if an opening exists. When the conflict touches operation, handing or egress, or changes the price, send an RFI.
One rule sits above all of that. The project's general notes override any default order of precedence, including the one in this guide.
If you estimate windows and doors, you’ve run into this: the window schedule and the elevations don’t say the same thing. It doesn’t happen on every set, and it doesn’t happen on every sheet, but it happens often enough that trusting one document over the other out of habit will eventually get a wrong unit built.
It is a common enough complaint that a window and door salesperson once asked residential architects on Reddit "why do you bother making door and window schedules that never match the floor plans, or the elevations?" One architect answered that their office works in Revit, "so discrepancies are minimized" (r/Architects). Both are fair. Some sets are tight, and some drift. The estimator does not get to choose which kind arrives.
This piece walks through which document wins field by field, why the two documents drift apart, a field-by-field way to catch the mismatches before they turn into a price, what the specs and wall sections add, how to log each conflict, and the one-line RFI that settles it.
Which document wins, field by field?
This is the default order of precedence we use for fenestration. The reasoning behind it is in the section on resolving conflicts further down.
| Field | Usually wins | Why | Send an RFI? |
|---|---|---|---|
| Size | Schedule | It is the table written to specify the unit | Yes, if the gap is more than nominal or changes the price |
| Glass, finish, hardware | Schedule (check the specs too) | Attributes are what the schedule exists for | Yes, if the spec says something else |
| Quantity | Elevations | They are the drawing of the actual wall | Yes, if "typ." or mirrored units leave it unclear |
| Location and mulling | Elevations | Only the drawing shows how units sit and join | Yes, if the floor plan disagrees |
| Operation | Neither by default | It changes hardware, price and sometimes code | Always |
| Handing | Neither by default | A reversed hand is a remake | Always |
| Egress | Neither by default | It is a code question, not a drafting one | Always |
| Does the opening exist? | Floor plan | It shows where the walls and openings are | Yes, if the plan and elevations disagree |
Read the three "Always" rows as the expensive ones. The table settles the routine cases so you can spend your RFIs where a wrong guess costs the most.
Why the schedule and the elevations drift apart
The schedule and the elevations usually come out of the same office, sometimes even the same drafter, but they don’t get revised in the same pass. That’s where most of the mismatches start.
Revisions land on one sheet, not both. An architect changes a window arrangement on the elevation to fix a proportion, and the schedule row that used to describe it doesn’t get touched until two revisions later, if it ever does. It works in reverse too: someone resizes an opening on the schedule to hit an energy code minimum, and the elevation keeps showing the old proportions. Each revision is another chance for the two to split.
Then there’s the word “typ.” on a schedule line, which really means “go count them yourself.” If the elevation picked up one more instance of that unit in a later revision, the schedule quantity is wrong, and nothing on the page tells you so.
Mirrored floor plans cause a specific kind of trouble. Sometimes the schedule uses one mark to cover both a unit and its mirror image; sometimes it lists two marks where the elevations only bother to show one. Handing especially tends to survive in the drawing and disappear from the schedule.
And there are the late changes. Three days before the set goes out, someone swaps a casement for an awning window to clear space over a countertop, or bumps a door up two inches. Whatever document was open on screen at that moment gets updated. The other one ships as it was.
Two documents built to answer different questions, revised by different people at different points in the schedule, will drift apart. That’s normal, and catching where they’ve drifted, before it becomes a purchase order, is the estimator’s job.
How do "typ." marks and mirrored units break the count?
Here is a simple example of how the numbers split. It is made up, but every piece of it shows up on real sets.
The schedule lists W-03 with a quantity of 12 and a remark: "typ." The elevations show W-03 four times on the north face, four on the south, three on the east and three on the west.
4 + 4 + 3 + 3 = 14.
The schedule says 12. The drawings show 14. Most likely, a late revision added one W-03 to each side elevation and nobody updated the schedule row. The "typ." told you to count, and the count disagrees.
Mirrored units add a second trap. If the east wing is a mirror of the west wing, those three W-03 casements on each side are not identical units: their handing flips. A schedule with one row for W-03 hides that. The handing guide covers how to split mirrored units into one line per hand before you count.
In this example, the table above says the elevations win on quantity, so you price 14. You also send an RFI, because 2 units out of 12 changes the price. The RFI turns your count into the architect's answer.
How to detect the mismatches: a field-by-field checklist
Reconciliation works better as a specific pass, one field at a time, than as a vague “check for problems.” For every mark on the schedule, walk through these:
- Mark. Every mark on the schedule should show up somewhere on the elevations, and every tagged opening on the elevations should show up on the schedule. Anything orphaned on either side is worth a second look before you count it.
- Quantity. Actually count each mark across every elevation, mirrored ones included, and check that against the schedule’s stated quantity. Marks labeled “typ.” deserve extra suspicion here, since that’s exactly where quantities go stale.
- Size. Compare the schedule’s width and height to the dimensioned elevation. No dimension on the elevation? Check the floor plan opening instead. If an opening has no dimension anywhere on the set, don’t guess at it. Send the question to the architect.
- Operation. The dashed sight lines on the elevation should match the operation column on the schedule. Drawing a fixed unit with vent lines (or the reverse) is one of the costlier things to get wrong, because it changes hardware, price, and sometimes code compliance all at once.
- Handing. Check handing on casements, doors, and sliders against the elevation, and if the plan is mirrored, check it against the mirrored elevation specifically, not the base one you’d naturally look at first.
- Glazing. Tempered, obscure, insulated makeup, spandrel. The schedule usually carries this, but general notes or the elevations themselves sometimes override it near hazardous locations, so it’s worth checking both.
- Egress. Bedrooms and other required exits have minimum clear-opening rules. A scheduled size that looks tight for a sleeping room opening is worth flagging even when the schedule and elevation happen to agree, because they can both be wrong the same way.
Write every discrepancy down as you find it, with sheet references on both sides. A mismatch you can’t point to on paper is one you’ll end up re-finding next week.
What about the specs and the wall sections?
The schedule and the elevations are two sources. Most sets have at least two more, and they can veto both.
The specifications. A glazing contractor's reconciliation checklist treats the problem as three documents: "The window/door schedule, the elevations, and the Division 08 specification sections that govern glass, finish, operation, and performance." Its rule for open conflicts is blunt: "Do not release fabrication while size, glass type, finish, or performance conflicts remain open" (AC Glass).
The wall sections. A section shows the header, the rough opening depth and the edge conditions. One estimating guide puts it this way: the schedule is the source of truth for "what is being sold," and the wall section is the source of truth for "how it is installed" (EnergyCheck). A section that shows less rough opening depth than the scheduled frame needs means the unit does not fit as drawn.
Not every guide agrees with our default on quantity. That same guide argues the schedule should drive the quantity takeoff, and that every unit should tie to a schedule line. We weigh the elevations more for quantity, because they are the drawing of the actual wall and a "typ." quantity on a schedule can go stale. Both approaches end in the same place: a unit that does not tie to a schedule line, or a schedule line with no unit, is a conflict to log and ask about. Neither guide says to guess.
Resolving conflicts before the shop floor
Once you’ve got the list, you need a rule for which document wins. A workable order of precedence for fenestration looks something like this:
- The schedule wins on attributes. Size, glazing makeup, finish, hardware: that’s what the document was written to specify, so when it disagrees with a rough elevation on these, trust the schedule.
- The elevations win on quantity, location, and configuration. How many units, where they sit, how they’re grouped or mulled together: that’s what the drawing of the actual building shows, and a table can’t out-argue a drawing of the wall it’s describing.
- The floor plan settles disputes about whether an opening exists at all, or where exactly the rough opening sits.
That order handles the routine cases. It doesn’t give you license to resolve the expensive ones on your own. Send an RFI instead whenever the conflict touches operation, handing, or egress; when the two documents disagree by more than a nominal amount; when either answer meaningfully changes the price; or when the project’s own general notes spell out a different precedence order than the one above, since the contract documents always override any default rule like this one.
An RFI costs you a day to answer. Guessing wrong costs you a remake, and a remake costs a lot more than a day.
How do you log mismatches? A discrepancy register
A list of conflicts in someone's notebook does not survive a revision. A discrepancy register does.
One audit guide recommends one row per opening, compared across the current plans, elevations, details and schedule, with every mismatch recorded "with its source sheet, revision, decision owner and status." It also makes a point worth keeping: "The audit identifies conflicts; it does not decide which dimension or notation is correct" (Meruzy).
A register for windows needs seven columns. The first four describe the conflict:
| Mark | Sheet A says | Sheet B says | Revision |
|---|---|---|---|
| W-03 | Schedule A-601: qty 12, "typ." | Elevations A-201/A-202: 14 shown | Rev 2 on both |
| D-04 | Schedule A-601: 3'-0" x 7'-0" | Floor plan A-101: 2'-8" opening | Rev 1 / Rev 2 |
The other three track it: decision, who decides, and status (open, asked, answered, priced).
Write each line as an observable difference between two sheets, never as your answer. "W-03 shown 14 times on the elevations, schedule says 12" is a fact. "W-03 should be 14" is a guess until the architect confirms it.
What does a one-line RFI for a window conflict look like?
Keep it to three lines. The architect should be able to answer it in one word or one number.
- Reference: "W-03. Schedule A-601 (Rev 2) lists quantity 12. Elevations A-201 and A-202 (Rev 2) show 14."
- Question: "Please confirm the quantity of W-03."
- What happens until you answer: "Our quote carries 14 and notes the discrepancy."
The third line matters. It tells the buyer what you priced, so nobody finds out at delivery. It also follows the order of precedence above, which keeps your quote consistent with your own rule.
What changes when an addendum lands?
An addendum revises sheets, and it rarely revises all of them at once. A revised elevation paired with an unrevised schedule is exactly how the drift in this guide starts.
When an addendum arrives, read the clouds and the revision block first. The guide to reading revision clouds covers what a cloud promises and what it does not. Then update only the units that changed, re-check those marks against the other documents, and add a register row for each new conflict. Handling revisions without recounting walks through that workflow.
What a remake actually costs
It’s tempting to skip all of this when the bid is due Friday. But think about what one wrong unit actually costs once it’s already built: the material and labor for the original piece, the same again for the replacement, freight in both directions, whatever crane or crew time sits idle at the site waiting on the new unit, and the slot in your own shop’s schedule you have to bump something else to make room for. Catch the mismatch at takeoff and the fix is a line in an RFI. Miss it, and you find out at installation, when it’s suddenly the most expensive window on the job, with your company’s name on the delivery ticket that has to make a return trip.
For the full list of fields every unit needs before it is priced, see the fenestration takeoff checklist.
FAQ
Does the window schedule override the elevations?
On attributes, usually yes: size, glass, finish and hardware. On quantity, location and how units are mulled, the elevations usually win. The project's general notes and contract documents override any default rule, so read them first. When the conflict touches operation, handing or egress, send an RFI.
Who decides when the plans conflict?
The architect or the design team responsible for the documents. The estimator's job is to find the conflict, log it with sheet references, and ask. Your quote can state what you priced until the answer arrives.
Should I price the schedule quantity or my own count?
Price your count from the elevations, note the schedule quantity next to it, and send an RFI when the two disagree. If the difference changes the price, say in the quote which number you used.
Wondering what this means for your team? Get your numbers in a 60-second fit check.