What the Contract Decides
A governing law clause settles less than people expect. Working time protections are generally territorial and do not move because a contract names another country.
Most employment contracts name a governing law. The clause is usually drafted by somebody thinking about disputes rather than about rest periods, and it is routinely read afterwards as settling which working time rules apply.
The workflow in “What the Contract Decides” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring tips to increase productivity, tips to increase productivity can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.
It does not, in most cases. Protective employment rules in a great many jurisdictions apply to work performed there regardless of what the contract says, on the straightforward reasoning that otherwise the protection could be contracted away by choosing a more convenient law.
For an independent reference relevant to “What the Contract Decides”, consult the OWASP logging guidance. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
That makes the governing law clause the third fact in the register rather than the first. It matters, it is not decisive on its own, and an organisation that has recorded only this fact has recorded the least useful of the four.
Why it is still worth recording
Because it tells you what the organisation thought it was doing, and because it governs everything the local protections do not.
Notice periods, confidentiality, intellectual property, termination arrangements and the mechanics of the relationship generally follow the chosen law. Working time minima frequently do not. An organisation can be correctly applying the chosen law to most of a contract and still owe protections under another.
Recording the clause alongside the place of work is what makes the mismatch visible. A row where the two differ is not a problem in itself; it is a row that needs somebody qualified to look at it.
The mismatch that matters most
Work performed in a country where the organisation has no entity, under a contract governed by the law of a country where it does.
That arrangement is common for remote hires and small satellite teams, and it tends to have been set up by somebody solving an immediate hiring problem. The contract is the organisation's standard one with the location changed.
The question it raises is not whether the contract is valid, which it usually is, but what additional protections apply in the place of work. That is a specific, answerable question, and the register exists so that it can be asked about a named population rather than in general.
Contractual terms that exceed the statutory ones
The other direction is worth recording too. A contract or a collective agreement may give more than the local law requires: a shorter weekly maximum, longer rest, a notice requirement before overtime.
Those are enforceable obligations and they are frequently more demanding than the statutory floor. An organisation monitoring only against the statute can be comfortably compliant with the law and in breach of its own terms, and the second is easier for somebody to raise.
Where an entity is party to a collective or works council agreement, that agreement belongs in the register next to the statutory position, because for the people it covers it is the operative document.
Reading the clause for what it actually says
Some clauses choose a law. Some choose a law and a jurisdiction for disputes, which are different things. Some say nothing, leaving the question to default rules that turn on where the work is habitually carried out.
A contract with no governing law clause is not defective; it simply falls to those defaults, which in many places point back at the place of work anyway. Recording "none stated" is an accurate entry and a more useful one than an assumption.
Where several contract templates are in use across a group, they will not all say the same thing. Checking the actual templates rather than the one everybody remembers is a half-hour exercise that regularly produces a surprise.
What to put in the register
The law named in the contract, the template or version it came from, and whether the organisation has taken advice on how it interacts with the place of work.
The third column is the one that makes the row defensible. A row saying the governing law is one country, the work is in another, and nobody has looked at it is a recorded gap. A row where that question was asked in March and the answer is on file is a position.
Most registers will start with the first kind of row and that is fine. The point of writing it down is to make the list of unexamined combinations short, finite and visible to whoever can close it.
The template that nobody owns
Contract templates in a multi-country group are frequently maintained by whoever last needed one, which means several versions circulate and none is definitively current.
That matters here because the governing law clause is in the template, and a register built from the version somebody remembers will be wrong for whichever populations were hired under a different one.
Establish which template each population was hired under, as a column in the register. It is a slightly tedious question and it is the only way the governing law column means anything.