Why issue drawings as PDF rather than native CAD files?

Because a PDF renders identically for everyone and cannot be accidentally edited in transit. A native CAD file (DWG, RVT) depends on the recipient having the right software and the right version, references external files, and is editable — fine for collaboration, risky for an issued record. A PDF set is the fixed, page-faithful snapshot of what was issued on a given date: the contractor, the consultant, and the authority all see the same lines at the same scale. Keep CAD for production and coordination; issue PDFs as the contractual record of each milestone.

How should I name and version an issued drawing set?

Use a consistent, sortable scheme that encodes project, sheet, and revision — for example a sheet number (A-101) plus a revision tag (Rev C) and an issue date. Keep the revision identifier inside the title block on the sheet itself, not just in the filename, so a printed page is self-identifying. For the set as a whole, name the file with the project, the issue purpose (Tender, Construction, As-Built), and the date. The goal is that anyone holding a sheet can tell exactly which issue it belongs to without opening a register.

What is the cleanest way to do revision control on PDF sets?

Treat each issue as an immutable, dated set and never overwrite a previous one. Maintain a drawing register (a simple spreadsheet) listing every sheet, its current revision, and the issue it went out in. When you re-issue, produce a new complete set, archive the old one read-only, and update the register. For spotting what actually changed between two issues, use a PDF compare tool that highlights differences rather than relying on revision clouds alone. The principle is borrowed from software version control: history is append-only, and you can always reconstruct exactly what was issued and when.

How do I compare two revisions to find what changed?

Use a PDF comparison tool that overlays or diffs the two versions and highlights additions, deletions, and moved content. This catches the changes a revision cloud missed and verifies that the only differences are the intended ones — important when a small edit can have contractual consequences. Compare sheet-by-sheet for a like-for-like set, and treat any unexpected difference as a flag to investigate before the set goes out. It is far more reliable than visually scanning two large drawings side by side.

Should issued sets be archived as PDF/A?

For the long-term record set, yes, consider PDF/A. PDF/A is the ISO-standardised archival profile of PDF designed for long-term preservation — it embeds all fonts and disallows features (like external references or certain encryption) that could make the file un-openable years later. For a building that must keep records for its operational life, archiving the final issued and as-built sets as PDF/A protects against the format drift that can render an ordinary PDF hard to open decades on. Working and interim issues can stay as standard PDF.

Is it safe to assemble confidential project sets with an online tool?

Only if the processing is client-side. Drawing sets can be commercially sensitive or security-relevant (think secure facilities), and server-side tools upload your files to a third party where they may be cached. Client-side (in-browser) tools assemble, compare, and compress the set locally so nothing leaves your computer — ScoutMyTool’s PDF tools work this way. For sensitive projects, confirm the tool is client-side, or use offline desktop software.

6 min read

PDF for architects — drawing sets + revision control

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

On the first project where I owned the drawing issue, the CAD was the easy part — the chaos was everything around it. Which set did the contractor actually have? Was the revision on the title block the same as the one in the register? Had anyone overwritten last month’s issue? The lesson stuck: for architecture, the PDF set is the contractual record, and the discipline that matters is how you assemble, version, and compare it. This guide is about that document workflow — building an issue set, controlling revisions like an append-only history, and diffing two issues to see exactly what changed — not about how to draw.

The drawing-set toolkit

Task	Tool	Why it matters
Assemble an issue set	Merge-PDF	Combine sheets into one ordered, issued set
Order + label sheets	Reorder + page numbers	Enforce sheet sequence (A-101, A-102…)
Spot what changed	Compare-PDF	Find revisions between two issues
Navigate a big set	PDF bookmarks	Jump to disciplines/sheets in a 200-page set
Stamp revision clouds/marks	Watermark / annotate	Mark "REVISED", issue date, status
Shrink for transmittal	Compress-PDF	Email or upload large sets within size limits

Step by step — issue and control a drawing set

Export sheets to PDF from CAD. Plot each sheet to PDF at the correct paper size and scale, with the revision and issue date already in the title block. The title block makes every printed page self-identifying.
Order and assemble the set. Put sheets in their standard sequence (general, then per discipline), merge them into one ordered PDF, and add sheet numbering so the set reads as a coherent document rather than a pile of pages.
Add navigation for large sets. For sets over a few dozen pages, add bookmarks for disciplines and key sheets so reviewers can jump directly rather than scrolling a 200-page file.
Issue immutably and update the register. Name the file with project, issue purpose, and date; archive it read-only; and update your drawing register with each sheet’s current revision. Never overwrite a prior issue — history stays append-only.
Compare against the previous issue. Before or after issuing, run a PDF comparison between this set and the last to confirm the only differences are the intended revisions. Investigate anything unexpected before it reaches site.
Compress for transmittal, archive the master in full. Send a compressed copy to fit email or portal limits, but keep the full-resolution master (and, for the record set, a PDF/A archive) untouched.

Borrowing revision control from software

The single most useful idea to import into drawing management is the software notion of append-only history. In version control you never edit the past; you add a new commit and keep the old ones, so you can always reconstruct any prior state. Apply the same to issues: each issued set is a dated, immutable artefact, the register is your log of what was current when, and re-issuing means producing a new complete set rather than patching an old one. Pair that discipline with a reliable compare step and you can answer the two questions that cause most site disputes — "which version did you have?" and "what changed?" — with evidence rather than memory.

FAQ

Why issue drawings as PDF rather than native CAD files?: Because a PDF renders identically for everyone and cannot be accidentally edited in transit. A native CAD file (DWG, RVT) depends on the recipient having the right software and the right version, references external files, and is editable — fine for collaboration, risky for an issued record. A PDF set is the fixed, page-faithful snapshot of what was issued on a given date: the contractor, the consultant, and the authority all see the same lines at the same scale. Keep CAD for production and coordination; issue PDFs as the contractual record of each milestone.
How should I name and version an issued drawing set?: Use a consistent, sortable scheme that encodes project, sheet, and revision — for example a sheet number (A-101) plus a revision tag (Rev C) and an issue date. Keep the revision identifier inside the title block on the sheet itself, not just in the filename, so a printed page is self-identifying. For the set as a whole, name the file with the project, the issue purpose (Tender, Construction, As-Built), and the date. The goal is that anyone holding a sheet can tell exactly which issue it belongs to without opening a register.
What is the cleanest way to do revision control on PDF sets?: Treat each issue as an immutable, dated set and never overwrite a previous one. Maintain a drawing register (a simple spreadsheet) listing every sheet, its current revision, and the issue it went out in. When you re-issue, produce a new complete set, archive the old one read-only, and update the register. For spotting what actually changed between two issues, use a PDF compare tool that highlights differences rather than relying on revision clouds alone. The principle is borrowed from software version control: history is append-only, and you can always reconstruct exactly what was issued and when.
How do I compare two revisions to find what changed?: Use a PDF comparison tool that overlays or diffs the two versions and highlights additions, deletions, and moved content. This catches the changes a revision cloud missed and verifies that the only differences are the intended ones — important when a small edit can have contractual consequences. Compare sheet-by-sheet for a like-for-like set, and treat any unexpected difference as a flag to investigate before the set goes out. It is far more reliable than visually scanning two large drawings side by side.
Should issued sets be archived as PDF/A?: For the long-term record set, yes, consider PDF/A. PDF/A is the ISO-standardised archival profile of PDF designed for long-term preservation — it embeds all fonts and disallows features (like external references or certain encryption) that could make the file un-openable years later. For a building that must keep records for its operational life, archiving the final issued and as-built sets as PDF/A protects against the format drift that can render an ordinary PDF hard to open decades on. Working and interim issues can stay as standard PDF.
Is it safe to assemble confidential project sets with an online tool?: Only if the processing is client-side. Drawing sets can be commercially sensitive or security-relevant (think secure facilities), and server-side tools upload your files to a third party where they may be cached. Client-side (in-browser) tools assemble, compare, and compress the set locally so nothing leaves your computer — ScoutMyTool’s PDF tools work this way. For sensitive projects, confirm the tool is client-side, or use offline desktop software.

Citations

Assemble your drawing set in the browser

ScoutMyTool Merge PDF combines your plotted sheets into one ordered issue set — entirely client-side, so commercially sensitive drawings never leave your computer. Then bookmark, number, and compress for transmittal.

Open Merge-PDF tool →