Skip to main content

Using the Change log report

A detailed guide to creating and understanding Change log reports in Humaans

Updated today

The Change log report provides an audit trail of changes made to employee records. Each row in the report describes a single field change, showing the previous and new values, when the change was made, and when it takes effect.


Overview

Unlike other report types that export a snapshot of current data, the Change log report exports a history of changes. This makes it useful for:

  • Auditing who changed what and when

  • Tracking compensation and role changes over time

  • Compliance and record-keeping

  • Feeding change data into external systems

The report is downloaded in CSV format.

Because this report is based on audit log data, changes can only go back to when Humaans started recording them. If you select a date range that extends before the recording start date, a notice will appear in the export window.


Creating a Change log report

  1. Go to Reports and either click the Change log template or click Create custom report and select Change log from the Report type dropdown.

  2. Set the Input period — this determines which changes are included. Only changes made or input during this period will appear in the report.

  3. Configure Identifier fields (see below).

  4. Apply any Filters to narrow down the employees whose changes you want to see.

  5. Select the Data fields you want to track changes for. The report will only show changes for the fields you select.

  6. Click Download CSV.


Identifier fields

Identifier fields are displayed at the start of each row and identify the employee whose data was changed. You can configure which fields to use as identifiers by clicking the pill buttons at the top of the export window.

Available identifier fields include:

  • First name, Last name

  • Work email

  • Department, Teams

  • Employee ID, Employee status

  • Any custom fields from the Basics, Employment, Job Role, and Offboarding sections

You must select at least one identifier field before you can download the report.


Report columns

The exported CSV contains the following columns:

Column

Description

Identifier fields

The columns before the "Field" column. These identify the person whose data changed.

Field

The name of the field that was changed

Next value

The new value of the field after the change

Old value

The previous value of the field before the change

Change date

The date the change was made in the system. Rows are sorted by this date.

Effective date

The date the change takes effect. For most fields this is the same as the Change date, but for compensation and job role changes this may be a future date.

End date

The date the item stops being effective (e.g. when a salary is replaced by a new one).


Understanding Change, Effective, and End dates

These three date columns capture different aspects of a change:

  • Change date — When the change was entered into Humaans. For example, if you update an employee's salary on 3 May, the change date is 3 May.

  • Effective date — When the change takes effect. For example, if you create a new salary on 3 May that comes into effect on 26 June, the effective date is 26 June.

  • End date — When the item being replaced stops being effective. For example, if the old salary was replaced and stopped being effective on 25 June, the end date is 25 June.


Available data fields

You can track changes across the following categories:

  • Basics — Name, email, phone, address, gender, nationality, birthday, etc.

  • Employment — Job title, department, manager, contract type, employment dates, leaving reason, etc.

  • Banking — Bank details, account numbers, sort codes

  • Compensation — All configured compensation types

  • Social — Custom social fields

  • Diversity — Custom diversity fields


Permissions

The data returned in the Change log report respects your permissions. Rows relating to fields you do not have access to are removed, and identifier fields are left blank for those entries.


Tips

  • For large organisations, use shorter date ranges (e.g. monthly rather than yearly) for faster downloads.

  • Only select the data fields you need — the report processes faster with fewer fields.

  • If you see an incomplete data notice, it means some fields started being recorded after the start of your selected period.

Did this answer your question?