Can Drunken My Boss Affect My Job Review?

My short take: yes, a boss showing up drunk can absolutely affect your review, and it can go either way — unfairly harsh, oddly lenient, or simply inconsistent. What I always do in those situations is keep everything professional and documented. Right after the meeting I type up a neutral summary of what was said and what I committed to, and I send it to the manager (and HR if the company culture supports that). That step does two things: it signals professionalism and creates a timestamped account that can be referred back to.

Beyond that, I gather objective evidence—sales numbers, completed project dates, client feedback—so that any subjective comment can be weighed against facts. If the drunk behavior is repeated or leads to a clearly biased review, I’d escalate quietly to HR or an equivalent channel. Over the years I’ve learned not to let one awkward encounter derail long-term performance; you protect yourself with records and calm communication, and you let the larger patterns of your work tell the real story. For me, that approach has kept my reputation intact even when leadership was less than stellar.

My gut tells me there's a real chance your boss being drunk can influence your job review — and not always in ways you'd want. If the person who writes or signs off on reviews is impaired, their memory, judgement, and emotional state can all be skewed. They might forget key achievements, conflate unrelated frustrations with your performance, or, on the flip side, hand out undeserved praise because they're not thinking clearly. Either outcome can ripple through HR systems: a bad rating affects raises, promotion eligibility, and the record that follows you for the next cycle.

If it were me, I'd try to be calm and strategic. First, document: keep copies of your measurable results, dates of major projects, emails that show your contributions, and any notes from the meeting. After a disconcerting review, I’d send a polite, factual follow-up email summarizing what was discussed — that creates a written record and gives the manager a chance to correct anything they said while impaired. If your company has a formal policy about impairment or professional conduct, read it and note the relevant parts. You can also discreetly talk to HR or a trusted colleague to understand options; sometimes asking for a review to be rescheduled if the manager seems unfit is perfectly reasonable.

This doesn't mean starting a war — retaliation and escalation can make things worse. My favorite weird consolation is that episodes like this have been done to death in shows like 'The Office', where drunken leadership creates chaos, but in real life the best leverage is calm documentation and measured escalation. Personally, I try to let the facts speak louder than the fog of a single bad meeting, and I've found that steady follow-up usually smooths things out.

Picture walking into a scheduled review and realizing the person across the table had been drinking. My instinct is to separate emotion from tactic: your immediate priority should be to protect your record, not react theatrically. If I were there, I'd stay composed, keep responses concise, and avoid arguing. Let them speak, take notes, and if anything feels off, politely suggest reconvening when everyone is clear-headed. That kind of calm buys you credibility.

After the meeting, I’d write a concise recap email that outlines what was said and any agreed next steps. That recap becomes essential if the feedback is unfounded or if it diverges from past performance documentation. If the company has a formal review process, ask HR about how ratings are finalized and whether a second reviewer signs off — many organizations require multiple signatures or calibration meetings that provide a safety net. If your workplace has a union or employee representative, you could consult them about fairness standards. I’ve seen managers go from belligerent to apologetic after being confronted with a clear, polite written trail; it’s surprising how often clarity fixes what a clouded moment caused. Personally, I prefer handling things with steady documentation and a few allies in the right places.