How to redline construction drawings in PDF

Redline conventions at a glance

Step by step — redlining a drawing set

1. Open a working copy. Keep the unredlined original untouched in the archive; redline on a duplicate.
2. Mark up with consistent conventions. Use Add Comment for callouts and clouds, applying the colour rules above — see the broader annotation tools guide.
3. Number each comment as you create it. Sheet-prefix + serial; the comment and its summary table reference each other by number.
4. Consolidate multi-reviewer markups. Either combine onto one master in a coordination session, or collect each reviewer’s annotated PDF and merge — see collaborative annotation.
5. Tabulate comments. Produce a summary list (CSV or PDF) of comments by number, area, disposition, raised-by — see Annotation Summary.
6. Issue a frozen redline set. Flatten the annotations into the page, name with issue/date, and add to the project archive.
7. Respond per comment. Design team returns the next sheet issue (incorporating accepted changes with rev clouds and a rev number) plus a written response keyed to each redline comment number.
8. Archive every cycle. Editable working redline + frozen issued redline + response document + revised sheet — named consistently, retained per project rules.

Pitfalls that break a redline cycle

• Marking the original instead of a copy. Lose the clean baseline.
• Inconsistent colours and strokes. Reviewer-to-reviewer noise — adopt one office convention.
• Unnumbered comments. The response cannot reference them; nothing closes.
• Three reviewers, three separate redlined PDFs, no consolidation. Comments are addressed three times — or missed.
• Issuing as editable annotations. The document of record can be altered after issue.
• Strokes too thin for print. Marks vanish on a plotted sheet.
• Response delivered without a sheet revision. "Accepted" with no incorporated change is unfinished work.
• Uploading commercial-sensitive drawings to a cloud tool without checking whether they leave the machine.

Related reading and tools

• PDF annotation tools: the per-mark detail behind redlining.
• Collaborative annotation: multi-reviewer consolidation.
• Compare two PDFs: visually checking what changed between issues.
• Combining permit packages: issuing the redlined set as part of a submittal.
• Engineering stamps and seals: the sealed-issue counterpart.
• Add Comment: callouts and clouds.
• Annotation Summary: tabulating the comment list.
• Flatten PDF: freezing the issued redline set.
• All ScoutMyTool PDF tools: the full toolkit.

FAQ

What colour and stroke conventions should I use for redlines?

There is no single global standard, but the practical convention across most construction-document teams is: red for changes required or instructions to act on, green for resolved or accepted, yellow for discussion or pending. Use clouds (an irregular oval enclosing the changed area) to mark a change in scope, strikethroughs on elements to be removed, and callouts with text for new instructions. Keep strokes thick enough to read on a printed sheet, not just on screen. Document your office's convention once in a one-page redline standard and apply it consistently across projects, so the team and the consultants learn one set of meanings rather than guessing per drawing. Consistent conventions are what make a redline set readable at a glance.

Should redlines go on the drawing or on a separate markup layer?

In a PDF workflow the redlines live as PDF annotations on top of the drawing page, which is functionally a markup layer — you can show or hide them, the underlying drawing is not altered, and you can flatten the redlines into the page when you want to issue a frozen redline copy. Treat the redlines as a working layer during review (kept editable, multiple reviewers contributing), and flatten only when you issue the redline set as a document of record. Keep the unredlined original drawing in your archive so you can reproduce a clean copy of the issued sheet at any time. The PDF craft is the same as for any annotated drawing — see the general annotation-tools guide for the per-tool detail.

How do I number redline comments so the team can act on them?

A redline comment is only actionable if the responding party can identify it unambiguously, so number each redline as you create it — Sheet-A-101-01, Sheet-A-101-02, etc., or your office's equivalent scheme — and keep the numbering stable through the review cycle. Pair the numbered cloud or callout with a summary table at the back of the sheet (or as a separate consolidated PDF) that lists every comment by number, its disposition, who raised it, and the response. Numbering makes the redline set referenceable in meetings, emails, and RFIs, and turns it from a scattered pile of marks into a closeable list. This is exactly how the construction RFI process scales — see the marking-up annotation tools and submittal-review patterns.

How do I consolidate redlines from multiple reviewers?

On any non-trivial project, multiple disciplines and parties review the same drawing — architect, structural, MEP, the client, contractor. Each marks up their own copy. To consolidate, either (a) hold a coordination session and combine the markups onto one master PDF as a single set, or (b) collect each reviewer's annotated PDF and use a combine-comments workflow that pulls all annotations onto a single sheet. As a PDF craft, the first approach is simpler when the reviewers are in the same room; the second is necessary when they are not. Either way, produce one consolidated redline set per issue cycle, numbered and tabulated, so the design team responds to one document rather than three. Consolidation is what stops the same comment being addressed three times and a different comment being missed.

When and how should I issue a redline set as a document of record?

When the review cycle on an issue concludes, you typically need a frozen redline-set document of record — the sheet as it was redlined, with all comments in place, at that point in time. To issue it, take the live (editable) redline copy, flatten the annotations into the page so the marks are baked into the PDF, name the file with the issue/date (sheet/rev-redline-YYYY-MM-DD), add it to the issue archive, and distribute the flattened copy. Keep the editable redline copy separately if the team will continue working on it. A frozen, flattened, dated redline set is what supports a coordination meeting record, a contract dispute, or a later review of what was raised and when — issuing it correctly is the same discipline as issuing any drawing revision.

How should the design team respond to redlines?

Once the redlined set is issued, the design team responds comment by comment in the order numbered, with a clear disposition for each — accepted (and incorporated into the next sheet revision), accepted with modification (and a description of the change), rejected (with a reason), deferred (to a later cycle, with a reason). The response is best produced as a written response document keyed to the redline comment numbers, accompanied by a sheet revision that incorporates the accepted changes (marked with rev clouds and rev numbers for the formal issue). Returning a green-cloud redline copy can be a useful interim, but the document of record is the next sheet issue plus the written response — that is what closes the cycle properly.

Is it safe to redline drawings in an online tool?

Construction drawings carry commercial and sometimes contractual sensitivity, so prefer a tool that processes files locally. ScoutMyTool annotates, comments, merges, and flattens entirely in your browser tab, so the drawing set never leaves your machine. For confidential or contractually-restricted project work, confirm the tool does not upload before using it, and follow your project agreement for redline distribution and retention.

Citations

1. Wikipedia — “Markup language,” the broader sense of the markup conventions. en.wikipedia.org/wiki/Markup_language
2. Wikipedia — “Construction document,” the documents being redlined. en.wikipedia.org/wiki/Construction_document
3. Wikipedia — “Request for information,” the construction RFI process tied to redline review. en.wikipedia.org/wiki/Request_for_information