Direct answer

Tell them, in writing, and fix what was actually wrong. Silence is the expensive option.

You were looking back at a finished job and there it is: a real mistake, sitting in work the client accepted and paid for months ago. Nobody has noticed. The temptation to leave it buried is strong, and it is almost always the wrong economics as well as the wrong instinct. If the client finds it first, the question stops being about the mistake and becomes about why you stayed quiet. If you bring it, with the fix attached, the same fact becomes proof you can be trusted with the next job. This page gives you the order: judge the mistake against the brief and the accepted record before you say anything, disclose it in one specific written message, fix genuine defects free as a separate recorded stage, and close the loop with the check that would have caught it.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 15, 2026. First published November 15, 2026. The records quoted below are real and public, read back from the live service on November 15, 2026.

Step 1. Judge the mistake against what was agreed, before you judge yourself

Not everything you would do differently today is a mistake. Sort what you found into three piles against the brief as it stood at delivery. Pile one, a defect: the work was wrong against the agreed spec, the source, or plain accuracy at the time it was delivered. A wrong figure, a broken link in a delivered file, a section that answers a different question than the brief asked. Pile one is yours, and it is the subject of this page. Pile two, a later change: the work was right when delivered and the world moved, a price changed, a rule changed, a name changed. That is maintenance, not a mistake, and it is priced like any new work. Pile three, taste with hindsight: you are better now and would phrase or structure it differently. That is not a mistake at all, and disclosing it as one confuses the client and devalues the original work. Write the sort down for the exact item, with the brief line it fails. If it is not pile one, this page is finished for you, and that is a real outcome, not a dodge.

Step 2. Tell them promptly, in one written message that carries the whole fact

Once it is pile one, do not wait for a natural moment, because every week of delay after you knew reads worse than the mistake itself. The message needs five things, in plain order. What the mistake is, named exactly, not softened into a possible issue. Where it sits, the file, page, or step, so the client can see it in seconds. What effect it has, honestly sized: what a reader or user would take from it as it stands. How you found it, briefly, because reviewing your own finished work is itself a good signal. And what you will do: the fix, free, by a stated date, delivered for their acceptance like any other stage. One message, no drip of follow-ups, no confession language that makes a small defect sound like a collapse. Clients absorb a specific disclosure with a fix attached remarkably calmly. What unsettles them is vagueness, because vagueness leaves the size of the problem to their imagination.

Step 3. Check the disclosure against the accepted record, so the scope of the fix is factual

Months later, memory inflates both ways: you remember the job as worse than it was, the client may remember promises that were never in the brief. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the decision layer to measure the old job against:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the accepted record as your template for the old job: which steps were delivered, which were checked, and the dated decision the client made over exactly that set. The mistake belongs to one named step on that record, and the fix is scoped to that step, not to a free reopening of the whole project. The pending record shows the opposite state to avoid in the fix itself: work checked, no decision recorded. A correction that drifts in without its own acceptance becomes the next argument about what was changed and when. Deliver the fix the way the original should close: a named stage, a stated change, and the client accepting the corrected version on the record.

Step 4. Fix it free, narrowly, and deliver the corrected version as its own stage

A defect against the agreed work is fixed at your cost. That is not generosity, it is the original bargain completing itself: the client paid for work that matched the brief, and pile one, by definition, did not. Keep the fix narrow and exact. Correct the mistake, check the immediate neighbours of the mistake for the same failure, and stop there. Improvements you spot along the way are a separate, priced conversation, offered plainly as such, never smuggled into the free fix and never used to dilute it. Deliver the corrected version as its own stage with a one line change note: what changed, where, and that nothing else was touched. Then get the corrected version accepted, so the record now holds both truths at once: the original delivery as it was, and the correction as its own dated event. That pair is worth more than a quiet overwrite, which destroys the evidence that you handled it well.

Step 5. Close with the check that would have caught it

The last step is for you, and a short version of it belongs in the closing message too. Name the check that would have caught this mistake before delivery: a source re-read, a figure recomputed from its inputs, a second pass on the exact step type that failed. Add that check to the way the next job runs, at the step, not as a general promise to be more careful. Telling the client the specific check you have added does two things. It converts an apology into a system change they can picture, and it gives you the honest line for the next sale: my work carries a record, my mistakes get found, disclosed, and fixed on that record. Freelancers lose clients over hidden mistakes and keep them over disclosed ones, because every client has been burned by the first kind and remembers the second kind when the next job is assigned.

What this page cannot settle

This page cannot decide your legal exposure if a mistake caused a client a serious, quantifiable loss; that turns on your agreement, the facts, and local law, and it deserves proper advice before any admission is framed, which is general information, not legal advice. It also cannot promise the client will react well: a disclosure can still cost a relationship where trust was already thin, and that risk is real even when disclosure is right. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the work was correct, which is exactly why the human check in step 5 matters. What the record settles is the factual frame: what was delivered, what was accepted, and what the correction changed, each on its own date.

Frequently asked questions

I found a mistake in work my client accepted months ago. Should I tell them and fix it free?

Yes, if the item was wrong against the brief or the facts at the time it was delivered. Judge it first against the agreement as it stood: a defect is yours, a later change in the world is maintenance, and something you would merely phrase better today is not a mistake at all. For a genuine defect, tell the client promptly in one written message that names the exact mistake, where it sits, what effect it has, how you found it, and the fix you will deliver free by a stated date. Fix it narrowly, correct the item and check its immediate neighbours, and deliver the corrected version as its own stage for the client to accept, so the record holds the original and the correction as separate dated events. Acceptance months ago does not convert a defect into the client's problem: they accepted work presented as matching the brief, and the honest reading of that bargain is that a proven mismatch gets corrected at your cost, whenever it surfaces.

The client accepted the work. Does acceptance not close the matter?

Acceptance closes the decision, not the facts. The client accepted the work as presented, on the understanding that it matched the brief; a defect neither side could see at the time was not knowingly accepted, which is why honest practice treats a proven defect as still yours after acceptance. That has limits, and naming them keeps the position credible: acceptance does close taste, scope, and direction questions, and later changes in the client's world are new work, not corrections. The line is the brief as it stood at delivery. Wrong against it, fix it free. Right against it and merely overtaken or regretted, price it as the new work it is. A delivery record helps because both sides can point at the same steps and the same dated acceptance instead of arguing from different memories of what was agreed.

What if the mistake is small and the client will probably never notice?

Small and unnoticed is exactly the case where disclosure pays best, because the cost of fixing is tiny and the trust bought is large. The client learns, from you and on your initiative, that finished work gets rechecked and that bad news travels fast in your practice. Compare the alternative honestly: the saving is one short fix, and the risk is that they find it during their own review, an audit, or a handover to someone new, at which point a small defect becomes a story about concealment that attaches to every other job you did for them. Size the disclosure to the mistake: a two line note and the corrected file for a small item, not a ceremony. Proportionate honesty is a habit clients can feel, and it is remembered at exactly the moment budgets are assigned.

Should I fix it silently without telling them?

No, for two practical reasons beyond the principle. First, a silent change desyncs every copy and record the client holds: their accepted version and your corrected version now differ with no dated event explaining why, and the first person to compare them finds a discrepancy that looks worse than the original mistake. Second, you lose the entire value of having found it. A disclosed correction is evidence about your practice that the client can repeat to the person who approves your next invoice. Deliver the fix as its own stage instead: change note stating what changed and where, corrected version, client acceptance on the record. The paperwork takes minutes and converts a quiet edit into a documented act of care.

How does a job record help when a mistake surfaces months later?

It keeps the original bargain inspectable. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, the client accepts on that record, and the acceptance view shows status, decider, date, and release state, so a late found mistake can be pinned to one named step, judged against the brief that step served, and corrected as a new dated stage without reopening the whole project from memory. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next client job on one record, so a mistake found months later is a step you can point to and a correction you can prove, not an argument about what was delivered: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related