Document created
An initial version of this presentation brings together the software pages and the contract example.
This is the starting point of the history shown here.
Words used on this website
Understand the words used on these pages
Short explanations to help you read the pages and prepare your questions. The technical article explains the mechanisms.
Keep the selected documents.
This example starts with the documents the business wants to follow.
- Where documents are kept
- The systems your company uses to store its documents. The IT team checks whether the software can work with them.
- A record’s history
- Retained versions and the links recorded between them, used to examine an earlier date.
- What was recorded
- Retained changes and actions, with their dates and links, make up the history available for review.
- Detecting a change
- Comparing contents and their hashes to identify changes and verify integrity.
- Recognising a file
- Technical information can help identify a file. Its meaning and reliability need to be checked for the tools used.
- Checking a collection
- A way to check whether a set of retained items has changed. The technical article explains how this works.
- Preventing changes or deletions
- Rules that restrict changing or deleting retained data. Their effect depends on the tools used and the rules chosen.
- Finding an earlier state
- Retrieving the versions retained for a chosen date. Recovered data still needs to be checked before it is used again.
- Evidence Pack
- A record prepared for sharing, with the information needed to check the items included.