Practical checklist
What this article covers
A copyable issue register with status definitions and one hypothetical example; distinguish logged, resolved and reviewer-approved.
An architectural redline tracker should connect the original comment, the instruction someone authorized, and the returned drawing that a reviewer checked. A tick beside a markup is not enough if nobody can identify which revision contains the change.
Use the proposed register below for a defined drawing package. It is an operational worksheet, not a substitute for design review or permission to issue drawings.
Build a record that survives a revision
Start with a package identifier, source drawing revision, marked-up file and named review lead. Give each comment a stable ID. Keep that ID when the drawing changes; add the new revision to its history.
| Field | What to record | Why it matters |
|---|---|---|
| Comment ID and location | Original ID, sheet, view and marked region | Finds the request again |
| Original observation | Author's wording and source file | Preserves what was actually raised |
| Agreed instruction | Authorized response and decision reference | Separates a question from a direction |
| Production owner | Person taking the next action | Avoids an unassigned item |
| Returned evidence | File revision and location of the response | Makes checking repeatable |
| Reviewer outcome | Name, date, result and remaining question | Separates pickup from acceptance |
A provider's sample issue report illustrates findings with identifiers and next actions. Our register adds an explicit connection between the decision and the returned evidence; it is not that provider's required format.
Keep status names tied to evidence
Use a small, agreed sequence: Logged, Clarification needed, Ready for pickup, Submitted for check, and Reviewer confirmed. Add Reopened when a later change invalidates the checked result. These are suggested project states, not software defaults.
“Submitted” means production believes it has responded. “Confirmed” means the named reviewer has checked that response within the assigned scope. Neither label independently authorizes construction or a wider design decision.
Bluebeam documents markup back-checking and status history. For a Revu-specific setup, use the markup status workflow; keep the same distinction between recording progress and granting authority.
Hypothetical example: a room label needs a decision
In this fictional package, comment R-017 asks to change a room label from “Meeting” to “Project Room.” A second reviewer asks to retain “Meeting.” The drafter links both comments, records the conflict and asks the designated decision owner to choose the wording.
Once a recorded answer is available, the drafter updates the assigned sheets and submits their revision references. The reviewer checks those locations before confirming R-017. If the same label appears elsewhere, record whether those occurrences are inside the agreed task.
Use a conflicting-redlines decision log for that unresolved choice. Do not silently discard the less recent comment.
Close the package without hiding exceptions
Before the next handoff, identify comments with no owner, no authorized instruction or no returned evidence. Use the pickup acceptance checklist for checking completed changes and the comment consolidation worksheet when several review sets overlap.
Where a comment concerns uncertain existing-condition information, link its underlying evidence question to the scan-to-BIM acceptance checklist. A drawing correction cannot establish facts that were never verified.
Nest's redline pickup guide explains the broader production handoff. For a defined package, discuss CAD drafting support with the review owner, source files and unresolved items identified.
Related guides and services
Keep the production handoff connected to the wider workflow:
Need help with current production work?
Tell us which drawings, models, visualizations, or review packages need attention. We can review the assignment, confirm availability, and explain whether a project package or dedicated monthly support fits.
Book a project callSend a project brief