Skip to main content
Feedback and conflict

What to say instead of “your work is sloppy”

Why it can fall flat

“your work is sloppy”

Most people hear “sloppy” as a verdict on who they are, not a note about what went wrong, so they get defensive and stop listening. You usually just want the errors fixed and the standard met next time.

Say this instead

  1. 01

    I found a few mistakes in the report. The totals on page 2 don't match the table. Can you recheck it before it goes out?

    Coworker · Chat

    Pointing to the totals that don't match the table makes the fix obvious and keeps the focus on the work.

  2. 02

    The last three reports needed corrections after they were submitted. I need them checked before they come to me. Can we go through your process this week?

    Someone you manage · Email

    A repeated pattern calls for this one, since it states the standard and offers a concrete next step.

  3. 03

    The files we received have inconsistent formatting and missing fields, so we can't use them as they are. Could you send a corrected version by Thursday?

    Client · Email

    Use it when a client's material is unusable, because it names the problem and a deadline without blaming anyone.

  4. 04

    This draft isn't at the standard we need yet. The numbers don't add up and there are typos throughout. Let's go over it together at 3pm.

    Someone you manage · Chat

    Choose this when you must be direct about quality but still want to help the person fix it.

  5. 05

    The role details you sent have the wrong location and pay band. Please correct them before you submit my profile.

    Recruiter / HR · SMS

    A recruiter's carelessness can affect you, so naming the wrong details and asking for a correction protects your profile.

  6. 06

    Quick heads-up: the slides still have wrong figures on 4 and 7. Can you fix them before the 10am meeting?

    Coworker · SMS

    Time pressure suits this short nudge, which names exactly which slides need fixing and by when.

  7. 07

    I'm seeing errors in the handover files this week, and they're slowing my part down. Could we agree on a quick check before files are passed on?

    Boss · Chat

    Raising a quality problem upward goes best when you describe its impact and propose a simple fix.

Examples

Email

Hi Yvonne, Thanks for sending the monthly report. I found several errors: the totals on page 2 don't match the table, and two region names are misspelled. Could you correct these and recheck the figures before it goes to Mohan tomorrow at noon? Happy to look at it together for ten minutes if that helps. Thanks, Finley

Chat

Hi Yvonne, I found a few mistakes in the report: the page 2 totals don't match the table. Could you recheck it before it goes to Mohan at noon tomorrow?

What to avoid

  • Labels like “sloppy”, “careless” or “lazy” describe the person instead of the work, so leave them out.
  • Words like “always” and “never” turn one problem into an argument about character.
  • Vague comments with no examples leave the person unable to fix what you haven't pointed to.
  • Sending the message in front of others is a mistake when it could be said privately.
  • Sarcasm or hints are a poor substitute for a clear request to fix the problem.

Rewrite your message

Add a few words about your situation for a better result.

19 / 500

To
Via
Add names (optional)

AI writes these suggestions. Your text is sent to Claude (Anthropic) only to create the answer — we don't store it. Please leave out sensitive details.

Related phrases