Write down what you think is expected, in five lines, and send it back to the person who asked. Ask one question: "What would make this a mistake?" Then agree what done looks like before you start. Unclear expectations are not a people problem. They are a missing piece of writing. On a staffing desk, "a couple of forklift people for Monday" turns out to mean five people, two of them certified, at the dock, at 6 a.m.
The translation problem
Here is the email. "Hey, can you get us a couple of forklift people for Monday? Thanks."
Here is what the client meant. Five people. Two of them need current forklift cards, the other three are general labor. They start at the loading dock, not the main gate. The shift starts at 6 a.m., and the site wants them there at 5:45. Steel-toe boots. The order runs three weeks.
A recruiter who sources "a couple of forklift people" sends two certified drivers for a 7 a.m. start. On Monday, the client is angry and the recruiter is confused. Nobody lied. Nobody wrote it down.
What to do, in order
1. Write what you heard. Five lines. What, how many, where, when, and for how long. "Two forklift operators, Monday, main gate, 7 a.m., ongoing?"
2. Send it back. "Here is what I have. Is this right?" Most people correct a written guess in one reply. They rarely volunteer the details without one.
3. Ask the mistake question. "What would make this go wrong?" The answer is the detail they forgot. "If they're not at the dock by 5:45, the lead sends them home."
4. Agree what done looks like. "Five people confirmed by Friday noon, two with cards, all told 5:45 at the dock." Now you both know.
5. Check against it before you deliver. Read the confirmation note against the five lines. Is every one of them in it?
Why this works on any desk
The same five steps work for an unclear report request from your boss, a vague task from a client, or a "quick thing" from a colleague. The written guess is the key. It is faster for people to correct something than to describe something from nothing, and it leaves a record you can check your work against.
For managers: stop sending unclear requests
If your team keeps guessing, look at what you send them. One line, two numbers and a date is usually enough. Or ask them to send the five-line guess back, and make it normal to do so. The ten minutes spent at the start are the cheapest ten minutes in the whole job.
Where M-Tracker fits
In M-Tracker, every piece of work starts from a written brief, the five lines above, and the finished work is checked against it before it goes to the manager or the client. The confirmation for Monday gets read against "five, two certified, dock, 5:45" before anyone sends it. The guessing stops at the start, not at the gate.
Try M-Tracker free14-day trial. No credit card. No employee surveillance.
Questions people ask
What if my manager will not clarify?
Send the written guess anyway and say you will proceed on it unless they say otherwise. A written guess that was never corrected is a much better position than a verbal one.
Is it my job to clarify, or theirs?
Whoever does the work pays for the guess. So it is worth your ten minutes, whoever's job it is.
How do I do this without sounding difficult?
"Here's what I've got, is that right?" sounds helpful, not difficult. It is the opposite of difficult: it is the thing that stops Monday going wrong.
Work you can trust, without redoing it.
Your team gets feedback before work reaches you, or your client.
Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy