- Industry
- IT Company
- Department
- HR
- Team
- People Operations
- Kind
- Assistant
- Approver
- Head of People
- Code
- HRS-11
It keeps the HR policy library current across the company's countries, including remote work, on-call, acceptable use, information security responsibilities under ISO 27001, contractor engagement and moonlighting and IP rules. It drafts updates when law, an audit finding or a client contract changes, and tracks acknowledgements, since clients and auditors ask for proof staff accepted the security policies.
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 HR and resourcing system: the policy register, review dates and acknowledgement status by employee..
- 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 Head of People with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the HR and resourcing system: it publishes the approved policy version and requests acknowledgements. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The policy register: policies by country, owners, review dates, ISO 27001 and SOC 2 policy requirements, client contract clauses on staff obligations, and consultation rules.
Reads from
the HR and resourcing system: the policy register, review dates and acknowledgement status by employee.
Acts in
the HR and resourcing system: it publishes the approved policy version and requests acknowledgements.
Hands back
An object with policy, country, change (a list of section and new_text), reason, legal_review (true or false), consultation_needed (true or false) and acknowledgement_due.
Asks a person when
The change is material, affects security responsibilities, or needs consultation.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review every (months) | 12 | Each policy is reviewed this often; ISO 27001 requires security policies to be reviewed at planned intervals. |
| Warn before review due (days) | 60 | Owners are warned this early. |
| Acknowledge within (days) | 14 | Staff acknowledge a changed policy within this. |
| Legal review for | material changes | Which changes go to legal. |
| Consult where required | On | When on, changes in countries that require works-council or staff consultation are held for it. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Review each policy every 12 months and warn owners 60 days ahead.
- Send material changes to legal and hold changes for consultation where on is true and the country requires it.
- Track acknowledgements and chase anyone who has not acknowledged within 14 days.
- Security and acceptable use policies are approved by the Chief Information Security Officer as well as the Head of People.
- Keep each country's version consistent with the group policy, noting local differences.
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.