Policy acknowledgment and training attestation
How do we get every employee's acknowledgment of a policy on hire and on each change, and show the examiner who acknowledged what and when?
Make each policy version a campaign with a record per person. On hire, and whenever a policy changes, Callvu identifies who must acknowledge it from the HR system, sends each employee the policy with a link, requires them to open it in full and attest by typed name in the approved wording, reminds until done, escalates the overdue to their manager, and writes completion per person and per version to the compliance record the examiner reads.
In scopeSimpleCallvu moves: chase and verify, write back
Last updated November 7, 2026.
The problem today
The code of conduct was updated in March, and the attestation report is a spreadsheet of who replied to the email.
Compliance sends the updated policy to all staff by email and asks for a reply. Some reply; some forward; some are on leave. The spreadsheet shows 80 percent. The examiner asks for the attestation of a specific loan officer on the fair lending policy, and the answer is a search of the compliance inbox.
Regulators expect a compliance management system in which policies are communicated, employees acknowledge them, and the bank can show it: the BSA program's training and acknowledgment, the information security program's acceptable use, the code of ethics and conflicts of interest, fair lending, the whistleblower policy. Each has a population, a version and a date.
The process is the same for every policy, which is why it should be one process.
How it runs
From the requestto the system of record.
A new hire's onboarding, a new or revised policy version published by compliance, or the annual attestation cycle opens a campaign. Callvu identifies the population from the HR system by role, department and location.
- Employee
- Opens the policy in full on their own screen, answers any comprehension questions the policy carries, and attests by typed name.
- Compliance
- Publishes the version, sets the population and the deadline, and sees completion and the exceptions.
- Manager
- Receives the escalation for overdue employees and confirms leaves or exits.
- Callvu
- Builds the population, sends, enforces the read and the attestation, reminds, escalates and records.
Classify the population
The policy version's scope rule (all staff, a role, a department, a location, new hires within a period) is applied to the HR system to produce the population, with each person's manager. A person who joins the population later (a hire, a transfer) is added automatically.
Chase and verify the read
Each employee receives the policy with a link; the policy is shown in full and the attestation step opens only after it has been displayed to the end. Where the policy carries comprehension questions, they must be answered. The attestation is by typed name in the wording compliance approved, with a timestamp and the policy version.
Remind and escalate
Reminders run on the campaign's schedule until the deadline; overdue employees are escalated to their manager with the list, and leaves and exits are confirmed from the HR system so the population stays right.
Write back
Completion per person, per policy version, with the timestamp and the attestation wording, is written to the compliance record, and the campaign report (completion, exceptions, escalations) is produced from it for the board and the examiner.
Where it ends: Every person in the population attested to the exact version, having opened it in full, and compliance can show any person's attestation on any policy and date. The Decision Trace shows the population rule and the campaign settings; the Audit Trace shows each delivery, read, attestation and escalation.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
Onboarding, a policy publication, or the annual cycle. The employee meets the process in a link on their own screen.
The back office
Compliance sets the campaign and reads the report; managers handle only the overdue. Nobody keeps a spreadsheet.
The Decision Desk
- An overdue employee goes to their manager in the Decision Desk with the list and only the allowed outcomes: remind, confirm leave or exit, or escalate to compliance.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
How does the bank know the employee read the policy?
The attestation step opens only after the policy has been displayed in full, and where compliance adds comprehension questions, they must be answered first.
What does the examiner see?
Any person's attestation on any policy version with the wording and the timestamp, and the campaign report with completion and exceptions.
What about new hires and transfers?
They are added to the population automatically from the HR system and attest within the onboarding period.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.