Most small companies discover their mistakes when the customer does. The invoice has the wrong amount, the document names the wrong product, the delivered file is the old version, the setup misses one agreed item. Each mistake is small, and each costs a phone call, a correction, and a little of the customer's trust.
A final check before work leaves the company catches many of these. It does not need a quality department. It needs a short list, one person responsible, and a note of what was found. This article describes a routine that takes a few minutes per job and fits a team of three to thirty people.
What counts as "leaving the company"
Decide which moments are covered. Typical ones are a quote or proposal sent out, an invoice, a delivered document or file, a finished installation, a software change handed to the customer, or a parcel handed to the courier. You do not need to check everything. Start with the one or two outputs where a mistake is most expensive or most embarrassing, and add more later.
Write the list of covered outputs on the same page as the checklist, so that nobody has to guess whether a particular job needs the check.
Build the checklist from real mistakes
A generic checklist from the internet is rarely used. A list built from your own errors is. Look at the last three months of complaints, corrections, credit notes and "sorry, that was our mistake" emails. If you keep a record of complaints, as described in a customer complaint log, it is the best source. Group the mistakes and write one check for each group.
Keep the list to five to eight items. Longer lists are skipped. Write each item as something that can be seen and answered yes or no:
- Right customer, right details: name, address, reference number and dates match the order.
- Matches the request: the work is compared with the original request or quote, line by line, not from memory.
- Right version: the file, document or build is the final one, not a draft.
- Numbers add up: prices, quantities and totals are recalculated, not just read.
- Works as the customer will use it: open the file, click the link, run the function once as the customer would.
- Nothing internal left in: no comments, notes, test data or internal prices.
The sixth item surprises people, but internal notes in a document sent outside are one of the most common and most awkward mistakes.
Choose who signs it off
The person who did the work is the worst person to check it. They see what they meant to write, not what is on the page. Where possible, the check is done by a colleague. In a very small team, the next best option is the same person after a break, using the list, with the original request open next to the result.
Name one person for each type of output, and one deputy for when that person is away. The sign-off can be as light as a tick in the job record and initials. What matters is that the work does not leave until the tick exists. If you have a regular handover between steps, as in packing and delivering orders, the check fits naturally just before it.
Keep the check short
Aim for two to five minutes per job. If the check takes longer, either the list is too long or the work is too complex for one check, and it should be split. For larger jobs, such as a software change, a longer check with real cases is appropriate; a method for that is in testing a change before staff see it.
Also agree what happens when the check fails. The simple rule: the person who checks says what is wrong, the person who did the work fixes it, and the check is repeated for the changed item. Nobody is blamed in the log; the point is to see what happens, not who did it.
Log what you find
Keep a log in a shared sheet with five columns: date, job reference, what was found, whether it was fixed before sending, and a category taken from your checklist. One line per finding. Include small findings fixed on the spot, because they show where mistakes start.
Two common objections: "we have no time for logging" and "we found nothing". Logging takes ten seconds per finding. And if the log stays empty for a month, either the work is very reliable or the check is not being done properly. Pick two jobs at random and check them again to find out which.
Use the log once a month
Once a month, spend fifteen minutes with the log. Count the findings per category. If one category appears three times or more, look for a change in the way the work is done, not a warning to be more careful. A wrong price on three quotes might mean the price list is in two places. A draft sent as final might mean file names do not show status. This monthly look is the same kind of routine as a one-page monthly operations review, and can be a single item in it.
Also count what you caught. The number of problems found before sending is a figure worth reporting: each one is a customer who did not have to ask for a correction.
When the customer finds it anyway
The check reduces mistakes; it does not remove them. When a mistake gets through, correct it quickly, add one line to the complaint log, and ask whether a checklist item would have caught it. If yes, and the mistake could happen again, add the item. If the list grows beyond eight items, remove the one that has found nothing in six months.
Start this week
Take the last five corrections you made for customers and write one checklist item for each. Choose who signs off the most expensive type of output and when. Create the log sheet with its five columns. Use it for the next ten jobs, then review what it found. That small start will show quickly whether the check pays for itself.