Reading the Contract Before You Rely On It
What to check in an employment contract before relying on it: which version applies, what changed since, and where contract and handbook disagree.
What one organisation found when it read a contract it had relied on for four years
The contract described a job the person had not done since 2021, and nothing recorded the change. Every row is what one organisation found in its own file, not a statement of what any jurisdiction requires.
Read the contract before you rely on a single clause in it, because the document in the file is usually not the agreement that is actually in force. Pay has changed, hours have changed, the role has changed twice, and none of it was written down — so the contract describes a job the person stopped doing some years ago.
The workflow in “Reading the Contract Before You Rely On It” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring how to monitor employees without being intrusive, how to monitor employees without being intrusive can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.
This matters because the contract is where notice, deductions, restrictions and the status of the handbook all come from. Building a process on a clause that was superseded by conduct is how organisations end up arguing about their own paperwork.
For an independent reference relevant to “Reading the Contract Before You Rely On It”, consult the NCSC insider-data guidance. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
Which version is in force
Start with the simplest question and expect it to be hard: what are the current terms? The answer is the signed document plus every variation since, and variations are rarely filed together with the thing they vary.
Pay reviews are usually recorded. Changes to hours, duties, reporting line, place of work and benefits frequently are not — they happened in a conversation, took effect the following Monday, and exist only in the fact that everyone behaved accordingly. A long enough period of everyone behaving accordingly can itself change the terms, which is precisely why the gap matters.
What to actually look at
- The notice provision, in both directions, and whether it differs from any policy that also states one.
- Whether pay in lieu of notice is permitted, and whether it is discretionary or a right.
- Any clause permitting deductions from pay, and what exactly it covers.
- Post-termination restrictions, and whether they were drafted for the role the person now holds.
- Confidentiality, and whether it has an end date or is open-ended.
- Whether the handbook is incorporated into the contract, and if so which parts.
- Place of work, hours and duties, read against what the person actually does.
Each of these takes a minute to check and each of them is capable of changing what the organisation can do.
Where the contract and the policy disagree
Organisations routinely operate two documents that say different things. The contract gives one month's notice; the policy says the notice period increases with service. The contract says nothing about redundancy pay; the handbook sets out a formula that has been applied for a decade.
Which prevails is a legal question and depends on how the documents are drafted and what has happened in practice. What is not in doubt is that discovering the conflict after a figure has been quoted to somebody is much worse than discovering it before. Read both, note the difference, and take advice on which governs before anything is said out loud.
Restrictions drafted for a different job
Post-termination restrictions are usually written when somebody is hired and almost never revisited. Somebody promoted from an administrative role into client management may be bound by nothing useful; somebody who moved the other way may be bound by restrictions far wider than their current role could justify.
Both situations are problems, in opposite directions. Neither is fixed at the point of exit, which is the point at which organisations first look. Whether a restriction drafted for a former role is enforceable at all, and what can be done about it, is a question for somebody qualified in the place concerned.
Clauses that were signed but never read
A deduction clause signed on somebody's first day is a common feature of training-cost and relocation arrangements. It will be relied on at the exit, often by somebody in payroll who has never seen it, and sometimes for a purpose it does not cover.
Before taking any deduction from a final payment, find the clause, read what it actually permits, and check that the facts match it. The clause that permits recovery of a specific course fee does not permit recovery of something else.
Where the signed copy actually is
A contract that cannot be produced is a contract that may as well not exist for most practical purposes, and a surprising number cannot be produced — filed under a maiden name, scanned without the signature page, held by a predecessor organisation, or stored in a system that was replaced in 2020.
Look for it before anything depends on it. If the signed copy has gone, the organisation is not without options, but it is in a different position and somebody should know that at the start. It cannot be retrofitted once a figure has been quoted on the strength of a clause nobody can show was agreed.
What to do with what you find
The realistic outcome of this exercise is a short list of gaps: no current version, variations undocumented, handbook status unclear, restrictions out of date. Record the list rather than resolving to fix it later.
Two of those gaps can be closed on the spot by issuing something now, and the rest cannot be closed retrospectively at all. Knowing which is which before the first conversation is the entire point, and it is the kind of work that cannot be retrofitted once a process has started.