Which drawing revision reaches the site?

Treat the publish step in Procore’s Drawings tool as the moment a revision becomes the governing drawing. Give it one named owner and a written rule for which option to click. Publishing is what makes a revision viewable to all users with access to the project’s Drawings tool. Clicking “Publish” instead of “Publish & Distribute” means subscribers get no notification. This rests on Procore’s Publish Drawings tutorial and its Drawings tool overview.

Why is the field still building from the superseded sheet?

An architect issues a revision. Document control uploads it, OCR fills in drawing information, and someone confirms the labels. Then the revision stops at a step that looks finished but is not. Procore’s Publish Drawings tutorial states that after drawings have been uploaded and reviewed, they will be in unpublished status until they are published. Unpublished drawings do not update the Current Drawings and will not be visible on mobile devices. The superintendent opening the set on a tablet still sees the previous revision as current. Nobody broke a rule in the system. The revision never crossed from uploaded to published, or crossed without anyone being told. That gap tends to surface later as rework, an RFI on a question already answered, or a dispute about which revision governed.

What does the publish step control?

The same tutorial sets out three things that change at the moment of publishing. First, visibility. Unpublished drawings are only visible to Drawings tool ‘Admin’ users, and publishing requires ‘Admin’ permissions on the Drawings tool. After publishing, drawings are viewable to all users with access to the project’s Drawings tool. Second, the current set. Publishing a newer revision of an obsolete drawing makes it current, while publishing an older revision of an obsolete drawing during backfilling keeps it obsolete. Third, scope. The tutorial states that all of the drawings in the upload will be published.

The tutorial also says drawings can be left unpublished for internal review, subcontractor pricing, or to restrict access to only Drawings tool ‘Admin’ users. Holding is a feature, not an error. The risk is a hold with no owner and no end date. Because the whole upload publishes together, we would keep a revision meant for pricing out of an upload meant for the field.

Who gets told, and where else does it land?

The Publish drop-down offers two options. Publish & Distribute publishes the drawings and sends a notification email and push notification to drawings log subscribers. Publish publishes them without sending a notification email to drawings log subscribers. The tutorial is explicit: subscribed users only receive notifications for published and distributed drawings. The Drawings tool overview adds that only users with ‘Admin’ permissions can subscribe or unsubscribe other users. When projects are connected via the Connection Manager tool, drawings published in the upstream project will automatically copy to the downstream project. One click can therefore reach another project’s team.

Which publish option should be the default?

The decision is which option your publisher uses for each kind of upload, and who approves the exceptions.

What to do this quarter

• Pull every upload still in unpublished status on active projects and note how long each has waited.
• Name one publisher per project with ‘Admin’ permissions on the Drawings tool, plus a backup.
• Write the rule: which uploads get Publish & Distribute, which get Publish, and who approves a hold.
• Compare the drawing log subscriber list with the foremen and trades who build from the drawings.
• Measure days from upload to publish for revisions that change field work.

What this means for a bottleneck worth $1M or more

This becomes worth redesigning as one domain when revisions arrive weekly across projects and rework or claims trace back to which revision governed. We would handle it as part of revisions and RFIs within project-information operations. Rules cover the predictable, such as which option each upload type gets. AI handles the messy, such as flagging a new revision inside a backfill upload. People approve consequential decisions, such as publishing a governing drawing. AI never decides alone. Order entry exceptions follow the same pattern: one owner and one record per exception.

Limits of this evidence

These are Procore support pages that describe how the Drawings tool is meant to work. They do not show how often revisions sit unpublished or how often the wrong option is chosen. They do not measure rework, RFIs or claims tied to publishing. They say nothing about other document control products. They also do not show whether subscribers act on the notifications they receive.