The Hidden Value of Documentation

Richard Munro
10th Nov, 2026

What happens when nobody can remember who agreed to what?

A crucial decision was made during a meeting. Everyone left the meeting with the same understanding of this decision on what will happen next. A week later, however, those recollections can be vastly different from what everyone understood immediately after the meeting. One person remembers the agreement, another remembers it as a still ongoing discussion, and someone else has forgotten the topic entirely.

The challenge is not that one agreement was forgotten, the project now has an element of uncertainty. This is where documentation becomes more than just paperwork.

On a construction project, documentation can feel like just another deliverable as set out by the PROCSA Matrix: preparing an agenda, issuing minutes, compiling an important report, the list goes on. Once completed it may feel as if the matter is managed. But documentation is more than just a receipt of an action being taken or a matter being discussed. It is the memory of the project which is one of the tools in how a project is managed effectively. It not only explains what has happened, but what is still to come and most importantly, the consequences of failing to deliver on what was agreed upon.

A construction project is dynamic, constantly changing, people come and go, designs develop, information is transferred, parties are appointed and budgets are reviewed. But when change happens the project still needs to recall what happened yesterday. Imagine that you join a project four months before practical completion, you are expected to make decisions regarding yesterday’s problems. Problems that were unknown to you before joining the team, conversations that you were not in the loop in. How do you understand the current situation? You read the documentation. The meeting minutes track important decisions and conversations regarding the project, the request for information (RFI) schedule identifies outstanding information owed by the consultants and, the procurement schedule shows planned appointments relating to the construction program. All matters that are difficult to recall if not documented.

The documentation becomes the project’s memory. People forget. Projects cannot afford to.

 

When things go wrong:

The hidden value of documentation becomes clearly obvious when a project encounters difficulties. Construction projects rarely proceed according to the planned program. Unforeseen delays occur, designs change, scope is increased, instructions are issued and responsibilities are disputed.

When this happens, parties naturally ask:

Who was responsible?

Under who’s instruction?

When and how was it communicated?

Questions that cannot be answered reliably from memory alone and if these questions cannot be answered: the project faces delays, conflict arises, relationships are damaged and additional costs are incurred. If the required documentation is not in place the questions are answered without supporting facts, leaving the project to defend its position with memories instead of evidence.

 

Bad information is no information.

On a construction project, information is only valuable if it can be trusted. An inaccurate date, incorrect revision, missing instruction, or a poorly recorded decision can be more dangerous than having no information at all since it creates false confidence. When the project team believes that information is correct, decisions are made around it, resources are committed and work progresses, until reality exposes the error.

Correcting inaccurate information may mean abortive/remedial work, delays, and additional costs. The objective is not to have more documents sitting in a project file, it is to ensure that the information within those documents reflects the current, agreed, and accurate positions of the project.

 

Documentation as a Foundation for Trust:

Trust on a construction project is built when all parties involved can rely on the same information. When decisions, responsibilities, deadlines, and changes are clearly documented, the client, consultants, and contractor can work from a shared understanding rather than their individual recollections. This creates true confidence, when people know what is expected of them and enables them to answer questions with accurate back up.

Dependable documentation therefore does something surprising; it reduces the need to argue about what was meant because the project has already established what was agreed upon. When people trust the information, they can spend less time questioning the past and more time focusing on what the project needs next.

 

The real deliverable:

The PROCSA Matrix may tell a project team that minutes must be produced weekly, reports monthly, schedules maintained and instructions formally recorded. These requirements are necessary, but they are not the real purpose. The real purpose is the result of the trusted documentation available to all.

A project team can continue with greater certainty because decisions are recorded. Risks are identified earlier when information is tracked. Clients can make informed decisions because the project’s position is clearly reported to them. Parties can be held accountable when responsibilities are formalised.

The real decision is clarity. And from clarity comes accountability, coordination, and control of the project. Documentation should not be treated as an administrative task alongside project management.

Documentation IS project management.

 

Conclusion:

Perhaps documentation is undervalued because its greatest contribution is often invisible. When it works, no one notices. The project simply continues. It is when the information is missing, unclear or forgotten that we suddenly understand its worth. That is the hidden value of documentation.

It is not merely the paperwork left behind by a construction project. It is the memory that allows the project team to understand where the project has been, the current status and what needs to happen next.

A PROCSA Matrix guides the project managers, developers, and all other parties on what documentation needs to be generated. A good project manager understands why it matters. Ultimately, successful projects are not built on bricks, concrete, and steel alone. But also, on decisions being understood, timing information correctly and accepting agreed responsibilities.

Documentation does not simply record the project. It gives the project a memory—and a project that can remember is a project that can be managed.

 

References

PROCSA (n.d.) Professional Client/Consultant Services Agreements. Available at: https://www.procsa.co.za/ (Accessed: 6 November 2026).

Joint Building Contracts Committee (JBCC) (2018) Guide to Completion and Payment. May 2018 agreements. Available at: https://jbcc.co.za/docs/JBCC%20Guide%20to%20Completion%20and%20Payment.pdf (Accessed: 6 November 2026).

Construction Industry Development Board (cidb) (2007) Implementing Employment Intensive Road Works: Manual 2 – Planning and Contract Management. Pretoria: cidb. Available at: https://www.cidb.org.za/wp-content/uploads/2021/04/Manual-2-Planning-and-Contract-Management.pdf (Accessed: 6 November 2026).

Baloyi, M. and Agumba, J.N. (2014) 'Causes of disputes in construction projects in South Africa: A case of Gauteng province', in Proceedings of the 8th Construction Industry Development Board (cidb) Postgraduate Conference, University of the Witwatersrand, Johannesburg, 10–11 February, pp. 179–187. Available at: https://hdl.handle.net/10210/13023 (Accessed: 6 November 2026).

Deacon, H., Kajimo-Shakantu, K. and le Roux, K. (2023) 'Contract administrators' perspective on claim events under the JBCC Principal Building Agreement in South Africa', Acta Structilia, 30(2). Available at: https://doi.org/10.38140/as.v30i2.7518 (Accessed: 6 November 2026).

 

<< Back to News Index

Search 

EARLIER POSTS