PM Role

The PM is the integrator between shop, engineering, and field.

Key Responsibilities

Maintain scope integrity
Control schedule and budget
Drive coordination meetings
Resolve conflicts early

Department Checkpoints

Shop

Fabrication readiness
Release sequencing

Engineering / Drafting

RFI resolution
Approved-for-fabrication drawings

Field

Install logic
Access and logistics

Deep Dive (Expanded): Project Manager as the "Information & Flow Controller"

In glazing/facades, your PM job is not just "manage paperwork." Your real role is to control flow across:

Engineering (design → buildable drawings)
Shop (drawings → fabricated parts)
Field (parts → installed façade)

Your success metric is simple:

No surprises. No missing information. No idle crews. No fabrication rework. No field rework.

That happens when the PM becomes the single source of truth and runs a tight "control loop" weekly (and daily for hot items).

4.1 PM Operating Doctrine

The PM owns three things:

Truth (schedule + scope + constraints)
Readiness (materials + drawings + manpower alignment)
Interfaces (scope overlaps, tie-ins, trade boundaries)

The PM does NOT own:

How a draftsperson details a mullion (Engineering Manager owns quality)
How the shop fabricates (Shop Foreman owns process)
How the field sets anchors (Foreman owns execution)

But the PM owns whether they have what they need on time.

4.2 PM Control System (Weekly Loop)

Non-negotiable weekly cadence:

Engineering coordination meeting
Shop release meeting
Field readiness meeting
PM/Super dashboard review
GC coordination meeting

Each meeting feeds the next. If you don't do this, you're reacting instead of managing.

4.3 Engineering Coordination (Zero-Error Engineering Handoff)

PM Goal with Engineering

Engineering should never wonder:

"What elevation is next?"
"What's holding fabrication?"
"Which detail is most critical?"
"What's the site condition reality?"

PM Deliverables to Engineering (Weekly Package)

Provide these in a single "Engineering Packet" folder/email:

Engineering Priority List (Top 10)
- Elevation/area
- Deadline (needed for shop release date)
- Risk rating (R/Y/G)
- Dependencies (RFIs, approvals, site conditions)
Critical Tie-In Register
- Every transition detail
- Who owns what (Nucleus vs other trade)
- Confirmed vs unconfirmed
- Required RFIs
RFI & Submittal Alignment Log
- RFIs that affect drawings
- Which sheets/details are impacted
- Current status
- "No release until resolved" flags
Field Condition Feedback
- Photos with markups
- As-built dimensions or survey points
- Anchor embed conditions
- Tolerance conflicts
Release Map
- What can be released now (approved + clear)
- What must wait (pending info)
- What needs partial release strategy

PM Rules for Engineering Efficiency

Never dump 200 sheets and say "review all."
Give engineering the next move: "Release Elevation A1-A3 by Friday; A4 blocked by RFI-12."
Engineering must know sequence: what's next in the field.
Engineering must know shop constraints: what is easiest/hardest to fabricate.

"Zero Error" Engineering Gates

Before any release to shop:

☐ Approved submittals align with drawings
☐ RFIs affecting detail are closed or documented for release risk
☐ Field conditions verified (dimensions, embeds, slab edges)
☐ Parts and assemblies match BOM/parts list structure
☐ Key sheets exist for shop + field

4.4 Shop Coordination (Fabrication Flow, No Missing Parts)

PM Goal with Shop

Shop should never ask:

"Is this approved?"
"Where's the parts list?"
"Which revision is correct?"
"When does the field need it?"

PM Deliverables to Shop (Release Package)

Every fabrication release must include:

Release Cover Sheet
- Project
- Area/elevation
- Release date
- Revision/date stamp
- "Fabricate by" date
- "Deliver by" date
- Notes on finish protection and handling
Fabrication Drawings
- Correct revision
- Clearly labeled
- Includes key sheets
Parts List / BOM
- Part number
- Qty
- Finish
- Location
- Bundle/shipping tag
- Field install zone reference
Hardware & Misc Materials List
- Anchors
- Fasteners
- Shims
- Setting blocks
- Gaskets
- Sealant accessories
Quality Hold Points
- Items requiring QA check before ship
- High-risk assemblies
Delivery Plan / Packaging Instructions
- Pack by elevation
- Pack in installation sequence
- Protect exposed finishes
- Label bundles per field zone

Shop Coordination Meeting (Weekly)

Agenda:

What's released this week?
What's blocked and why?
What's fabricated and ready?
What's shipped and where is it staged?
What is missing (misc hardware, gaskets, anchors)?
What is the next field need?

"Zero Error" Shop Gates

Before shipment:

☐ Bundle labels match field elevation/zone
☐ Qty verified vs BOM
☐ Finishes inspected and protected
☐ All misc hardware included
☐ Packing list scanned and uploaded (ACC/Procore folder)

4.5 Field Coordination (No Idle Crews, No "Where's the Material?")

PM Goal with Field

Field should never:

Wait on material
Install wrong revision
Guess at tie-ins
Lose track of inventory

PM Deliverables to Field (Weekly + Daily Hot Items)

Field Install Plan (2-Week Lookahead)
- Elevations scheduled
- Crew size planned
- Required materials list
- Access requirements
- GC prerequisites (scaffolds, lifts, laydown)
Material Status Map
- Onsite
- At shop
- In transit
- Not ordered / delayed
- Missing misc items
Install Packet by Elevation
- Key sheet
- Detail callouts
- Approved submittal excerpt
- RFI clarifications
- Sealant requirements for that zone
Daily "What's Coming Tomorrow" Note
- What the crew will install next
- What must be staged
- What constraints exist

Field Coordination Rules

PM must ensure foreman has one folder that is always current:
- "Current Approved Drawings"
- "Current RFIs affecting install"
- "Current Material Receipts + packing lists"
PM must provide simple maps, not giant plan sets:
- "We are installing Gridline 1-5 Levels 3-5"
PM must track constraints:
- Access, lift availability, laydown, crane picks, swing stages

"Zero Error" Field Gates

Before installing an elevation:

☐ Material staged and inventoried
☐ Correct revision drawings confirmed
☐ RFIs clarified and communicated
☐ Sealant/joint plan confirmed
☐ Access and laydown confirmed with GC

4.6 How the PM Makes All Three Run Smooth (The "Single Source of Truth" System)

The PM must build 5 core tools. These are the backbone of zero-error execution.

Tool 1 — Master Constraint Log

Tracks everything that can stop work:

Submittals
RFIs
Long-leads
Access
Trade conflicts

Rule: If it's not in the log, it doesn't exist.

Tool 2 — Material Control Ledger

Tracks:

Ordered
Received at shop
Shipped
Received onsite
Installed

Include:

Packing lists uploaded
Bundle tags match elevations

Tool 3 — Release Register

Tracks every release to shop:

Area/elevation
Revision
Date released
Dependencies cleared
QA hold points

Tool 4 — 2-Week Lookahead Plan

Shared between PM + Super + Foreman + Shop:

What's being fabricated
What's being delivered
What's being installed

Tool 5 — RFI/Submittal Impact Matrix

Shows:

Which RFI impacts which elevation
Which submittal impacts which release

4.7 "Zero Error" Practices (What Separates Elite PMs)

Practice 1 — Package everything

No scattered emails. No multiple spreadsheets. One controlled package per release.

Practice 2 — Make the shop your customer

If shop succeeds, field succeeds. Give shop what they need with clarity.

Practice 3 — Make the field your priority

Idle crews burn profit faster than almost anything. Your goal is to keep them installing.

Practice 4 — Control revisions ruthlessly

One wrong revision in the field can destroy weeks of margin.

Practice 5 — Push constraints early

If something is trending yellow, treat it like red until proven otherwise.

4.8 PM Checklist (Engineering + Shop + Field Control)

Daily PM Checks (15 minutes)

☐ Any new RFIs/submittals affecting releases?
☐ Any deliveries missed or shifted?
☐ Any shop releases needed in next 72 hours?
☐ Any field scope at risk of idle time?
☐ Any GC access issues?

Weekly PM Control Checks

☐ Engineering priority list issued
☐ Shop release register updated
☐ Material ledger updated
☐ Field install packets issued
☐ Dashboard reviewed with Super

NucleusCommand