Safety Plan, Change Management, and Project Controls Documentation

Safety Plan, Change Management, and Project Controls Documentation

This lab brings together three core project management disciplines into a single integrated workflow. By the end of this session you will have produced a site-specific safety and health plan, processed a complete change-order cycle, and prepared an earned-value status report—the same three deliverables a construction manager is expected to manage simultaneously on a live project.

Part 1: Site-Specific Safety and Health Plan

A site-specific safety and health plan is not a generic handout. It is a controlled document tailored to the exact hazards present on your project. OSHA construction standards (29 CFR Part 1926) establish the legal minimum; your plan must meet or exceed those requirements.

Hazard Identification is the foundation. Walk through the project scope and list every significant hazard category: excavation and trenching, fall hazards from elevated work surfaces, crane and hoisting operations, electrical hazards from temporary power or proximity to energized lines, and confined spaces if the scope includes manholes, vaults, or enclosed structures. Each hazard must be paired with a control measure—elimination, substitution, engineering control, administrative control, or PPE, in that hierarchy.

PPE Matrix by Task translates hazard controls into a table every worker can read. List each task in one column and the required PPE in the next: hard hat class, eye protection type, glove specification, high-visibility vest, foot protection, and any task-specific items such as fall protection harnesses or arc-flash rated clothing. This matrix becomes a training aid at toolbox talks.

Emergency Action Plan must include site-specific evacuation routes drawn on the site plan, assembly point locations, names and contact numbers for emergency coordinators, procedures for contacting 911 and the nearest hospital, and protocols for specific emergencies such as fire, utility strike, or medical event. Generic language fails a real emergency.

Incident Reporting Procedure defines what gets reported, to whom, and by when. Near misses must be reported, not just injuries. The procedure must identify the responsible supervisor, the form used, and the timeline for OSHA recordable incident submission consistent with OSHA requirements.

Toolbox Talk Schedule demonstrates that safety training is ongoing, not a one-time orientation. Schedule weekly talks keyed to the upcoming work activities—excavation week, steel erection week, electrical rough-in week—so the topics are relevant when workers need them.

Subcontractor Safety Compliance section establishes that every subcontractor must submit their own safety plan, designate a competent person on site, and comply with your project safety requirements as a condition of contract.

In this lab you will upload your plan to Procore as a controlled document, assign it a version number (e.g., Rev 0), and set the distribution list. Version control ensures everyone on the project team is working from the same current document.

Part 2: Change-Order Administration

Changes are inevitable. The discipline is in processing them completely and accurately every time.

The cycle begins with a Request for Information (RFI) when a field condition or design gap is discovered. The RFI documents the question, the party responsible for answering, and the date issued and answered. When the owner directs a change, the contractor prepares a Proposed Change Order (PCO) that re-prices the affected quantities using the same unit costs as the original estimate and identifies any schedule impact in working days. A Change-Order Log in Procore tracks every PCO by number, description, status, dollar value, and schedule days.

Once the owner accepts the PCO, both parties execute a formal change-order document. The AIA G701 (or equivalent) is the industry-standard form: it references the original contract, describes the change in scope, states the agreed price adjustment and revised contract sum, and states the revised contract time. After execution you must update your estimate cost codes and revise your CPM schedule to reflect the added or deleted work. Skipping either step creates a gap between your contract records and your project controls.

Cost and schedule discipline: recalculate the critical path after each approved change. A scope addition that lands on the critical path extends contract duration; one that falls on a float-rich path may not. Document both the cost impact and the schedule impact even when one of them is zero.

Part 3: Earned Value Management

Earned Value Management (EVM) gives you a single, integrated view of cost and schedule performance at any point in the project.

Key formulas:

• Planned Value (PV): the budgeted cost of work scheduled through the status date
• Earned Value (EV): the budgeted cost of work actually performed (% complete × budget)
• Actual Cost (AC): the real cost incurred for the work performed
• Schedule Performance Index (SPI): EV ÷ PV (above 1.0 = ahead of schedule)
• Cost Performance Index (CPI): EV ÷ AC (above 1.0 = under budget)
• Estimate at Completion (EAC): Budget at Completion (BAC) ÷ CPI

An SPI below 1.0 means you have accomplished less work than planned. A CPI below 1.0 means each dollar of work is costing more than budgeted. Both can be true simultaneously, and both require corrective action.

Narrative matters. Numbers without interpretation are not a project status report. Translate each index into plain language: what activity is running late, why costs are over, and what specific corrective action—with a quantified impact on forecast cost at completion—you are proposing.

When you identify corrective actions, be specific: "Increase concrete crew from four to six workers on Activity 14 to recover eight schedule days, reducing forecast EAC by approximately $12,400 based on current CPI" is actionable. "Work harder" is not.