AI assistsWorkflow guide · not independently tested

Cross-check drawing keynotes against the project manual's spec sections in both directions with AI

Drawings and specs are one set of contract documents, but keynotes can point to sections that were deleted, and sections can sit in the project manual with nothing on the drawings calling for them. Export the keynote list from Revit (or have AI read the note blocks off the PDF set), export the project manual's table of contents, have Claude or ChatGPT normalize both lists, and use Copilot in Excel to match them both ways and list dead references, unreferenced sections and keynote text that does not match the section title. The architect and spec writer decide what each mismatch means.

Architect · Architecture · Autodesk Revit · Claude · ChatGPT · Microsoft Excel · Microsoft Copilot

Content updated · Tool links listed below; vendor features and pricing change, so confirm with the vendor

Short answer

Use Claude or ChatGPT, then Copilot in Excel: The AI normalizes the drawing keynote list and the project manual table of contents into matching section numbers, then Copilot matches them both ways and lists dead references, unreferenced sections, keys reused with different text, and wording that differs from section titles. Drawings and specs are one set of contract documents, but keynotes can point to sections that were deleted, and sections can sit in the project manual with nothing on the drawings calling for them. Export the keynote list from Revit (or have AI read the note blocks off the PDF set), export the project manual's table of contents, have Claude or ChatGPT normalize both lists, and use Copilot in Excel to match them both ways and list dead references, unreferenced sections and keynote text that does not match the section title. The architect and spec writer decide what each mismatch means. A person still checks: every flagged row by the architect or spec writer; unreferenced sections are questions, not errors, and section content is still read by a person.

AI tie-in

Tool: Claude or ChatGPT, then Copilot in Excel

The AI normalizes the drawing keynote list and the project manual table of contents into matching section numbers, then Copilot matches them both ways and lists dead references, unreferenced sections, keys reused with different text, and wording that differs from section titles.

Prompt 1

Here are two lists [paste or upload]: list A is the keynotes on our drawings (key, keynote text, sheet numbers) and list B is our project manual table of contents (section number, section title, included or deleted). For each keynote, extract the section number the key points to, ignoring any suffix after the section number. Then give me four tables: keynotes whose section is missing from list B or marked deleted; sections in list B that no keynote points to; keys that appear with more than one different text; and keynotes whose text uses different terms from the section title. Copy keys, numbers and titles exactly, flag anything you cannot parse, and do not judge whether the drawings or specs are correct.

Prompt 2

Read the general notes and keyed note blocks on these sheets [upload PDF sheets]. Build a table with one row per note: sheet number, note key or number, note text exactly as printed, and any spec section number the note cites. Write UNREADABLE for anything you cannot read and do not add or correct section numbers.

Human check: Every flagged row by the architect or spec writer; unreferenced sections are questions, not errors, and section content is still read by a person.

The problem

Cross-check drawing keynotes against the project manual's spec sections in both directions with AI. This is a common, time-consuming task for a architect.

What this workflow does

Drawings and specs are one set of contract documents, but keynotes can point to sections that were deleted, and sections can sit in the project manual with nothing on the drawings calling for them. Export the keynote list from Revit (or have AI read the note blocks off the PDF set), export the project manual's table of contents, have Claude or ChatGPT normalize both lists, and use Copilot in Excel to match them both ways and list dead references, unreferenced sections and keynote text that does not match the section title. The architect and spec writer decide what each mismatch means.

How it works: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.

Your checkpoint: Matching numbers and titles shows where to look; it does not confirm the detail and the specification say the same thing. The architect and spec writer review every flagged row and decide the fix, and the content of each section is still read by a person.

Before you start

  • Access to the named tool; confirm license, version and cost with the vendor.
  • A small, non-confidential sample to try the workflow on first.
  • A qualified person to review the output before it is used.

Tools and access

Follow the steps

  1. Export the keynotes in use: in Revit, a keynote legend or schedule exported to text, plus the keynote text file the project loads. If notes are loose text or the set came from CAD, upload the PDF sheets to Claude or ChatGPT and have it read the note blocks into a table with the sheet number, copying keys and text exactly.
  2. Export the project manual's table of contents (section number, title, and whether the section is included or deleted) from your spec software or the issued PDF.
  3. Have Claude or ChatGPT normalize both lists: pull the section number each keynote points to (a key with a suffix after the section number still points to that section), keep the keynote text and the sheets it appears on, and flag keys it cannot parse rather than guessing.
  4. Paste both normalized lists into Copilot in Excel and have it match them both ways: keynotes pointing to sections not in the manual or marked deleted, sections in the manual that no keynote or drawing note references, the same key used with different text, and keynote wording that differs from the section title, each as its own row.
  5. The architect or spec writer reviews every row. Plenty of sections are never keynoted (general requirements, for example), so an unreferenced section is a question, not an error. Run consultant disciplines separately if they use their own keying.
  6. Re-run at every issue: permit, bid, each addendum and conformed set, and keep each run's list with that issue.

Try a small example

Replace the bracketed fields with your own project details. No tested sample run is published for this workflow yet.

Sample input

Fill in the bracketed [fields] in the text below with your project data.

Starter prompt

Here are two lists [paste or upload]: list A is the keynotes on our drawings (key, keynote text, sheet numbers) and list B is our project manual table of contents (section number, section title, included or deleted). For each keynote, extract the section number the key points to, ignoring any suffix after the section number. Then give me four tables: keynotes whose section is missing from list B or marked deleted; sections in list B that no keynote points to; keys that appear with more than one different text; and keynotes whose text uses different terms from the section title. Copy keys, numbers and titles exactly, flag anything you cannot parse, and do not judge whether the drawings or specs are correct.

Expected output

Not published yet. Treat any output as a draft and check it against the source documents.

Check the result

  • Every value, citation or quantity traces back to a source document.
  • Missing information is marked as missing, not filled in.

Limits and recovery

  • Matching numbers and titles shows where to look; it does not confirm the detail and the specification say the same thing. The architect and spec writer review every flagged row and decide the fix, and the content of each section is still read by a person.
  • Check your organization’s data policy before sharing project files with third-party tools.

Stop or switch when: The source cannot be verified, permissions are missing, or the result contains unsupported facts.

Frequently asked questions

How does AI help with this?

Claude or ChatGPT, then Copilot in Excel: The AI normalizes the drawing keynote list and the project manual table of contents into matching section numbers, then Copilot matches them both ways and lists dead references, unreferenced sections, keys reused with different text, and wording that differs from section titles. A person still checks: Every flagged row by the architect or spec writer; unreferenced sections are questions, not errors, and section content is still read by a person.

How do I cross-check drawing keynotes against the project manual's spec sections in both directions with AI?

Export the keynotes in use: in Revit, a keynote legend or schedule exported to text, plus the keynote text file the project loads. If notes are loose text or the set came from CAD, upload the PDF sheets to Claude or ChatGPT and have it read the note blocks into a table with the sheet number, copying keys and text exactly. Export the project manual's table of contents (section number, title, and whether the section is included or deleted) from your spec software or the issued PDF. Have Claude or ChatGPT normalize both lists: pull the section number each keynote points to (a key with a suffix after the section number still points to that section), keep the keynote text and the sheets it appears on, and flag keys it cannot parse rather than guessing. The full step list is above.

Does this use an AI agent or regular software?

It is labeled AI assists: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.

What tools do I need?

Autodesk Revit, Claude, ChatGPT, Microsoft Excel, Microsoft Copilot. Confirm license, version and cost with the vendor, and try it on a small non-confidential sample first.

Has this workflow been tested?

Workflow guide · not independently tested. Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.

Evidence and maintenance

Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.

Know what does the work.

Agent executes
An AI agent calls connected tools to carry out bounded actions. You set permissions and review the result.
AI assists
AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
Conventional automation
Rules or specialist software perform the task. No AI agent is required.