All articles
Updated

Published by Deta

Tracing the Thread: Managing Design Markups and Decisions Throughout Construction

How drawing reviews, submittals, site observations, RFIs, and revisions connect—and what makes their record useful through construction and handover.

Architecture & constructionIdeas · Coordination · Construction · Handover
Design team comparing architectural and services drawings around a table

Coordination brings related drawings and the people responsible for them into the same discussion.

A simple modification on a floor plan rarely stops with a single line. Moving a doorway triggers a cascade of consequences: partitioning shifts, light switches require relocation, door schedules need updating, and subcontractors must adjust their pricing. Months later, during demolition, an unmapped utility might force yet another revision. Long after construction wraps up, someone operating or renovating the building will need to know why that door ended up where it did.

These exchanges form part of the professional work surrounding the drawings. AIA Contract Documents describes instruments of service as the drawings, specifications, and other materials through which design professionals develop and communicate their work. Markups participate in that process: a loose sketch can explore an option, while a returned review comment can explain a decision that others must act on.

That flexibility creates the difficulty. The same red line can mean “what if,” “please clarify,” or “revise and resubmit.” Its appearance alone cannot tell the next reader which. As a markup becomes part of the project record, it needs to retain who made it, which drawing they saw, its purpose, and what followed. The doorway’s journey shows why that context matters.

Design Exploration and Spatial Coordination

In early project stages, markups serve as exploratory tools. A quick sketch of an entrance gives a client something concrete to evaluate while allowing the designer to test spatial flow. An unresolved note or open question on a sketch is not a flaw—it actively records an avenue worth pursuing.

As an option gains approval, review shifts from design exploration to technical coordination. The RIBA Plan of Work 2020 designates Stage 3 as the phase for spatial coordination, where architectural and engineering information is coordinated before detailed technical documentation begins.

At this stage, a directive like "move opening" is merely the starting point. Coordinated design review must ask the broader questions:

  • Does the light switch still fit on the adjacent wall stub?
  • Does the door tag match the door schedule specifications?
  • Which consultants need to revise adjoining junction details?

An effective markup identifies these interdependencies, assigns explicit follow-up actions, and documents the rationale behind decisions so future reviewers do not have to waste time reconstructing the context.

Submittal Review: Bridging Design and Procurement

Shop drawings and product submittals represent the contractor’s and supplier’s interpretation of how design intent will be physically fabricated and installed. Timing and thoroughness in this phase are critical: incomplete packages stall decisions, while delayed responses can cause fabrication backlogs and jobsite delays.

For the doorway, a comment on the frame may depend on hardware information that has not arrived. Bill Schmalz’s 2017 Submittal Triage recommends checking completeness and required reviewer involvement early. That check gives the markup its context: what information was available, and what remained unresolved when the reviewer responded.

The AIA–MBA Joint Committee recommends coordinating related submittals. In the record, the returned frame comments should therefore remain identifiable with the package reviewed and its related hardware submission. A later reader needs to distinguish an unanswered coordination question from an accepted arrangement.

Once returned, those comments become part of the review record. Action stamps, written comments, and status designations need to agree so the recipient can distinguish a request for revision from permission to proceed under the project’s procedures. Further discussion should not obscure what the returned package actually said.

Field Realities: Documenting Site Conditions

Construction routinely reveals physical conditions that could not be verified during design. When demolition uncovers a hidden utility line directly across a proposed doorway, the design team needs precise, objective field information to evaluate potential solutions.

Two construction professionals relate a doorway observation to a drawing and a site photograph

The plan locates the observation; the photograph records the visible condition.

Field documentation requires a clear separation between observation and action:

  • The Plan identifies the physical location of the issue.
  • The Photograph captures the visible field condition. As recommended by AIA site photography guidance, photos should be linked directly to field-report observations, shot from angles that clearly explain the conflict, and include scales or context views (e.g., pairing a close-up of the obstruction with a wide shot showing its location relative to the overall space).
  • The Written Record logs essential facts: opening ID, date, drawing revision used, and any physical measurements taken.

Crucially, project teams must keep the statement "existing service line crosses proposed opening" separate from "shift opening 300 mm toward corridor." The former is an objective observation; the latter is a proposed design change that requires formal technical review and approval.

Managing RFIs and Tracking Milestones

Requests for Information (RFIs) exist to route technical inquiries to the appropriate design professional. A high-quality RFI clearly states the conflict, provides context and supporting documents, and explicitly identifies which ongoing work is delayed pending a resolution.

A sketch proposing a new doorway position may help answer the RFI, but the record must show when that proposal became an agreed response. AIA’s 2017 construction administration recommendations caution against introducing unacknowledged redesign through RFIs or submittals. Retaining the question, response, and affected drawing together makes the change explicit.

Resolving a door location via an RFI often requires updated details, schedule revisions, and explicit instructions to field personnel. Simply issuing an RFI answer does not automatically authorize extra cost or physical work—that authority depends on formal contract change management procedures.

To prevent critical loose ends, project teams must track the distinct milestones of a change:

MilestoneWhat It EstablishesWhat May Still Remain Unresolved
Question AnsweredThe technical response addresses the site condition.Related design impacts and any required change pricing.
Documents UpdatedDrawings and schedules reflect the decision.Distribution to trade contractors and field execution.
Work Carried OutPhysical installation or alteration is completed.Required field inspection, testing, or sign-off.
Follow-Up RecordedInspection outcomes and verification are logged.Any outstanding exceptions.

Closing an RFI query in a tracking log must never cause incomplete downstream execution or document revisions to disappear from management view.

Revision vs. Status: Clarifying Permitted Drawing Use

When a revised drawing is issued, reviewers must establish two critical facts: what specifically changed, and what the drawing is authorized to be used for. An updated file date alone answers neither question.

The UK BIM Framework’s 2020 Guidance Part C, now listed in the IMI Framework’s archived guidance, stresses the vital distinction between a drawing's revision level (tracking changes) and its status code (defining permitted use). Information shared for review and comment is distinct from information authorized and accepted for construction. The conventions belong to the UK framework; contractual authority depends on the project’s agreed procedures.

While automated CAD/BIM overlays can highlight geometric differences—showing that a doorway moved—they cannot reveal whether that shift fully resolves a pending query or coordinates with other trades. For this reason, original markups should remain linked to the specific drawing version on which they were written, preserving exactly what the reviewer evaluated at that point in time.

Creating a Handover Record that Endures

At project completion, documentation transitions to a new user group: facility managers, maintenance technicians, and future renovation teams. A final record drawing showing the door's final location will not explain why it was shifted to avoid a hidden utility.

AIA–MBA guidance on recording construction changes highlights that record drawings assembled from approved shop drawings, change orders, and contractor sketches must clearly convey reality without asserting unverified precision—especially regarding concealed elements.

A comprehensive handover relies on complementary records, each serving a distinct function:

  • Punch Lists track incomplete or non-conforming items prior to completion.
  • Commissioning records, described in WBDG guidance, include issue-resolution logs, verification reports, and information needed for operation.
  • Operational & Aftercare Information, described in RIBA Plan for Use, provides maintenance training, operational guidance, and post-occupancy evaluation context.

The challenge is to preserve both the open discussion and the moments when something was settled or circulated. A working markup can keep developing; the copy returned to a contractor must remain identifiable as the copy they received. That distinction carries the doorway’s history beyond the people who remember the conversation.

How Deta Fits into the Project Record

Deta connects three parts of the record: base PDF versions, collaborative markup branches, and issued copies. Reviews can evolve while the drawing they refer to—and the copy circulated—remain identifiable.

THE DRAWING AND ITS RECORD
One plan, connected reviews
Explore the tree to see the base document, a markup branch, and an issued copy.
A1.1 · Ground floor planV2.2
Southern Serenity ground floor plan by Design with FRANK1
AI-generated example of a timber-framed interior with electrical rough-in01 Framing & servicesAmira Silva · Site observation
Branch
A shared space for the review
Markups, notes, and photographs on a particular base version.
Site photographs and notes sit alongside the drawing in a separate branch. The team can return to the observation in the context of the version reviewed.
Amira Silva · Site architectMaya Chen · Architect
Versions
›Issued records1
›Issued records1
Real Southern Serenity plan by Design with FRANK. Illustrative history, markups, stamp, and fictional participants; the same sheet represents both versions here. The site photo is AI-generated.

Review together on a branch

Named branches keep consultant reviews and site observations separate on the same PDF version. The tree identifies who started each branch and when; colleagues can add markups, notes, and photographs together.

Carry the review into the next version

A revised PDF becomes a new version, preserving the earlier drawing and its reviews. Compare the base PDFs, then copy a branch forward to continue coordination. Reviewers still check that carried-forward comments fit the revised drawing.

Retain the copy you issue

Issue saves a dated PDF with the markups burned in and links it to the tree. Later branch edits leave that copy unchanged. Distribution and approval remain part of the project’s agreed procedures.

The working review stays open to change; the issued copy preserves what was put forward.

Explore Deta’s PDF markup and drawing review workflows for architects, from collaborative reviews to version control and site follow-up.