Mark Up a Plan Set for Field Use

A. Finished-Package Specification

Deliverable set: one markup legend; one marked field set covering every sheet requiring critical, coordination, sequencing, or inspection markup; one cross-sheet reference index; one field-checklist index; one distribution log; and one archive record of superseded field sets.

B. Deliverable Schedule (Component Schedule)

Component	Quantity	Source	Required Fields	Preparation / Purpose
Markup legend	1	Established before markup begins	Colors, symbols, clouds, tags, comment formats	Fixes a consistent system before any sheet is marked
Marked field set	1 per required sheet	Current approved plan set	Critical dimensions, field verification, trade interfaces, sequence, hold points, revisions, open items	Delivers the controlled field communication layer
Cross-sheet reference index	1	Frequently used details, sections, schedules, specifications	Topic, source sheet, destination sheet, status	Speeds field navigation to supporting information
Field-checklist index	1	Marked sheets and related discipline checklists	Sheet, related checklist, chapter source	Links the marked set to the checklists that depend on it
Distribution log	1	Issued field sets	Recipient, issue date, revision, replacement instructions	Controls who is using which version of the field set
Archive record	1	Superseded field sets and closed markups	Sheet, revision, supersede date, replacement reference	Preserves the audit trail while removing outdated sets from field use

C. Source Material Takeoff

• Primary source: the current approved plan set, specifications, revision log, approved RFIs, and approved submittals available at the time this chapter begins.
• Governing source: the Chapter 17 conflict register, including every open item and every approved response received to date.
• Reference tools: one straightedge, sticky flags or tabs, and a fixed set of markup colors and symbols.
• Recording medium: one authorized paper or digital markup platform capable of holding all six deliverable components listed in Section B.

D. Acceptance Standards

Check	Standard
Legibility	Every marked sheet remains readable as a source document; no original linework, text, or dimension is erased or obscured
Currency	Every marked sheet reflects the current approved revision; no superseded revision remains in the active field set
Open-item visibility	Every unresolved RFI or conflict is marked clearly as open; no open item is presented as resolved
Observation separation	Every field observation is labeled as an observation and dated and authored; none is presented as design information
Attribution	Every marked sheet records markup author, date, purpose, and source revision
Distribution control	The distribution log accounts for every recipient of the current field set and every replaced prior issue

E. Preparation — Confirm Source Documents and Markup System

1. Obtain the current approved plan set, specifications, revision log, approved RFIs, approved submittals, and conflict register. Collect the complete set of governing documents identified in Section C before marking any sheet.
2. Confirm every source document's issue and revision before markup begins. Cross-check each sheet against the current revision log; do not mark a sheet whose current status has not been confirmed.
3. Select the authorized paper or digital markup platform and establish version control. Record the platform and version-control method on the Markup Authorization Record.
4. Create a markup legend for dimensions, field verification, trade interface, sequence, inspection, approved change, question, completed item, and hold point. Define one distinct symbol or color for each category before marking begins.
5. Assign markup colors, symbols, clouds, tags, and comment formats consistently. Record the finished assignment on the markup legend template and apply it without exception.
6. Record markup author, date, purpose, source revision, and distribution status. Enter these fields on every marked sheet before adding further annotation.
7. Preserve original linework, text, dimensions, and references so they remain readable. Verify legibility on a sample sheet using the selected markup colors before marking the full set.
8. Do not erase, overwrite, or obscure source information. Confirm the markup platform supports layered annotation without altering the underlying source file or sheet.

F. Critical Dimension and Field-Verification Marking

1. Mark the controlling overall dimensions, grids, baselines, elevations, centerlines, and layout references. Use the legend's dimension symbol on every sheet where a controlling reference governs later work.
2. Highlight dimensions that must not be scaled or inferred. Apply the "do not scale" flag from the legend at each written dimension identified during Chapters 1 through 16 as controlling.
3. Mark dimensions and conditions requiring field verification before fabrication or installation. Apply the field-verification symbol at every location carried forward from the discipline chapters or the Chapter 17 register.
4. Identify property, survey, benchmark, utility, and site-control information needed in the field. Mark these locations on the site and foundation sheets using the field-verification symbol.

G. Coordination, Trade Responsibility, and Sequencing Marks

1. Mark foundation, framing, opening, equipment, and penetration locations requiring cross-trade coordination. Apply the trade-interface symbol at every location identified in the Chapter 17 conflict register or the discipline checklists.
2. Identify trade responsibility only where the approved scope and documents establish it. Label a trade interface only when the contract, division responsibilities, or approved coordination process assigns it; leave unassigned interfaces marked as open items.
3. Label owner-furnished, contractor-furnished, delegated-design, work-by-others, allowance, alternate, and excluded items. Apply the appropriate label directly at each item's location from the governing specification or schedule.
4. Mark sequencing dependencies such as backing before closure, rough-in before cabinets, flashing before cladding, or inspection before concealment. Use the sequence symbol and a brief cross-reference to the governing note or detail.
5. Mark pre-pour, framing, rough-in, air-seal, waterproofing, fire-stop, roofing, envelope, equipment, testing, and final inspection hold points. Apply the hold-point symbol at each location where work must stop for inspection, testing, or approval.
6. Mark approved mockups, samples, shop drawings, submittals, and manufacturer-review requirements. Apply the approved-change or hold-point symbol as appropriate, referencing the submittal number.
7. Add field reminders that restate document requirements without introducing new design. Write each reminder as a restatement of an existing note, detail, or specification requirement, with its source reference.
8. Mark access, service, clearance, protection, storage, and temporary-condition concerns. Apply the field-use symbol at each location documented in the discipline chapters.

H. Revision, RFI, and Open-Item Marking

1. Cloud and tag approved revisions and approved RFI responses incorporated into the set. Use the approved-change symbol and cite the revision number or RFI number and its approval date.
2. Identify unresolved RFIs and conflicts clearly as open items. Use the question symbol and cite the Chapter 17 conflict register item number at each open location.
3. Do not convert an unanswered question into a presumed field direction. Confirm no open item has been marked with the approved-change or completed-item symbol.
4. Mark areas where work must stop or remain exposed pending clarification or inspection. Apply the hold-point symbol together with the related open-item citation at each affected location.

I. Cross-Reference, View, and Field-Observation Marking

1. Add cross-sheet references to details, sections, schedules, specifications, and submittals used most frequently in the field. Record each reference in the cross-sheet reference index with source and destination sheet numbers.
2. Create room, elevation, area, or trade-specific views where authorized while retaining source references. Build any additional view only from information already present in the approved documents, and cite its source.
3. Link photographs, field measurements, and verified conditions to exact locations and dates. Attach each field observation to its marked location with author, date, and method of verification.
4. Label field observations separately from design information. Apply a distinct observation label from the legend so no observation is mistaken for a design requirement.
5. Create a field-checklist index linked to the marked sheets. List every discipline checklist from Chapters 3 through 16 that applies to each marked sheet.

J. Review and Publication

1. Review the markup against the Chapter 17 conflict register and approved responses. Confirm every register item is reflected as either an approved change or a clearly marked open item.
2. Check that superseded revisions, closed questions, and outdated reminders have been removed or archived. Compare every marked sheet against the current revision log a second time before publication.
3. Print or publish the field set at legible size and verify graphic scales where scaling is authorized. Confirm reproduction size and check the graphic scale before authorizing any field scaling.
4. Protect the field set from weather, uncontrolled editing, and unauthorized distribution. Confirm the platform or physical set has an appropriate protective cover, access control, or file permission.
5. Create a distribution log identifying recipients, issue date, revision, and replacement instructions. Record every recipient of the current field set and the replacement instructions for any prior issue.
6. Perform a final quality check for legibility, current status, complete references, consistent symbols, and unresolved-item visibility. Use the Acceptance Standards table in Section D as the final check.
7. Archive the prior field set and issue the new set through document control. Move every superseded field set to the archive record and confirm the new set is the only version distributed as current.