To check a Revit door schedule with AI before you issue drawings, compare your model schedule against the approved type matrix, fire‑door matrix, room list, and any vendor docs. The AI flags parameter mismatches—such as D‑108 showing a different width and type across sources—while you ask the named source owner to decide; fire ratings remain source‑controlled, not AI‑chosen.
What AI can check in a Revit door schedule
AI helps by pulling values from multiple sources (model schedules, spreadsheets, PDFs) and aligning comparable fields so conflicts appear clearly. Your team still decides which source governs and approves changes in the model. Treat engineered decisions—door types that drive geometry, fire and smoke ratings, and hardware sets—as owner‑confirmed inputs. The AI only compares and ranks discrepancies; it does not determine ratings or substitute types on its own. For broader QA/QC patterns you can adapt to this review, see Avoiding Costly Mistakes: Automating QA/QC in Revit Models.
Prepare door schedules and approved source documents for comparison
Establish the sources you will compare and name their owners. Typical set:
• Model door schedule (Architect)
• Approved type matrix/spec (Architect or door vendor)
• Fire‑door matrix (Fire engineer or Architect)
• Room/space list (Architect or Interiors)
• Vendor spreadsheets or marked‑up PDFs (Door vendor)
Export the door schedule to CSV and place all inputs in a dated folder. A Revit schedule export does not automatically include your view filters or other model settings, so keep a brief note of which schedule view produced the export. Use a consistent identifier (commonly the Mark) as your match key; if duplicates exist, flag them before comparing. A copied Revit view is not a frozen snapshot—re‑export when you re‑run the check, and do not assume a schedule of selected objects proves others stayed unchanged.
Compare door types, dimensions, and identifiers with AI assistance
Have the AI align like‑for‑like fields across sources so people only review true differences:
• Identifier integrity: Mark present and unique in the issue phase; duplicates and blanks flagged.
• Type alignment: Family/Type and Type Mark in the model vs the approved type matrix; mismatches listed.
• Dimension fields: Compare the model’s dimension fields to the matrix’s nominal entries. When a door type drives size, a size mismatch often indicates the wrong type was applied.
• Room‑side references: To Room/From Room should resolve in the relevant phase; blanks can be valid (for example, some exterior doors). Do not try to overwrite these fields from a spreadsheet; they depend on placement and room boundaries.
• Ratings and hardware (source‑controlled): Model parameters for fire/smoke rating and hardware set are checked against the governing matrices or lists; the AI only flags differences or blanks so the responsible owner can confirm.
Rank conflicts by impact (for example, type or rating mismatches above comment differences) so the right owners see the most consequential items first. If two non‑governing sources disagree (say, a vendor sheet vs a marked‑up PDF), ask the named owner which governs; never choose based on the newest filename.
Make door schedule QA findings visible in Revit
Revit schedules expose model parameters as fields and can be configured via schedule view properties to focus QA data. See Autodesk’s explanation of configurable schedule fields and view properties in Schedules: About schedules and their properties.
Practical setup for a QA‑specific Door schedule view:
• Fields: include identifiers (Mark), Family/Type, Type Mark, key dimensional fields, Level and available phase-related fields, optional Fire/Smoke Rating and Hardware Set if your families expose them, plus a Comments or QA Status parameter you control.
• Itemization and counts: turn on “Itemize every instance” when hunting duplicates. Row counts are not element counts unless itemization and filters make that explicit.
• Sorting and grouping: sort by Level, then by Type, then by Mark to cluster issues logically.
Revit filters can target fixed values or blanks but cannot compare two arbitrary fields directly; keep cross‑field comparisons (for example, model vs matrix) in the AI‑compiled report. Also, Design Option is not an ordinary instance text parameter—avoid attempting to drive it from schedules or external imports.
For teams that want to stand up QA‑focused schedules quickly, see Auto‑Build Schedules and Sheets with AI this Weekend.
Door schedule example: resolve a width and type conflict
Consider a single, focused review item to illustrate the process:
• What’s conflicting: In the model schedule, D‑108 carries Type A and a certain width entry. In the approved type matrix, D‑108 is listed as Type B and its dimension fields do not match the model. A vendor spreadsheet happens to mirror the model’s Type A entry.
• What the AI delivers: A concise record showing D‑108 with side‑by‑side values—model vs type matrix—and a note that the vendor document aligns with the non‑governing source.
• What you do next: Ask the type‑matrix owner to confirm which type governs for D‑108. Do not use the latest filename or timestamp as a tie‑breaker. Keep fire‑door and hardware confirmations on their own tracks; parameter comparison does not substitute for engineered approvals.
• After confirmation: Update D‑108 in Revit to the approved type and ensure the dimension fields align with that type’s intent. If changing a Type affects many instances, coordinate your approved type strategy first; modifying a shared type value can cascade across doors.
Review and apply approved door schedule corrections
A single conflict record is enough to drive a clean decision. For each item, capture:
• Element: D‑108 (Mark)
• Fields in conflict: Type, width
• Sources compared: model schedule, approved type matrix, vendor spreadsheet (not governing)
• Governing source and owner: named person and document
• Decision and date: confirmed values and approver
Apply changes only after owner confirmation. Avoid inferring design validation from Revit warning counts or system colors. Re‑run the AI comparison to confirm the conflict is cleared or formally waived. Remember that a schedule export reflects current model values and not the filters that produced it, so keep your QA schedule settings documented alongside the export.
Using ArchiLabs Desktop for door schedule review tasks
ArchiLabs Desktop can operate alongside Revit and your project files to assemble sources, extract comparable fields, flag conflicts like the D‑108 width/type disagreement, and prepare ready‑to‑apply edit lists once owners approve. Teams often share spreadsheets, marked‑up PDFs, annotated screenshots, and short screen recordings so the AI understands context; availability of specific integrations depends on application versions, plans, accounts, and permissions.
Start with one level and its current approved references. Export the schedule, inspect the comparison, and take the first real discrepancy to the responsible source owner.
Avoid costly mistakes when doing Revit QA/QC. By doing so, you can reduce project cost and timeline overruns and improve your team's performance.
Upgrade your weekend workflow: use AI to auto-build schedules and sheets, save hours, reduce errors, and launch projects faster.