HR audit: what you prepare and what you should get at the end.

A useful audit starts from a business question and ends with a list of priorities someone can pick up on Monday morning.

A consultative HR audit is an analysis commissioned by the company, not an official inspection and not a certification. Its conclusions serve the internal decision, and the value comes from how precisely the opening question is framed.

The business question, the purpose, the scope

"Check our HR" leads to a long report that is hard to use. A useful question sounds different: what risks appear if we take on 40 people at a new site; what slows us down when hiring; what someone from outside would find if they looked at our personnel files.

The scope follows from the question: which areas are analysed, which are not, over what period and for which categories of roles. A written scope shortens the audit and makes the report comparable with a future check.

What you prepare, with controlled access

Only the documents relevant to the scope are prepared. Depending on the purpose, these may be relevant: the internal rules and applicable procedures, the contract and job description templates, the records of working time and leave, the hiring and termination flow, the training records, the privacy notices given to employees.

Access stays controlled: named people, a single transmission channel, anonymisation wherever the analysis does not need names. Establish which data each check requires and limit access to the people who need it.

The sample and the limits of the conclusions

Documents show the intention. Practice shows up in real situations: a few recent hires, a few terminations, one month of time records, a few exceptional cases. The sample is chosen together and written into the report.

That is also where the limit comes from: the conclusions describe what was seen in the sample analysed, in the period analysed. A consultative audit does not replace legal advice and does not guarantee the outcome of an external check. Stated openly, this limit makes the report more useful, not weaker.

The deliverable: six fields for every point

A report built this way can be turned into a work plan. The priorities are revisited on an agreed calendar, with an owner and a review date for each action.

Preparing the opening meeting

What you clarify at the start

The business question, written in a single sentence.

The areas inside the scope and those deliberately left outside it.

The people named for document access and the transmission channel.

The sample of situations and the period covered.

Who receives the report and who decides on the resulting priorities.

Illustrative example: documented duties versus actual work

The situation is hypothetical. A job description lists the duties written at hiring, three years ago. In the conversation with the person and the manager it turns out that part of the current work is different: they took over coordination of a new flow and handed over some of the older tasks.

The observation is written as a difference between document and practice, with the evidence from the sample. The impact is described for the company's situation — for instance, performance reviews run on criteria that no longer describe the work. No legal verdict is issued; updating the document is proposed and it is settled who carries that forward.

The same logic applies to any difference between what is written and what happens: first the finding and the evidence, then the internal decision.

The practical step

Write the business question in one sentence and the list of areas inside the scope. The rest, including the sample, is settled in the first conversation. What the gap between the file and the practice looks like is also described in the situation on documents and practice.

Let's settle what is worth checking.

We start from your question and fix the scope. See how we work on HR audit and compliance.

Let's settle what is worth checking →