[AUDIO LOGO]

It's an important thing to understand, as we explained in other lessons, documents go through various changes and stages. On a construction project, that creates a risk, the risk being working with old or out-of-date information.

Globally, it's estimated that over 50% of rework is caused by poor data and miscommunication. That was valued at $280 billion in 2018. Even for a relatively small market like Australia and New Zealand, the cost of rework is huge. We must make sure that documents are updated when they should be and update them correctly.

Here's the key thing to remember, when you add a document for the very first time, you simply upload it. Then, when the next revision or version of the document is ready, we update the original document. What we end up with is a single instance of each document that contains multiple versions or revisions.

We upload a brand new document, then we update it with the next version. The old version is not lost but instead remains available. And we'll take a look at that in another lesson. Then, we update it again and so on. Enough talking. Let's show you how this works.

Here we are in the Document Register again. Let's imagine some time has passed and the document that we added previously has been updated. Now we need to replace the current version of that document with the new version.

Let's locate the document. Then, we click on the three dots and select Update. We now see all the information for the current document. What we need to do is decide what needs changing.

Generally, it's a good idea not to change anything unless required, as it may cause confusion for the project team. Obviously, if we spot a mistake, we should correct it. But for now, we'll just alter the revision from C to D. Often, the Status will need changing too, depending on what's happened to the document. But we'll leave it as is for now.

The only other thing we'll change here is the Revision date. This field is not on every project, but if it is, it's good practice to ensure it's correct. Make sure it matches the actual revision date for the document being updated.

One other field that is often enabled on projects is the Comments field. This allows you to add some notes as to why the document has been updated. And that's all part of good document control. And it helps others understand what changes might have been made to the document.

When we're done, we choose the new document and click Update document. We then have the option of transmitting it. And remember, no other organization has access to this new revision until we do this.

Remember, when you add a document for the very first time, you upload it. Then, when the next revision or version of the document is ready, you update the original document. And this maintains the document history correctly.