Use AI to Prepare a Drawing Revision Review.

A revised drawing set arrives while the project manager is preparing the next trade visit. The immediate task is to find what needs attention and connect it to work already planned. A paragraph saying “the kitchen layout changed” leaves that work undone.

Datum recommends testing AI as a preparation step for drawing revision review. Ask it to produce a list of possible changes with locations in both versions, plus a separate record of sheets it could not compare. A person responsible for the project still verifies the differences and decides what follows.

Confirm which documents belong in the comparison

Start with the earlier issued set, the replacement set, and the accompanying revision notice if one exists. Record each file’s issue date and stated status. A newer filename alone does not establish that a drawing is approved for field use.

Build a sheet list before asking for differences. Pair sheets by their identifiers and titles, then check those pairs yourself. PDF page positions can change when sheets are added or removed. Keep added sheets, removed sheets, and uncertain matches visible in the list.

Use an environment your company has approved for project records. Give the assistant only the relevant sets and context. Keep the originals available so the reviewer can open the actual sheet rather than relying on a copied excerpt.

Check that the tool can read the drawing

Anthropic’s current PDF documentation describes processing pages as images alongside extracted text. It also notes that dense documents can reach processing limits before the stated page limit. Its Vision documentation supports comparing multiple labeled images and explains that larger images may be downscaled before processing.

Those capabilities make a comparison worth testing. They do not establish that an assistant will detect every change in a construction drawing. Datum’s recommendation is to start with a small, matched group of sheets and inspect whether the tool can read the notes, symbols, and dimensions involved.

If a detail is too small, provide a legible crop with its sheet identifier and location, while retaining the full sheet for context. Label both versions clearly. An unreadable dimension should remain unresolved; do not ask the assistant to infer it from the apparent size of the drawing.

Ask for a review list you can check

• Location: sheet identifier, room or detail, and a way to find the same area in both versions.
• Earlier version: the relevant note, dimension, or depicted condition, with its source location.
• Revised version: the corresponding evidence, or an explicit statement that it could not be found or read.
• Possible consequence: a question for the reviewer about affected work, clearly separate from the observed difference.
• Review status: unverified, confirmed by the named reviewer, or unresolved with the next check recorded.

Keep a coverage record beside the change list. It should identify supplied sheets, matched pairs, and anything the assistant skipped or could not interpret. “No difference reported” is a statement about the tool’s output. It is not proof that a sheet is unchanged.

Follow a changed note into the affected work

Consider a hypothetical revision: a kitchen elevation changes a cabinet note from a fixed shelf to a pullout. The AI lists the wording change and its location. That gives the project manager a specific item to check against the original and revised sheets.

The next questions belong in the review: Does the cabinet order reflect this revision? Is a related detail still showing the earlier arrangement? Who needs to resolve any disagreement before work proceeds? The assistant can draft those questions, but the drawing comparison alone cannot answer them.

Have the responsible reviewer record what was confirmed, who must act, and which existing order or instruction needs review. Route unresolved design questions through the project’s normal clarification process. Keep purchasing changes and trade instructions subject to the approvals your team already uses.

Test for missed changes before relying on the list

Choose a past revision with a change record that an experienced reviewer can verify. Run the comparison using only documents available when that revision arrived. Then check both kinds of error: changes the assistant missed and differences it reported that were only shifts in page layout or formatting.

Include an added sheet and a hard-to-read detail in the trial. Check whether the assistant exposes those limits. Count reviewer correction time as part of the task; a long list of false alarms may take more effort to resolve than the original comparison.

Bring a redacted pair of drawing revisions and your team’s review checklist to a conversation with Adam. Datum’s Training work helps your staff learn to build and run tools around a defined task, including the checks needed before its output enters a live project.

• Check project PDFs before asking AI to summarize
• Prepare an RFI someone can answer
• Explore Datum Training
• Book a Conversation

Next step, if this note maps to a problem on your desk: book a conversation with Adam. Thirty minutes, weekday evenings, Eastern time.