title: Construction Manager slug: construction-manager aliases: - General Contractor - Project Superintendent - Construction Project Manager - Site Manager category: Skilled Trades tags: - scheduling - critical-path - cost-control - site-safety - trade-coordination difficulty: advanced summary: >- The single throat to choke between an owner's intent and a finished, safe structure — sequencing trades and money so each can do its part without tripping over the others, and catching the problem while it is still cheap. contributors: - soul-atlas last_reviewed: null provenance: ai-generated created: '2026-06-27' updated: '2026-06-27' related: - slug: project-manager type: adjacent note: Same schedule-cost-scope craft applied to a physical, site-bound product - slug: architect type: collaboration note: Holds the design the CM builds and answers RFIs - slug: civil-engineer type: collaboration note: Holds the structural/site design the CM realizes - slug: cost-estimator type: collaboration note: Sets the budget the CM must hit - slug: construction-inspector type: collaboration note: Verifies the code compliance the CM is responsible for - slug: electrician type: collaboration note: One of the trades the CM sequences and coordinates specializations: - Project Superintendent - Preconstruction Manager - Cost / Project Controls Manager - Self-Perform Operations Manager country_variants: [] sources: - title: Construction Project Management (Gould & Joyce) kind: book - title: CPM in Construction Management (O'Brien & Plotnick) kind: book - title: OSHA 29 CFR 1926 (Construction safety standards) kind: standard status: draft reviewers: [] sections: - heading: Purpose markdown: >- A building is the most complex temporary organization most industries ever assemble: dozens of trades, thousands of materials, hundreds of decisions a day, all converging on a fixed site under weather, regulation, and a budget that was set before anyone knew what the ground hid. Construction management exists to make that chaos finish — on time, on budget, safely, and to the drawings — by sequencing the work, coordinating the trades, controlling the money, and absorbing the endless surprises without letting them cascade. The construction manager is the single throat to choke between an owner's intent and a finished, safe, occupiable structure. Without them, every project is a collision of independent subcontractors each optimizing their own scope while the whole drifts late, over, and dangerous. - heading: Core Mission markdown: >- Deliver the project safely, on schedule, within budget, and to the contracted quality — by sequencing the work and the trades so each can do their part without tripping over the others, and by catching the problem while it's still cheap. - heading: Primary Responsibilities markdown: >- The work is planning and scheduling (the critical-path sequence of every activity and the resources behind it), cost control (the budget, buyout, change orders, and cash flow), procurement and subcontractor management (buying out the trades and holding them to scope and schedule), coordination (resolving the daily conflicts between trades, drawings, and field reality), quality control (building to the drawings, specs, and code), and — above all else — site safety. Day to day a construction manager runs the look-ahead schedule, walks the site, chairs coordination meetings, processes RFIs and submittals, negotiates change orders, manages the inspection and closeout process, and spends enormous energy on the handoffs between trades where schedule and quality are won or lost. - heading: Guiding Principles markdown: >- - **Safety is the first deliverable, not a constraint on the others.** A project that injures someone has failed regardless of its schedule and budget. The walk-around and the stand-down come before the milestone. - **Sequence is everything.** You can't drywall before rough-in, can't pour before inspection. The plan is a dependency graph, and the manager's craft is keeping the critical path moving. - **Catch it on paper, not in the field.** A clash found in coordination costs an eraser; the same clash found after the slab is poured costs a demolition. - **The schedule and the budget are the same document.** Time is money in the most literal sense — every day of delay burns general conditions and liquidated damages. - **Manage the float, protect the critical path.** Slack is a resource to spend deliberately; the activities with none are where attention lives. - **Document everything.** On a project headed for a dispute, the daily log and the paper trail are the only truth that survives. - heading: Mental Models markdown: >- - **The critical path (CPM).** The longest chain of dependent activities sets the finish date; only delays on it delay the project, and only acceleration of it pulls the date in. - **Float as a budget.** Non-critical activities have slack; spending it knowingly is fine, spending it blindly turns non-critical work critical without warning. - **The cost-loaded schedule / earned value.** Progress is measured in value earned against value planned and spent (CPI/SPI), not in activities that "feel" done. - **The iron triangle (scope-cost-time, with quality and safety).** You cannot change one without moving the others; every owner request is a triangle adjustment. - **The trade-handoff as the failure point.** Most schedule and quality problems live at the seam between one trade finishing and the next starting; manage the seams, not just the spans. - **Risk register and the contingency.** Every project has known unknowns (weather, soils, permits); contingency is the priced reserve against them, and it's spent, not saved. - **Lean / Last Planner.** Reliable short-term commitments from the people doing the work beat a beautiful master schedule no trade believes. - heading: First Principles markdown: >- - A construction site is a temporary factory that is reconfigured daily; its output is a sequence, not a stockpile. - Every problem gets more expensive the further downstream it's discovered. - The plans are never complete or correct; the field always asks questions the drawings didn't answer. - You don't control the trades' labor directly — you control the conditions and sequence that let them be productive or not. - heading: Questions Experts Constantly Ask markdown: >- - Is anyone about to get hurt today, and what on this site could do it? - What's on the critical path this week, and what could knock it off? - What does this change really cost — in dollars, in days, and in ripple to other trades? - Is the next trade's predecessor actually done, inspected, and ready? - What do I know now that the budget and schedule didn't, and where's that going? - Which RFI or submittal, unanswered, stops work in two weeks? - Where's my contingency, and is what I'm spending it on a real unknown or a mistake I'm hiding? - heading: Decision Frameworks markdown: >- - **Schedule recovery.** When behind, analyze the critical path and choose among re-sequencing (free), overtime/added crews (costs money), and fast-tracking (overlapping design and build, adds risk) — never accelerate non-critical work. - **Change-order evaluation.** For every change, price the direct cost, the schedule impact, and the ripple to other trades; get it authorized before proceeding or eat it. - **Buyout / sub selection.** Award scope on the balance of price, schedule reliability, capacity, and past performance — the cheapest bid that can't deliver is the most expensive. - **Build vs. defer the risk.** Use the risk register to decide what to mitigate now (de-risk early) versus carry as priced contingency. - heading: Workflow markdown: >- 1. **Preconstruction.** Review drawings for constructability and clashes, build the budget and master CPM schedule, plan procurement and site logistics. 2. **Buyout.** Solicit, scope, and award subcontracts; lock in long-lead procurement. 3. **Mobilize.** Site setup, safety plan, permits, and the logistics of access, storage, and craft flow. 4. **Execute and coordinate.** Run the look-ahead schedule, daily walks, coordination meetings, RFIs/submittals; keep the critical path moving and the trades de-conflicted. 5. **Control cost and quality.** Track earned value, process change orders, run inspections and quality checks against spec and code. 6. **Close out.** Punch list, commissioning, inspections, as-builts, warranties, and owner handover. 7. **Learn.** Post-project review of estimate vs. actual and what the schedule missed. - heading: Common Tradeoffs markdown: >- - **Speed vs. cost.** Acceleration (overtime, more crews, fast-tracking) buys schedule at a premium and added coordination risk. - **Cost vs. quality.** Value-engineering to hit budget can erode the quality the owner is paying for; some substitutions are false economy. - **Self-perform vs. subcontract.** Self-performing buys control and margin but adds risk and overhead; subbing transfers risk at a price. - **Float consumption vs. flexibility.** Spending slack early to look ahead of schedule removes the buffer for the surprises still coming. - **Owner relationship vs. contract enforcement.** Eating small changes preserves goodwill; eating too many erases the margin and invites more. - heading: Rules of Thumb markdown: >- - Walk the site every day; the schedule lies, the site doesn't. - The cheapest time to fix anything is before it's built. - Protect the critical path; let non-critical slip if it must. - Get the change order signed before the work, or expect not to be paid for it. - A trade waiting on another trade is your problem, not theirs. - Document the day as it happened; memory and motive both fade by the deposition. - If two subs are pointing at each other, the answer is in the sequence you set. - heading: Failure Modes markdown: >- - **A safety incident** — the failure that overrides every other metric and can shut the job down. - **Critical-path slippage unnoticed** — float quietly consumed until a non-critical delay becomes the whole project's delay. - **Change-order chaos** — uncontrolled scope creep without authorization, destroying the budget and the paper trail. - **Trade stacking / out-of-sequence work** — too many trades crammed into the same space to recover time, killing productivity and quality. - **Buyout gaps** — scope that no subcontract covers, discovered in the field as a cost and a delay. - **Quality defects discovered late** — rework after enclosure, at multiples of the original cost. - heading: Anti-patterns markdown: >- - **Schedule by optimism** — a master schedule with no float and no risk reserve that no trade believes. - **Managing from the trailer** — running the job off reports instead of the daily walk, so problems are learned late. - **Lowest-bid buyout** — awarding scope to subs who can't perform, then chasing them all project. - **Crashing non-critical work** — spending money to accelerate activities that weren't holding the finish. - **Hiding contingency spend** — burning the reserve on hidden mistakes until it's gone when a real unknown hits. - heading: Vocabulary markdown: >- - **Critical path / CPM** — the activity chain that determines the finish date. - **Float / slack** — schedule slack on non-critical activities. - **RFI** — request for information; a formal question to the design team. - **Submittal** — contractor's product/shop-drawing data submitted for approval. - **Change order** — an authorized modification to scope, cost, or time. - **Buyout** — awarding subcontracts and locking procurement against the budget. - **General conditions** — the time-based cost of running the project (supervision, trailer, equipment). - **Punch list** — the closeout list of items to complete or correct. - **Earned value (CPI/SPI)** — cost and schedule performance indices. - **Liquidated damages** — contractual penalty per day of late completion. - heading: Tools markdown: >- - **Scheduling software** (Primavera P6, MS Project) — for CPM and resource planning. - **Project/cost management platforms** (Procore, Autodesk Build) — for RFIs, submittals, daily logs, and budget. - **BIM and clash detection** (Revit, Navisworks) — to find conflicts on paper before the field. - **The daily log and look-ahead schedule** — the operational and legal heartbeat of the job. - **Estimating software and the schedule of values** — for budget and progress billing. - **The site walk** — the irreplaceable instrument; reality lives there, not in the reports. - heading: Collaboration markdown: >- The construction manager is the hub of a temporary organization: the owner (who holds the intent and the money), the architect and engineers (who hold the design and answer RFIs), the subcontractors and trades (who do the work and own their scopes), suppliers, inspectors and the authority having jurisdiction, and the safety officer. The defining relationships are the ones at the handoffs — between design and field, and between one trade and the next — where the CM's coordination turns independent scopes into a coherent build. Friction is constant and structural: every party optimizes its own cost and schedule, and the CM's job is to align them to the whole, holding subs to scope while keeping the owner's trust through changes and surprises. - heading: Ethics markdown: >- Construction decisions are matters of life safety — for the workers on site and the public who will occupy the structure for decades — and the money involved creates constant pressure to cut corners that don't show. Duties: never compromise worker or public safety for schedule or budget, and stop work when it's unsafe; build to the code and the drawings even where a defect would be hidden; bill honestly and substantiate change orders rather than padding them; pay subcontractors what they're owed for work performed; and tell the owner the truth about cost and schedule early, when they can still act, rather than at the deadline. The gray zones — accepting a marginal substitution, allocating blame in a delay claim, deciding when "good enough" meets the spec — are where the CM's integrity protects both the people in the building and the people who built it. - heading: Scenarios markdown: >- **The slab is poured and the conduit's in the wrong place.** An electrician's RFI reveals that embedded conduit conflicts with a structural beam — and the slab is already scheduled to pour tomorrow. The CM stops the pour. The cost of a day's delay and a coordination meeting is trivial against the cost of chipping out a cured slab. They trace it to a clash that BIM coordination should have caught, resequence to resolve it, and tighten the coordination review so the next conflict dies on paper. Catch it on paper, not in the field. **Behind schedule on the critical path.** Steel erection ran two weeks late and the project is now behind. The instinct is to throw overtime at everything. The CM instead analyzes the critical path: only the activities on it move the finish. They accelerate steel and its immediate successors with added crews, re-sequence follow-on trades to work in parallel where the building permits, and leave non-critical work alone — recovering the date for the least money instead of burning cash on activities that weren't holding anything up. **A flood of owner changes.** Midway through, the owner keeps requesting "small" upgrades verbally, expecting them absorbed. The CM recognizes uncontrolled scope creep and resets the process: every change gets priced for cost, schedule, and trade ripple, and authorized in writing before work proceeds. It briefly strains the relationship, but it protects the budget, the paper trail, and ultimately the owner — who can now see what each "small" change actually costs before committing. - heading: Related Occupations markdown: >- The construction manager orchestrates the trades the Atlas captures individually — the **electrician**, **plumber**, **carpenter**, **ironworker**, and **heavy- equipment operator** whose sequenced work they coordinate. They share the schedule-cost-scope discipline of the **project manager** (the same craft applied to a physical, site-bound product) and the **operations manager**. The **architect** and **civil/structural engineers** hold the design the CM builds, and the **construction inspector** verifies the code compliance the CM is responsible for. The **cost estimator** sets the budget the CM must hit. - heading: References markdown: |- - *Construction Project Management* — Frederick Gould & Nancy Joyce - *Construction Management Fundamentals* — Knutson, Schexnayder et al. - *The Lean Builder / Last Planner System* — Lean Construction Institute - AIA and ConsensusDocs contract families - *CPM in Construction Management* — James O'Brien & Fredric Plotnick - OSHA 29 CFR 1926 (Construction safety standards)