To lead through project delays and overruns, establish a verified forecast, disclose the exposure early, and run a dated recovery plan with clear owners and decision rights. Your goal is to replace false certainty with reliable facts, controlled choices, and timely decisions.
A development starts to lose control when the approved schedule and budget stop reflecting current conditions. Forecasts drift, unresolved changes accumulate, and teams delay bad news because they fear the reaction.
You can regain control without pretending to know every outcome. The process starts by separating verified facts from assumptions, then connecting each recovery decision to scope, cost, time, cash flow, quality, and risk.
Why Delays And Overruns Become A Leadership Test
A delayed development is rarely just a scheduling problem. It tests whether you can create clarity when commercial pressure, incomplete information, and competing priorities are pulling the team in different directions. If leaders demand an immediate recovery date before validating the data, teams often produce a date that sounds acceptable but cannot be defended. That creates a second credibility problem when the revised commitment is missed.
Your conduct sets the standard for how the team responds. If meetings focus on blame, people protect their positions, filter information, and avoid ownership. If discussions focus on evidence, decisions, and accountable actions, you create space for earlier reporting and faster resolution. Accountability still matters, but it should follow a verified understanding of what happened.
You also need to accept that recovery involves choices. Preserving the original scope, completion date, budget, quality standard, and risk position may no longer be possible. Your job is to show stakeholders which trade-offs are available, what each choice costs, and when a decision must be made. Leadership becomes visible through disciplined choices, not optimistic promises.
Diagnose The Real Drivers Before Setting A Recovery Date
Before announcing a new completion date, determine what is driving the delay and whether the current plan contains credible logic. Review the baseline schedule, approved changes, current progress, procurement status, design maturity, labor productivity, access constraints, and outstanding decisions. Separate completed work from reported progress, since percentage-complete estimates can hide unfinished activities. Confirm physical progress through records, site observations, quantities, or other measurable evidence.
Run a critical-path review using the Critical Path Method (CPM). Identify the activities controlling completion, the available float, and any near-critical paths that could become controlling. A delayed activity does not automatically delay the project if it has usable float. A small delay on a critical activity can have a direct effect on completion.
Classify the causes so you can select the right response. Common drivers include incomplete design, late owner decisions, contractor underperformance, supply chain disruption, inaccurate productivity assumptions, scope growth, access restrictions, and poor sequencing. Some causes require schedule correction, others require commercial action or governance changes. Treating every problem as a contractor performance issue can distract you from owner-controlled delays and unresolved scope decisions.
Rebuild The Schedule, Cost Baseline, And Forecast
Once you understand the causes, rebuild the project forecast from current conditions rather than adjusting the original plan until it appears acceptable. Start with a statused schedule that records actual starts, actual finishes, remaining durations, dependencies, constraints, and realistic resource assumptions. Remove outdated logic and unexplained lags. Check that the recovery schedule can be traced to the work teams are expected to perform.
Recalculate cost exposure at the same time. Your forecast should include actual cost to date, committed cost, approved changes, pending changes, expected claims, escalation exposure, remaining procurement, internal costs, and risk allowance. Cash flow also needs attention because an affordable total forecast can still create a short-term funding problem. Map expected payments against available funding and approval dates.
Estimate at completion equals actual cost to date plus the forecast-to-complete. The forecast-to-complete should represent the expected cost of finishing the remaining work under current conditions. It should not be the unused portion of the original budget unless that amount still reflects a credible estimate. Compare the new forecast with the approved baseline and explain each major movement.
Earned Value Management (EVM) can support this review when scope, progress measurement, and cost data are reliable. Cost variance compares earned value with actual cost, and schedule variance compares earned value with planned value. These indicators can expose performance drift, but they do not replace a logic-based schedule review. A favorable summary metric can still conceal a threatened completion date.
Communicate Bad News Early Without Losing Trust
Stakeholders usually react more strongly to late surprises than to early warnings supported by evidence. Communicate once you have enough verified information to describe the exposure, even if the final recovery plan is still being developed. State what has happened, what is known, what remains uncertain, and when the next decision-quality update will be issued. Avoid presenting an early working estimate as a firm commitment.
Use ranges when uncertainty remains. You can present a likely completion window, a current cost range, the main assumptions, and the events that could move the forecast. Attach decision gates to those ranges so stakeholders know when uncertainty should narrow. This gives them usable information without creating false precision.
Keep the message controlled and consistent. Board members, investors, lenders, project teams, contractors, and customers may need different levels of detail, but the underlying facts should align. Use one approved set of schedule, cost, risk, and scope information. Conflicting figures from different teams can damage confidence faster than the overrun itself.
A strong update should cover five points: the current position, the causes, the forecast range, the recovery actions, and the decisions required. Assign an owner and due date to every requested decision. If a delayed approval affects the critical path or cost forecast, show that connection directly. Stakeholders can then see the cost of waiting.
Build A Recovery Plan Around Explicit Trade-Offs
A project recovery plan converts the revised forecast into dated actions. It should identify the work controlling completion, the resources required, the decisions needed, the responsible owners, and the measures used to track progress. Every action should connect to a defined schedule or cost effect. General instructions to “work faster” or “improve coordination” do not create control.
Test recovery options against scope, time, cost, risk, cash flow, safety, and quality. Schedule compression can include resequencing work, overlapping selected activities, changing work methods, adding shifts, or securing earlier procurement. Each option carries limits. Adding people can reduce productivity when access is constrained, supervision is limited, or new workers need time to learn the work.
Scope decisions may create more reliable gains than broad schedule acceleration. Value engineering can remove cost or simplify delivery without weakening the required function. Phased delivery can protect an operational milestone while lower-priority work continues. Scope deferral should be documented so temporary removal does not return later as uncontrolled scope growth.
Set a small number of recovery measures. Track critical-path movement, milestone reliability, planned versus completed work, productivity, change exposure, contingency drawdown, and cash flow. Review trends rather than isolated weekly results. A single good reporting period does not confirm that the turnaround is working.
Control Change Orders, Claims, And Contingency
Unresolved changes can distort the cost forecast and create commercial disputes. Establish one change register covering the description, origin, scope effect, schedule effect, cost estimate, contractual status, owner, and required decision date. Reconcile it against contractor notices, design instructions, meeting records, and procurement commitments. Items should not disappear from the forecast simply because formal agreement is pending.
Separate entitlement, causation, and value when reviewing claims. A contractor may have complied with a notice requirement, yet the claimed event may not have caused the full delay stated. A valid delay event may affect time without supporting every requested cost. Structured analysis helps you evaluate the claim without relying on broad statements or personal recollections.
Maintain contemporaneous records. Daily reports, schedule updates, correspondence, photographs, labor records, design logs, procurement records, and decision histories can establish what occurred and when. Follow the contract’s notice and documentation requirements. Informal discussions can support resolution, but they should not replace required written records.
Contingency reserve generally covers identified uncertainty within the approved project plan. Management reserve is held for uncertainty that sits outside the detailed cost baseline and is released through defined authority. Do not use either reserve to hide known scope or approved changes. Record every drawdown, its cause, the remaining exposure, and the authority that approved it.
There is no universal contingency percentage that suits every development. Set the amount from the risk register, design maturity, procurement status, delivery strategy, market exposure, and schedule uncertainty. Risk-based estimating and simulation can help you compare confidence levels. Reassess the reserve as risks retire, appear, or change in value.
Protect Safety, Quality, And Team Capacity
Recovery pressure can encourage longer shifts, crowded work areas, rushed inspections, and shortcuts in sequencing. These actions can create incidents, rework, and lower productivity, which push the project further behind. Review every acceleration proposal for safety and quality effects before approval. A recovery action that creates larger downstream losses is not a recovery action.
Protect quality hold points, inspection requirements, testing, commissioning, and design review. If a step must be resequenced, confirm that later work will not conceal unfinished or defective work. Track rework separately from planned production. Rising rework is an early warning that pressure is weakening execution.
Team capacity also requires active management. Turnarounds increase meeting volume, reporting demands, decision fatigue, and conflict between commercial and delivery teams. Define who attends each meeting, what decisions belong there, and which reports can be stopped. Give key people time to solve problems rather than filling every hour with status updates.
Keep accountability specific and fair. Ask owners to commit to actions they control, then remove barriers that require senior authority. Recognize verified progress without declaring victory too early. Teams stay engaged when priorities remain stable, decisions arrive on time, and leaders respond to bad news without creating fear.
Strengthen Governance And Decision Rights
Many overruns worsen because decisions move through unclear approval paths. Define which decisions belong to the project director, steering group, board, design authority, commercial team, and client representative. Set financial and schedule thresholds for escalation. Give each decision a deadline based on its effect on procurement, construction, commissioning, or cash flow.
Use stage-gate reviews at major commitment points. Before releasing major procurement, construction packages, or acceleration funding, confirm scope maturity, schedule logic, estimate quality, risk exposure, and approval authority. A gate should produce a decision, conditions for approval, or a clear rejection. It should not become another reporting meeting with no accountable outcome.
Independent project review can help when internal data is disputed or confidence has fallen. The review can test schedule quality, estimate assumptions, progress measurement, commercial exposure, and recovery feasibility. Independence matters because delivery teams can become attached to their own assumptions. The review should strengthen decisions rather than create a parallel management structure.
Align reporting cycles across schedule, cost, risk, change, and cash flow. A schedule updated weekly and a cost report updated monthly can create conflicting views of the same project. Set a common status date and define cut-off rules. This allows leaders to compare information drawn from the same reporting period.
Act In The First 48 Hours
The first 48 hours should stabilize information and stop avoidable exposure. Do not wait for a polished recovery plan before tightening controls. Freeze discretionary scope changes, identify immediate critical-path threats, and confirm who holds decision authority. Preserve records and establish a single reporting route for new issues.
Appoint a small recovery team covering delivery, planning, cost, commercial management, design, risk, and stakeholder communication. Give the team a clear mandate and access to source data. Set short reporting intervals during stabilization, then reduce the frequency once control improves. Keep the leadership group small enough to make decisions quickly.
- Confirm the current schedule status date and approved baseline.
- Validate physical progress on critical and near-critical work.
- List unresolved changes, claims, commitments, and major risks.
- Calculate an initial forecast-to-complete and cash requirement.
- Identify decisions needed within seven, fourteen, and thirty days.
- Issue a controlled stakeholder update using verified information.
- Set the date for the full recovery plan and independent review.
Some FAQs About Project Delays And Overruns
What Should You Do When A Project Is Behind Schedule And Over Budget?
Confirm the real status before committing to a new date or budget. Validate progress, review the critical path, rebuild the forecast-to-complete, freeze avoidable changes, and assign owners to immediate decisions. Communicate the initial exposure with stated assumptions. Follow with a dated recovery plan once the underlying data has been tested.
How Do You Create A Credible Project Recovery Plan?
Build the plan from current progress, remaining work, resource capacity, procurement status, schedule logic, commercial exposure, and active risks. Link each recovery action to an owner, deadline, cost, and measurable effect. Test the plan against safety, quality, cash flow, and delivery constraints. Obtain approval for any scope, funding, or contractual changes needed to execute it.
How Do You Handle Scope Creep During Recovery?
Route every proposed change through a controlled review before work begins. Record the reason, cost, schedule effect, funding source, and approval authority. Reject changes that do not support required outcomes or recovery priorities. If a change must proceed urgently, document the interim authority and complete the formal review promptly.
How Do You Manage Extension-Of-Time Requests?
Review the contract requirements, submitted notices, event records, schedule logic, and effect on the critical path. Separate owner-caused, contractor-caused, concurrent, and neutral delay where the contract requires those distinctions. Assess time entitlement separately from cost entitlement. Preserve the analysis and decision record in case the issue moves into formal dispute resolution.
How Do You Keep The Team Motivated During A Turnaround?
Give the team stable priorities, prompt decisions, realistic workloads, and visible support from leadership. Remove unnecessary reporting and repeated meetings. Address poor performance directly without turning every review into a blame session. Motivation improves when people can see that their work changes the forecast and that unresolved barriers receive attention.
How Do You Prevent Cost Overruns From Recurring?
Improve estimating discipline, schedule quality, design maturity, risk analysis, change control, and approval timing before the next major commitment. Compare the original assumptions with actual results and record why they differed. Update productivity rates, procurement allowances, and risk values using verified project information. Strengthen assurance at stage gates rather than relying on end-of-project lessons.
How Do You Lead A Project Through Delays And Cost Overruns?
- Confirm the baseline and forecast-to-complete.
- Communicate impacts early.
- Build a dated recovery plan.
- Control changes, claims, and contingency.
- Protect safety, quality, and morale.
Lead The Turnaround With Facts, Choices, And Discipline
You regain control of project delays and overruns by improving the quality and speed of decisions. Verify the schedule and cost position, disclose credible ranges, and connect recovery actions to named owners and dates. Make scope, funding, and schedule trade-offs openly rather than burying them inside optimistic forecasts. Protect safety, quality, records, and team capacity as pressure rises. A development can survive a missed milestone, but repeated surprises and unsupported commitments will make recovery far harder.
References
- United States Government Accountability Office, Cost Estimating and Assessment Guide
- United States Government Accountability Office, Schedule Assessment Guide
- Project Management Institute, Project Management Body of Knowledge Guide and Standards
- Project Management Institute, Practice Standard for Scheduling
- International Organization for Standardization, Project Management Guidance
- AACE International, Recommended Practice 29R-03, Forensic Schedule Analysis
- McKinsey Global Institute, Reinventing Construction
- Construction Industry Institute.
Menachem Silber is a Brooklyn-based real estate developer and co-founder of Lightstone Management, with 15+ years leading affordable and mixed-use projects nationwide. He has overseen development of 1,000+ NYC housing units valued at $500M+, manages a multi-state rental portfolio, and, via Lightstone Holdings, invests in small-business lending and blockchain ventures.



