10. Scheduling, Resource and Cost Management

Introduction and context

Property development is often judged by visible outcomes—an approved scheme, a completed building, leased space, or a profitable sale. Yet these outcomes depend on a less visible discipline: coordinating time, people, materials, equipment, finance, information, and decisions. A development may be technically sound and commercially attractive but still fail because construction is delayed, resources are poorly sequenced, costs escalate, or cash is unavailable at critical moments.

Scheduling, resource and cost management therefore form an integrated control system. The schedule describes when work should occur; resource management determines whether the required labour, plant, materials, consultants, and organisational capacity are available; cost management translates the plan into financial commitments, forecasts, and controls. In practice, none of these dimensions can be managed independently. A compressed programme may require additional labour and premium procurement. A cheaper construction method may extend the programme. A delayed planning approval may alter financing costs, contractor claims, and the development appraisal.

This chapter develops the principal methods used by property development managers and project teams to plan and control these relationships. It focuses on critical path analysis, PERT, resource levelling, cost planning, value engineering, cash-flow forecasting, earned value management, and schedule–cost control. The emphasis is not merely on calculation, but on interpretation and managerial judgement.

Learning objectives

By the end of this chapter, the reader should be able to:

1. Construct and interpret activity networks, critical paths, floats, and milestone schedules.

2. Apply PERT to activities subject to uncertainty.

3. Diagnose resource overloads and develop practical resource-levelling responses.

4. Prepare cost plans, budgets, contingencies, and cash-flow forecasts for development projects.

5. Distinguish cost reduction from value engineering and assess whole-life value.

6. Use earned value indicators to evaluate schedule and cost performance.

7. Integrate schedule, resource, procurement, and financial information for project control.

8. Identify governance, ethical, contractual, and technological risks in project monitoring.

The integrated logic of a development plan

A development programme normally moves through interdependent phases: feasibility, land acquisition, planning and design, statutory approvals, procurement, construction, commissioning, marketing or letting, and handover. The sequence is not always linear. Design changes may arise from cost review; procurement feedback may influence specifications; financing conditions may require revised phasing; and market evidence may cause a change in unit mix.

A schedule is consequently more than a list of dates. It is a model of project logic. Each activity has a defined scope, duration, predecessor relationship, resource requirement, and cost consequence. The quality of the schedule depends on the quality of its assumptions. A date presented with false precision can be more dangerous than a carefully expressed range.

Three planning levels are particularly useful:

• The strategic or master programme establishes major phases, gateways, milestones, and external dependencies.
• The baseline programme provides detailed activities, logic, durations, responsibilities, and planned resources.
• The short-term or look-ahead programme converts the baseline into actionable commitments, often over two to six weeks.

The baseline should be approved through a formal governance process. It is not a static promise that prevents change; it is a reference against which authorised change and actual performance can be measured.

Network scheduling: from activities to critical paths

The critical path method (CPM) represents a project as a network of activities connected by logical relationships. Common relationships include finish-to-start, start-to-start, finish-to-finish, and start-to-finish, although finish-to-start is most frequently used. Activities may be shown as nodes in an activity-on-node network, with durations assigned to them.

The forward pass calculates the earliest dates at which activities can begin and finish. If an activity has duration d, earliest start ES, and earliest finish EF, then:

EF = ES + d

For an activity with several predecessors, its ES is normally the greatest EF of those predecessors. The backward pass calculates the latest dates that will not delay the project completion. If LF is latest finish and LS is latest start:

LS = LF − d

For an activity with multiple successors, LF is normally the smallest LS of those successors. Total float is calculated as:

Total Float = LS − ES = LF − EF

Activities with zero total float form a critical path under the stated assumptions. Delay to a critical activity will delay the planned completion date unless corrective action changes the logic, duration, or working pattern. A project can have more than one critical path, and near-critical paths deserve attention because small delays may make them critical.

CPM is valuable because it distinguishes important work from merely busy work. However, it does not automatically identify the most important commercial risk. An activity with float may still be strategically important if it controls a financing drawdown, a tenant commitment, a statutory condition, or a long-lead procurement decision.

Illustrative network calculation

Assume a small development has the following activities:

| Activity | Description | Duration | Immediate predecessor |

|---|---|---:|---|

| A | Finalise design brief | 4 weeks | — |

| B | Obtain planning approval | 8 weeks | A |

| C | Prepare technical design | 6 weeks | A |

| D | Tender and appoint contractor | 5 weeks | C |

| E | Mobilise and commence works | 2 weeks | B, D |

| F | Construct building | 20 weeks | E |

| G | Commission and hand over | 3 weeks | F |

Activities A–B require 12 weeks, while A–C–D requires 15 weeks. Activity E can therefore begin after 15 weeks, assuming both approval and contractor appointment are complete. The total planned duration is 15 + 2 + 20 + 3 = 40 weeks. In this simplified network, A–C–D–E–F–G is critical and the planning approval branch has three weeks of float. If approval is delayed by four weeks, however, it becomes critical and the completion date moves unless mitigation is introduced.

This example also illustrates why critical path analysis should be revisited after design development, procurement, approval decisions, and major changes. The critical path is a condition of the current network, not a permanent characteristic of the project.

PERT and uncertainty in activity durations

CPM generally uses one duration estimate for each activity. The Program Evaluation and Review Technique (PERT) recognises that durations may be uncertain. Three estimates are obtained:

• optimistic time (a): the duration under favourable conditions;
• most likely time (m): the duration considered most probable; and
• pessimistic time (b): the duration under adverse but credible conditions.

The expected duration is commonly estimated as:

te = (a + 4m + b) / 6

The approximate variance is:

Variance = [(b − a) / 6]²

For example, if a planning condition is expected to take 4 weeks optimistically, 7 weeks most likely, and 16 weeks pessimistically, the expected duration is (4 + 28 + 16)/6 = 8 weeks. The wide range signals material uncertainty. A manager should not hide this uncertainty by presenting only the eight-week figure; it should be reflected in contingency, decision gates, and stakeholder communication.

PERT is useful for planning approvals, utility connections, specialist fabrication, negotiations, and other activities influenced by external parties. Its assumptions should be treated carefully. Activity durations may not follow the implied probability distribution, estimates may be correlated, and political or regulatory changes may create discontinuities. Scenario analysis and simulation can supplement PERT where the project is large or highly uncertain.

Resource planning and levelling

A logically feasible schedule may be impossible with the available resources. Resource planning identifies the people, trades, materials, equipment, information, cash, and management attention required by each activity. Resource loading attaches quantities or effort profiles to scheduled activities. A histogram can then reveal periods in which demand exceeds capacity.

Resource smoothing adjusts activities within available float without changing the project completion date. Resource levelling goes further: it resolves over-allocation even if the completion date must move. Typical responses include changing activity sequence, splitting work, using alternative crews, subcontracting, changing shift patterns, procuring earlier, substituting materials, or revising the construction method.

Levelling is a managerial optimisation problem. A decision to add a second crew may reduce time but increase supervision, congestion, safety risk, and cost. Delaying a non-critical activity may preserve labour capacity but consume float and create a new critical path. The preferred solution should be evaluated against time, cost, quality, safety, logistics, and contractual consequences.

Resource constraints are often caused by more than physical scarcity. A project may have enough total labour but insufficient qualified supervisors; enough materials in the market but inadequate storage; or enough cash in aggregate but not at the date of a major payment. Consequently, resource schedules should include procurement lead times, approval durations, delivery windows, and payment obligations.

Cost planning across the development life cycle

Cost planning begins before detailed design. At feasibility stage, the development appraisal may use benchmarks such as cost per square metre, elemental rates, or comparable schemes. As scope becomes clearer, the estimate should evolve into an elemental cost plan, a procurement budget, and finally a control budget linked to the work breakdown structure.

A robust cost plan separates at least the following categories:

• land and acquisition costs;
• professional, statutory, and legal fees;
• enabling works and site preparation;
• construction and external works;
• financing and holding costs;
• marketing, letting, and sales costs;
• client-side project management and administration; and
• risk allowances and contingency.

Contingency should not be a concealed reserve used to make an unrealistic estimate appear viable. It should reflect identified uncertainty, such as incomplete design, ground conditions, market prices, or approval risk. A distinction should be made between design development allowance, risk contingency, and management reserve. The authority to draw each allowance should be defined.

Cost planning must also recognise the difference between committed cost, forecast cost, and actual cost. Committed cost is contractually or commercially obligated; actual cost has been recorded; forecast cost represents the expected final outcome. A project can appear within budget because invoices are low while commitments and forecast liabilities are high.

Value engineering

Value engineering is a structured process for achieving required functions at optimum whole-life value. It is not synonymous with indiscriminate cost cutting. A cheaper façade that increases maintenance, reduces energy performance, or undermines marketability may destroy value. Value engineering asks what function is required, what it costs, what alternatives can deliver it, and what risks those alternatives create.

A typical workshop identifies functions, analyses cost drivers, generates alternatives, evaluates technical and commercial feasibility, and records decisions. For a residential scheme, alternatives might include standardising bathroom layouts, revising structural spans, selecting locally available finishes, or changing plant configuration. The analysis should include capital cost, programme effect, maintenance, energy, replacement, user experience, regulatory compliance, and residual value.

Value engineering is most effective before design decisions become difficult or expensive to change. Late substitution can generate redesign, delay, claims, waste, and reputational damage. Decisions should be recorded in a value register with an owner, estimated saving or value gain, approval status, and effect on scope and risk.

Cash-flow forecasting and financial timing

Profitability and liquidity are different. A development may be profitable on completion but fail because cash is insufficient during construction. Cash-flow forecasting maps expected receipts and payments by period, often monthly. It should be prepared on a time-phased basis and updated as procurement, valuation, sales, financing, and construction information changes.

Typical outflows include land payments, professional fees, statutory charges, contractor mobilisation, progress payments, taxes, interest, insurance, marketing, and retention releases. Inflows may include equity, development finance drawdowns, grants, presales, staged customer payments, refinancing, or disposal proceeds. Forecasts should show opening cash, inflows, outflows, net movement, closing cash, and minimum funding requirement.

The forecast should model payment timing rather than merely spreading total cost evenly. Construction expenditure often follows an S-curve, but actual profiles vary with mobilisation, procurement of long-lead items, valuation rules, retention, variations, and seasonal productivity. Interest is affected by the timing of drawdowns and repayments, so a schedule delay may increase finance cost even where the physical cost remains unchanged.

Sensitivity testing should examine changes in completion date, sales rate, interest rate, construction cost, drawdown timing, and contingency consumption. A useful forecast includes a base case, downside case, and specified management actions. It should also identify the point at which additional equity or refinancing becomes necessary.

Earned value management and schedule–cost control

Earned value management (EVM) integrates scope, time, and cost through three measures:

• Planned Value (PV): the authorised budget for work scheduled to be completed by a particular date.
• Earned Value (EV): the authorised budget for work actually completed by that date.
• Actual Cost (AC): the actual cost incurred for the completed work.

From these measures:

Schedule Variance (SV) = EV − PV

Cost Variance (CV) = EV − AC

Schedule Performance Index (SPI) = EV / PV

Cost Performance Index (CPI) = EV / AC

If EV is £4.0 million, PV is £5.0 million, and AC is £4.5 million, then SV is −£1.0 million, CV is −£0.5 million, SPI is 0.80, and CPI is 0.89. The project is behind the planned value of work and is spending more than the budgeted value of the work completed.

At completion, the budget is the Budget at Completion (BAC). A simple estimate at completion is:

EAC = BAC / CPI

Other formulas may incorporate schedule and cost performance differently, depending on whether current performance is expected to continue and whether remaining work will be performed according to the original budget. The formula is less important than the reasoning behind the forecast.

EVM requires credible measurement rules. Physical progress should not be confused with money paid. A contractor may receive a large advance while little work is complete; conversely, substantial work may be completed before valuation. Progress rules such as weighted milestones, quantity installed, or 0/100 and 50/50 conventions should be agreed in advance and applied consistently.

EVM has limitations. It may not capture quality defects, safety exposure, design maturity, commercial disputes, or the strategic importance of a delayed activity. Schedule variance expressed in monetary terms can also be difficult to interpret as calendar delay. EVM should therefore be combined with critical path analysis, risk reporting, quality inspection, and cash forecasting.

An illustrative integrated case

Background

The following is a fictional illustrative case. Meridian Estates plans a 120-unit mixed-use development on a previously industrial site. The scheme includes ground-floor commercial space, structured parking, and public-realm works. Planning approval is conditional on highway improvements and a contamination remediation plan.

Situation and problem

The initial 22-month programme showed a comfortable completion date, but the cost plan was based on early concept information. During technical design, contamination risk increased, the utility provider extended its connection lead time, and the contractor reported that the proposed façade system required a longer procurement period. At the same time, the lender required evidence that peak funding would remain within the agreed facility.

Analysis

The project manager re-baselined the network. The utility connection and remediation activities were placed on the logic network rather than treated as general assumptions. The utility activity became part of a near-critical path. A resource histogram also showed that the same specialist crew was scheduled simultaneously for remediation and basement works.

The cost team divided the estimate into committed cost, forecast cost, and risk allowances. A monthly cash-flow model showed that the original programme created a funding peak two months earlier than anticipated because of advance payments for façade materials. EVM was introduced after the construction baseline was approved, with physical progress measured through weighted work packages.

Strategy and solution

The team adopted four measures. First, remediation was partially resequenced so that unaffected areas could proceed while test results were finalised. Second, the façade specification was reviewed through a value-engineering workshop. A locally available system met the required performance but reduced procurement uncertainty; the design change was approved only after checking appearance, thermal performance, maintenance, and planning implications. Third, the contractor and lender agreed a revised drawdown profile tied to certified progress rather than procurement orders alone. Fourth, the specialist crew was supplemented temporarily, but only during the period where the additional resource removed a critical constraint.

A risk allowance was not simply removed to show a saving. The value register recorded the source of the saving, residual risks, responsible owner, and approval authority. The programme dashboard reported critical and near-critical paths, three-week look-ahead constraints, CPI, SPI, forecast completion, and peak cash requirement.

Outcome

The illustrative project avoided a forecast four-week delay, although the revised sequence increased short-term management complexity. The alternative façade did not produce the largest nominal saving; its principal benefit was reduction of procurement uncertainty and protection of the funding profile. The cash-flow forecast became more reliable because commitments and payment dates were separated from physical progress.

Learning points

The case demonstrates that schedule, cost, resources, and cash are connected through decisions. A schedule gain is not automatically beneficial if it creates disproportionate cost or safety risk. A cost saving is not genuine if it transfers cost to maintenance or causes delay. Most importantly, early warnings are valuable only when they are linked to accountable actions and decision dates.

Risks, limitations, and common mistakes

Several recurring errors weaken project control. The first is excessive detail without reliable logic. A schedule containing thousands of activities may still be unhelpful if relationships are artificial or updates are delayed. The second is treating the baseline as a political commitment rather than a realistic planning model. Unrealistic dates encourage concealment and late reporting.

Other common mistakes include:

• failing to include approvals, procurement, testing, commissioning, and handover activities;
• ignoring resource constraints when calculating the critical path;
• using optimistic durations without analysing external dependencies;
• reporting percentage complete without an agreed measurement basis;
• confusing cash paid with cost incurred and physical progress;
• consuming contingency without recording the associated risk;
• approving design changes without assessing programme and cash effects;
• levelling resources without checking contractual milestones or site logistics; and
• producing forecasts that are not updated after known events.

There are also conceptual limits. CPM assumes sufficiently stable logic and duration estimates. PERT can give a misleading appearance of statistical precision. EVM can reward reported progress without revealing poor quality if measurement rules are weak. Cost plans are vulnerable to inflation, market volatility, design development, and scope ambiguity. Professional judgement remains essential.

Governance, ethics, and professional responsibility

Project controls influence funding decisions, investor communications, contractor payments, and public or community commitments. Deliberately understating costs, delaying recognition of a forecast overrun, manipulating progress percentages, or using contingency without authority is professionally unacceptable. Reports should distinguish fact, estimate, assumption, and judgement.

Governance should establish approval thresholds, change-control procedures, delegated authority, audit trails, version control, and escalation rules. The project manager should ensure that schedule and cost data are traceable to source records. Contractual reporting obligations must be respected, but contractual compliance should not replace honest risk communication.

In property development, ethical decisions also include safety, accessibility, environmental performance, labour practices, and effects on future occupants and surrounding communities. Value engineering must never remove essential safety or statutory performance. A short-term saving that transfers risk to users or the environment is not responsible value management.

Digital tools, analytics, and emerging practice

Contemporary project teams increasingly connect scheduling, estimating, procurement, document control, and accounting through common data environments. Building information modelling can link quantities and design changes to cost plans and planned work packages. Cloud-based dashboards provide more frequent visibility of progress, commitments, risks, and cash positions.

Automation can support quantity take-off, update comparisons, invoice matching, and early-warning alerts. Predictive analytics may identify patterns associated with delay or cost growth, but its output depends on reliable historical and project data. Artificial intelligence can assist with schedule risk analysis, document classification, and scenario generation; it should not replace professional approval of assumptions, contractual interpretation, safety decisions, or stakeholder commitments.

Digital integration also creates risks: inconsistent data structures, unauthorised changes, cyberattack, poor access controls, and false confidence in dashboards. A concise dashboard is useful only when underlying definitions are understood. The project team should maintain a data dictionary, clear ownership, controlled permissions, and documented update frequency.

Best-practice approach

A disciplined control cycle can be summarised as follows:

1. Define scope through a work breakdown structure and identify deliverables, assumptions, interfaces, and acceptance criteria.

2. Build a logically linked schedule including approvals, design, procurement, construction, commissioning, and handover.

3. Estimate durations using evidence, ranges, and explicit risk assumptions.

4. Load resources and test the programme against real capacity, access, procurement, and cash constraints.

5. Develop an elemental cost plan and time-phase it into a budget and cash-flow forecast.

6. Establish a controlled baseline with agreed progress, cost, change, and reporting rules.

7. Update actual progress, commitments, costs, risks, and forecasts at an agreed frequency.

8. Investigate variances by cause rather than merely describing them.

9. Evaluate corrective actions for their time, cost, quality, safety, contractual, and stakeholder effects.

10. Record approved changes and reforecast transparently without erasing the original performance history.

This approach turns project control from retrospective reporting into active management.

Chapter Summary

Scheduling, resource and cost management are interdependent elements of property development control. CPM identifies logical dependencies, critical paths, and float, while PERT accommodates uncertainty through three-point duration estimates. Resource loading and levelling test whether the programme is achievable with available labour, equipment, materials, information, and management capacity.

Cost planning should evolve from early feasibility estimates into an approved, time-phased control budget. Value engineering seeks optimum whole-life value rather than superficial cost reduction. Cash-flow forecasting protects liquidity by modelling the timing of inflows, outflows, drawdowns, and funding peaks. EVM links planned value, earned value, and actual cost to provide integrated performance indicators, but it must be supplemented by critical path, quality, risk, and cash analysis.

Effective project control depends on credible assumptions, disciplined change management, ethical reporting, reliable data, and timely corrective action. Digital tools improve visibility and analysis, but professional judgement remains central to interpreting uncertainty and making balanced decisions.

Key Terms

Critical path: The longest logical sequence of activities determining the earliest project completion date.

Critical activity: An activity with zero or minimal float whose delay may delay project completion.

Float: The amount of time an activity can be delayed without violating a defined project or successor constraint.

Forward pass: A scheduling calculation that determines earliest start and finish dates.

Backward pass: A scheduling calculation that determines latest permissible start and finish dates.

PERT: A duration-estimation method using optimistic, most likely, and pessimistic estimates.

Resource loading: Assigning resource requirements to scheduled activities.

Resource levelling: Adjusting the programme to resolve resource over-allocation, potentially changing completion dates.

Resource smoothing: Adjusting activities within available float to reduce resource fluctuations without changing completion.

Cost plan: A structured estimate of project costs allocated to elements, packages, or phases.

Control budget: An approved financial baseline against which performance is measured.

Contingency: An allowance for identified uncertainty or risk within an approved scope.

Value engineering: A systematic process for achieving required function at optimum whole-life value.

Cash-flow forecast: A time-phased projection of project receipts, payments, and funding requirements.

Planned Value: The authorised budget for work scheduled by a particular date.

Earned Value: The authorised budget associated with work actually completed.

Actual Cost: The cost incurred for work performed by a particular date.

Cost Performance Index: Earned Value divided by Actual Cost, indicating cost efficiency.

Schedule Performance Index: Earned Value divided by Planned Value, indicating progress against planned value.

Estimate at Completion: A forecast of the total cost expected when the project is complete.

Review Questions

Short Answer Questions

1. What is the difference between total float and the critical path?

2. State the three duration estimates used in PERT.

3. Distinguish resource smoothing from resource levelling.

4. What is the difference between committed cost and actual cost?

5. Define Planned Value, Earned Value, and Actual Cost.

Long Answer Questions

1. Explain how a critical path is calculated and discuss why it may change during a property development.

2. Discuss the role of cost planning from feasibility through construction and completion.

3. Explain why value engineering should be distinguished from simple cost cutting.

4. Describe the components and uses of a development cash-flow forecast.

5. Evaluate the benefits and limitations of earned value management in construction projects.

Analytical / Application Questions

1. A project has EV of £3.6 million, PV of £4.0 million, and AC of £3.2 million. Calculate SV, CV, SPI, and CPI, and interpret the results.

2. A specialist activity has optimistic, most likely, and pessimistic durations of 5, 8, and 17 weeks. Calculate its PERT expected duration and explain how the uncertainty should influence planning.

3. A proposed resource-levelling action reduces the programme by two weeks but requires an additional crew and increases site congestion. What criteria should the project manager use to decide whether to adopt it?

22. Multiple Choice Questions with Answers

Question 1

In a CPM network, an activity has ES = 10 weeks, EF = 16 weeks, LS = 12 weeks, and LF = 18 weeks. What is its total float?

A. 2 weeks

B. 4 weeks

C. 6 weeks

D. 8 weeks

Correct Answer: A. 2 weeks

Question 2

Which statement best describes the critical path?

A. The sequence with the highest direct cost

B. The sequence with the greatest number of activities

C. The longest logical sequence determining planned completion

D. The sequence using the most labour

Correct Answer: C. The longest logical sequence determining planned completion

Question 3

Using PERT, what is the expected duration when a = 4, m = 7, and b = 16 weeks?

A. 7 weeks

B. 8 weeks

C. 9 weeks

D. 10 weeks

Correct Answer: B. 8 weeks

Question 4

Resource smoothing normally means that activities are adjusted:

A. Only by adding labour

B. Within available float without changing completion

C. After the project has finished

D. By removing all contingency

Correct Answer: B. Within available float without changing completion

Question 5

Which is the best example of value engineering?

A. Removing required fire protection to reduce cost

B. Selecting an alternative façade that meets performance requirements and reduces whole-life cost

C. Delaying payment to conceal an overrun

D. Reducing inspection activities regardless of risk

Correct Answer: B. Selecting an alternative façade that meets performance requirements and reduces whole-life cost

Question 6

A project has EV = £4 million, PV = £5 million, and AC = £4.5 million. What is the CPI?

A. 0.80

B. 0.89

C. 1.11

D. 1.25

Correct Answer: B. 0.89

Question 7

A CPI below 1.0 generally indicates that:

A. The project is receiving more value than planned for its cost

B. The project is spending more than the budgeted value of completed work

C. The project is ahead of schedule

D. No cost forecast is possible

Correct Answer: B. The project is spending more than the budgeted value of completed work

Question 8

Why can a profitable development still experience financial failure?

A. Profit and liquidity are identical measures

B. Cash receipts may occur after payments and funding obligations arise

C. Construction costs never affect cash flow

D. A development appraisal excludes all finance costs

Correct Answer: B. Cash receipts may occur after payments and funding obligations arise

Question 9

Which practice most improves the credibility of progress measurement for EVM?

A. Allowing each contractor to define percentage complete differently

B. Using agreed, consistent rules linked to physical deliverables

C. Measuring progress only by invoices paid

D. Updating progress only at final completion

Correct Answer: B. Using agreed, consistent rules linked to physical deliverables

Question 10

A project dashboard shows an acceptable CPI but a near-critical procurement path is slipping. What is the most appropriate interpretation?

A. The project is fully controlled because CPI is acceptable

B. The project has no risk until cost variance becomes negative

C. Cost performance is acceptable, but schedule and procurement risk require action

D. The procurement delay should be ignored if it has current float

Correct Answer: C. Cost performance is acceptable, but schedule and procurement risk require action