Claude Cowork can help prepare a reconciliation between a drawing register and an issued PDF set. Ask for a page-by-page index, source references, and a list of differences for review. The resulting spreadsheet should explain what was observed and what remains uncertain before anyone turns it into a BIM update.
What can Claude Cowork do for architecture teams?
Cowork runs cloud task sessions that can work with documents and spreadsheets. It supports project instructions and plugins; local files and computer actions require the connected Claude Desktop app to remain open. This reflects the current Cowork documentation, checked November 4, 2026.
For an architecture team, a drawing-set reconciliation is a useful task to evaluate because the output can be checked against the original pages. Ordinary file access does not itself provide a Revit connection. The first deliverable is a review workbook, with modeling decisions handled after the discrepancies are understood.
Prepare project PDFs and spreadsheets for a Cowork task
Define the issue date and disciplines in scope. If the supplied PDFs contain only the architectural issue, a mechanical sheet in a combined project register should not automatically be reported missing. Establish which register rows are expected in this particular package.
Use copies of the issued files and register. Keep original formulas, duplicate rows, and values intact; those may explain a discrepancy. A combined PDF is acceptable. What matters is indexing every relevant page and retaining a reference that lets the reviewer reopen it.
Request one observed-index row per page with the file name, page number, visible sheet number, title, issue or revision information, and evidence location. Preserve printed text before applying naming rules. File names and bookmarks help navigation, but should not override the visible title block.
If a page cannot be read reliably, label it “needs manual check.” An empty extraction is not evidence that a sheet is absent. Ask for these pages in a separate review queue, linked to their original file and page.
The comparison should retain both values: what the register says and what the PDF shows. Put proposed normalizations or actions in separate fields. This makes it possible to review a punctuation difference without erasing the evidence of a more substantial title change.
Example: reconcile a drawing register with an issued PDF set
Consider a hypothetical architectural issue with three discrepancies. The identifiers below illustrate the review process; they are not findings from a customer project.
A103 is not found in the supplied set. The register expects a Level 03 plan. The AI extraction does not locate it, but two pages are unreadable. At this point the correct status is “not found; coverage incomplete.” A reviewer checks those pages and the remaining scope. Only after that check should the record say the sheet is absent from the received package. The issuer then confirms whether it was intentionally held or omitted.
A201 has a different title. The register says “Enlarged Plans — Core,” while the visible PDF title block says “Interior Elevations — Core.” Record both strings with the source locations. This is more than punctuation normalization, but it does not establish which record should change. The reviewer needs the issue decision and the actual drawing content before approving a correction.
A501 appears twice. Two received pages carry the same sheet number. Preserve both page references and their visible revision information. They could be repeated exports, different revisions, or another packaging error. The spreadsheet should ask for the cause, rather than propose renumbering a model sheet before anyone knows whether two model sheets exist.
The useful output is a small set of explained exceptions. Each exception names the evidence, the unresolved question, and the person who can resolve it. Repeating the same cases in a summary, checklist, and proposed change list adds volume without improving the decision.
Review the spreadsheet before using it for BIM updates
First check coverage: every page in the supplied scope should have an observed row or a clearly documented exclusion. Reopen pages behind consequential differences and resolve unreadable items. Counting spreadsheet rows alone cannot establish that the correct pages were inspected.
Then assign a decision to each exception. A missing issued sheet might require another export rather than a model edit. A retitled sheet might require a register correction. A duplicated PDF page might require only a packaging correction. These outcomes should remain distinct in the approved action list.
For actions that do affect Revit, record the target sheet, exact approved value, source decision, responsible author, and reviewer. Keep the observed index unchanged beside this list. The team should be able to answer both “what did we receive?” and “what did we decide to change?”
When the correction is complete, compare the resulting deliverable with the approved action. If the issue was a PDF packaging problem, inspect the replacement PDF package. If the action changed a model field, verify that field and any affected display in the native model. Choose the evidence that matches the action.
For implementation options, see Revit automation with macros, Dynamo, Python, and AI.
Claude Cowork vs a Revit MCP connection
The document task above reads PDFs and a register. A Revit MCP connection exposes tools that a compatible client can use against a running model. Uploading an RVT file or receiving a plausible sheet list does not establish that such a connection exists or that the model was queried.
Keep this distinction in the handoff. Cowork's reviewed workbook can describe the intended changes; the selected modeling workflow must demonstrate access to the correct document and fields. ArchiLabs Desktop provides native Revit and AutoCAD integrations on Windows for model work and documentation, with the specific task assessed in the team's environment.
For the first trial, choose one small issued package and retain the originals. Review the page index and exceptions with the person who issued it before expanding the process to a larger drawing set.
Compare Revit macros, Dynamo, Python, and AI assistants to automate BIM tasks faster, reduce errors, and pick the best workflow.