Job changes and history
Change someone's job from the date it takes effect, have line managers propose changes for HR to approve, and keep every change in a job history that's never rewritten.
Agoo is in early access. This page describes the feature as it ships to early-access organisations; screens are illustrative.
"Promote Abena Asante to Senior Accountant from 1 November, reporting to Efua Mensah" is one job change: it can change several things at once, from a date. Job changes are on every plan, in Console → People on a person's HR record.
What a change can include
| Field | Notes |
|---|---|
| Job title and grade | |
| Department | One that isn't archived |
| Position | A vacant one, or the one they hold (Growth and above) |
| Line manager | Never themselves, never a loop |
| Sites | |
| Employment type and contracted hours a week | |
| Contract, contract ends and probation ends | A fixed-term contract has an end date |
| Legal name, date of birth and statutory numbers | Corrections only, by HR or asked for by the person |
Every change takes effect on a date from up to 90 days ago to a year ahead. Give a reason when you can; line managers and people asking for a correction must give one (up to 500 characters), so whoever approves it knows why.
Who makes a change
Owners, Admins and HR choose Change job on someone's record.
- Today, or a date that has passed: Apply now changes the record at once. A past date is kept in the history as the date it took effect.
- A future date: the change is Scheduled and shows on the record as "From 1 November". On that day, within an hour of midnight where your organisation is, Agoo applies it by itself.
- Want a second pair of eyes? Send for approval routes it to the people who approve changes, like a manager's proposal.
HR limited to some sites changes the jobs of people at their sites.
Who approves changes
Changes that need approval are approved by HR by default. Owners, Admins and HR can choose instead, in Console → Settings → People and HR, under Who approves changes to people's jobs:
| Choice | Who decides |
|---|---|
| HR only (default) | HR |
| Line manager, then HR | The person's line manager first, then HR |
| No approval | Nobody: a proposal is accepted as soon as it's made, and the record says so |
| Custom chain (Enterprise) | Up to five steps, always including HR or a named person |
A line manager never approves a change to someone's job alone: HR, or the person you name, always has the last word. Nobody approves their own change. Approvers see what changes, from what to what, from when and why, and decide in the Console. Like leave, a change nobody decides moves up after the time you set (72 hours by default), and deputies cover approvers who are away. See Who approves leave for how deputies and moving on work.
What happens to a change
| Status | Means |
|---|---|
| Waiting for approval | With its approver |
| Scheduled | Approved, or made by HR, for a date still to come |
| Applied | The record has changed, and the history has its lines |
| Declined | The approver said no, with a note the requester sees |
| Called off | Withdrawn before it applied, by whoever asked for it or by HR |
| Couldn't be applied | Something changed before its date, such as the position being filled or the manager leaving. Whoever asked is told why, and HR makes a new change |
Changes waiting for approval, scheduled or that couldn't be applied show on the person's record and in Console → People → Change requests. Whoever asked is told when theirs is decided, and when one couldn't be applied. Approvers and HR are told when one waits for them; each person chooses how in Account → Notifications, under People and HR.
Job history
Every change to a job, title, grade, department, position, manager, sites, employment type, contract, hours, start or leaving date, is a line in the person's job history, with the date it took effect, what it was before, who recorded it and why. Lines are never edited or removed while the record is kept: a correction is a new line. Changes made before People and HR arrived, such as earlier changes of line manager, were added from the audit trail.
The person, HR and their line managers see the history, on the record in the Console and in My record in Agoo Workspace.
In the audit trail
Asked for a change to someone's job, Approved a change to someone's job, Declined a change to someone's job, Applied a change to someone's job, Couldn't apply a change to someone's job and Called off a change to someone's job, each with who and when.
For developers
With the hr:read and hr:write scopes (Pro and above), read a person's employment history and job changes and make a change from a date. The
person.job_changed webhook (Growth and above) fires when a change applies, whoever made it. See the API reference.
Departments and positions
Keep your departments with their heads, parents and cost centres, and on Growth and above the positions inside them, filled or vacant.
Pay accounts
Keep the bank and mobile money accounts each person is paid into, encrypted, with a fresh check before any change, the person told every time, and This wasn't me if it wasn't them.