Skip to content
Aurora

The Sharing Playbook

How to send revised drawings to an external project team

Send a drawing issue with the right revisions, a short change note and replies you can use. Includes a free drawing-issue worksheet.

Project Coordination · Aurora Datarooms

Archive Date Published
Three colleagues test a room layout with floor tape and a chair in a private garden studio.

Get The Free Worksheet

When you send revised drawings, list the sheets that changed, identify the new revision of each one, and say what recipients may use the issue for. Link to the checked files and explain which earlier copies they replace. Ask the people affected by the change to confirm that they have the right set before they continue their review or work.

A designer moves a partition in a small office fit-out. The revised plan reaches the estimator, but the services consultant still has last week's layout. Both reply with useful comments, based on different rooms. A short issue note would give them a common starting point and show which related drawings still need checking.

The note, a drawing list and a short follow-up all work with your existing project folder or document system.

Agree what this issue is for

Begin with the next action: comment on a layout, update an estimate, coordinate another drawing, or use a formally approved issue for work. Use the status names your project already follows. A later revision number alone doesn't tell someone what they are allowed to do with it.

Name the person who can release the issue and the person who will answer questions. In a small practice, that may be the same person. Confirm any required review or approval before sending the package.

For the office fit-out, the purpose could be: "Please review the revised meeting-room layout and update your comments. This issue is for coordination. Construction authorization will follow through the agreed project process."

If your project requires a formal drawing register, transmittal or common data environment, issue the drawings there. A transmittal is the record of the files sent and their recipients. If you also use a shared folder, say that it only supports that system, so teams can tell which issue governs their work.

Keep the drawing number and revision separate

Record the drawing number, title, revision and issue date from the drawing itself. Check the title block against the filename and your drawing list. Rename a confusing download if needed, but don't change the drawing's stated revision just to make the names match.

Keep the software's upload version separate too. The third upload of a file might still be drawing revision B if an earlier upload corrected a filename. Procore's drawing guidance, for example, describes recognizing an existing drawing number and adding an uploaded revision to its history. That is a specific drawing-management feature. Procore's revision guidance.

For a multipage PDF, say whether the whole file is replaced and list the revised sheets within it. Check the exported PDF page by page; uploading the right filename is only the start of that check.

Show the changed sheets and the related checks

You don't need to give every sheet a new revision just because one sheet changed. Make the mix explicit so recipients can assemble the correct set.

For example, a small coordination issue might contain:

SheetRevision in this issueChange and next action
A-101, ground-floor plan03, replaces 02Meeting-room partition moved. Estimator checks quantities; services consultant checks the effect on outlets.
A-201, interior elevations02, unchangedIncluded as reference. Designer checks whether the changed partition affects these elevations.
M-101, services layout05, unchangedConsultant checks the connection to A-101 revision 03 and reports any mismatch.

The list shows the open coordination questions. It doesn't prove that the drawings are compatible. The people responsible for the design need to resolve those questions before an issue is approved for the next purpose.

If a sheet is withdrawn, say so explicitly and identify its replacement if one exists. Keep the earlier issue in the project's approved record location, clearly separated from the set people use for current work.

Send one short issue note

Give the issue a reference that you can use in replies. List the recipients, files, purpose and response date. Make the link point to the collection you actually checked.

A note you could adapt:

Issue OF-07: meeting-room coordination. Please open the drawing set linked below and check A-101 revision 03, which replaces revision 02 for this review. A-201 revision 02 and M-101 revision 05 are included unchanged. The partition location has changed. Please confirm the revisions received, replace earlier working copies for this review, and send any affected quantities or coordination questions by Thursday at 3 p.m. Lisbon time. Contact Alex if a file is missing or the drawings conflict.

Before sending, check that each recipient has access to the files their task needs. Keep internal estimates, unrelated projects and private comments outside the shared collection. The free drawing-issue worksheet below has space for the sheets, recipients and replies.

Keep a record of the exact issue

Save the issue note and the exact files it describes in the agreed project record. A link to a changing file won't, by itself, show what the recipient could see on the day you sent the note.

Specialist systems can help with this. Autodesk's transmittal report records file versions and recipient actions, and its documentation says the reported attributes are snapshots from transmittal creation. If you use that tool, check its report alongside the files you issued. Autodesk's transmittal documentation.

With a simpler sharing system, keep the issued files and note yourself. Follow the project's existing retention and approval process. A completed worksheet is useful coordination material; it doesn't replace required contractual records or technical sign-off.

Ask for a useful reply

"Received" can mean that someone saw the email. Ask them to confirm the drawing revisions and any effect on their task. If they use downloaded or printed copies, ask them to replace the earlier working set and tell anyone else who received it.

Keep the replies short and specific:

  • "A-101 revision 03 received. Earlier estimating copy replaced. Quantity review due Thursday."
  • "A-101 revision 03 received. M-101 revision 05 needs a coordination check. Please confirm before we continue that part of the review."
  • "Link opens, but A-201 is missing. Please restore access and confirm the set."

A view or download record can help you follow up. It doesn't tell you that someone checked the drawing, understood the change or approved it. Contact anyone whose missing reply could hold up the next step.

Use Aurora for the shared review files

For a small external review, you can keep files in an Aurora library and select which ones appear in each room. For example, one room could serve the estimator and another the services consultant. Groups and individual permissions refine access within those rooms.

When you replace a shared source file, the rooms that share it show the current version when people reopen or refresh it. Downloaded and printed copies stay as they were. Keep unreleased working drawings separate until they are ready to be shared, and send the issue note through your agreed communication channel.

Aurora's file version history does not replace the drawing revision on a sheet, a formal transmittal, or an engineering approval workflow. Keep those records through the process your project uses.

To try the sharing setup, use three small sample PDFs in one library and two rooms. Replace one sample, reopen each room that shares it, and check the revision shown in the file. That task fits the current 30-day Starter trial and its two-room allowance.

Try Aurora with a sample project.

Before you close the issue

Check that the file list matches the issued copies, each recipient can open what they need, and the people affected have confirmed their revisions or raised a specific question. Record who will resolve each open question and when. Then the next project call can focus on the design decision with everyone working from a known set.

If copies have already diverged, the guide to aligning reviewers on the same version shows how to compare their starting points before combining comments.

Drawing issue worksheet

Free to use and adapt. Keep your completed worksheet in your own project files.

Download Worksheet (.md)

Use this before sending revised drawings. Fill the drawing list from the actual files, send a short issue note, then record recipients' replies. Keep the completed note and exact issued files in your project's agreed record location.

Issue details

  • Project:
  • Issue reference:
  • Prepared by:
  • Released by, with required approval checked:
  • Sent date, time and timezone:
  • Purpose and permitted use:
  • Current-set location:
  • Exact issued-files record location:
  • Contact for questions:
  • Reply due date, time and timezone:

Drawing list

Drawing number and titleFilename and pageNew revision and issue dateReplacesChanged or unchangedChange summary and required check

For a multipage PDF, state whether the complete file is replaced and identify the changed sheets. Add withdrawn sheets and their replacements. Check the title blocks against this list.

Recipient follow-up

Person and taskSheets neededAccess checkedRevision confirmation and dateEarlier working copies replacedQuestion or next action, person and due date

Message to adapt

Issue [reference] for [purpose]. Please open [location]. The attached list identifies the current sheets and revisions, including any unchanged reference sheets. [Brief change summary.] Please confirm the revisions received, replace the earlier working copies for this task, and report missing files or conflicts to [contact] by [date, time, timezone]. [State any restricted use or outstanding approval.]

Final checks

  • Drawing title blocks, exported pages and list agree.
  • Related sheets and unresolved coordination questions are identified.
  • Required release approval is recorded.
  • Each recipient can open the files their task needs.
  • Unrelated or private material is excluded.
  • Exact issued files and note are retained through the agreed process.
  • A view/download entry is kept separate from an explicit revision confirmation or approval.
  • Downloaded and printed copies are handled through recipient follow-up.

Use your project's required drawing-control and approval process alongside this worksheet.

Sources