Assigned
The named person belonged to the audience for a named policy version and received a due date.
FROM DISTRIBUTION TO FOLLOW-UP
Track policy compliance by version, audience, and unresolved action
See who received the current policy, who responded, who raised a question, what is overdue, which waiver is active, and who owns the next step—without treating a sent email as proof.
The workspace distinguishes awareness evidence from operational compliance. An acknowledgment proves a response to a version; it does not by itself prove that work follows the policy.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
- Version-specific assignments
- Overdue and questioned responses
- Exceptions with expiry and review
6response states3levels of follow-up0sent-email assumptions
Separate awareness, understanding, exception, and operating evidence
A useful tracker answers the question behind each claim instead of collapsing every signal into “compliant.”
Acknowledged
The person recorded a response to that version at a known time.
Question raised
The employee could not confirm understanding and the issue has a follow-up owner.
Exception controlled
A departure has an evaluated risk, conditions, review date, expiry, and accountable owner.
Operation verified
The underlying process record or audit evidence shows whether the requirement was followed.
Connect policies to controls and findings →Keep the requirement, policy, control, and proof connected
Acknowledgment is one evidence type. A stronger compliance view also shows why the policy exists, how the requirement is implemented, and which operating records reveal a gap.
Requirement
Name the applicable law, regulation, contract, standard, risk decision, or internal mandate and its accountable owner.
Policy obligation
Link the exact current policy and version that translates the requirement into an organizational expectation.
Control or procedure
Identify the approval, inspection, access review, training, transaction, or recurring procedure that implements the policy.
Evidence and gap
Retain the result, exception, finding, corrective action, owner, and due date instead of treating a distributed document as compliance proof.
Use denominators that a manager can investigate
Percentages should open the people, version, audience, and unresolved reason behind them.
| View | Numerator | Denominator | Action list |
|---|---|---|---|
| Acknowledgment coverage | Acknowledged on time | People assigned to that version | Opened, overdue, questioned, declined |
| Review health | Reviews completed by due date | Policies due for review | Overdue and awaiting decision |
| Exception control | Active waivers reviewed on time | All active waivers | High-risk, due, expired, missing conditions |
| Publication readiness | Assignments ready before effective date | Planned audience assignments | Missing owner, due date, channel, or accessible version |
Turn every gap into a specific next action
The tracker should help managers resolve the reason—not only send another reminder.
Never opened
Check assignment, access, leave status, and delivery before escalating.
Question raised
Answer the question, clarify the policy or procedure, and retain the response.
Overdue
Assign accountable follow-up and escalate by audience, risk, and elapsed time.
Declined or exception needed
Route the issue to the policy owner or risk owner; do not overwrite it as acknowledged.
Policy tracking is one part of compliance management
Use the tracker for version delivery, responses, review, and exceptions. Broader compliance software may also need requirements, controls, tests, risks, findings, remediation, regulatory content, and assurance.
Good policy-tracking fit
Audience assignments, acknowledgments, questions, reminders, waivers, review cycles, and manager drill-down.
Needs connected evidence
Actual compliance often lives in training, inspections, approvals, transactions, access reviews, incident records, and audits.
Needs specialist compliance depth
Consider a GRC platform for regulatory mapping, controls testing, regulatory change, enterprise risk, and assurance workflows.
Practical questions about policy compliance tracking software
What should policy compliance tracking include?+
Track the current version, required audience, assignment date, due date, response state, response time, questions, follow-up, waivers, review dates, and the operational evidence needed for the actual requirement.
Is policy acknowledgment proof of compliance?+
It is evidence that a person responded to a specific version. It is not automatically proof of understanding, training, capability, or compliant behavior.
How do you calculate policy acknowledgment rate?+
Divide people who acknowledged the assigned version within the chosen time window by people who were required to acknowledge that version. Keep exclusions and audience changes visible.
Can Jodoo send reminders and route exceptions?+
A configured App can use automation and workflow to remind owners, route reviews, and show overdue items. Pilot the exact escalation, identity, delivery, and evidence requirements.
How should policy questions be handled?+
Keep the response open, assign an owner, answer the question, decide whether content or training must change, and only record confirmation after the employee can respond accurately.
VERIFY THE POLICY AND ITS OPERATING EVIDENCE
Start with one audience and one version you can verify
Use the example to trace assigned people to responses, questions, overdue follow-up, and exceptions. Then connect the tracker to the operating evidence that matters for your policy.
Use the compliance tracking app