What it covers
Keep the exact evidence associated with what a customer or staff member saw.
Documents and assets
Document acknowledgement
Record acknowledgement against a specific document version.
How it works
Record which version someone acknowledged
Capture acknowledgement against a specific document version so the evidence remains tied to the content that was presented. This gives teams a clearer record than a general checkbox detached from the file.
In practice
Keep acknowledgement evidence associated with the exact document version.
When to use it
Useful situations
- Record acknowledgement of a current policy version.
- Keep compliance evidence connected to the actual file.
- Review which version a person saw.
A working path
How the work moves
Publish
Make the relevant document version available through its permitted path.
Request
Ask the intended staff member or customer to acknowledge it.
Review
Open the acknowledgement evidence against the exact version.
Illustrative scenario
revised terms
A customer acknowledges version three of revised terms; the team can later distinguish that acknowledgement from earlier versions. The acknowledgement records the version number and the person who responded, giving the team evidence that remains meaningful after the document is revised again.
Before you start
What to check
- Acknowledgement records refer to a specific document version.
- Access to documents and acknowledgements follows record permissions.
Does an acknowledgement cover future edits?
No. It remains linked to the version presented.
Can customers acknowledge files?
Where the file is deliberately shared through the supported portal flow, yes.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.