Check the data permission first
Use AI with real workplace material only if the exact tool, account, purpose and data category are approved by your employer and any relevant client obligations. Review notes, Slack messages, performance observations and paraphrases can remain confidential without names. General-chat practice uses fictional material only. If authorization is unclear, write the real document privately without AI; do not solve the uncertainty by pasting a “redacted” version.
A 360 review request lands in your inbox asking for feedback on a colleague, or your manager asks you to write up specific feedback for someone you supervise. You have a general sense of how it’s gone (mostly good, with one recurring friction point), but turning that general sense into clear, specific, useful written feedback is harder than it sounds. AI is a real help here for structure and phrasing. It is not a source of the actual content, and treating it as one is where this goes wrong.
This is a different problem from refusing to rank people with AI, which covers the specific danger of asking a model to score or rank a person. This article assumes you are not asking for a score; you are writing qualitative feedback about specific behavior, and the risk is different: AI smoothing your actual observations into something vaguer, harsher, or more generic than what you actually witnessed and intended to say.
Do not use it for formal discipline, protected disclosures, discrimination or accommodation decisions, safeguarding, redundancy, or termination. Follow the controlling process and obtain qualified review.
The rule: examples are yours, structure is AI’s
Use specific observations with dates or source references: for example, a missed report deadline or an interruption you witnessed. Without authorized evidence, AI cannot establish what happened; a request to “write feedback about someone who could communicate better” may produce invented incidents. Keep record-backed facts, your recollection and your interpretation distinguishable so the person can respond to the actual claim.
Never let AI generate an example, incident, or specific behavior in a piece of feedback about a real person. If you cannot recall a concrete instance to support a point, either find one before writing the feedback or drop the point; a general impression without a specific example is not useful feedback, and an invented one is worse than none.
A workflow that keeps examples real
Step 1: List your own specific observations first
Before opening any AI tool, write down what you actually remember: specific situations, what the person did, and what the effect was. The Center for Creative Leadership’s widely used Situation-Behavior-Impact model is a useful shape for this even before AI enters the picture: situation (when/where), behavior (what specifically happened, described neutrally), impact (what effect it had) (Center for Creative Leadership, “Use SBI (Situation-Behavior-Impact) to Inquire About Intent”).
Step 2: Use AI to organize and phrase, not to generate content
Here are specific observations I want to give as feedback to a
colleague: [notes authorized for this exact tool and purpose; otherwise a fictional exercise]. Help me
phrase these clearly and professionally using this same structure.
Do not add any example, behavior, or impact that I did not
describe above. Keep the tone matched to what I actually intend;
do not make constructive points sound harsher than I described them,
and do not soften a genuine concern into vague praise.
The second instruction matters as much as the first; a model asked to “make this diplomatic” will sometimes round a real, specific concern into a euphemism vague enough that the person receiving it cannot tell what to actually change.
Step 3: Check the tone against your actual intent, in both directions
Read the draft back and ask two separate questions: does this sound harsher than what I actually meant to say, and does this sound softer or vaguer than what I actually meant to say? Both directions cause real damage; overcorrected harshness can misrepresent a minor issue as a serious one, and overcorrected softness can bury a real, actionable concern so deep in diplomatic language that the person never registers it as something to change.
Step 4: Verify every example against its source before sending
For each claim, identify the authorized record or clearly attributed recollection supporting it. Check the date, wording and scope; uncertainty in memory stays uncertain in the draft. If no source supports the event, remove the claim instead of treating fluent wording as corroboration.
If the feedback will feed into a decision about pay, promotion, or a formal performance process, use your organization’s official feedback form or channel rather than an informal AI-drafted note, and follow whatever process your HR team has defined for that specific context; a well-phrased private message is not a substitute for the record a formal process requires.
Polish is not fairness
It is easy to assume that AI-polished feedback is automatically fairer feedback, because it reads calmer and more structured than a first draft written in frustration or haste. Polish and fairness are different things. Specificity and evidence are checks on a draft, not guarantees of fairness; context, relevant standards and the recipient’s account can also matter. A calmly worded piece of feedback built on a vague or invented example is not an improvement on a rougher one built on something real; it is a better-dressed version of the same problem.
Catch drift in both directions
Invented observation: “In Tuesday’s planning meeting, you interrupted twice while I explained the test result. I lost my place and did not finish the explanation.” A harsh rewrite, “You repeatedly undermine colleagues,” invents a broader pattern and motive. A softened rewrite, “You bring energy to discussion,” hides the actual concern.
A bounded draft preserves the specific meeting, observed interruptions and the speaker’s reported impact, then asks: “Could we let each person finish before responding?” This is a teaching example, not a judgment about a real colleague. CCL’s SBI guidance separates situation, observable behavior and impact; intent can be asked about rather than inferred.
Compare real feedback with your authorized records and clearly attributed recollections. A statement’s polished tone does not establish fairness or accuracy. Use the controlling formal process for matters affecting discipline, discrimination, accommodation, safeguarding or employment status.



