Ethics & Integrity
Code of Conduct Acknowledgement
A code of conduct only binds an employee who has signed it, so the acknowledgement record is the foundation of every later disciplinary action.
Why Code Acknowledgement Matters
Signed acknowledgement of the code of conduct converts a policy document into an enforceable standard each employee has accepted, supporting the integrity expectations of King IV and the Public Service Regulations. Without a complete acknowledgement record, consequence management for ethics breaches becomes contestable and AGSA may flag the control as ineffective. AuditPro Core reconciles signed acknowledgements against the employee establishment so accounting officers can prove the code reaches everyone it should bind.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Acknowledged
89%
▲ 4%
Post-revision re-signs
67%
behind schedule
Never acknowledged
138
New hires within 14 days
94%
Acknowledgement rollout after code revision
Acknowledgement gaps by directorate
| Directorate | Outstanding | Rate % |
|---|---|---|
| Corporate Services | 22 | 92 |
| Infrastructure | 41 | 83 |
| Community Services | 38 | 86 |
| Finance | 9 | 96 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Acceptance Creates Obligation
An employee is bound by the code from the point they acknowledge it, not from the point it is published. The signed record is what makes the obligation enforceable.
On Appointment
New employees should acknowledge the code as part of onboarding, before they begin exercising authority. A gap here means staff act before accepting the standards that govern them.
Existing Staff and Updates
When the code is revised, existing employees must re-acknowledge the updated version. Acknowledgement of a superseded version does not bind staff to new provisions.
Completeness of the Record
The control is only as strong as its coverage of the full establishment. Unsigned employees are exactly the population where enforcement later fails.
How AuditPro Core Bridges the Gap
- Establishment reconciliation: AuditPro Core matches signed acknowledgements against the active employee list to expose gaps.
- Onboarding workflow: new appointees are tracked until acknowledgement is captured, with outstanding cases escalated.
- Version control: when the code is updated, re-acknowledgement is required and monitored across existing staff.
- Audit-ready register: the acknowledgement status exports as evidence of an enforceable code for AGSA review.
Key Takeaways
- The code binds an employee only from the moment they acknowledge it.
- Acknowledgement belongs at onboarding, before new staff exercise authority.
- Revised codes require fresh acknowledgement; old signatures do not cover new provisions.
- An incomplete acknowledgement record is where disciplinary enforcement later collapses.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.