5. Planning, Design and Pre-Construction Management

Introduction and Context

Real estate value is substantially determined before construction begins. Land acquired at the wrong price, an incomplete approval strategy, an impractical master plan, or an inadequately coordinated design can undermine a project long before the first foundation is excavated. Pre-construction management therefore converts an investment proposition into a legally permissible, technically feasible, financially viable and procurable project.

The pre-construction phase extends from the initial development concept to tender readiness. It includes land assembly, due diligence, entitlement and approval management, master planning, design development, cost planning, constructability review, value engineering, procurement strategy and project governance. These activities are interdependent. A change in permissible floor area affects the master plan; the master plan affects infrastructure and cost; cost affects product positioning and financing; and the procurement strategy affects the level of design information required before tender.

For a real estate manager, pre-construction is not merely a technical design exercise. It is a multidisciplinary decision-making process involving investors, landowners, planners, architects, engineers, lawyers, authorities, lenders, operators, contractors and future users. Its purpose is to reduce uncertainty while preserving sufficient flexibility to respond to market evidence and regulatory change.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain the relationship between land assembly, development rights, design and project feasibility.

2. Structure a systematic entitlement, approval and due diligence process.

3. Evaluate master planning and design development decisions from commercial, technical and user perspectives.

4. Apply constructability review, value engineering and cost-planning principles.

5. Design an appropriate governance and decision-control framework for pre-construction.

6. Identify major risks, ethical issues and technology applications in the period before tender.

7. Interpret a project scenario and recommend a defensible route to tender readiness.

From Development Idea to Tender Readiness

A project normally progresses through a sequence of decision gates rather than a single linear workflow. The precise names differ across jurisdictions and organizations, but the underlying logic is broadly similar:

Opportunity definition establishes the intended use, target market, investment rationale, location strategy and preliminary development capacity. Land and legal due diligence determines whether the site can be controlled and developed as assumed. Feasibility and concept planning test the relationship between development potential, revenue, cost, risk and timing. Entitlement planning identifies the approvals and conditions needed to make the project lawful. Master planning and schematic design translate the concept into a spatial and operational proposition. Design development and technical coordination provide sufficient information to define performance, cost and construction methods. Pre-tender governance confirms that the project is ready to invite comparable bids.

A useful decision principle is that each stage should answer a different question:

• Is the opportunity strategically and commercially attractive?
• Can the land and development rights be secured?
• Is the proposed use legally permissible and technically feasible?
• Can the design deliver the intended value within the investment limit?
• Can contractors price, schedule and build the project with acceptable uncertainty?

Proceeding to the next stage without resolving the appropriate question creates what may be called premature certainty. A project can possess attractive drawings while still lacking a defensible title, reliable utility capacity or an approved development envelope.

Land Assembly and Development Control

Land assembly is the process of acquiring, consolidating or otherwise controlling parcels needed for a coherent development. It may involve outright purchase, options, conditional contracts, joint ventures, long leases, easements, development agreements or compulsory acquisition where legally available. Assembly is especially important for mixed-use schemes, infrastructure-led projects and developments requiring contiguous access or a minimum site area.

The economic value of a parcel is not simply its market price. It depends on the development rights that can realistically be obtained, the cost of assembly, holding costs, relocation obligations, abnormal site costs, taxes, transaction expenses and the timing of control. A parcel that appears inexpensive may be costly if it has fragmented ownership, unresolved boundaries, restrictive covenants or no reliable access.

A land-control strategy should examine:

• title, ownership, encumbrances, liens and competing claims;
• cadastral boundaries, surveys and possible encroachments;
• access, rights of way, easements and service corridors;
• existing leases, occupants, informal users and relocation obligations;
• zoning, permitted uses, density, height, setbacks and parking requirements;
• environmental constraints, contamination, flood risk and protected features;
• infrastructure capacity and connection obligations; and
• acquisition conditions, taxes, transaction costs and conditions precedent.

Development control should be distinguished from ownership. A developer may control a project through a long lease or development agreement without owning the freehold, while ownership alone does not guarantee an immediate right to develop. The project manager must therefore map legal control, physical control and regulatory control separately.

Land assembly often creates negotiation and ethical risks. Pressure on small owners, opaque intermediary arrangements, selective disclosure of development intentions and inadequate treatment of occupants may produce legal disputes and reputational harm. A professional approach requires documented valuation logic, consistent treatment of affected parties, conflict-of-interest declarations and compliance with applicable land and anti-corruption laws.

Entitlements, Approvals and Due Diligence

An entitlement is a legal or administrative right to undertake a specified development. Entitlements may include land-use permissions, subdivision approval, development permission, building approval, environmental clearance, heritage consent, traffic approval, utility connections, fire and life-safety approval, occupancy certification and sector-specific licences. The precise system is jurisdiction-dependent, but the management problem is universal: the development must be converted from an intention into an authorized project.

Approval management begins with an approval matrix. The matrix identifies each approval, responsible party, submission requirement, decision authority, expected sequence, dependencies, validity period, conditions and risk of refusal. It should be a live management instrument rather than a static checklist. For example, a traffic assessment may be required before a planning decision, while a fire strategy may depend on the final building configuration and evacuation assumptions.

Due diligence should be multidisciplinary. Legal due diligence confirms rights and obligations. Planning due diligence tests the development envelope. Technical due diligence considers geotechnical, environmental, topographical, hydrological, utility and infrastructure conditions. Commercial due diligence tests demand, competition, pricing, absorption and operating assumptions. Financial due diligence examines taxes, funding conditions, cash-flow timing and sensitivity to delay.

The distinction between hard constraints and manageable constraints is useful. A statutory prohibition, protected wetland or inadequate legal access may be a hard constraint. A difficult utility relocation, parking solution or phased construction arrangement may be manageable but costly. The distinction helps management focus resources on genuine go/no-go issues rather than treating all problems as equivalent.

Approvals should be managed through a risk-based schedule. Critical-path approvals require early engagement, complete submissions and contingency planning. Informal discussions with authorities may improve understanding, but they do not replace formal approval. Reliance on verbal assurances is a frequent professional error.

Master Planning as a Value-Creation Exercise

Master planning organizes land, buildings, movement, open space, infrastructure, public realm and development phasing into a coherent whole. It is not merely the placement of buildings on a site. It establishes how people arrive, move, work, live, interact and receive services over time.

A master plan should integrate at least five dimensions. First, the spatial structure defines blocks, plots, building envelopes, streets, landscape and public or private areas. Second, the movement structure addresses pedestrians, public transport, private vehicles, servicing, emergency access and parking. Third, the infrastructure structure coordinates water, drainage, power, communications, waste and energy systems. Fourth, the economic structure considers saleable or lettable area, phasing, construction packages, operating costs and revenue generation. Fifth, the social and environmental structure addresses accessibility, safety, climate response, ecological performance and community impact.

Master planning involves trade-offs. Higher density may improve land efficiency and transit viability but increase infrastructure demand, congestion or shadowing. More parking may support marketability but consume valuable land and weaken public-realm quality. A larger central open space may improve identity and wellbeing but reduce immediately monetizable area. These choices should be assessed through whole-life value rather than a single gross-area metric.

Phasing is a critical part of the plan. A first phase must be financially and operationally viable without depending on infrastructure that will only exist in a later phase. Temporary access, construction logistics, utility capacity, sales sequencing and the location of future amenities should be considered from the beginning. Poor phasing can leave partially completed districts, stranded infrastructure or an unattractive first release.

Design Development and Interdisciplinary Coordination

Design development converts a development brief into coordinated architectural, structural, building-services, landscape, civil and specialist information. The brief should state not only area and appearance but also user requirements, performance standards, operational model, durability expectations, sustainability targets, accessibility requirements, security principles, maintenance philosophy and budget limits.

The design brief is the principal link between strategy and design. A weak brief produces late changes because stakeholders have different interpretations of quality, flexibility or operational performance. A good brief identifies measurable outcomes. For example, “high-quality office accommodation” is less useful than requirements concerning floor-plate efficiency, daylight, floor loading, adaptability, acoustic performance, energy intensity and servicing.

Design maturity generally develops from concept or feasibility design through schematic design, design development and technical or construction documentation. The boundaries differ by procurement route. Under a design-bid-build arrangement, tender information is normally more complete before contractor appointment. Under design-and-build, the employer’s requirements may be issued earlier, but the allocation of design responsibility must be explicit. In either case, design maturity should be assessed by information content and coordination, not by the apparent attractiveness of drawings.

Interdisciplinary coordination is essential because many failures occur at interfaces. Examples include structural beams conflicting with duct routes, façade systems failing to accommodate movement, drainage levels conflicting with landscape design, or fire access being compromised by public-realm features. Coordination reviews should include spatial review, code compliance, access and maintenance review, operational simulation and constructability analysis.

The design freeze is a controlled decision, not an assumption that design will never change. It establishes which elements are fixed, which remain provisional, who may authorize changes and how changes affect cost, schedule, approvals and performance. Freezing design too early can suppress beneficial innovation; freezing it too late transfers design uncertainty into procurement and construction.

Constructability and Buildability

Constructability is the extent to which a design facilitates efficient, safe, economical and predictable construction. Buildability is closely related and often emphasizes practical ease of execution. Both require the construction team’s perspective before tender.

A constructability review considers site access, temporary works, logistics, crane positions, excavation support, sequencing, material handling, tolerances, repetitive elements, prefabrication, workforce capability, local supply chains, weather exposure, safety and commissioning. It also examines whether the design can be inspected, maintained and safely altered during its useful life.

Constructability is not a request to reduce design ambition automatically. Rather, it tests whether the intended outcome can be achieved through a reliable method. A complicated façade joint, for example, may be justified by performance or identity, but the project team should understand its procurement lead time, installation tolerance, mock-up requirement and maintenance consequences.

Early contractor involvement may be appropriate where the project has unusual ground conditions, complex logistics, specialist systems or a compressed schedule. However, it should be governed carefully so that technical advice does not become an uncompetitive procurement advantage. Independent benchmarking, transparent scope definition and conflict controls remain necessary.

Cost Planning, Risk Allowances and Value Engineering

Cost planning is a continuous process of aligning design decisions with the investment case. It differs from a single estimate prepared at the end of design. Cost planning establishes a cost model, updates it as information improves and explains the effects of design and market changes.

A robust cost plan separates at least:

• land and transaction costs;
• professional and statutory fees;
• enabling works and demolition;
• construction works by element or package;
• infrastructure and external works;
• finance, insurance, taxes and marketing;
• client contingencies and design development allowances; and
• escalation and other time-related allowances.

The cost manager should state the basis of measurement, price date, assumptions, exclusions, procurement assumptions and confidence range. A low estimate with hidden exclusions is less useful than a transparent estimate with an explicit uncertainty range.

Contingency is an allowance for identified or reasonably foreseeable uncertainty; it is not a device for concealing an unrealistic budget. It should be allocated according to risk and progressively reduced only as uncertainty is resolved. Escalation, by contrast, addresses changes in prices over time. Mixing the two obscures the project’s exposure.

Value engineering is a structured method of achieving required functions at optimum whole-life value. It is not synonymous with indiscriminate cost cutting. The value relationship may be expressed conceptually as:

Value = Function or performance delivered ÷ Life-cycle cost

A value-engineering workshop identifies functions, examines alternatives and evaluates effects on capital cost, operating cost, time, risk, quality, revenue and user experience. For instance, replacing a material may reduce initial cost but increase maintenance, replacement frequency or energy use. A sound decision therefore considers life-cycle consequences.

Value engineering should occur early, when changes can be made without major redesign. Late value engineering often becomes “value destruction” because it removes visible features without revisiting the underlying function or business case. Decisions should be recorded in a value register showing the proposal, affected function, cost effect, programme effect, risks, responsible decision-maker and approval status.

Procurement Strategy and Tender Readiness

Procurement strategy determines how design, construction, risk and price will be organized. Common approaches include traditional design-bid-build, design-and-build, construction management, management contracting and negotiated or two-stage arrangements. No method is universally superior.

Traditional procurement can provide greater design definition before tender and clearer price comparison, but it may delay construction and retain design risk with the client. Design-and-build may improve integration and offer a single point of responsibility, but the employer must define performance requirements clearly and manage the risk of reduced design control. Two-stage procurement can obtain contractor input early while preserving competition, but it requires strong cost governance and an agreed process for converting pre-construction services into the construction contract.

The choice should reflect project complexity, design maturity, market capacity, client capability, desired risk allocation, funding requirements, schedule and the importance of price certainty. Risk should be allocated to the party best able to control it, not simply transferred to the party with the weakest negotiating position.

Tender readiness requires more than issuing drawings. A project is generally ready when the scope is sufficiently defined, approvals and conditions are understood, interfaces are allocated, site information is reliable, pricing assumptions are stated, the programme is credible, the contract strategy is approved, and unresolved matters are visible and managed. Typical tender information includes employer’s requirements or specifications, drawings, schedules, bills or pricing documents, geotechnical and survey information, draft contract conditions, programme requirements, quality standards and bidder instructions.

A tender-readiness review should test whether bidders can submit comparable offers. Ambiguous scopes produce artificial price differences, qualifications and later claims. The project team should identify provisional sums, client-supplied items, design portions, utility responsibilities, testing requirements and commissioning obligations explicitly.

Project Governance and Decision Rights

Governance is the system through which authority, accountability, information and assurance are organized. Pre-construction projects require governance because multiple parties make decisions with different incentives and incomplete information.

A practical governance structure may include an investment or steering committee, a project director, a development manager, a design manager, a cost manager, a planning and approvals lead, a legal adviser, a risk function and specialist consultants. The structure should be proportionate to project scale but must clarify who recommends, who decides, who reviews and who is informed.

Useful governance instruments include a responsibility assignment matrix, decision log, risk register, assumptions register, change-control procedure, design deliverables schedule, approval tracker, cost report, programme, document-control protocol and stage-gate checklist. The assumptions register is particularly important because feasibility models often contain assumptions about density, price, absorption, approvals, utility capacity and construction duration. Each material assumption should have an owner, evidence status and review date.

Change control should distinguish between design development, client change, statutory change, unforeseen condition and correction of error. Every material change should identify its effect on cost, time, quality, risk, approvals, operations and revenue. Governance is weakened when decisions are made informally in meetings and not recorded.

Independent assurance or peer review is valuable at major gates. It can challenge optimism bias in cost, programme and approvals, while preserving management ownership of the project. Good governance does not eliminate uncertainty; it makes uncertainty visible early enough to manage.

Applied Case: The Riverside Exchange Development

Background

The following is an illustrative case. A developer proposes Riverside Exchange, a mixed-use project on a 4.2-hectare former industrial site near a metropolitan transport corridor. The concept includes residential units, flexible workspace, retail, a public plaza and a mobility hub. The site consists of four parcels controlled through separate agreements. The investment committee has approved expenditure on planning and design but has not yet authorized construction.

Situation and Problem

The preliminary feasibility study assumed a high development density and direct connection to a municipal sewer. During due diligence, the team discovered possible soil contamination, an easement crossing one parcel, uncertain utility capacity and a planning policy requiring a transport-impact assessment. The architect’s initial concept also placed the loading area where the easement restricted construction. Meanwhile, the cost plan exceeded the investment limit by 9 percent. Senior management faced pressure to submit a planning application quickly in order to protect the launch date.

Analysis

The project team first separated fatal or potentially fatal issues from issues capable of mitigation. The easement and fragmented land control affected the physical plan and legal certainty. The sewer assumption affected both cost and programme. Contamination required investigation before the remediation strategy could be priced. The transport assessment was a critical approval dependency. The cost overrun was not attributable to one design feature; it resulted from excessive basement provision, an elaborate façade, inefficient servicing and optimistic assumptions concerning infrastructure contributions.

A risk workshop rated the main risks by probability, impact, proximity and controllability. It concluded that submitting an ambitious application without resolving the easement and access strategy could create redesign and reputational risk. The correct response was not simply to delay the project, but to re-sequence the work.

Approach and Solution

The developer adopted five measures. First, it negotiated a conditional amendment with the parcel owner and commissioned a boundary and easement survey. Second, it undertook intrusive environmental investigations and obtained an independent remediation opinion. Third, the civil engineer developed two drainage strategies: a municipal connection subject to capacity confirmation and an on-site attenuation solution. Fourth, the design team revised the master plan to move servicing, reduce basement dependence and create a more efficient building grid. Fifth, a value-engineering workshop compared façade systems, parking ratios, public-realm specifications and plant-room arrangements using whole-life criteria rather than initial cost alone.

The governance committee then established a stage gate requiring evidence of land control, acceptable environmental risk, a defensible transport strategy, updated cost plan and approval pathway before authorizing the planning submission. The design manager introduced a coordinated model, a design responsibility matrix and fortnightly interface reviews. The cost manager reported base cost, risk allowances and escalation separately.

Outcome

The revised plan reduced the apparent floor-area efficiency slightly but improved access, phasing and construction logistics. The project’s cost exposure moved within the investment limit after design changes and a more realistic infrastructure allowance. The planning submission was made later than originally hoped, but it was supported by better technical evidence and fewer unresolved assumptions. The project was subsequently considered tender-ready only after the main approval conditions, technical interfaces and procurement documents were aligned.

Learning Points

The case demonstrates that speed is not the same as progress. Early expenditure on surveys, legal clarification and coordinated design can prevent much larger downstream costs. It also illustrates that value engineering must protect function and long-term performance, while governance should make assumptions and decision dependencies visible. Most importantly, a planning application, an investment approval and a tender package are different milestones and should not be treated as interchangeable.

Risks, Common Mistakes and Professional Limitations

Pre-construction decisions are exposed to optimism bias, incomplete information and pressure to announce dates. Common mistakes include acquiring land before verifying development rights; treating preliminary area schedules as guaranteed yield; ignoring abnormal ground conditions; assuming utilities are available; allowing design disciplines to progress independently; using contingency to conceal scope gaps; selecting procurement before understanding design maturity; and approving changes without a cumulative-impact review.

Another risk is scope creep, in which stakeholder requests accumulate without an explicit decision about budget or programme. The opposite risk is excessive early rigidity, where a concept is defended despite evidence that market demand, planning policy or construction economics have changed.

Limitations also arise from model uncertainty. Feasibility models depend on assumptions about rent, sales values, absorption, interest rates, inflation, tax, construction productivity and timing. Scenario analysis and sensitivity testing do not predict the future, but they reveal which assumptions deserve management attention. A sophisticated model cannot compensate for poor source data or weak governance.

Ethically, project teams must avoid misleading authorities, lenders, investors or purchasers through selective presentation of risks. Consultants should disclose conflicts of interest, contractors should not receive unfairly privileged information, and sustainability claims should be supported by verifiable performance criteria. Accessibility, displacement, environmental impact and community effects should be treated as substantive project considerations rather than public-relations issues.

Digital Practice and Emerging Developments

Building information modelling can support spatial coordination, quantity extraction, clash detection, asset data and construction sequencing. Geographic information systems assist in land assembly, infrastructure analysis, accessibility studies and environmental mapping. Common data environments improve document control by maintaining a controlled record of current information and approvals.

Automation can assist with approval tracking, design checking, cost-plan comparison, change logs and risk dashboards. Artificial intelligence may support option generation, document classification, anomaly detection and scenario analysis, but its outputs require professional validation. It may reproduce errors in source data, misunderstand jurisdiction-specific rules or create apparently precise recommendations without a defensible evidence base. Governance should therefore require traceability, human review, data security and clear responsibility for decisions.

Emerging practice increasingly emphasizes embodied carbon, climate resilience, circular construction, adaptive reuse, digital twins and design for disassembly. These developments expand the meaning of value. A project that has a lower initial cost but high carbon exposure, poor adaptability or significant future maintenance obligations may not represent the best investment. The pre-construction phase is the point at which much of this whole-life performance is designed into the asset.

Best-Practice Principles

Effective pre-construction management rests on several principles:

1. Secure and verify land control before relying on development yield.

2. Treat approvals as a managed network of dependencies, not a checklist.

3. Test commercial, legal, technical and environmental assumptions together.

4. Use the design brief to express measurable user and performance outcomes.

5. Involve construction and operations expertise before key design decisions are fixed.

6. Maintain a transparent cost plan with explicit assumptions and risk allowances.

7. Use value engineering to protect function and whole-life value, not merely reduce capital cost.

8. Match procurement strategy to design maturity, client capability and risk allocation.

9. Use stage gates and documented decision rights to control uncertainty.

10. Do not declare tender readiness until scope, interfaces, approvals and pricing information are sufficiently defined.

Chapter Summary

Planning, design and pre-construction management transform a real estate opportunity into an authorized, coordinated and procurable project. Land assembly must be assessed through legal, physical and regulatory control, while entitlement management requires a live approval matrix and evidence-based due diligence. Master planning integrates spatial, movement, infrastructure, economic, social and environmental considerations, including the practical requirements of phasing.

Design development should be guided by a measurable brief and supported by interdisciplinary coordination, constructability review and controlled design decisions. Cost planning is continuous and must separate base cost, contingency, escalation and other allowances. Value engineering seeks optimum whole-life value rather than indiscriminate savings. Procurement strategy should reflect design maturity and allocate risk to the party best able to manage it. Finally, project governance makes assumptions, responsibilities, changes and decision gates visible. Digital tools can improve coordination and analysis, but professional judgment, ethical conduct and human accountability remain essential.

Key Terms

Land assembly: Consolidation or control of multiple parcels for an integrated development.

Development control: The legal, contractual and practical ability to undertake and manage development.

Entitlement: A legal or administrative right to develop land for a specified use or intensity.

Approval matrix: A schedule identifying required approvals, dependencies, responsibilities and status.

Development envelope: The three-dimensional limit within which development may occur.

Due diligence: Systematic investigation of legal, planning, technical, environmental, commercial and financial conditions.

Master plan: An integrated framework for land use, buildings, movement, infrastructure, open space and phasing.

Design brief: A statement of required functions, performance, quality, operational and commercial outcomes.

Design freeze: A controlled decision establishing which design elements are fixed and how later changes are governed.

Constructability: The extent to which a design supports safe, efficient and predictable construction.

Cost plan: A structured, progressively updated forecast of project expenditure based on stated assumptions.

Contingency: An allowance for identified or reasonably foreseeable uncertainty.

Value engineering: A structured analysis of alternatives to optimize function, performance and life-cycle value.

Procurement strategy: The selected method for organizing design, construction, risk, price and contractual responsibility.

Tender readiness: The condition in which scope, information, approvals, interfaces and commercial documents support comparable bids.

Stage gate: A formal decision point at which evidence is reviewed before further commitment.

Scope creep: Uncontrolled expansion of project requirements without approved adjustment to cost, time or resources.

Common data environment: A controlled digital system for storing, managing and sharing project information.

Review Questions

Short Answer Questions

1. Why is land ownership different from development control?

2. What information should an approval matrix contain?

3. Define constructability and state two matters it examines.

4. Why should escalation be separated from contingency in a cost plan?

5. What is the purpose of a design freeze?

Long Answer Questions

1. Explain the relationship between land assembly, entitlements, master planning and project feasibility.

2. Discuss how a development brief supports design development and interdisciplinary coordination.

3. Compare traditional procurement and design-and-build procurement in relation to design maturity and risk allocation.

4. Explain the principles and limitations of value engineering in a real estate project.

5. Describe a governance framework suitable for taking a mixed-use project from concept to tender readiness.

Analytical / Application Questions

1. A proposed project has attractive market demand but unresolved access rights, uncertain utility capacity and a cost plan 12 percent above budget. Recommend the sequence of investigations and decision gates that should precede a planning submission.

2. A design option reduces capital cost by replacing a durable façade with a cheaper system but increases maintenance and energy costs. How should the project team evaluate the proposal?

3. A contractor claims that tender documents are adequate, while bidders submit widely different qualifications. Diagnose the likely pre-construction weaknesses and propose corrective actions.

22. Multiple Choice Questions with Answers

Question 1

Which statement best explains why ownership alone does not guarantee development potential?

A. Ownership automatically expires when planning policy changes

B. Development also depends on legal rights, approvals, access and physical feasibility

C. Only contractors can determine whether land may be developed

D. Ownership is relevant only after construction begins

Correct Answer: B. Development also depends on legal rights, approvals, access and physical feasibility

Question 2

What is the primary purpose of an approval matrix?

A. To replace statutory approvals with internal approval

B. To identify approval dependencies, responsibilities, requirements and status

C. To calculate the contractor’s final profit

D. To freeze all design decisions permanently

Correct Answer: B. To identify approval dependencies, responsibilities, requirements and status

Question 3

A master plan that places a future infrastructure requirement outside the first phase creates which principal risk?

A. The first phase may be unable to operate independently

B. The project will necessarily have excessive design quality

C. The site will automatically receive additional density

D. Tender bids will become identical

Correct Answer: A. The first phase may be unable to operate independently

Question 4

Which is the strongest example of constructability review?

A. Selecting a building colour without considering installation

B. Testing crane positions, sequencing, access, tolerances and material handling

C. Increasing the marketing budget before design coordination

D. Removing all specialist systems from the design

Correct Answer: B. Testing crane positions, sequencing, access, tolerances and material handling

Question 5

Why should contingency and escalation be reported separately?

A. They are identical allowances with different names

B. Contingency addresses uncertainty, while escalation addresses price change over time

C. Escalation is a legal approval and contingency is a design discipline

D. Separating them eliminates all project risk

Correct Answer: B. Contingency addresses uncertainty, while escalation addresses price change over time

Question 6

Which value-engineering decision best reflects whole-life value?

A. Choosing the cheapest material regardless of maintenance performance

B. Deleting a required safety system to preserve the budget

C. Comparing capital, operating, maintenance, performance and user effects of alternatives

D. Postponing all cost analysis until construction is complete

Correct Answer: C. Comparing capital, operating, maintenance, performance and user effects of alternatives

Question 7

A project with incomplete design, complex interfaces and a need for contractor input may be suited to which approach?

A. A carefully governed two-stage procurement approach

B. Tendering without defining responsibilities

C. Ignoring specialist advice until after completion

D. Issuing inconsistent information to different bidders

Correct Answer: A. A carefully governed two-stage procurement approach

Question 8

Which item is most indicative of tender readiness?

A. A visually attractive concept image

B. An unresolved scope with informal verbal agreements

C. Defined scope, coordinated interfaces, credible programme and suitable pricing information

D. A cost estimate with undisclosed exclusions

Correct Answer: C. Defined scope, coordinated interfaces, credible programme and suitable pricing information

Question 9

In the Riverside Exchange case, why was submitting an immediate planning application considered risky?

A. Planning applications never require technical evidence

B. Unresolved easement, access, environmental and infrastructure issues could force redesign

C. The project had no proposed use

D. The cost plan was already below the investment limit

Correct Answer: B. Unresolved easement, access, environmental and infrastructure issues could force redesign

Question 10

What is the most appropriate governance response to a material design change?

A. Implement it informally if the architect supports it

B. Record its effects on cost, time, quality, risk, approvals and operations before authorization

C. Ignore cumulative impacts if the change appears minor

D. Transfer all responsibility to the future contractor

Correct Answer: B. Record its effects on cost, time, quality, risk, approvals and operations before authorization