Organisations today must be more responsive than ever. A new market, an acquisition, a new regulation: compensation decisions are sometimes made within timeframes that leave little room to reconstruct the context.
Responsiveness depends on what was clarified beforehand. An organisation that knows what it does, how it does it, why it does it, and within what frame responds quickly because it does not have to rediscover its own rules with every request. One that has not done this reopens the same debate every six months, with different participants and conclusions that vary.
An earlier article in this series, [[comp-ben-silent-cost-hasty-decisions]], argued that what protects an organisation is neither caution nor slowness, but the frame. This article is its user manual.
This clarity is not a matter of intentions. It rests on instruments: documents whose nature is understood, assigned responsibilities, traced decisions, and mechanisms that keep the whole up to date. These are what make the difference between an organisation able to explain its decisions and one that applies them without knowing why.
Documentation, a lever often misunderstood
The first question is which type of document you choose to draft.
A policy sets a direction. It states what the organisation decides and lays down requirements to follow. For example, positioning base salaries at the median of the reference market, or restricting the allocation of a company car to certain functions. It does not go into details, nor does it answer every practical question.
A procedure defines roles and responsibilities, flows, ownership of the process, and the minimum requirements to meet to accomplish the work. It identifies the information and the resources needed. It is what makes it possible to assess whether the work was carried out in accordance with what was defined, using objective criteria.
A work instruction details the execution of the process set out in the corresponding procedure and allows it to be adapted to specifics. It aims at the regularity, the completeness and the accuracy of the work. Its application is limited to the perimeter it was written for, a business line, a function or a discipline.
Then come forms, checklists, templates and other useful materials. They serve daily application, and a procedure or an instruction may refer to them.
Confusing these documents has very concrete effects. It leads to writing a policy when a how-to is expected, or to detailing execution in a document meant to set a principle. Both cases create confusion where clear guidance is expected.
The entries that make the difference
Quality management formalised this discipline well before HR, through the ISO standards. These leave each organisation to adapt its documentation to its needs, and practice has retained a common base of sections worth formalising: purpose, scope, roles and responsibilities, process, definitions, records, references, flowchart, revision history.
A section without content is not deleted, it carries the mention “not applicable”. The difference looks tiny and it is decisive: it shows that the question has been examined.
Within this structure, a few entries make the difference and keep the system standing over time.
The reference framework, first. Sometimes in the form of a legal or contractual framework, or a standard, the point is to clarify on what basis the rule rests, and therefore what will cause it to evolve. A rule tied to an identified provision gets revised when that provision changes. A floating rule never gets revised.
The owner, next, meaning a designated function, not a department. A document whose owner is “HR” has no owner. The difference is felt the day a question arises and no one knows whom to address it to. Attributing it to a function makes it exist within its prerogatives.
The effective date and the revision date, which seem obvious yet are regularly missing. Without the first, you cannot establish which rule applied at a given moment. Without the second, nothing signals that a document has not been revised in six years.
The rationale, the “why”, is the entry most often omitted, and yet the one that clarifies the reasons and the motivations behind the rules in place, by indicating what they were meant to frame or correct at the moment they were set. It helps settle the situations that the wording of the rule does not cover, and is akin to the ratio legis found in a legal context.
To this is added a requirement that appears in no section: a document that cannot be found produces no effect. Where it is filed is part of the document, in the same way as its content.
The sensitivity of documents
Not all compensation documents are shared in the same way. A principle of salary policy, such as the rules for awarding bonuses, can be widely shared. A detailed internal analysis of gaps may have restricted distribution. Individual compensation data call for access limited to authorised persons, according to their missions and the obligations in force.
This point falls under a different discipline from document structure: information security. It handles it through distinct steps, classifying information by level of sensitivity, and then stating that level on the document itself and in the messages concerning it.
Public, internal, confidential, strictly confidential, the number of classification levels matters less than their clear definition and their consistent application. A classification level only has effect if it entails concrete rules of access, storage, transmission and retention.
A marking does not however bar an obligation to inform. The pay transparency directive makes the criteria for determining pay and pay progression accessible to workers in its Article 6, opens in its Article 7 an individual right to receive one’s own pay level and the average pay levels, broken down by sex, for the categories of workers performing the same work or work of equal value, and prohibits preventing a worker from disclosing their pay for the purposes of the enforcement of the principle of equal pay. Confidentiality is therefore decided document by document, also identifying the information whose communication is due.
Document control
Control takes on a precise content here. The revision history indicates, for each version, the number, the date, the description of the change and its reason. A numbering that distinguishes substantive revisions from formal changes makes the history easier to read.
Retention also follows rules. Tracing decisions does not mean keeping everything indefinitely, and records that contain personal data call for a retention period and defined access in light of the GDPR rules in force.
The allocation of responsibilities
Documents state what is to be done and who answers for it, document by document. They do not always make the articulation of these responsibilities readable at the scale of the process.
The RASCI remains the most useful tool to clarify it, provided its central distinction is understood. R designates the one who carries out. A designates the one who answers for the decision and who can only be a single person. S designates those who provide operational support, C those consulted before deciding, I those informed afterwards. The recurring difficulty almost never bears on C and I. It bears on the confusion between R and A, that is, between the one who prepares the file and the one who assumes its result.
The flow diagram directly extends this allocation. It associates each step with the role that performs it and the document that accompanies it, form, checklist or record. Its strongest usefulness appears at the moment you draw it: that is where the implicit circuits are discovered, and the points at which the process stops without anyone being responsible for it. An example appears at the end of [[job-evaluation-qualifying-the-request]].
Other structuring elements
Decision-making bodies, such as committees, define where collective arbitrations are made, with what composition and what trace. A committee without a record of decisions produces arbitrations that no one will be able to justify afterwards. The useful trace bears on the decision, its date, the authority that made it and the criteria applied, not on the entirety of the exchanges.
Signature delegations establish who represents and legally binds the organisation, for what type of act, up to what level and how many signatures are necessary. Segregation of duties and the control of financial flows are long-standing principles of internal control. The US Sarbanes-Oxley Act of 2002 strengthened, for the companies within its scope, the obligation to formalise and assess internal controls over financial reporting, which spread these principles internationally.
Keeping the system alive
The last group of instruments is the one most often neglected, because it produces nothing visible as long as it works.
Regulatory watch is its first element. A rule compliant at the moment it was drafted may cease to be, and the gap does not signal itself. It appears in a check, a dispute or an audit, that is, at the worst moment.
The review cycle is its backbone. Each document has a deadline at which its owner takes a position on its validity. To this is added a channel open to all to propose a revision outside the cycle, approval remaining that of the owner. The first mechanism ensures that nothing lies dormant, the second that the organisation surfaces what it observes on the ground.
Event-triggered revision completes the system. It is not the years that make a rule unsuitable, it is the changes. A setup in a new country, a significant change in headcount, a reorganisation: each of these events calls for a review of the rules it affects, and the list of these triggers benefits from being anticipated.
Without these three mechanisms, the system remains accurate on paper and ceases to be so in practice. This is the organisational amnesia described in [[expatriation-pay-transparency-governance]]. An individual status that no one can date any more and a collective rule whose rationale no one knows any more stem from the same mechanism, at two different scales.
What pay transparency changes
None of these instruments is new. What changes is the level of demonstration expected.
As explained in [[expatriation-pay-transparency-governance]], Article 18 of the directive provides that, where a worker establishes before a competent authority or national court facts from which it may be presumed that there has been pay discrimination, it is for the employer to prove that there has been no such discrimination. The same burden falls on the employer when it has failed to comply with its transparency obligations, except for a breach that was manifestly unintentional and minor.
It is useful to prepare your organisation.
The essentials
A responsive organisation is not an organisation that decides quickly. It is an organisation that has clarified in advance what it does, how, why and within what frame.
This supposes distinguishing the types of documents, giving them a common base of sections, adapted to their nature, and inscribing in them the reference framework, the owner, the dates, the rationale and the level of confidentiality. It supposes then controlling versions, so as to be able to establish what applied at a given date. It supposes naming who executes and who answers, and tracing arbitrations. It supposes finally securing the watch, holding a review cycle, and revising at each event that justifies it.
None of these instruments produces compliance on its own. Together, they give the capacity to retrieve, explain and defend your decisions. The directive does not impose each of these instruments, it makes their absence much more risky.
Documenting the rules, naming their owners, tracing decisions and keeping versions: this is what the HDH (HR Decision Hub) platform makes it possible to set up and to maintain.