What Was Said at Interview
Why assurances given during recruitment turn into rota constraints nobody has recorded, what they cost, and the two-minute habit that prevents the whole category.
A sentence said in an interview can constrain a rota for a decade. "You wouldn't be doing nights in this role." "We'd keep you off the weekend rotation." "It's a Monday-to-Friday job in practice."
The constraint in “What Was Said at Interview” becomes useful only when its source, cost and effect on coverage are visible. A team considering a practical approach to employee time tracking for employee time tracking can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
None of that reaches the rota. It reaches one person, who reasonably plans around it, and surfaces years later as a conflict between what somebody was told and what the pattern now needs.
The assumptions behind “What Was Said at Interview” can also be checked against Human Resources for Health research. Record what applies locally and what requires qualified advice.
Why it happens so consistently
Recruitment is a selling activity under time pressure. The person describing the role wants to fill it, knows the current pattern, and describes that pattern as though it were a property of the job.
They are not being dishonest. They are describing today and the candidate is hearing a commitment, and neither of them writes anything down because nothing feels like it has been agreed.
What the person heard
Usually something firmer than what was said. "We don't tend to ask people in this role to do nights" is heard as "no nights", and the difference only becomes visible when the first night shift is proposed.
That asymmetry is predictable enough to design around, which is what the rest of this page is about.
The two-minute habit that prevents it
At the end of the conversation, whoever is recruiting writes down any statement made about hours, pattern or location, and puts it in the offer or in a note to the file.
- Write down any statement made about hours, pattern or location.
- Decide whether the organisation means it as a commitment.
- Put the agreed version in the offer, or correct it in the conversation.
- Record either outcome with the date.
Two minutes. It converts an assurance into a recorded arrangement or into a correction, and both are better than the third outcome, which is a disagreement in four years that neither party can evidence.
The correction is the valuable part
Writing it down forces the recruiter to decide whether they meant it. A good proportion of these statements turn out, on contact with a keyboard, to be descriptions rather than commitments, and the sentence that gets written is the accurate one.
That conversation is much easier at offer stage than at the point the pattern changes, and it is the same conversation.
What to do with the ones already out there
Every team has them, unrecorded, from managers who have gone. They surface one at a time, usually at the worst moment.
When one surfaces, treat it as a live question rather than as a dispute about history: here is what you understood, here is where we are, what can we agree now. Whether the original statement has any contractual force is a question for somebody qualified in the place concerned, and it is usually not the question that resolves the situation.
Why "it was never in writing" is a bad opening
Because it may be wrong, and because it converts a solvable scheduling problem into a dispute about credibility. The person is not usually mistaken about what they were told.
The useful opening concedes the point that costs nothing: you were told that, here is what has changed, here is what we can do. Most of these end in an agreement that the rota can live with.
The pattern of them across a team
Worth mapping once. Ask the question neutrally — what were you told about hours when you joined — and a surprising number of people have an answer, often from the same two or three recruiting managers.
The map is useful in itself and it is also diagnostic: a cluster from one manager is a recruitment practice problem, not a rota problem.
The induction gap
The second-best moment to catch these is induction, and almost nobody uses it. A single line on the induction checklist — "any agreements about hours or pattern, recorded here" — catches most of what the offer missed.
It also establishes, in the first week, that arrangements are recorded rather than remembered, which quietly changes what people expect later.
What to record and where
The statement, the date, who made it, and whether the organisation is treating it as an agreement. If it is an agreement, it joins the register with a review date like any other.
If it is not, say so to the person at the time. An unresolved assurance sitting in a file is worse than either answer, because it will be found later by somebody who has to guess what it meant.
The cost of the whole category
Small individually and large in total. In most teams, three or four people have an understanding about their pattern that the rota does not know about, and the rota discovers each one by breaching it.
Recording them is cheap. Discovering them one at a time, under pressure, in front of the rest of the team, is the expensive way, and it is the current method nearly everywhere.