How to Build a Door Schedule from CAD Blocks

A door schedule is where downloaded blocks earn their keep or get you in trouble

Downloading a door block and dropping it into a plan is the easy half of the job, the door schedule is where all those individual insertions get turned into something a contractor can actually build from, a table listing every door by mark, size, mechanism, material, and hardware note, cross referenced back to the plan by a tag number at each opening. I've seen plenty of plans where the blocks are placed perfectly and the schedule is an afterthought, thrown together at the end from memory rather than pulled directly off what's actually in the drawing, and that's exactly where mismatches creep in, a door swapped on plan during a late revision that never made it back into the schedule row.

Setting up tags before you build the table

Before building the schedule itself, every door opening on the plan needs a tag, usually a small circle or hexagon with a mark number or letter inside it, placed near the opening, and the convention worth adopting early is numbering by floor and sequence, D101, D102 and so on, rather than a flat sequential list across the whole building, because it keeps the numbering meaningful even as the plan grows. AutoCAD's field and table tools can pull door counts and even some block attributes automatically if the blocks carry attribute data, but a huge share of downloaded blocks, including most free libraries, don't ship with attributes built in, so realistically you are tagging manually and building the schedule as a standard table, which is completely fine and still the normal workflow for a huge share of practicing drafters.

Consistency in tag placement matters more than people expect too, keep the tag on the same side of every door symbol, say always just inside the hinge point, rather than wherever there happens to be blank space on that particular sheet, because a reviewer scanning a busy plan for tags relies on that predictability to find them quickly. It sounds like a small thing until you're the one hunting for a tag that got tucked behind a furniture block on one specific door out of forty.

What each schedule row actually needs to carry

At minimum a usable door schedule row needs the mark number, width and height, the mechanism, swing, double acting, sliding, pocket, or bifold, the material or construction type, laminated, wood panel, glazed, the swing hand where applicable, left or right, and a fire rating column even if most rows just say none, because a blank cell reads as an oversight during review while an explicit none reads as a checked and confirmed entry.

For instance a row built off the 1000 mm laminated door block on this site would read something like D101, 1000 x 2100, single acting swing, laminated flush, left hand, none, and a row off the double acting door block would swap the mechanism and hardware columns to double acting, spring hinge, not applicable for swing hand since it opens both ways.

A remarks or notes column is worth adding too, even if most rows leave it blank, since it's the natural home for anything that doesn't fit cleanly into the standard columns, a note that a specific door needs to be rated for sound transmission, or that a particular opening requires an automatic operator, or that a supplier substitution was approved for one specific unit. Trying to cram that kind of detail into the material or hardware column instead just makes those columns inconsistent across the sheet.

Keeping the schedule and the plan honest with each other

The failure mode to actually guard against is drift, the plan gets revised, a door gets resized or its mechanism changes from swing to pocket, and the schedule row doesn't get updated to match, so at the end of every revision pass I do a straight count check, count the door tags on the plan, count the rows in the schedule, and if those two numbers don't match something's been added or removed on one side without the other. It's a blunt check but it catches the most common error fast, and it takes a couple of minutes on even a large residential plan.

Beyond the count check, it's worth spot checking a handful of rows against the plan directly at the end of every issue, picking maybe five doors at random and tracing them from tag to schedule row to actual block geometry, confirming the mechanism noted in the schedule actually matches the arcs drawn at that opening. A pure count match tells you nothing got added or removed, but it won't catch a door that was resized on plan without the schedule row being updated to match, which is exactly the kind of drift a spot check does catch.

Grouping blocks by type speeds up the whole process

One workflow habit that saves real time, group your downloaded blocks by mechanism and material before you start placing them rather than searching fresh each time you need one, so your project's block palette might hold the 1000 mm laminated door and 1200 mm dd laminated door for standard interior swings, the double acting door and 1000 mm wide dd double acting for pass through conditions, and the double panle bs swing vestibule door or french double door for entrance and feature openings, all pre staged and ready to drop in. When the schedule's built at the end, you are working from a small known set of block types rather than reverse engineering what each individual insertion actually is, which is a surprisingly common problem on plans that have been through several drafters.

Handling revisions and hardware groups without losing track

On a project that goes through several revision cycles, and most do, it helps to add one more column to the schedule that a lot of drafters skip, a hardware group or set number rather than spelling out every hinge and lockset detail on every single row. Group doors that share identical hardware, same hinge type, same lockset, same closer if applicable, under a single hardware set reference, HG1, HG2 and so on, defined once in a legend at the bottom of the schedule sheet. That single change makes late revisions dramatically less error prone, because if a hardware spec changes partway through a project, you are editing one legend entry instead of hunting through forty individual rows trying to remember which doors shared that same hardware.

I also keep a simple revision column on the schedule itself, a small triangle or a rev number next to any row that changed since the last issue, which mirrors the standard revision cloud convention used on the plan sheets and gives a reviewer a fast way to see exactly what changed in the door schedule without having to compare every row from scratch.