Rejecting Work Against a Specification
Rejection is the central instrument a buyer holds, slower and blunter than correcting somebody, and it works only if there is something to reject against.
Reads as a businessReads as employmentCuts both waysDepends where you are
Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. Correction is commercial here, and it is slower and blunter than the thing it replaces.
Rejection is the central instrument a buyer actually holds. It is slower and blunter than telling somebody to fix it, and it only works at all if there is a document saying what the work was supposed to be.
The practical issue in “Rejecting Work Against a Specification” becomes clearer when expectations and evidence are visible to both sides. Used for boss vs leader, a structured way to review boss vs leader can add time and project context, provided the purpose is disclosed, access is limited and every consequential interpretation receives human review.
Everything in the first two sections of this collection exists so that this article has something to operate on.
A broader benchmark for “Rejecting Work Against a Specification” is available through Gartner project-management insights. Use it alongside the brief and day-to-day facts so general guidance supports rather than replaces case-specific judgement.
What rejecting actually is
A statement that the delivered thing does not meet what was agreed, identifying which part, and a request that it be delivered as agreed.
It is not a judgement about the person, it does not require anybody to agree that they did badly, and it does not depend on persuading anyone. That is its whole value.
Why it is slower
Because it goes through a document rather than through a conversation. Finding the clause, writing the rejection, sending it, waiting for the response, agreeing what happens next — two days where an employer would take ten minutes.
That is the price, it is real, and it is paid in every single engagement where something goes wrong.
Rejecting well
Four things in the message and nothing else:
- What was delivered.
- The specific requirement it does not meet, quoted.
- What has to change for it to be accepted.
- When it is needed by.
No adjectives, no assessment of effort, no discussion of how it happened. A rejection that strays into any of those invites a conversation about the person, which is the conversation you do not want to be having.
The rejection you cannot make
If the requirement was never written down, you cannot point at it, and the exchange becomes your opinion against theirs.
At that point most buyers do one of two things: accept work they are unhappy with, or start directing. Both are expensive, and both are consequences of an afternoon that was skipped at the start.
Partial rejection
Common and worth doing explicitly. Three of the four deliverables meet the specification and the fourth does not.
Accepting what is good and rejecting what is not keeps the engagement moving and keeps the record accurate. Rejecting everything because one part failed is a blunt response that suppliers reasonably resent, and it tends to produce an argument about the whole engagement rather than about the item.
Accepting with a note
Sometimes the work does not meet the specification and you need it anyway, now. Accepting it is the right commercial call.
Record what was accepted and what it did not meet. That costs a sentence and it means the next conversation starts from a shared position rather than from a supplier who believes everything has been fine.
The acceptance that never happens
A quiet failure worth naming. In many engagements nobody ever formally accepts anything; work arrives, gets used, and gets paid for.
That is fine until it is not, and the moment it is not you discover that nothing was ever assessed against anything. Acceptance does not require a process. It requires somebody saying, in writing, that this meets what we agreed.
When the specification was wrong
It happens, and a supplier who delivers exactly what was specified has delivered. Rejecting work for failing to meet a requirement nobody wrote is not available.
The honest route is to treat it as a change, agree it, and pay for the difference. Buyers who instead lean on the supplier to fix a specification failure for nothing are spending the relationship, and the supplier is keeping count.
Who does the rejecting
Whoever has the authority to accept. In a surprising number of businesses the person managing the work day to day cannot formally reject anything, so they correct instead, which is the instrument they have rather than the one they should be using.
Putting acceptance authority where the work is managed removes most of the reason for informal correction, and it is a change to an internal approval list rather than to anything commercial.
Rejecting work from somebody you like
The hardest version and the one that most often does not happen. A supplier who has been good for two years delivers something that does not meet the specification, and the buyer fixes it internally rather than have an awkward exchange.
Done once, that is kindness. Done consistently, the supplier never learns that the standard is enforced, the specification stops governing anything, and the eventual conversation is far worse than the four small ones that were avoided.
What it leaves you with
A thinner and more reliable instrument than correction. It does not make anybody better, it does not improve a weak supplier, and it cannot fix an engagement that was wrong from the start.
What it does is let you refuse to pay for work that is not what you bought, without a conversation about anybody's performance. For a commercial arrangement that is the right instrument, and it is available to any buyer who wrote the specification down.