Most recommendation letters are warm, generous and completely useless, because they contain only adjectives. A reader who has seen fifty of them discounts praise entirely and looks for specifics — what this person did, how much of it, and what happened. Two specifics beat ten adjectives. Three samples: a manager writing for a direct report, a peer, and the version you draft yourself when asked to.
The standard case. Notice how little of it is praise and how much is simply what happened, stated precisely.
I have managed Bilal Ahmed directly for four years, from April 2022 until the present, in his role as Senior Accountant at Nishat Textile Mills. I am writing this without reservation and at his request.
Bilal owns the month-end close for three of our entities. When he took it on, close took twelve working days. It now takes six. He achieved that not by working longer hours but by standardising our intercompany reconciliation, which was the actual bottleneck and which three people before him had not identified.
In 2023 he ran a reconciliation audit on his own initiative and recovered PKR 3.2 million in duplicate vendor payments. Nobody asked him to look. He has also filed three years of sales and income tax returns without a single penalty, which in my experience is unusual.
He supervises two accounts officers. One of them was promoted last year, largely on the strength of how Bilal had developed her. He is the person I give work to when I need it to be correct rather than fast, and he is straightforward about what he does not know, which I value more than confidence.
I am sorry to lose him and would re-employ him immediately. I am happy to be contacted directly about any of the above.
A peer cannot speak to how someone performs under management, so the letter should be honest about that and concentrate on what a colleague actually sees.
I have worked alongside Bilal Ahmed for four years. I am not his manager — I run internal audit and he runs the entity closes, so we sit on opposite sides of the same process. That is the perspective this letter offers.
Across three annual audits, Bilal has been the person in finance whose working papers did not need to be sent back. In 2024 and 2025 his sections were signed off without a single follow-up query, which was true of nobody else in the department.
When I raised a control weakness in the payment approval process in 2023, he did not defend it, which is the usual reaction. He rebuilt the threshold and the review step within a month and asked me to test it afterwards. That exchange is the reason I agreed to write this.
I would work with him again on any process where the numbers have to be right and the audit trail has to survive scrutiny.
The common request in Pakistan and much of the region: your manager agrees, then asks you to draft it. This is what a self-drafted letter should look like — factual, restrained, and easy for them to sign.
Hamza Ali has reported to me for three years as a Software Engineer at Systems Limited, from February 2023 to the present.
He rebuilt our core API layer, reducing median response time from 800 milliseconds to 320. He delivered the Stripe payments integration that now processes approximately 15,000 transactions each month, and he took automated test coverage from 34 per cent to 81 per cent, which halved the number of production hotfixes we ship.
He mentors two junior engineers, both of whom reached independent production releases within their first four months, against a team average closer to seven.
In my assessment his particular strength is that he volunteers unglamorous work — test coverage, documentation, on-call runbooks — which is uncommon and disproportionately valuable in a small team.
I recommend him without reservation and can be contacted at the details above.
Read a stack of recommendation letters and they converge on the same vocabulary: hardworking, dedicated, reliable, an asset to any organisation. The words are meant sincerely and they carry no information, because they appear in every letter including the lukewarm ones.
What a reader is actually looking for is evidence that the writer knows this person well enough to say something only they could say. One precise incident does that. Two numbers do it. A qualified judgement — "correct rather than fast" — does it better than any superlative.
A useful test before signing: could this letter be sent about a different person by changing the name? If yes, it has said nothing, however warm it sounds.
One page. A recommendation letter that runs to two pages is usually padding, and padding is read as an absence of substance.
It is extremely common here for a manager to agree and then ask you to write it. It is not dishonest — they will read, edit and sign it, and their signature is the endorsement. But it is difficult to do well, because the instinct is to write what you wish someone thought of you.
And attach the same referee brief from your reference set — the role, the dates, the numbers. It gives them the material to add something you would never have thought to include.
Experienced readers know that a lukewarm letter is more informative than a warm one, and they read for the signals.
If you are asked to write for someone you cannot genuinely recommend, the honest option is to decline. A weak letter damages them more than no letter, and they will not know why.
All three samples are free to read and copy. Want them as editable Word files, or a letter drafted from the actual record so your manager only has to check and sign? Both take a minute.
Build mine with Hexa → Download all three · FreeThe people above are illustrative examples written for teaching purposes. Names, employers, registration numbers and figures are invented and should not be copied into a real application — use them as a shape to pour your own verified numbers into.