How do I issue a navigable drawing set?

An architectural set spans many sheets across disciplines, so navigation is essential: assemble it into one PDF with a bookmark outline by discipline and sheet number, a sheet index, and page numbering so anyone can reference a specific sheet. Keep sheets large-format and crisp so dimensions, notes, and fine detail stay legible when zoomed or plotted to scale. Issue it as a PDF so it renders identically for the client, consultants, and contractors on any device. A clean, indexed, navigable set is far more usable on site and in coordination than a folder of loose sheets, and it reflects a well-run practice.

How do I track revisions and compare issues?

Architecture is iterative, and you must be able to show exactly what changed between issues. Use clear revision marking (revision clouds, rev numbers and dates on each affected sheet), and when reviewing a new issue against the prior one, overlay them with a visual comparison that highlights what changed rather than hunting by eye across two large sheets. This is invaluable for coordination and for catching unannounced changes. Pair it with disciplined issue naming and an archive of every issue, so the revision history is reconstructable — which sheet showed what, on which date. The combination of rev marking plus compare-and-archive is how an architect keeps control of a moving design.

How should RFIs be handled?

An RFI resolves a question during construction, and its value is in being specific and traceable: mark up the exact area of the drawing the question concerns, state the question and proposed answer clearly, and log it numbered and dated. As a PDF, an RFI is a marked-up drawing excerpt plus the question/answer, archived in the RFI log as the project record of what was asked and decided. Consolidate review comments into a single summary so nothing is missed across the team. A clean, numbered, dated RFI trail is exactly what protects the project in disputes and what good construction-administration runs on.

How do I manage submittals?

Submittals (product data, shop drawings, samples documentation) come in for the architect to review and approve, so the workflow is to receive, review/stamp, annotate with comments, and return them, while keeping an organised, logged record of each submittal's status. As PDFs, mark up submittals with review comments and stamps, archive the reviewed copy, and track the log so you know what is outstanding. Submittal review has professional and contractual significance, so a clear, dated, archived record of what was submitted, reviewed, and returned matters. Treat it like the RFI process: organised, logged, and traceable.

Why is version control so critical here?

Because construction proceeds from issued documents, and the practice must be able to show exactly what was issued and current at any point — for coordination, for payment certification, and critically for disputes and professional liability. Name files with issue/revision and date, distribute only the current issue, and archive every issue so you can reconstruct the drawing of record for any date. Building from a superseded sheet is enormously costly in construction, so the version discipline is risk management for the architect, not bureaucracy. An architect who can produce the exact current and historical issued documents instantly is protecting both the project and the practice.

How do I keep specifications usable alongside drawings?

Specifications are the written counterpart to the drawings, and they should be searchable and bookmarked so a specific section is findable fast, and kept version-controlled in sync with the drawing issues. As PDFs, ensure the specs contain real (searchable) text and a navigable structure, and issue them alongside the drawing set so the document of record is complete. Coordination problems often hide in mismatches between drawings and specs, so keeping them issued together and current reduces that risk. A searchable, navigable, current spec set paired with the drawings is the complete construction document the project relies on.

Is it safe to handle project documents with an online tool?

Architectural documents can be commercially sensitive and carry professional liability, so prefer a tool that processes files locally. ScoutMyTool compares, annotates, merges, bookmarks, and compresses entirely in your browser tab, so project documents never leave your machine. For confidential or contractually-restricted project work, confirm the tool does not upload before using it.

5 min read

PDF for architects: drawing sets, revision history, and RFIs

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

Architectural practice is documentation under professional liability: drawing sets issued and reissued, revisions that must be tracked, RFIs and submittals that must be logged, and an issue history you may have to reconstruct years later. When the document discipline is tight, coordination is smooth and the practice is protected; when it slips, you get build-from-the-wrong-sheet errors and disputes you cannot answer. This guide is the architect’s PDF workflow — issuing navigable sets, comparing revisions, managing RFIs and submittals, keeping specs in sync, and maintaining a rigorous version history. (It shares much with the civil-engineering drawing workflow, focused here on architecture.)

The documents a project runs on

Document	Use	PDF need
Drawing set	Design + construction	Large-format, navigable, versioned
Revision (rev cloud)	Track changes	Compared to prior issue; dated
RFI	Resolve questions	Marked-up, logged, dated
Submittal	Approve products	Stamped, annotated, archived
Specifications	Written requirements	Searchable, bookmarked
Issue record	What was issued when	Every issue archived

Step by step — a drawing-document workflow

Issue a navigable set. Merge sheets with Merge PDF, bookmark by discipline/sheet with Add Bookmarks, add a sheet index and page numbers.
Keep sheets crisp and to scale. Large-format, legible detail, compressed losslessly — see quality vs. size.
Compare revisions. Overlay a new issue against the prior with Visual Diff to see exactly what changed — see comparing PDFs.
Mark up RFIs precisely. Annotate the exact area with Add Comment, log numbered and dated — see annotation tools.
Review and log submittals. Stamp and annotate submittals, archive the reviewed copy, track the log; consolidate review comments with Annotation Summary.
Number sheets/exhibits consistently. Stable references (see Bates-style numbering) so everyone cites the same thing.
Version and archive every issue. Issue/date on each sheet, distribute only the current issue, archive all issues — the discipline detailed for the civil-engineering drawing set.

PDF for civil engineers: the shared drawing-set discipline.
Compare two PDFs: revision review.
PDF annotation tools: RFIs and submittal markups.
Share without losing quality: crisp drawings.
Bates numbering: stable sheet references.
Visual Diff tool: compare issues in your browser.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

How do I issue a navigable drawing set?: An architectural set spans many sheets across disciplines, so navigation is essential: assemble it into one PDF with a bookmark outline by discipline and sheet number, a sheet index, and page numbering so anyone can reference a specific sheet. Keep sheets large-format and crisp so dimensions, notes, and fine detail stay legible when zoomed or plotted to scale. Issue it as a PDF so it renders identically for the client, consultants, and contractors on any device. A clean, indexed, navigable set is far more usable on site and in coordination than a folder of loose sheets, and it reflects a well-run practice.
How do I track revisions and compare issues?: Architecture is iterative, and you must be able to show exactly what changed between issues. Use clear revision marking (revision clouds, rev numbers and dates on each affected sheet), and when reviewing a new issue against the prior one, overlay them with a visual comparison that highlights what changed rather than hunting by eye across two large sheets. This is invaluable for coordination and for catching unannounced changes. Pair it with disciplined issue naming and an archive of every issue, so the revision history is reconstructable — which sheet showed what, on which date. The combination of rev marking plus compare-and-archive is how an architect keeps control of a moving design.
How should RFIs be handled?: An RFI resolves a question during construction, and its value is in being specific and traceable: mark up the exact area of the drawing the question concerns, state the question and proposed answer clearly, and log it numbered and dated. As a PDF, an RFI is a marked-up drawing excerpt plus the question/answer, archived in the RFI log as the project record of what was asked and decided. Consolidate review comments into a single summary so nothing is missed across the team. A clean, numbered, dated RFI trail is exactly what protects the project in disputes and what good construction-administration runs on.
How do I manage submittals?: Submittals (product data, shop drawings, samples documentation) come in for the architect to review and approve, so the workflow is to receive, review/stamp, annotate with comments, and return them, while keeping an organised, logged record of each submittal's status. As PDFs, mark up submittals with review comments and stamps, archive the reviewed copy, and track the log so you know what is outstanding. Submittal review has professional and contractual significance, so a clear, dated, archived record of what was submitted, reviewed, and returned matters. Treat it like the RFI process: organised, logged, and traceable.
Why is version control so critical here?: Because construction proceeds from issued documents, and the practice must be able to show exactly what was issued and current at any point — for coordination, for payment certification, and critically for disputes and professional liability. Name files with issue/revision and date, distribute only the current issue, and archive every issue so you can reconstruct the drawing of record for any date. Building from a superseded sheet is enormously costly in construction, so the version discipline is risk management for the architect, not bureaucracy. An architect who can produce the exact current and historical issued documents instantly is protecting both the project and the practice.
How do I keep specifications usable alongside drawings?: Specifications are the written counterpart to the drawings, and they should be searchable and bookmarked so a specific section is findable fast, and kept version-controlled in sync with the drawing issues. As PDFs, ensure the specs contain real (searchable) text and a navigable structure, and issue them alongside the drawing set so the document of record is complete. Coordination problems often hide in mismatches between drawings and specs, so keeping them issued together and current reduces that risk. A searchable, navigable, current spec set paired with the drawings is the complete construction document the project relies on.
Is it safe to handle project documents with an online tool?: Architectural documents can be commercially sensitive and carry professional liability, so prefer a tool that processes files locally. ScoutMyTool compares, annotates, merges, bookmarks, and compresses entirely in your browser tab, so project documents never leave your machine. For confidential or contractually-restricted project work, confirm the tool does not upload before using it.

Citations

Wikipedia — “Architectural drawing,” the drawing set and its conventions. en.wikipedia.org/wiki/Architectural_drawing
Wikipedia — “Request for information,” the construction RFI process. en.wikipedia.org/wiki/Request_for_information
Wikipedia — “Submittals (construction),” the submittal review process. en.wikipedia.org — Submittals

Issue, track, and defend your documents

Assemble navigable sets, compare revisions, and manage RFIs with ScoutMyTool’s in-browser tools — project documents never leave your machine.

Open Visual Diff →