Architectural Redline Pickup Acceptance Checklist

A redline pickup is ready for acceptance when the assigned reviewer can trace each authorized instruction to the returned drawing and record whether it was implemented within scope. A completed markup list alone does not demonstrate this.

This proposed checklist focuses on checking the response to comments. It is not an as-built survey, a code review or permission to issue drawings.

Identify the three records before comparing

Keep the source drawing revision, the authorized markup or decision, and the returned revision together. They should be clearly related, not necessarily carry the same revision identifier: a returned drawing normally needs its own traceable identity under the project's document rules.

If the reviewer received a different source set from the drafter, resolve that mismatch before judging the pickup. The redline tracker can connect the records.

Use an evidence-led acceptance sheet

The sample issue report from Redline Markups illustrates linking findings with next actions. Our acceptance sheet adds the returned-file evidence needed to distinguish implementation from a statement that implementation occurred.

Review the agreed scope, including its referenced locations. Do not claim a complete package review if you checked only a sample.

Hypothetical example: the label changed but its reference did not

In this fictional assignment, P-009 authorizes changing a drawing-view title from “Lobby Plan” to “Reception Plan” and updating its identified sheet index entry.

The returned view title has changed, but the listed index entry still says “Lobby Plan.” Record a partial pickup, identify the two locations and return the specific remaining action to the drafter. Do not reopen unrelated design decisions or describe the partial result as fully accepted.

When the revised package arrives, check both locations again and retain the checked revision. If the instruction had covered only the view title, ask the review lead whether the index is an additional authorized task rather than silently expanding scope.

Resolve ambiguous comments before accepting them

Use the comment consolidation worksheet when multiple review sets hide duplicates or incompatible requests. A reviewer should not accept a guessed interpretation simply because the drawing looks tidy.

For Revu users, Bluebeam's back-checking guidance describes moving between markups and their list entries. Inspect the drawing evidence as well as the recorded status.

Return a limited, understandable outcome

Use outcomes such as accepted for the reviewed task, returned for correction, or awaiting a decision. State exclusions and unresolved items beside the outcome. Confirm who may authorize the next issue separately; the worksheet does not transfer that authority.

Nest's redline pickup support guide explains preparing a reviewable assignment. When discussing CAD drafting support, provide the comparison baseline and acceptance owner so the returned files can be checked against a clear request.