These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Vendor IT Security Assessment
- Process
- Document control
Document control
Review policy versions and keep acknowledgment evidence with the right document.
Step by step
-
Prepare version Document Controller
The Document Controller records title, version, effective date and the attached policy or procedure.
- Identify the file, version and effective date.
- Updates Controlled documents
-
Review document Document Controller
The version enters review so the responsible team can inspect the file and its stated effective date.
- Present the version for a decision.
- Updates Controlled documents
-
Approve version Document Controller
The Document Controller records the reviewed outcome on the document before it is used in assessment work.
- Record the approved state of that version.
- Updates Controlled documents
ApprovalA person approves before the work moves on. -
Collect acknowledgment Document Controller
The Document Controller records a person's acknowledgment against the approved document version and its date.
- Link person, document and acknowledgment date.
- Updates Training acknowledgments, Controlled documents, People
-
Replace version Document Controller
When an updated procedure takes effect, the earlier document can be marked obsolete while its linked acknowledgments remain traceable.
- Preserve older version references.
- Updates Controlled documents, Training acknowledgments
Who does what
Roles and permissions- Document Controller
- , Auditor, Inspector, Admin
Set up Vendor IT Security Assessment your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.