What "Done" Means: How to Know the Job Is Really Finished

It is Friday afternoon, and a shop owner asks the question every owner asks: "Did the week's order confirmations go out?" The answer comes back quickly — done, all sent. On Monday, three customers ring in to ask where their orders are. The confirmations went out, mostly. Three were never sent, because those three orders had no email address on file, and nobody's job was to notice. The work was marked done when the work stopped, not when the result existed.

This article was drafted with AI assistance. It is written in plain English for people who run businesses, not for people who build software, and it makes no claim about any particular product. It is about the smallest word in any working day — "done" — and why it causes more trouble than any other word when you hand work to someone, or something, else.

Done is a result, not a feeling

Most of us use "done" to mean "I worked on it and I stopped." That is a feeling, not a result. A job is done when something in the world has changed in the way you wanted: the customer has the reply, the invoice has gone out, the booking is in the diary. Everything short of that is "worked on," and "worked on" is not the same thing.

This matters more when the work is done by a system on your behalf. A person who gets stuck will usually come and tell you. A system that gets stuck will usually just stop, quietly, and report that it finished — because from its side, it did everything it could do. The three missing confirmations were not a failure of effort. They were a failure of definition: nobody had said what "done" meant, so "no more orders I could process" counted as done.

The fix is not more effort. It is a clearer finish line.

Write down what done looks like, before the work starts

Before you hand a job over, write one sentence that says what finished looks like. Not how it should be done — what the result is. "Every customer who ordered this week has a confirmation in their inbox." "Every invoice has a matching payment, or a note saying why not." "Every enquiry has a reply, or a reason it is waiting."

One sentence is enough, and it does two jobs at once. First, it tells the person or system doing the work exactly when to stop. Second, it tells you exactly what to check when they say they have stopped. If the sentence cannot be checked — if you cannot look at something and say yes or no — it is not finished yet. Rewrite it until it is.

This is also the moment to name the exceptions. The three orders with no email address were not a surprise anyone should have had to discover on Monday. If the rule is "every customer has a confirmation," then an order with no address is not a customer with a confirmation — it is a problem, and the job is not done until someone has decided what happens to it. Write the exception into the sentence: "Every customer has a confirmation, or their order is on the exceptions list with a name next to it."

Three questions for finished work

When the work comes back marked done, you do not need to redo it. You need to check it — and checking is a much smaller job than doing. Three questions cover most of it.

First, did it reach the right person? A reply sent to the wrong address is not a reply. A confirmation filed in the wrong folder is not a confirmation. Check the destination, not just the fact that something was sent.

Second, did it say the right thing? Read one or two examples properly, not just the first line. The wrong price, the wrong date, the wrong name — these are the mistakes that look invisible from a distance and obvious up close. A quick read of a sample catches what a summary never will.

Third, is there a record I can look at? If you cannot see what was done — what went out, when, to whom — you cannot check it, and you cannot fix it when it goes wrong. A job with no record is a job you have to take on trust. Trust is fine. Trust with a record is better.

Spot-check, don't re-do

The fear that stops most owners from handing work over is the fear of having to check everything, which would take as long as doing it yourself. But checking everything is not the job. Checking a sample is.

Five out of fifty, picked at random, tells you almost everything you need to know about the other forty-five. If the five are right, the system is working. If one of the five is wrong, you have found a problem early and cheaply — and you now know exactly what to look for in the rest. Checking is not a sign of distrust. It is how trust is built, a little at a time, on evidence instead of hope.

And when the check finds a mistake, treat it as useful news. A mistake found in a sample is a mistake you can fix before it reaches a customer. A system that is never checked will still make mistakes — you will just find them later, when they cost more.

The short version

A job is not done when the work stops. It is done when the result you asked for exists, and you can point at it. Write that result down in one checkable sentence before the work starts, name the exceptions, and check a small sample when it comes back: the right person, the right thing, a record you can look at. That is the whole routine. It takes five minutes, and it is the difference between handing work over and merely hoping it happened.

Ready-made AI agents for small businesses, built in public.