Tag blocks and extract a schedule with Data Extraction in AutoCAD

Defining an attribute with ATTDEF

Type ATTDEF to open the Attribute Definition dialog. Set a Tag (the field name, like WIDTH or TYPE, with no spaces), a Prompt (the question shown when inserting), and a default Value. Position the attribute text where you want it relative to the block geometry and click OK.

The Tag is the column header your schedule will use, so name it clearly. Define one attribute per piece of data you want to schedule — a door might carry TYPE, WIDTH and FIRE_RATING as three separate attribute definitions placed near the door geometry.

Building attributes into the block

Select the geometry together with the attribute definitions and run BLOCK to define the block, or add the ATTDEFs to an existing block with BEDIT. When attributes are part of the block definition, every future insertion prompts for their values, so each instance can carry its own data.

Order matters a little: the sequence in which you select attributes during BLOCK sets the order AutoCAD prompts for them on insert. Pick them in a logical order — type, then width, then rating — so filling values at insertion time flows naturally.

Filling attribute values per instance

As you insert the block, AutoCAD prompts for each attribute, or you can fill them later by double-clicking an instance to open the Enhanced Attribute Editor (EATTEDIT). This is where one door becomes 'Type 1, 1000 mm' and another becomes 'Type 6, 900 mm' — same block, different data.

For many instances, the Block Attribute Manager (BATTMAN) and find-and-replace style edits help you fill or correct values in bulk. Accurate per-instance values are what make the extracted schedule meaningful, so it is worth filling them as you go rather than at the end.

Running the Data Extraction wizard

Type DATAEXTRACTION (or EATTEXT in older versions) to launch the wizard. Create a new extraction, choose the data source (the current drawing, selected objects, or whole folders of drawings), then select which blocks to include. On the next page tick the properties and attributes you want as columns — Count is offered automatically.

The wizard previews the table: each row a block (or a grouped count), each column an attribute or property. Refine which columns appear, set whether to combine identical rows into a count, and you have a schedule built from the drawing's own data.

Placing the table or exporting to a spreadsheet

At the end of the wizard, choose to insert the result as an AutoCAD table in the drawing, export it to an external file (CSV or XLS), or both. Inserting it as a table puts a live door or furniture schedule right on the sheet; exporting hands the data to a procurement or estimating spreadsheet.

The inserted table is linked to the extraction definition, so when the drawing changes — you add doors, edit widths — you can update the table to re-read the current data rather than rebuilding it. That link is what keeps a schedule trustworthy as the design evolves.

Keeping the schedule in sync

After edits, right-click the extraction table and choose Update Table Data Links, or re-run the extraction, so the counts and values reflect the latest drawing. A schedule that silently goes stale is worse than none, so make updating it part of your issue routine.

For multi-sheet or multi-file projects, point the extraction at a folder so it tallies across drawings into one combined schedule. Combined with consistent attribute tags across your block library, this scales a single-plan door schedule up to a whole-project register with the same workflow.

The payoff of all this tagging is that the drawing becomes the single source of truth. Instead of maintaining a separate spreadsheet that someone has to remember to edit, the schedule is generated from the geometry itself, so a door added in plan shows up in the count and a width changed on an instance flows into the table. That tight coupling between the drawing and its schedule is the real reason to invest in attributes up front: it removes an entire class of errors where the plan and the schedule say different things, which is exactly the kind of discrepancy that causes problems on site.

Keeping attribute tags consistent across a library

Data extraction is only as good as the tags behind it. If one door block calls its width WIDTH and another calls it W, the wizard treats them as two different columns and your schedule fragments. Settle on a small, fixed set of tag names — TYPE, WIDTH, RATING for doors; CODE, DESCRIPTION for furniture — and use the same names across every block in your library.

When the tags are consistent, you can extract a clean combined schedule from a folder of drawings in one pass, with every door lining up under the same columns regardless of which file or which block it came from. That consistency is worth enforcing as a library standard, because retrofitting tag names across hundreds of existing blocks later is far more painful than agreeing them once at the start.