You may be asked to produce a signed document, related approval emails, and evidence of compliance with a process.
Would others be able to readily locate this information?
At minimum you want to be able to demonstrate an activity took place, when, and by whom. There are several practices which can help.
What you’ll learn:
- Give Every Important Record a Home
- File the Decision, Not Just the Document
- Make Cross-Platform Document Access Reliable
- Keep Versions and Permissions Under Control
- Set Retention Rules Before Cleanup Day
- Run Small Audit Checks Throughout the Year
- Wrapping It Up
Give Every Important Record a Home
You may have the executed document on someone’s desktop, a policy somewhere on network shares, and records of completion of training elsewhere.
Bringing all of these together to respond to an enquiry can be time-consuming. According to a UK government survey carried out from October 2024 to January 2025, 62% of surveyed businesses considered completing paperwork and keeping records a regulatory burden..
As a baseline, determine appropriate storage locations for various classes of document, such as signed agreements, policies and training records. You would then expect to see all executed agreements held in an agreed location, and policies managed and stored appropriately, with training completed and recorded by the relevant functions.
Decide on conventions for titling to aid retrieval. For instance, 2026-11_Name of Supplier_Contract_Executed is relatively self-explanatory, compared to, say, Contract_Final_v2.
These guidelines don’t need to be exhaustive, just ensure there is an individual accountable for each library and communication to users of where to place applicable documents.
Ideally, a third party would be able to navigate to these documents.
File the Decision, Not Just the Document
Approval emails can show who agreed to proceed, why standard terms changed, and when an activity was authorised.
It is preferable that this information does not remain solely in individuals’ email inboxes. For teams using Microsoft 365, there are solutions available to allow users to file emails and associated attachments to SharePoint through Outlook SharePoint integration.
For a supplier contract, keep the relevant approval emails with the signed agreement. This shows how the decision was authorised.
As appropriate, you would want to record:
- the matter being agreed;
- the individual or individuals agreeing;
- effective date; and
- the associated document or version number.
Of course you don’t want to file all correspondence relating to the subject, just pertinent ones, for example setting out agreement or necessary approvals.
Make Cross-Platform Document Access Reliable
Obviously it is helpful if users can access documents via multiple applications and devices. However, this does not mean documents should be duplicated across platforms.
Aim to have a central repository of appropriate documents. Users should then be able to easily navigate back to this. Some tips:
- Link to the original whenever possible instead of circulating extra editable copies
- Apply useful metadata such as project, customer, document type or date
- ask others to navigate to the document via the various methods available to them.
Ask a colleague to find an approved policy using a different application or device. You may identify areas for improvement. If multiple versions appear, you clearly have issues around where documents are being saved by users.
Keep Versions and Permissions Under Control
Multiple “final” versions can lead to uncertainty, where people may not know which one to use. Figures may differ between them or amendments may have been made post-approval.
Most platforms allow a degree of version control. Users can typically access previous iterations, ascertain what changes were made, and revert if required.
However, this alone will not indicate whether each version was approved. Consider who will approve documents, how this will be evidenced, and whether prior versions should be deleted. Marking as Draft, Approved, Superseded and so on may be helpful, as long as consistently applied. Clearly, the title of the file alone may be insufficient.
Consider also who requires access to each document. For example, those reviewing invoices probably do not require access to all employee information. Access should be granted on a need-to-know basis, and reassessed periodically, for example upon staff changes.
The aim is that those requiring the information can readily access it, but it is not widely available.
Set Retention Rules Before Cleanup Day
Retaining all information indefinitely creates a backlog of superseded versions and other records the business no longer needs.
However, deleting information prematurely could mean you are unable to satisfy a requirement to retain it.
Therefore, consider what documents you hold, the purpose, minimum period to be retained and subsequent action. This is good practice to follow in relation to personal data.
You should seek advice as applicable on periods to retain various classes of document, depending on the nature of your business, legal obligations or contractual requirements.
If you have Microsoft 365, you can apply retention policies to a scope, such as a SharePoint site or Exchange mailbox. Alternatively, you can apply retention labels to specific documents or emails. It will depend on what is most suitable.
Naturally, ensure no litigation holds apply prior to deletion, and document who sanctioned deletion and when.
Run Small Audit Checks Throughout the Year
You should periodically review that processes continue to be followed. Select some examples across various areas monthly, and consider:
- Can others readily locate the relevant document?
- Are approvals or other supporting information available?
- Do appropriate individuals have access, and no others?
- Can you identify who is responsible for it, and associated retention requirements?
Log any deficiencies and allocate actions to remediate. For example, approvals may not have been filed, or users continuing to send copies by email. You can address this by amending relevant procedures.
Occasionally, select an executed agreement, and try to identify the relevant approvals and applicable policies. You may then be aware of any gaps in process, for example information not being passed on appropriately.
This exercise is designed to highlight any breakdowns in processes.
Wrapping It Up
There are many opportunities throughout the life cycle of a document to ensure good document control, from initial titling, recording relevant information, approving versions, and reviewing for archiving.
Pick one area to focus upon initially, implementing the suggestions above, and ask others to test whether they can successfully retrieve relevant information. Expand to other areas in due course.
These habits save time spent gathering information should an audit take place, but you will also benefit from improved quality information on a day-to-day basis.




