What We've Learned From Being on the Receiving End of Door Schedules

We don't write door schedules. Contractors and architects do. But we're usually the ones who find out when something in one doesn't quite add up.

A schedule arrives, we start working through it against a hardware list or a fire strategy note, and somewhere in there is a door number that doesn't match anything, or a rating that doesn't line up with what the room next to it needs. That's not a criticism of anyone's process. It's just what happens on real projects, and it's taught us a fair amount about what to look for before we ever start manufacturing.

The Same Door Number Rarely Means the Same Thing Twice

If there's one thing that trips people up more than anything else, it's a door number that got reused, dropped, or renumbered somewhere between one design revision and the next.

It sounds like a small clerical thing. It isn't. We've had cases where door 214 on the schedule we received didn't match door 214 on the hardware list, because one had been updated after a late layout change and the other hadn't. Nobody did anything wrong exactly, the update just didn't reach both documents at the same time.

Now we cross-check numbering against whatever supporting documents we're given before committing anything to production. It adds a step. It also means we're not the ones manufacturing forty doors against a specification that quietly stopped being accurate three revisions ago.

Fire and Acoustic Ratings Are Where We Get the Most Questions

Ask us what part of a schedule generates the most back-and-forth with a project team, and it's almost always the rating column. Not because the numbers are wrong most of the time, but because the schedule alone doesn't always tell us why a particular door needs the rating it's assigned.

That context matters more than people expect. A rating that looks unusually high for a corridor door sometimes turns out to be correct, because of something specific in the fire strategy we wouldn't know just from looking at the schedule. Other times, it turns out to be a leftover from an earlier version of the layout that's since changed.

We've started asking directly rather than assuming either way. It's a two-minute conversation that's saved more than a few projects from manufacturing something that would've needed reworking later.

Big Orders Reveal Problems Small Ones Never Would

A ten-door schedule is easy to sanity-check by eye. A four-hundred-door schedule across a multi-building development is a different animal entirely, and it's where we've seen the most inconsistency slip through unnoticed.

Usually it's something like a hardware type specified one way for towers A and B, and slightly differently for tower C, with no note explaining whether that's intentional or an oversight. On paper, both versions are technically valid. Installed next to each other across a development, the difference is exactly the kind of thing that gets noticed and questioned during handover.

We've gotten more insistent about flagging these inconsistencies back to the project team before manufacturing, even when they might be intentional, because guessing wrong in either direction creates a problem, either producing something the project didn't actually want or holding up an order waiting on a clarification that could've happened weeks earlier.

What We Actually Do With a Schedule Once We Receive It

It's not glamorous, but it works. Every schedule we receive gets checked against door numbering, hardware references, and any fire or acoustic documentation we've been given, before it becomes a production order. Anything that doesn't line up gets flagged back to the project team as a question, not silently assumed one way or the other.

We also keep a version record on our side. If a revised schedule comes in later, we can see exactly what changed from the version we last worked against, rather than trying to compare two documents by memory or eye.

None of this prevents every issue. Schedules are complicated documents managed by busy people across multiple firms, and something will occasionally slip through anyway. But it's meant fewer surprises during manufacturing, and fewer awkward conversations after doors have already shipped.

Questions We Hear Often About This

Do you flag every inconsistency you find, even small ones? Generally yes, especially on larger orders. A small inconsistency on a ten-door project is easy to resolve verbally. The same kind of thing on a four-hundred-door order is worth confirming in writing before we manufacture against it.

What happens if a revised schedule arrives after we've already started production? We compare it against the version we're working from and confirm with the project team exactly what's changed before adjusting anything already in progress.

Can you help reconcile a door schedule against a separate hardware schedule before we finalize either? Yes, and it's usually easier to do that before both are locked in rather than after, since discrepancies are simpler to resolve while everything's still in draft.

Is this kind of check something you only do for large developments? No, we apply the same numbering and cross-reference check regardless of project size, though the volume of issues we tend to catch is naturally higher on larger, multi-building orders.

The Honest Take

A door schedule is only as reliable as the coordination behind it, and coordination between multiple firms on a live project is never perfect. We've stopped expecting a flawless schedule and started building a process that catches the gaps before they turn into a manufacturing mistake.

If you're working through a schedule for an upcoming project and want a second set of eyes on it before things get locked in, we're glad to take a look.