Digital Construction, BIM and Emerging Practice

Introduction

Construction planning and management are being transformed by digital technologies. Traditional planning relied heavily on drawings, spreadsheets, paper records, telephone calls and periodic site meetings. These methods remain useful, but they often produce fragmented information, delayed reporting and weak visibility of project performance. Digital construction connects planning, design, procurement, site production, quality, safety, cost and facilities management through structured information and collaborative platforms.

Building Information Modelling (BIM) is central to this transformation, but digital construction is broader than BIM. It includes scheduling and project-management software, common data environments (CDEs), mobile reporting, drones, sensors, Internet of Things (IoT) systems, digital twins, artificial intelligence (AI), modular construction and data-driven decision-making. These tools do not automatically improve a project. Their value depends on reliable data, competent people, clearly defined processes, appropriate contracts and effective governance.

For construction engineers, digital competence is therefore a professional capability rather than an optional computer skill. A planner must understand both what a technology can do and how it should be applied safely, ethically and economically.

Learning Objectives

After studying this chapter, a student should be able to:

1. Explain the role of scheduling and project-management software in construction control.
2. Describe BIM-based planning, information requirements and model coordination.
3. Explain the purpose and operation of a common data environment.
4. Evaluate mobile reporting, drones, IoT systems and digital twins.
5. Interpret the potential and limitations of AI-assisted forecasting and optimisation.
6. Identify cybersecurity, privacy, data-quality and ethical risks.
7. Relate digital practice to lean construction, modular delivery and sustainability.
8. Recommend future skills and implementation practices for a construction organisation.

1. Digital Construction as an Integrated Management System

Digital construction is the planned use of digital information, communication networks, software, sensing and automation across the asset life cycle. Its purpose is not merely to replace paper. It is to improve the quality, accessibility, timeliness and traceability of decisions.

A useful distinction is:

• Digitisation: converting analogue information into a digital form, such as scanning a paper drawing.
• Digitalisation: improving a process using digital tools, such as electronic approval workflows.
• Digital transformation: redesigning organisational practices, responsibilities and business models around connected information.

A project may possess many digital files without being digitally mature. Digital maturity requires consistent information standards, interoperable systems, capable users and management commitment.

The construction information cycle commonly includes:

1. defining information requirements;
2. producing or collecting information;
3. checking and approving information;
4. sharing information with authorised users;
5. using information for decisions and field operations;
6. recording as-built and operational information; and
7. retaining or archiving information for future use.

This cycle is closely related to project controls. The planner compares the approved baseline with actual progress, forecasts future performance and recommends corrective action. Digital systems can accelerate this cycle, but they cannot compensate for an unrealistic baseline or inaccurate site observations.

2. Scheduling and Project-Management Software

Construction scheduling software supports the development, analysis and communication of a project programme. Common functions include activity definition, logical relationships, calendars, resource assignment, cost loading, baseline comparison, progress updating, forecasting, reporting and what-if analysis.

2.1 From activities to an executable programme

A schedule should represent work that can be planned, assigned, measured and controlled. Typical development steps are:

1. define the project scope and work breakdown structure (WBS);
2. divide work packages into activities;
3. estimate activity durations;
4. identify logical relationships;
5. assign calendars, resources and constraints;
6. calculate dates and identify critical activities;
7. review constructability and resource feasibility;
8. approve a baseline; and
9. update the programme using verified progress data.

The WBS decomposes the project into deliverables and work packages. It should not be confused with an organisational chart or a list of trades. A good WBS provides a logical structure for schedule, cost, responsibility and reporting.

2.2 Network logic and critical path

Most scheduling systems use a precedence network. In a finish-to-start relationship, the successor cannot start until the predecessor has finished. Other relationships include start-to-start, finish-to-finish and finish-to-start with lag. Excessive use of mandatory constraints can conceal the real logic and weaken forecasting.

For an activity, the basic forward-pass relationships are:

where ES is early start, EF is early finish and d is activity duration. For a network with a project completion date, a backward pass determines late dates. Total float may be expressed as:

where LS and LF are late start and late finish. These relationships assume a consistent time unit and a defined scheduling convention. The critical path is the longest path through the network in terms of controlling completion; in a simple deterministic network, activities on that path commonly have zero total float. In real projects, calendars, constraints, multiple completion milestones and resource limitations can make criticality more complex than a single path.

Worked example. Activity A takes 4 working days. Activity B takes 3 days and follows A. Activity C takes 5 days and also follows A. Activity D takes 2 days and follows both B and C. The two paths are A–B–D = 4 + 3 + 2 = 9 days and A–C–D = 4 + 5 + 2 = 11 days. Therefore, under the stated logic and assumptions, A–C–D controls the 11-day completion duration. Path A–B–D has 2 days of path difference, although individual float must be calculated from the complete network.

2.3 Baselines, updates and performance measurement

A baseline is the approved reference programme against which actual progress and forecasts are compared. It should be preserved and changed only through controlled approval. Updating a schedule involves entering actual starts and finishes, remaining durations, quantities installed, reasons for variance and revised logic where justified.

A percentage complete is meaningful only when its measurement rule is defined. For example, a concrete activity might be measured by verified installed volume, while design may use approved deliverables. “Started” is not equivalent to “50% complete”.

Earned value management (EVM) combines schedule and cost information. The principal quantities are:

• Planned Value (PV): budgeted value of work scheduled by a status date.
• Earned Value (EV): budgeted value of work actually completed by that date.
• Actual Cost (AC): actual cost incurred for the completed work.

Two common indices are:

SPI is the Schedule Performance Index and CPI is the Cost Performance Index. They are dimensionless ratios. Values below 1 indicate less earned value than planned or less value earned per unit of cost, respectively. EVM requires a credible time-phased budget, objective progress measurement and consistent cost recording. SPI should not be interpreted as a direct percentage of time acceleration or delay in every circumstance.

2.4 Selecting and governing software

Software selection should consider project scale, contract requirements, interoperability, user skills, security, licensing cost, offline capability and reporting needs. Important controls include:

• a standard WBS and coding system;
• named schedule owners and update responsibilities;
• a defined data date and reporting calendar;
• approval of baselines and changes;
• version control;
• documented assumptions and constraints;
• training and user access management; and
• regular schedule health checks.

A visually attractive programme can still be defective if it contains open ends, excessive lags, unrealistic durations, missing procurement activities or unverified progress.

3. BIM-Based Planning

BIM is a process for creating, managing and exchanging structured information about a built asset. A BIM model may include geometry, materials, specifications, spatial relationships, quantities, classifications, manufacturer data, maintenance information and status. BIM is not simply three-dimensional computer-aided drafting.

3.1 Dimensions and uses of BIM

The labels 3D, 4D, 5D and 6D are used in industry, although their exact meanings vary. A common interpretation is:

Some organisations use 7D for facilities management or sustainability. The label is less important than clearly defining the information and workflow required.

3.2 4D planning

In 4D planning, model objects are associated with schedule activities. The resulting simulation can show the planned sequence of excavation, structure, services, finishes, access routes and temporary works. It can reveal spatial and temporal conflicts that are difficult to identify in separate drawings and bar charts.

A 4D model is not automatically a valid construction plan. It must still consider temporary works, crane access, material storage, safety zones, workface congestion, inspection points, commissioning and handover. Model elements must be coded consistently with schedule activities, otherwise the visualisation may be misleading.

3.3 Model coordination and information requirements

BIM delivery should begin with information requirements, not software selection. An appointing party may specify organisational information requirements, asset information requirements and exchange information requirements. A project information standard then defines naming, classification, coordinates, file formats, approval states, model detail and model information content.

A BIM execution plan identifies responsibilities, model uses, software, coordination procedures, federation rules, issue management and information exchange dates. It should be treated as a project management document and updated when project arrangements change.

Clash detection may identify:

• hard clashes, in which physical elements occupy the same space;
• clearance clashes, in which required access or maintenance space is blocked; and
• workflow or time-space clashes, in which activities compete for an area or resource at the same time.

The purpose of coordination is not to eliminate every geometrical intersection at any cost. Issues must be prioritised according to safety, function, constructability, cost, programme and contractual responsibility.

4. Common Data Environments

A CDE is a managed source of information for collecting, managing, distributing and preserving project information. It may be cloud-based, server-based or a combination, but it must provide controlled workflows rather than merely acting as a shared folder.

Typical information states include:

1. Work in progress: information being developed by its originator.
2. Shared: information issued for coordination or wider review.
3. Published or authorised: information approved for a defined purpose.
4. Archived: superseded or retained information preserved for audit and future reference.

The exact terminology varies by standard and organisation. The essential principles are status control, revision identification, permissions, review records and an auditable history.

A CDE should define who can create, review, approve, download, modify and delete information. File naming conventions should identify the project, originator, volume or system, level or location, type, role and revision where appropriate. Metadata often provides more reliable searching than file names alone.

A CDE reduces the risk of teams constructing from superseded drawings, but it creates new risks if synchronisation is poor, access is misconfigured or users download local copies without checking status. The project team must establish a clear “single source of truth” and communicate how field personnel obtain current information.

5. Mobile Reporting, Drones and IoT

5.1 Mobile reporting

Mobile applications allow supervisors and engineers to record inspections, photographs, checklists, requests for information, quality observations, safety events, delivery records and daily diaries at the workface. Advantages include faster communication, location and time stamps, reduced transcription and improved traceability.

Good mobile forms are short, logically sequenced and designed for field conditions. They should allow offline capture where connectivity is unreliable and synchronise securely when a connection becomes available. Mandatory fields should be limited to information genuinely required; otherwise users may enter meaningless values simply to submit a form.

Photographs should be linked to a location, date, subject, description and responsible action. A photograph without context is weak evidence. Digital signatures and approvals must be governed so that they represent an actual review rather than an automatic button press.

5.2 Drones and reality capture

Unmanned aerial systems can support progress photography, topographic survey, stockpile measurement, roof inspection, façade inspection and safety observation. Photogrammetry can produce orthomosaics and point clouds when images are captured with adequate overlap, control points and suitable lighting.

Use of drones requires attention to aviation rules, site permissions, competence, weather, exclusion zones, privacy and data storage. A drone survey is not automatically accurate enough for setting out or payment measurement. Accuracy must be verified against known control points and the survey specification.

Laser scanning and 360-degree imaging can also compare as-built conditions with design models. The value of reality capture depends on the decision it supports: detecting a deviation early can be valuable, whereas collecting a large point cloud without a defined use creates storage and processing cost.

5.3 IoT and connected site systems

IoT systems connect sensors, equipment and software through communication networks. Construction examples include concrete maturity sensors, environmental monitors, equipment telematics, worker-location systems, vibration sensors, water-level sensors and energy meters.

A typical chain is: sensor → gateway → network → data platform → analysis → management action. Failure at any link can produce misleading results. Sensors require calibration, maintenance, correct placement, power management and protection from damage. Data must be interpreted in relation to construction conditions rather than treated as unquestionable truth.

6. Digital Twins

A digital twin is a digital representation of a physical asset or process that is connected to the physical world through data and is used to understand, monitor or predict behaviour. A static BIM model is not necessarily a digital twin. A twin generally requires an identified physical counterpart, ongoing data exchange, a defined purpose and sufficient accuracy for the decisions being made.

For example, a building twin might combine the asset model with occupancy, temperature, energy and equipment-status data. During construction, a developing twin may compare planned and actual installation, track commissioning status and support handover. The twin should be designed around decisions such as maintenance planning, energy optimisation or safety monitoring.

Digital twins face challenges involving data ownership, sensor reliability, interoperability, cyber risk, cost and long-term maintenance. A highly detailed model is not automatically useful if operational data are incomplete or if facilities staff cannot use the system.

7. AI-Assisted Forecasting and Optimisation

AI and machine-learning tools can analyse large datasets to identify patterns, classify images, predict delays, estimate costs, optimise sequences and support document search. Examples include predicting the likelihood of schedule slippage from progress trends, detecting safety helmet compliance in images and identifying abnormal equipment behaviour.

A predictive model typically uses historical or current input variables to estimate an outcome. Inputs might include planned duration, actual production rates, weather, crew size, change volume, procurement status and observed progress. The output is a forecast, not a certainty.

A simple forecasting measure is the mean absolute error:

where n is the number of observations, yᵢ is the observed value and ŷᵢ is the predicted value. Both values must use the same unit, such as days or cubic metres. MAE treats all errors linearly and is easy to interpret; other measures may be appropriate where large errors have special significance.

AI implementation should follow a disciplined sequence:

1. define the management decision and success criterion;
2. identify lawful, relevant and reliable data;
3. clean and label the data;
4. separate training, validation and test data where modelling is used;
5. check performance against a practical baseline;
6. examine bias, uncertainty and failure cases;
7. pilot the system with human oversight; and
8. monitor performance after deployment.

AI limitations include poor-quality historical records, changing project conditions, biased training data, lack of explainability, automation bias and cybersecurity threats. A model trained on one contractor’s projects may not generalise to a different market, contract type or climate. AI should assist professional judgement, not remove accountability for safety, quality or contractual decisions.

Optimisation tools may generate a schedule that is mathematically efficient but operationally unacceptable. For example, a sequence may minimise duration while creating unsafe congestion or impossible access. Constraints must therefore include practical, legal and ethical requirements, not only cost and time.

8. Cybersecurity, Data Ethics and Governance

Construction organisations are attractive targets for cybercrime because they hold financial information, personal data, designs, access credentials and operational details. Threats include phishing, ransomware, unauthorised access, insider misuse, malware, data leakage and manipulation of project records.

A proportionate cybersecurity programme includes:

• multi-factor authentication;
• least-privilege access;
• timely software and device updates;
• encryption in transit and at rest where appropriate;
• secure backups tested through restoration exercises;
• phishing and social-engineering training;
• supplier and cloud-platform due diligence;
• incident response procedures; and
• logging, monitoring and periodic access reviews.

Data ethics extends beyond technical security. Project teams should consider whether data collection is necessary, whether people have been informed, whether surveillance is proportionate, whether data are accurate and whether automated decisions could unfairly affect workers or suppliers. Facial recognition and worker tracking require especially careful justification, legal review and consultation.

Information governance should assign ownership, stewardship and accountability. A model author may be responsible for model content, while the information manager controls exchange procedures and the project manager controls approval and use. These roles should be stated in contracts and project plans. Data retention and deletion should follow legal, contractual and operational requirements.

9. Lean Construction, Modular Delivery and Sustainability

Digital tools can support lean construction, but lean is a management philosophy rather than a software package. Lean construction seeks to improve value and reliability by reducing waste, making workflow predictable and involving those who perform the work.

The Last Planner System, for example, uses collaborative planning, constraint removal, make-ready processes and reliable weekly commitments. Digital planning boards can improve visibility, but they do not replace conversations among trade contractors and supervisors. A useful measure is the percentage of planned tasks completed, provided the reasons for non-completion are analysed rather than used for blame.

Modular and off-site construction benefit from digital coordination because components must be designed, manufactured, transported and installed to precise requirements. BIM can connect design, fabrication, logistics and site assembly. However, modular delivery shifts risk upstream. Late design changes, inadequate tolerances, transport restrictions and incomplete interfaces can cause significant disruption.

Digital information supports sustainability through material quantity analysis, embodied-carbon assessment, energy monitoring, waste tracking and design alternatives. Digital analysis should distinguish between embodied and operational impacts and should state boundaries, assumptions and data quality. A software output is not a sustainability fact unless the underlying assessment method and data are credible.

10. Illustrative Case: BIM and Mobile Control on a Community Health Centre

Background

A medium-sized contractor is constructing a two-storey community health centre. The project includes complex mechanical and electrical services, a tight urban site and a completion date linked to public funding. The contractor previously relied on weekly spreadsheet updates and printed drawings.

Problem

During early construction, service routes conflicted with beams and ceiling zones. Progress reports arrived several days after inspections, and subcontractors sometimes used superseded drawings. Management could not reliably distinguish design delay from site productivity loss.

Analysis

The project team reviewed the information flow and found four principal weaknesses: inconsistent drawing revisions, no common activity coding between the schedule and model, unstructured site photographs and late constraint identification. The team also recognised that introducing software alone would not solve unclear responsibilities.

Approach and solution

The team established a CDE with controlled work-in-progress, shared, authorised and archived states. The BIM execution plan assigned model responsibilities and required service zones to be coordinated before installation. The programme was restructured so that major model elements and installation work packages used common codes. A 4D review was held every two weeks for the next work areas.

Supervisors used a mobile application to complete inspection checklists and attach location-tagged photographs. The application was configured for offline use. A drone survey was used monthly for roof and external progress, while total-station checks verified critical dimensions. A dashboard compared planned quantities, verified installed quantities, open coordination issues and constraints.

Outcome

The revised process identified several service conflicts before installation and reduced repeated site queries. Management also discovered that apparent schedule delay was partly caused by late approvals rather than low labour productivity. The project did not become “automatic”; experienced engineers still reviewed model issues, field conditions and subcontractor proposals.

Learning points

1. The CDE improved control because information states and responsibilities were defined.
2. 4D planning was effective because model objects and schedule activities shared a coding structure.
3. Mobile reporting improved timeliness only because forms and approval rules were designed for field use.
4. Reality capture supported decisions when surveys were checked against known requirements.
5. Digital implementation produced organisational learning, not merely new files.

This is an illustrative case, not a report of a specific real project.

11. Implementation Strategy and Future Skills

A practical digital implementation should begin with a small number of high-value use cases. Examples include drawing control, progress measurement, inspection management or material tracking. The organisation should establish a baseline process, pilot the digital method, measure benefits and refine the approach before scaling.

A digital adoption plan should address:

• business objectives and measurable benefits;
• current capability and gaps;
• information standards and interoperability;
• hardware, software and connectivity;
• training and change management;
• procurement and contractual responsibilities;
• cybersecurity and data protection;
• support, maintenance and system exit arrangements; and
• review of outcomes and lessons learned.

Future construction professionals need a combination of technical, analytical and human skills. These include information management, schedule logic, model interpretation, data literacy, visual communication, cybersecurity awareness, field verification, collaborative problem-solving and ethical judgement. Coding can be useful for automation and data analysis, but the fundamental skill is defining a sound construction problem before selecting a digital solution.

Digital competence must also include the ability to challenge a system. A dashboard may display precise numbers that are based on incomplete observations. A model may appear coordinated while omitting temporary works. An AI forecast may be statistically impressive but operationally irrelevant. Professional responsibility requires questioning assumptions, checking evidence and escalating uncertainty.

Challenges and Limitations

Digital construction has significant limitations:

• high initial investment and continuing subscription costs;
• fragmented software ecosystems and interoperability problems;
• inconsistent standards between organisations;
• poor data quality and duplicate data entry;
• resistance to altered roles and workflows;
• inadequate connectivity on remote sites;
• dependence on vendors and proprietary formats;
• unclear ownership of models and derived data;
• cyber and privacy risks;
• false confidence in visualisations or dashboards; and
• unequal access to training and equipment.

The correct response is not to reject technology, but to match technology to purpose, risk and organisational capability. A paper checklist may remain appropriate where a digital device would be unsafe, impractical or less reliable. Digital transformation should improve construction outcomes, not create unnecessary administrative work.

Best-Practice Checklist

Before adopting a digital construction system, ask:

1. What decision or problem will the system improve?
2. Who owns the information and who is accountable for action?
3. What data are required, and how will their accuracy be checked?
4. How will information be versioned, approved and archived?
5. Can systems exchange data without excessive re-entry?
6. What happens when connectivity, hardware or software fails?
7. Are privacy, safety, contractual and cybersecurity risks controlled?
8. Have field workers and subcontractors been involved in design?
9. How will benefits be measured against a baseline?
10. What human review is required before a decision is implemented?

Chapter Summary

Digital construction integrates information, software, sensors and professional processes across the asset life cycle. Scheduling software supports WBS development, network logic, baselines, updates, forecasting and performance measurement, but its outputs depend on credible data and sound planning assumptions. BIM adds structured asset information and can connect geometry, time, cost and operations. A CDE provides controlled information states, permissions, revision history and a reliable source of project information.

Mobile reporting, drones, reality capture and IoT systems improve the speed and richness of field information when they are properly designed, calibrated and governed. Digital twins extend BIM by connecting a digital representation with an operating physical asset. AI can assist forecasting, classification and optimisation, but predictions require relevant data, validation, uncertainty analysis and human accountability.

Cybersecurity, privacy, data ethics and information ownership are core management responsibilities. Digital methods can support lean construction, modular delivery and sustainability, but technology does not replace collaboration, reliable workflow or professional judgement. Successful implementation begins with a clear problem, defined information requirements, capable users, controlled processes and measurable benefits. Future construction engineers therefore need both digital literacy and the critical judgement to recognise when digital evidence is incomplete or misleading.

Key Terms

Artificial intelligence (AI): Computer-based methods that perform tasks associated with human reasoning, classification, prediction or decision support.

Baseline: An approved reference plan used to compare actual and forecast performance.

BIM: A process for creating, managing and exchanging structured information about a built asset.

Common data environment (CDE): A managed source for collecting, reviewing, sharing and archiving project information.

Critical path: The controlling sequence of activities that determines project completion under stated scheduling assumptions.

Digital construction: The use of connected digital information and technologies to improve construction and asset management.

Digital twin: A connected digital representation of a physical asset or process used for monitoring, analysis or prediction.

Earned Value (EV): The budgeted value of work actually completed by a specified date.

Internet of Things (IoT): A network of connected devices that collect and exchange data.

Lean construction: A management approach focused on value, reliable workflow and reduction of waste.

Machine learning: Computational methods that learn patterns from data to make predictions or classifications.

Model coordination: The process of checking and resolving spatial, information and workflow conflicts between models or disciplines.

Photogrammetry: Measurement and modelling using photographs, commonly to produce maps or point clouds.

Reality capture: Collection of digital information about existing physical conditions using scanning, imaging or surveying.

Schedule Performance Index (SPI): The ratio EV ÷ PV, indicating earned value relative to planned value.

Work breakdown structure (WBS): A hierarchical decomposition of project scope into deliverables and work packages.

Version control: A system for identifying, managing and retrieving successive information revisions.

4D BIM: BIM that links model information with time and construction activities.

Review Questions

Short Answer Questions

1. Distinguish digitisation, digitalisation and digital transformation.
2. What is the purpose of a construction schedule baseline?
3. State two advantages and two limitations of mobile reporting.
4. How does a CDE differ from an uncontrolled shared folder?
5. Why is a digital twin more than a static BIM model?

Long Answer Questions

1. Explain how a WBS, network logic, baseline and progress update work together in project control.
2. Discuss the benefits and limitations of 4D BIM for construction planning.
3. Describe the information states and governance requirements of a CDE.
4. Evaluate the use of drones and IoT sensors for construction monitoring.
5. Explain how cybersecurity and data ethics should influence digital construction implementation.

Analytical / Application Questions

1. A project has repeated drawing errors and late site reports. Propose a digital information workflow, including responsibilities, approvals and field verification.
2. A contractor wants an AI model to predict delay from historical project data. Identify the data, validation, governance and human-review requirements before deployment.
3. A modular building project is experiencing transport, tolerance and installation conflicts. Analyse how BIM, 4D planning, lean methods and a CDE could be combined to reduce the problems.

Multiple Choice Questions with Answers

Question 1

What is the primary purpose of a construction schedule baseline?

A. To provide an approved reference for comparing actual and forecast performance

B. To replace all site inspections

C. To eliminate the need for change control

D. To record only completed activities

Correct Answer: A. To provide an approved reference for comparing actual and forecast performance

Question 2

In a simple deterministic network, which sequence generally controls project completion?

A. The sequence with the fewest activities

B. The sequence with the longest controlling duration

C. The sequence with the highest labour cost

D. The sequence entered most recently

Correct Answer: B. The sequence with the longest controlling duration

Question 3

What does 4D BIM commonly add to a 3D model?

A. Tax records

B. Time and construction sequence information

C. Cybersecurity software

D. Only photographic images

Correct Answer: B. Time and construction sequence information

Question 4

Which CDE state normally contains information being developed by its originator?

A. Archived

B. Published

C. Work in progress

D. Contractually closed

Correct Answer: C. Work in progress

Question 5

A project has EV = 80 and PV = 100, using the same monetary units. What is its SPI?

A. 0.80

B. 1.25

C. 20.00

D. 180.00

Correct Answer: A. 0.80

Question 6

Which practice best improves the reliability of drone survey data?

A. Ignoring weather and lighting conditions

B. Using known control points and checking accuracy against requirements

C. Assuming every photograph has construction-grade accuracy

D. Storing images without location information

Correct Answer: B. Using known control points and checking accuracy against requirements

Question 7

What is a key limitation of an AI forecasting model trained on historical projects?

A. It can never process numerical data

B. It may not generalise to different project conditions

C. It automatically removes all professional responsibility

D. It requires no data validation

Correct Answer: B. It may not generalise to different project conditions

Question 8

Which cybersecurity measure limits users to only the access they need?

A. Least-privilege access

B. Public password sharing

C. Uncontrolled downloading

D. Disabling software updates

Correct Answer: A. Least-privilege access

Question 9

Which statement best describes lean construction?

A. Using the most expensive software available

B. Reducing waste and improving reliable workflow and value

C. Eliminating all collaboration with subcontractors

D. Maximising work-in-progress at every stage

Correct Answer: B. Reducing waste and improving reliable workflow and value

Question 10

Why can a mathematically optimised construction sequence still be unacceptable?

A. Optimisation always increases duration

B. It may ignore safety, access, congestion or practical constraints

C. It cannot include any activities

D. It is unrelated to project conditions by definition

Correct Answer: B. It may ignore safety, access, congestion or practical constraints