The One‑Page Impact Note I Use in Appraisals (and the ₹60,000 it Bought Me)
How I stopped relying on memory and last‑minute chats during appraisal season: a one‑page, evidence‑first impact note I share 48 hours before my review.
Written by: Rohan Deshpande
I remember waiting outside the meeting room while my manager wrapped up a 45‑minute calendar cluster. It was appraisal week. My hands were sweaty for a stupid reason: I’d rehearsed my achievements in my head for days, and every rehearsal added a little more noise. I was about to ask for a raise I needed — not just wanted — to cover a rent increase and a ₹7,000 monthly EMI. My company’s review buffer felt thin; last quarter they’d frozen hikes for a small team. This felt like one of those “say the right thing, at the right time” moments, and I had nothing to hand her except nerves.
Then I handed over a single A4 page.
That one page — structured, raw, and evidence‑first — replaced the rehearsed monologue. It got read in full. Two weeks later I had a ₹60,000 raise (around 5% on my then ₹12 lakh package), and a clearer conversation about promotions. I’ve used the same format across three companies since. It’s not magic. It’s structure and respect for someone else’s time.
Why a page, not a spreadsheet Because calendars are full. Because managers skim. Because appraisal processes in Indian startups and midsize companies are noisy: approvals bounce between engineering leads, HR, and the founding team; raises get trimmed if the paper trail is thin. A spreadsheet with 20 tabs will bury you. One page forces prioritization.
The constraints also shape the format: your manager likely sees 12–20 review notes in a week. They have slow HR forms to fill and a backlog of 6‑day‑week catchups (yes, I’ve worked at places where Fridays doubled as review days). A single page that answers four practical questions quickly is far more usable than a novel.
The exact one‑page structure I use I learned this the hard way: early on I tried a narrative email. It read like an award speech. It failed. Later, after a run where my manager forwarded my long doc to HR and HR flagged a claim I couldn’t back, I adopted a stricter format. The page now has three sharp blocks, each one 2–4 short lines:
- Impact headline (one sentence)
- Example: “Reduced payment failure rate from 3.6% to 1.1% for UPI flows; estimated revenue recovery ≈ ₹1.2L/month.”
- Evidence — 2–4 bullets with numbers, links, and artifacts
- PR#842 (merged, Sept), Jira ISSUE-313 (customer complaints down 42%), Grafana panel link: /d/payment‑flow
- Short note on methodology if numbers need context: “A/B rollouts, excluding weekends, 30‑day window.”
- Ask & next step (concrete)
- “Request: ₹60,000 CTC increase or fast‑track to L3 within next cycle based on impact. Next step: propose roadmap for Q3 — three small projects to scale this work.”
I keep language plain and quantify everything I can. If a metric is fuzzy, I say so and give the exact sample/date range or a link to the raw runbook. I sign and include a 48‑hour warning: “I’ll drop this here 48h before our meeting so you can scan it.”
Why 48 hours? Two reasons. First, calendars are chaotic in India — managers shift meetings, get pulled into client calls, and read documents when time opens up. Second, it gives them time to ask clarifying questions before the appraisal, so the meeting becomes a decision conversation, not a discovery session.
The failure that forced me to improve I once overreached. In my enthusiasm I claimed “decreased churn by 2% contributing ₹2 lakh ARR” and sent the page without attaching logs. HR asked for backup. The recovery math relied on a narrow cohort I hadn’t documented. That conversation felt awkward. The manager believed me but HR didn’t. It stalled the raise and cost a week of momentum.
After that I added a fourth small thing to the note: an “evidence pack” folder link with 3 items max — a screenshot, a PR, and the raw query or dashboard. No one likes fishing for receipts in appraisal season. Give them the receipts.
How I handle soft outcomes and team bias Not every win is numeric. I used to dismiss mentorship and code review work as “soft.” That used to be my weakness. Now I add a one‑line impact with a concrete signal: “Mentored 3 interns; 2 promoted to SDE‑1, average onboarding ramp reduced from 30 to 21 days (onboarding dashboard link).” If you can’t point to a metric, point to a dependency removed, a ticket that stopped reoccurring, or a saved escalation call in PagerDuty. Link to the Slack thread or post‑mortem.
Tradeoffs and the small cost The honest tradeoff: this takes time. I spend 30–60 minutes preparing this page each cycle. For that, I get sharper appraisal conversations, faster HR decisions, and less mental wear. It’s an investment — especially when appraisals come twice a year. There’s also a human cost: crafting the right language can feel like self‑promotion, and if your manager prefers verbal nuance, a sheet can seem blunt. I judged that the reduced ambiguity outweighs the awkwardness.
A note on numbers and negotiation Ask for a number or a concrete next step. Don’t say “open to discussion” as your only line. For me, ₹60,000 was not arbitrary: I benchmarked internal bands, compared three offers, and calculated a cost of living gap with my projected expenses (rent + EMI + buffer). If your firm has frozen cash, propose alternatives: a promotion with deferred comp, a learning budget, or a review in 3 months with clear KPIs.
What I walked away with The single most useful rule I adopted: prepare an evidence‑first note, keep it to one page, and give 48 hours. It turned my appraisals from noisy monologues into focused conversations. It bought me a measurable raise and a better haggling position. It also made me respect the other person’s time — which, surprisingly, worked in my favour more often than I expected.
If you try it, don’t skip the evidence pack. When I did, it cost me a week and a ₹15,000 delay. The page is small. The discipline isn’t. But it’s the simplest thing that turned appraisal theatre into a predictable process for me.