Signed in Your Handwriting: The Reference You Write Says More About Your Judgement Than Their CV
Photo: Sgfgross, CC BY-SA 4.0, via Wikimedia Commons
It usually arrives on a Tuesday, in the middle of a week that already has too much in it. A former colleague, or someone you line-managed for eight months before they moved teams, is leaving. A hiring manager somewhere wants to hear from you. Can you do a reference by Friday?
Most younger leaders treat this as admin. It is not. A reference is a leadership document with your name at the bottom of it, and it will be read by strangers who have never met you and will never meet you. They will form a view of your colleague, certainly. But they will also form a view of the person who wrote it — how they think, how they weigh people up, whether they are the sort of manager who says something useful or something safe.
That is worth getting right, and it is not complicated. It just takes a bit more care than a rushed paragraph on a Friday afternoon.
Start with the spine of facts
Before you reach for adjectives, write down what is simply true. Dates of employment, job title, who they reported to, what the role actually covered, whether it was full or part time, and whether they are leaving voluntarily. This factual skeleton does two jobs: it makes the reference usable by whoever is checking boxes on the other end, and it keeps you honest. If you cannot write the spine confidently, you should not be writing the rest of it either.
A useful test: could you defend every line of this document in an email to your own manager, or to HR, if someone queried it six months from now? If a sentence would make you wince in that scenario, cut it.
Specific beats superlative every time
Here is the thing nobody tells you about references: everyone is excellent. Everyone is hard-working, dedicated and a real team player. Those words have been used so often they have stopped carrying information, and experienced recruiters skip straight past them looking for evidence.
One concrete example does more work than a paragraph of praise. The migration project they quietly held together. The client relationship they inherited and improved. The handover document that meant the team did not lose a fortnight. Name the thing, say what they did, say what changed as a result. Two of those, well chosen, will beat six generic sentences.
If you genuinely cannot think of a single example, that is information too. Sit with it before you start typing.
Know what a UK reference actually is
This is where a lot of early-career managers overthink it. In the UK, a reference is usually a short factual confirmation rather than the long character essay you might imagine from American films. There is generally no legal obligation to provide one unless your contract, a regulator or a sector rule says otherwise, and most organisations have a policy on who gives them and in what form.
Two practical points worth knowing. First, references should be accurate and not misleading — so if you say something, you need to be able to stand behind it. Second, some subjects are simply off limits. The Equality Act 2010 means you should not be commenting on protected characteristics, and opinions about sickness absence, health, family plans or anything in that territory have no place in a professional reference. Consult your HR team or the ACAS guidance if you are unsure, and treat this article as a starting point rather than legal advice.
Many employers now use a standard template with a handful of yes-or-no questions. Do not be sniffy about that. A clean, honest template completed properly is worth more than a florid letter that dodges the question.
When you cannot honestly praise them
This is the situation that actually keeps people awake, and it is more common than the leadership books admit. Someone was not great. They know it, you know it, and now they are asking you to help them move forward.
You have options, and all of them are better than a glowing fabrication.
You can provide a factual reference only — dates, role, scope — and say clearly that this is what you are offering. You can decline, politely and without drama, and explain that you do not feel you can write something helpful. You can point them towards someone better placed, perhaps a more senior manager or a previous line manager who saw more of the good work.
What you must not do is let them find out second-hand. If you are going to give a factual-only reference or decline, tell them before they put your name down. That conversation is awkward for four minutes and saves a relationship. Being ambushed by your own referee is a particular kind of sting, and people remember it for a decade.
Have the conversation before the document
Even in the easy cases, a quick call helps. Ask what the role is, what the hiring manager seems to care about, and whether there is anything they would particularly like you to cover if it is genuinely there to be said. You are not agreeing to inflate anything. You are making sure the strongest true version of your colleague lands on the page.
While you are at it, tell them what you plan to write. Nobody has ever regretted that small courtesy.
The traps worth avoiding
Faint praise is more visible than people think. A sentence that stops suspiciously short, or a warm paragraph about someone's punctuality, tells a reader plenty. Either say the useful thing or stick to facts — the coded version just looks like cowardice.
Over-claiming is the other failure. Do not assert confidence about things you never saw. If you have no evidence they would manage a team, say what you did see and leave the rest alone. Your credibility is the currency here, and it does not refill quickly.
And check the template properly before it goes out. Every year, someone's reference arrives with another candidate's name still in the second paragraph. It is a small thing that reads as a very large one.
Your name, at the bottom
At the end, add a line offering to be contacted if a conversation would help. It signals that you meant what you wrote and that you are not hiding behind a PDF.
Then keep a copy, retain it in line with your organisation's data policy, and get on with your day. One last habit worth building: jot down the good things your team does as they happen, a line or two, a couple of times a month. When December arrives and the reference requests land, you will not be reconstructing eight months of work from memory at half past five on a Friday. You will just be writing it down.