top of page
Search

The Cost of Poor Information: Why Quality Management Does Not End at Handover

Writer: Mzukisi Qunta
Mzukisi Qunta
Nov 2
15 min read

By: Mzukisi Qunta

Published: October 2026


Introduction

Construction and infrastructure projects generate enormous amounts of information. From feasibility studies and engineering calculations to drawings, specifications, inspection records, material approvals and asset registers, every stage of a project depends on information being produced, reviewed, communicated and used correctly. Yet despite the amount of time and money invested in developing this information, many organisations continue to experience avoidable delays, rework, conflicting instructions and difficulties when handing completed assets over to their owners.

The problem is not always a lack of information. In many cases, the information exists, but it is incomplete, outdated, inconsistent, difficult to retrieve or unsuitable for the purpose for which it is being used.


A drawing may have been approved but not distributed to the correct people. A model may contain the required geometry but lack the information needed for procurement or maintenance. An inspection record may have been completed without providing sufficient evidence that the relevant work meets the specified requirements.


These situations demonstrate why information management should not be treated as an administrative function separate from quality management. The reliability of information influences how work is planned, how decisions are made, how requirements are verified and how the final asset performs. When information is unreliable, even technically competent teams can make incorrect decisions.


Research into construction rework has repeatedly identified information technology, working procedures and project changes among the factors associated with poor project performance. Love (2016), for example, examined predictors of rework in civil infrastructure projects and found that ineffective use of information technologies and a lack of clearly defined working procedures were among the variables associated with rework costs. More recent research by Love (2025) also highlights the difficulty organisations face in measuring the actual financial consequences of rework, particularly where costs are incompletely recorded. These findings reinforce the need to consider information quality as part of the wider system through which construction work is planned, controlled and delivered.


The important question, therefore, is not simply whether an organisation has a document control procedure or uses a digital information platform. It is whether the organisation can demonstrate that the right information reaches the right people, at the right time, in a form that allows them to perform their work correctly.


The difference between information and reliable information

Organisations often measure their information management capability by the systems they have implemented, the volume of information they retain or the extent to which their processes have been digitised. These measures can provide useful context, but they do not necessarily establish whether the information can be relied upon.


A document management system may contain thousands of drawings and records while employees still struggle to identify the current approved revision. A project may use Building Information Modelling (BIM) without having clear arrangements for verifying the completeness and suitability of the information contained in its models. Similarly, a contractor may maintain detailed inspection records without being able to demonstrate that the recorded inspections correspond to the correct locations, materials or stages of construction.


The distinction becomes clearer when information is considered in relation to its intended use. A drawing used for design coordination may serve a different purpose from a drawing issued for construction. A model developed to communicate design intent may not contain all the information required for fabrication, installation or asset maintenance. The fact that information is available does not automatically make it appropriate for every subsequent activity.


Information quality should therefore be assessed against defined requirements. Depending on the application, this may include accuracy, completeness, consistency, traceability, approval status, accessibility and suitability for the intended purpose. These characteristics are connected, but they are not interchangeable. Information can be accurate but incomplete, complete but outdated, or correctly approved but inaccessible to the people who need it.


This is particularly important in engineering, where decisions are often dependent on information produced by several disciplines. Structural design may depend on architectural layouts, mechanical services may depend on available space and clearances, and construction sequencing may depend on the coordination of several work packages. An error or omission in one information exchange can affect activities well beyond the team that originally produced the information. The challenge is to establish controls that address these relationships rather than relying exclusively on the quality of individual documents.


How poor information becomes a construction cost

The financial consequences of poor information are not always immediately visible. A missing detail may initially generate a request for information. The request may require a designer to investigate the issue, a contractor to suspend an activity and a project manager to coordinate the response. If the answer requires a design change, the consequences may extend to procurement, fabrication, installation and programme planning.


In other circumstances, the work proceeds before the issue is identified. The resulting correction may require materials to be removed, components to be replaced or completed work to be modified. The direct cost is relatively easy to recognise, but the wider consequences can be more difficult to quantify. Labour may be diverted from productive work, equipment may remain idle, inspections may need to be repeated and subsequent activities may be delayed.


Research by Love (2025), published in the Journal of Construction Engineering and Management, provides a useful illustration of the difficulty of measuring these costs. In an exploratory study using actual contractor project data, pre-completion field rework averaged 0.38% of contract value, while the authors estimated that the figure could rise to approximately 0.76% when post-completion corrections were considered. The study also found that recorded rework costs had been substantially underreported. These figures relate to the projects examined and should not be treated as a universal industry benchmark. They nevertheless demonstrate why organisations should not assume that the costs recorded in their existing systems represent the full financial impact of rework.

Poor information is not the cause of every construction defect or delay. Client changes, material failures, workmanship, unforeseen site conditions and design development can all contribute. However, information management determines how effectively many of these issues are communicated, assessed and controlled.


Consider a project where a supplier manufactures components using an outdated drawing. The immediate response might be to investigate the supplier's quality controls and determine whether the manufacturing process complied with the issued information. However, a complete investigation should also examine why the outdated drawing was available, whether the current revision was clearly identifiable, how superseded information was controlled and whether the supplier's receipt of the approved revision was confirmed.


Without this investigation, the organisation may correct the immediate problem while leaving the underlying weakness in place. The same failure can then occur on another work package, with another supplier or on a different project. The financial case for information management is therefore not limited to reducing administrative effort. It includes preventing avoidable errors, improving productivity, reducing uncertainty and ensuring that decisions are based on reliable information.


Why document control alone is not enough

Document control is an essential part of a quality management system. It establishes arrangements for reviewing and approving documents, managing revisions, controlling distribution and retaining records. ISO 9001:2015 addresses these requirements through clause 7.5, which covers documented information (International Organization for Standardization [ISO], 2015).


However, effective document control does not necessarily provide a complete information management solution. A procedure may establish how a drawing is approved and issued without defining how the information will be coordinated with other disciplines, checked against downstream requirements or transferred into an asset owner's operational systems.


This distinction becomes particularly important in large organisations, where different departments may use separate systems and maintain their own records. Engineering may manage drawings, procurement may maintain supplier documentation, construction may use site inspection systems, and operations may hold maintenance information in an asset management platform. Each system may function adequately in isolation while the connections between them remain weak.


The resulting problem is often one of responsibility and process design rather than technology. If no one has clearly established which system contains the authoritative information, who is responsible for updating it or how changes are communicated to affected parties, employees may create local copies to keep their work moving. These copies can gradually become competing sources of information.


Adding another software platform does not necessarily resolve this problem. In some cases, it introduces another location in which information must be maintained and reconciled. A more effective approach begins with understanding the information lifecycle. Organisations need to establish what information is required, who produces it, who verifies it, who approves it, how it is distributed and how it will be used later. The control arrangements should reflect the consequences of information failure and the needs of the people relying on the information. This is where information management becomes a business process rather than simply a document storage activity.


The relationship between ISO 9001 and ISO 19650

ISO 9001 and ISO 19650 address different but complementary aspects of organisational control. ISO 9001 establishes requirements for a quality management system, including process control, documented information, monitoring, corrective action and continual improvement. The ISO 19650 series addresses the management of information over the life cycle of built assets using BIM.


ISO 19650-1:2018 establishes concepts and principles for information management, while ISO 19650-2:2018 addresses information management during the delivery phase of assets (ISO, 2018a, 2018b). Together, these standards provide a useful basis for understanding how information requirements, responsibilities, exchanges and verification arrangements should be established within construction projects.

The relationship is particularly relevant when considering the difference between producing an information deliverable and demonstrating that it satisfies the requirements for its intended use. A model may have been submitted on time, but that does not necessarily establish that its information is complete, coordinated or suitable for the next stage of the project. Similarly, a document may have passed through an approval workflow without providing sufficient evidence that the technical requirements have been met.


Quality management can support the definition of these verification processes, the assignment of responsibilities, the management of nonconformities and the evaluation of performance. Information management can establish the arrangements through which the information is produced, exchanged, reviewed and made available.

Neither function should be expected to compensate for weaknesses in the other.

An organisation may have a mature quality management system but lack clear information exchange requirements. Equally, it may operate a well-structured common data environment without having effective arrangements for verifying the technical quality of the information being exchanged.


The objective should be to connect these controls so that information requirements are established before work begins, verification takes place at appropriate stages and information failures are investigated as part of the wider management system.


BIM is not the same as information management

One of the persistent misunderstandings in the built environment is the assumption that implementing BIM automatically resolves information management problems. BIM provides methods and tools for developing and coordinating digital representations of assets, but the reliability of the resulting information depends on the processes, responsibilities and requirements governing its production and use.


A coordinated three-dimensional model can still contain incorrect asset data, incomplete specifications or information that has not been verified for the intended purpose. A project may also produce technically accurate models while failing to manage the exchange of information between design, construction and operational teams.


Abanda et al. (2025), in their examination of ISO 19650 through process modelling, highlight the importance of understanding information management as a sequence of connected activities involving multiple stakeholders. Their work reinforces the point that effective information management requires attention to processes and communication, rather than an exclusive focus on digital models or software.


This has practical implications for organisations investing in BIM capability. Software training and model production skills are important, but they must be supported by clear information requirements, defined responsibilities, consistent checking procedures and reliable exchange arrangements.


For example, a structural model may be geometrically coordinated with the architectural model, but the information needed for procurement may still be incomplete. The contractor may need verified quantities, material specifications, fabrication details and confirmation of design status before placing orders. If these requirements are not established and checked, the project may experience delays despite having invested significantly in digital coordination.

The same principle applies to the use of a common data environment. A CDE can support the controlled sharing of information, but it does not remove the need for people to follow agreed processes. The platform must be configured appropriately, responsibilities must be understood, and the information within it must be managed throughout its lifecycle. Technology enables the process. It does not replace the need to design and control it.


Information quality across the supply chain

Construction projects depend on relationships between clients, consultants, contractors, subcontractors, manufacturers and suppliers. Information moves between these parties at different stages, and each participant may have different systems, working practices and contractual responsibilities.


This creates a particular challenge when information requirements are not communicated clearly at the outset. A supplier may receive a drawing but not understand which information must be returned with the manufactured product. A subcontractor may complete an installation without knowing what evidence is required for inspection or handover. A client may expect asset data in a particular format without having established how that data will be collected and verified during the project.


These issues are often discovered late because the information requirements become most visible when a deliverable is rejected or a handover deadline approaches. By that stage, the cost of correcting the problem may be significantly greater than the cost of establishing the requirements earlier.


Information requirements should therefore be incorporated into procurement, appointments, work-package planning and quality control arrangements. Each party should understand what it is expected to produce, the applicable format and standard, the required delivery date, the verification process and the person responsible for acceptance.


This does not mean that every organisation must use identical software. What matters is that information can be exchanged and used reliably, with sufficient traceability to establish its origin, status and suitability. Interoperability is particularly important in this context. The UK BIM Framework identifies the ability to exchange and use information independently of the technologies used to produce it as an important consideration for effective information management (UK BIM Framework, 2023). Where information cannot be transferred or interpreted reliably between systems, organisations may have to resort to manual re-entry, duplicate records or additional checking.


The result is increased effort and a greater opportunity for errors. Supply-chain information management should consequently be treated as part of project planning and quality assurance, rather than an activity left until the information is required.


The handover problem: delivering an asset versus delivering information

Project completion is often measured through physical progress, testing, commissioning and contractual milestones. Yet an asset can be physically complete while the information required to operate and maintain it remains incomplete, inconsistent or difficult to use.


This creates a problem for the organisation taking responsibility for the asset. Maintenance teams may need equipment specifications, inspection records, operating instructions, warranty information and details of installed components. If these records are missing or unreliable, the owner may have to spend additional time locating information, inspecting the asset or recreating records that should have been provided during delivery.


The Scottish Futures Trust's BIM guidance on transferring information into an asset information model illustrates the importance of planning this exchange between project delivery and the operational phase. It recommends defining the structure, process and content of the information to be transferred so that project information can support the asset owner's operational systems (Scottish Futures Trust, n.d.).


The important point is that handover requirements should influence the information produced throughout the project. If the asset owner requires particular information about equipment, components or maintenance activities, these requirements should be established early enough for the project team to plan how the information will be collected, verified and delivered.


Waiting until practical completion to assemble the required records creates unnecessary pressure. It can also expose gaps that are expensive to resolve because the people who produced the original information may have moved on, suppliers may no longer be readily available, and completed work may be difficult to inspect. A more effective approach treats handover as a planned information delivery process with defined requirements, responsibilities and verification stages. Information should be checked progressively, rather than accumulated at the end of the project.


This also changes the way handover quality should be assessed. The question is not simply whether the contractor has submitted the required files. It is whether the information is complete, accurate, traceable and usable by the people who will operate the asset. The value of information extends beyond the date on which the construction contract is completed.


Measuring information quality and its cost

If organisations want to improve information management, they need to understand where information failures occur and what those failures cost. Without reliable data, management may recognise that rework is a problem but remain unable to determine which processes contribute most significantly to it.


The starting point is to establish meaningful measures that connect information quality to operational performance. These might include the number of information-related requests for clarification, the frequency of work undertaken using superseded information, the proportion of information deliverables accepted at first review, the time required to resolve information discrepancies and the cost of rework attributable to information failures.


However, these measures must be defined carefully. A high number of requests for information does not automatically indicate poor performance. Some requests are necessary to resolve legitimate uncertainties or accommodate design development. Equally, a low number of reported information issues may reflect effective control, but it could also indicate that employees are not reporting problems. The figures need to be interpreted in context and supported by an understanding of the causes.


Where rework occurs, organisations should distinguish between the direct cost of correcting the work and the wider consequences for productivity, programme, procurement and subsequent activities. They should also avoid assuming that every defect or delay is an information management failure. Root-cause analysis is essential. A problem attributed to an incorrect drawing may actually have originated in an unclear design requirement, a late change, an ineffective approval process or a failure to communicate revised information. Corrective action should address the cause that allowed the problem to occur, not merely the most visible symptom.


The information collected through this process should feed into internal audits, management reviews and improvement planning. Over time, it should help the organisation identify recurring weaknesses and determine whether changes to its processes are producing better results. Information quality then becomes something that can be evaluated and improved, rather than an expectation that exists only within a procedure.


What organisations should do differently

Improving information management does not necessarily require a complete overhaul of existing systems. In many organisations, the more useful starting point is to understand how information is currently produced, controlled and used, then identify the points at which failures are most likely to occur.


The first step is to establish clear information requirements. Project teams should understand what information is needed, why it is needed, who is responsible for producing it and how its suitability will be assessed. These requirements should be aligned with the work being undertaken and the information required by downstream activities.


The second step is to clarify responsibilities. The people producing information, reviewing it, approving it, distributing it and using it should understand their respective roles. Where responsibilities overlap, the organisation should establish how decisions will be made and how conflicting information will be resolved. The third step is to strengthen verification. Checks should take place at appropriate stages and should assess whether information meets the applicable requirements. This may involve technical reviews, coordination checks, inspections, validation of asset data or confirmation that the correct revision has been issued.


The fourth step is to establish reliable information exchange arrangements. The organisation should identify authoritative information sources, control revisions and ensure that relevant users can access approved information when required. Where multiple systems are used, the interfaces between them should be understood and managed.


Finally, information failures should be treated as opportunities to improve the management system. Recurring discrepancies should be investigated, corrective actions should address underlying causes, and the effectiveness of those actions should be evaluated. Management should also consider whether employees have the skills, resources and authority needed to follow the agreed processes.


These actions are most effective when they are connected to the organisation's existing quality management system. Creating a separate information management initiative without linking it to operational controls can result in duplicated procedures and competing responsibilities. The objective is not to produce more information about the work. It is to ensure that the information produced supports the work itself.


Conclusion

Poor information is often treated as a documentation problem, but its consequences are operational. It can influence design decisions, procurement, construction sequencing, inspection, commissioning and the long-term management of completed assets. When information is incomplete, unreliable or poorly controlled, the resulting problems can extend well beyond the document or model in which the issue first appeared.


Quality management provides a framework for understanding these failures, controlling the processes that produce information and investigating the causes of recurring problems. Information management provides the arrangements through which information is defined, created, exchanged, verified and maintained. BIM can support these activities, but the effectiveness of the process depends on more than the technology being used.


The relationship between ISO 9001 and ISO 19650 is therefore important. One supports the wider management of quality and process performance, while the other provides a framework for managing information in the built environment. Used appropriately, they can help organisations establish clearer responsibilities, improve information reliability and reduce the likelihood that avoidable errors will affect project delivery.


The same principles apply beyond construction. Any organisation that relies on information to make decisions, coordinate activities or demonstrate compliance needs to consider whether its information is reliable and suitable for its intended use.

The most effective approach is to treat information quality as an integral part of operational quality. Requirements should be established early, responsibilities should be clear, information should be verified at appropriate stages, and failures should be investigated in a way that improves the system rather than simply correcting the immediate error.


Ultimately, delivering a project is about more than completing the physical work. It is about ensuring that the people who design, construct, operate and maintain the asset can rely on the information they receive.


A project is not truly complete when the files have been handed over. It is complete when the information required to use, operate and maintain the asset is reliable, traceable and fit for purpose.


References

 
 
 

Comments


bottom of page