User: Alwayslearningelec, Location: NJ
Asked on: Thursday, October 10, 2024 at 1:38 pm EDT
Answered on: Thursday, March 6, 2025 at 3:44 am EST
Question: When a job does not do well your able to point out and quanitfy things from the estimating side e.g. footages used vs. estimated. etc.How can you "prove" or "pinpoint" if a job was not managed properly by PM or super which lead to job not doing well?
Okay, this is a crucial question for project analysis and improvement. It's not as straightforward as comparing quantities on an estimate, but it's definitely possible to identify and "prove" mismanagement on a project. Here's a breakdown of how to pinpoint potential PM/Superintendent shortcomings when a project underperforms
1. Establish Key Performance Indicators (KPIs) and Track Them:
Proactive Tracking is Key
The best way to "prove" mismanagement is to have data that shows it. If you don't track, you're relying on anecdotes, which are less convincing. Implement systems to track these metrics throughout the project, not just after it's failed.
Examples of KPIs to Track
Schedule Adherence
Planned vs. Actual Completion Dates (Milestones and Overall)
Are key milestones being missed? How frequently? By how much?
Critical Path Analysis
Track progress on the critical path. Delays here directly impact the overall schedule.
Float Utilization
Are activities using up float unnecessarily? This is a sign of potential poor planning.
Cost Control
Budget vs. Actual Costs (by Task/Phase)
Where are the cost overruns happening?
Change Order Management
How many change orders are there? What is the total value of change orders? Are they due to design errors, unforeseen conditions, or scope creep (potentially from poor communication or planning)? Analyze the reasons for the change orders.
Labor Productivity
Track labor hours spent on specific tasks and compare them to estimated hours. If productivity is consistently low, it could indicate supervision issues, lack of training, or poor coordination.
Material Waste
Excessive material waste can be a sign of poor planning or supervision.
Quality Control
Number of Rework Items
Excessive rework is a significant indicator of quality issues and potential mismanagement. Track the reason for the rework (e.g., poor workmanship, incorrect materials, lack of inspections).
Inspection Reports
Review inspection reports for recurring issues.
Punch List Items
A long and detailed punch list at the end of the project can indicate a lack of attention to detail during construction.
Communication & Coordination
Number of RFIs (Requests for Information)
A high volume of RFIs can suggest incomplete drawings, poor coordination between trades, or a lack of understanding of the project requirements. Analyze the types of RFIs. Are they repetitive?
Meeting Minutes
Review meeting minutes to identify recurring issues, unresolved problems, and communication breakdowns.
Submittal Turnaround Time
Delays in submittal approvals can impact the schedule.
Number of Safety Incidents
A high number of safety incidents can indicate poor safety management on the site.
2. Conduct Thorough Root Cause Analysis
Don't Jump to Conclusions
Just because a project went poorly doesn't automatically mean the PM/Super was at fault. A structured investigation is crucial.
Methods for Root Cause Analysis
The "5 Whys"
Ask "why" repeatedly to drill down to the underlying cause of a problem.
Fishbone Diagram (Ishikawa Diagram)
Brainstorm potential causes in categories like manpower, methods, machines, materials, measurement, and environment.
Pareto Chart
Identify the "vital few" causes that contribute to the majority of the problems.
Areas to Investigate Related to PM/Super
Planning and Scheduling
Was the initial schedule realistic? Did the PM/Super proactively update the schedule and communicate changes? Did they identify and mitigate potential risks?
Resource Allocation
Were adequate resources (labor, equipment, materials) allocated to the project? Were resources available when needed?
Coordination
Did the PM/Super effectively coordinate between different trades, subcontractors, and the owner? Were there conflicts or communication breakdowns?
Communication
Did the PM/Super maintain clear and consistent communication with the project team, the owner, and other stakeholders? Were issues addressed promptly?
Problem-Solving
How effectively did the PM/Super address problems and challenges that arose during the project? Did they escalate issues appropriately?
Decision-Making
Were decisions made in a timely and informed manner?
Subcontractor Management
How were subcontractors selected and managed? Were their contracts clearly defined? Were their performance monitored?
Risk Management
Was a risk management plan in place? Were risks identified and mitigated proactively?
Site Management (Superintendent Specific)
Was the site organized and safe? Were materials properly stored and protected? Was there effective quality control? Were daily reports accurate and complete? Were workers following plans.
3. Gather Evidence and Documentation
Review Project Documentation
This is critical. Collect and analyze:
The Project Estimate
The baseline against which actual performance is measured.
The Project Schedule
The original schedule and all revisions.
Meeting Minutes
Key for understanding discussions, decisions, and action items.
Daily Reports
Written by the superintendent, they provide a daily log of activities, manpower, equipment, and any issues encountered.
RFI Logs and Responses
To understand communication and problem-solving.
Change Order Logs and Documentation
To analyze the reasons for changes.
Submittal Logs and Approvals
To track the submittal process.
Inspection Reports
To assess quality control.
Cost Reports
To track budget vs. actual expenses.
Photos and Videos
Can provide visual evidence of site conditions, progress, and potential problems.
Contracts
Review the responsibilities and obligations of all parties involved.
Interviews
Conduct interviews with project team members, subcontractors, and the owner to gather their perspectives. Ask open-ended questions to encourage them to share their experiences and observations.
4. Compare Actual Performance to Expectations
Quantify the Impact
Don't just say "the schedule was delayed." Say "the schedule was delayed by 3 weeks, resulting in an additional $X in labor costs."
Relate Problems to PM/Super Responsibilities
For example: "The high number of RFIs related to MEP coordination indicates a lack of thorough review and coordination by the PM during the planning phase." Or "The excessive material waste on the framing activity suggests inadequate supervision and training by the superintendent."
Identify Patterns
Are there recurring problems? Do certain activities consistently run over budget or behind schedule? This can point to systemic issues with the PM/Super's approach.
5. Focus on Specific Examples and Be Objective
Avoid Generalities
Instead of saying "the PM was disorganized," provide a specific example: "The PM failed to distribute updated drawings to the subcontractors, resulting in rework and delays."
Use Data to Support Your Claims
Refer to specific documents, reports, and data to back up your observations.
Be Objective and Fair
Acknowledge any external factors that may have contributed to the project's problems, such as unforeseen conditions or owner-driven changes. Avoid blaming the PM/Super without sufficient evidence.
In Summary
"Proving" or "Pinpointing" mismanagement requires a systematic approach that involves:
Proactive Data Tracking
Implement systems to track key project metrics from the outset.
Thorough Investigation
Conduct a root cause analysis to identify the underlying causes of problems.
Evidence Gathering
Collect and review project documentation and conduct interviews.
Quantifiable Analysis
Compare actual performance to expectations and quantify the impact of problems.*
Objective Assessment: Avoid generalizations and focus on specific examples supported by data.By following these steps, you can develop a well-supported and objective assessment of the PM/Super's performance and identify areas for improvement in future projects. Remember, the goal is not just to assign blame, but to learn from the experience and prevent similar problems from happening again. Flag for review