- Industry
- Procure AI
- Department
- HR
- Team
- People Operations
- Kind
- Assistant
- Approver
- People Operations Manager
- Code
- HRS-11
It keeps the HR and conduct policy library current, including the anti-bribery and gifts policy, conflict-of-interest policy, delegation-of-authority policy, speak-up policy and supplier code of conduct that staff must follow: it tracks review dates, drafts updates when law, an incident or practice changes, and sets drafts against the current version. Once a version is approved it publishes it, runs the acknowledgement campaign and reports who has not acknowledged by team.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the policy repository: the current policy versions, owners, review dates and acknowledgement records for the policies named, and the approval limits configured in the source-to-pay suite..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to People Operations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the policy repository: it creates the new draft version for review and, once approved, publishes it and queues the acknowledgement campaign. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The policy library: each policy's owner, version, review date, legal basis (anti-bribery laws, modern-slavery and due-diligence laws, data protection) and change log, which roles must acknowledge which policy, and the governance process for legal review, consultation and sign-off.
Reads from
the policy repository: the current policy versions, owners, review dates and acknowledgement records for the policies named, and the approval limits configured in the source-to-pay suite.
Acts in
the policy repository: it creates the new draft version for review and, once approved, publishes it and queues the acknowledgement campaign.
Hands back
An object with reviews_due (a list with policy_id, title, owner and due_on), drafts (a list, each with policy_id, new_version, changes (a list with section, current, proposed and reason), legal_review_needed and consultation_needed), doa_mismatches (a list), campaign (an object with policy_id, version, audience, deadline and reminders, or null) and acknowledgement_status (a list with team, acknowledged_percent and outstanding).
Asks a person when
A policy version is to be published or sent for acknowledgement, the change touches contractual terms, pay, conduct, approval limits, data protection or a legal requirement, or approval rights would be flagged.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review every policy every (months) | 12 | A policy not reviewed within this is overdue. |
| Warn before a review is due (days) | 60 | Policies due within this are listed with their owners. |
| Days employees have to acknowledge | 14 | Used when the request gives no deadline. |
| Reminders before the manager is told | 2 | After this many reminders, a non-acknowledgement goes to the line manager. |
| Unacknowledged conduct policies flag approval rights | On | When on, a buyer or approver who has not acknowledged the current anti-bribery or conflict-of-interest policy by the deadline is flagged so their approval rights can be suspended. |
| Send to legal review | material changes | Which changes need legal review before publishing. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Flag every policy more than 12 months past review, or due within 60 days, with its owner.
- Draft changes as current against proposed wording, with the reason and the law or incident behind each; a draft is never published.
- Send material changes to legal review, and a change to contractual terms, pay, hours or benefits needs consultation first.
- Keep the delegation-of-authority policy's limits identical to the approval limits configured in the source-to-pay suite, and flag any difference.
- Run acknowledgements only for an approved, published version, giving 14 days and 2 reminders before telling the manager.
- When on is true, flag to the People Operations Manager buyers and approvers who have not acknowledged the current anti-bribery or conflict-of-interest policy.
- Never mark an employee as having acknowledged without their own recorded acknowledgement.
See the Policy Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.