Direct answer

A warranty should promise the work matched the deal. Not that nothing will ever change.

A one year warranty sounds like a single simple promise, and clients often ask for it as a comfort line without picturing what it would actually pay out on. Left undefined, it can be read later as a year of free changes, free support, and free repairs for damage other people cause. Defined properly, it is a fair and even useful term: for a stated period from acceptance, if the delivered work fails to match what was agreed, you put it right. This page draws that definition line by line: what a warranty should cover, what it should never be stretched to cover, how a claim is made and remedied so both sides know the steps, where the year starts on the record, and how to price the risk when a client wants the period long or the scope wide.

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. Define the warranty as a defect promise, anchored to the agreed work

One sentence does most of the work: during the warranty period, if a deliverable fails to do what the agreement and the accepted record say it should do, you will correct it. Every word earns its place. The standard is the agreed work, not the client's later hopes, not current best practice, not what a competitor shipped last month. The trigger is a failure against that standard, shown concretely, not a feeling that something could be better. And the promise is correction of that deliverable, which bounds the remedy from the start. Write the sentence before you discuss the period at all, because a year of a narrow promise is a modest term, while a year of an undefined one is an open account. Clients who want genuine assurance accept the sentence readily, since a defect promise is what assurance actually means. Resistance to the sentence itself tells you the ask was never really about defects.

Step 2. List what it covers: defects present in the work as delivered

Coverage, stated as a short list both sides can test a claim against. Errors in the delivered work itself: wrong figures, broken functions, files that fail in the form they were delivered. Failures against the written spec or brief, where the deliverable measurably does something other than what was agreed. And defects that were present at delivery but only reasonably discoverable later in normal use, which is the honest reason a period longer than a few weeks exists at all. Each covered item shares one trait: the fault was in the work when it changed hands. A useful test for any claim is to ask where the fault lived on delivery day. If the answer is inside the deliverable, it is a warranty matter. If the answer is in the world around the deliverable, it belongs to step 3, however the claim is phrased.

Step 3. List what it does not cover, or the year fills up with other work

The exclusions are not fine print, they are half the agreement, and a client is better served by seeing them plainly than by discovering them mid claim. Changes and new requirements: anything the client now wants that was not in the agreed work is a new stage, priced as such. Damage and alteration by others: edits by the client's team or another supplier, and breakage caused by those edits, are repairs, not warranty corrections. Outside change: platforms, rules, prices, and third party services that moved after delivery, making formerly correct work stale, are maintenance. Misuse and off-spec use: failures from using the deliverable for something it was not built or agreed for. Outcomes: results in the client's market, sales, traffic, or rankings, which no deliverable can honestly promise. Write the list into the term itself. A warranty with named edges gets claimed against calmly. A warranty without them gets claimed against for everything, once, and argued about for the rest of the relationship.

Step 4. Set the claim steps and the remedy, and start the clock on the acceptance record

A claim should run like a small machine both sides already understand. The client reports the defect in writing, naming the deliverable and the agreed line it fails. You confirm within a stated number of days whether it is a covered defect, judging it against the record, not from memory. Covered defects are corrected within a stated window proportionate to the fault, and the correction is delivered and accepted as its own stage. The remedy is correction of the deliverable; it is not a refund of the whole engagement for one defect, not a penalty, and not an extension of the period for the rest of the work, though the corrected item itself reasonably carries the remainder of its period. The clock question matters as much: the year runs from a date both sides can prove. 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 date a warranty wants:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the accepted record for decided_at: that timestamp, the moment the client accepted this exact set of steps, is the clean start of a warranty year, provable by either side at any point in it. The pending record shows the trap: work checked but never accepted has no agreed start date, and a warranty argued from delivery emails and memory is a dispute waiting for its first claim. Get acceptance recorded, and the period, the covered set, and the clock all hang off the same dated event.

Step 5. Price the period and the breadth, instead of absorbing them silently

A warranty is risk you hold for a year, and risk has a price whether or not it is written down. A narrow defect warranty over a few months on stable deliverables is cheap to give and most professionals include it without a line item. As the asks grow, a year, then broader language, then response times measured in hours, the expected cost stops being trivial: claims handling, context reloading on old work, and the small real chance of an expensive defect all land on you. Price that honestly, either as a visible warranty line in the quote or folded into the rate with the term named, and offer the trade in the open: the narrow standard term included, the extended version available at its price. Clients respect the arithmetic because it proves the promise is real, a thing being underwritten rather than a word being waved. What never works is the silent absorb: a broad year signed at a standard price teaches the client the term is free, and makes resentment of the first legitimate claim under it almost certain.

What this page cannot settle

This page cannot tell you what warranty obligations the law where you work implies regardless of what you sign, or whether a particular clause would hold; consumer facing work and regulated work carry extra rules in many places, and this is general information, not legal advice. It also cannot set the right period for your trade: a year is long for fast moving digital work and short for physical installations, and your own claims history is better evidence than any general page. No work can be honestly offered as certain to perform, and a warranty is a correction promise, not a promise that defects are impossible. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the work was defect free. What the record settles is the start date, the accepted scope, and the correction history the warranty is measured against.

Frequently asked questions

My client wants a one year warranty on my work. What should a warranty cover?

It should cover defects: places where the delivered work fails to match the agreement and the accepted record, where the fault was in the work on the day it was delivered, including faults only reasonably discoverable later in normal use. It should not cover changes and new requirements, damage or edits made by the client or another supplier, outside changes that make correct work stale, misuse, or results in the client's market. Define it in one sentence, defects against the agreed work, corrected by you, then set the machinery: claims in writing naming the deliverable and the line it fails, a stated window for your decision and for the correction, correction as the remedy, and the period running from the recorded acceptance date so the start is provable by both sides. A year of that narrow promise is a reasonable term on stable work. A year of undefined promise is a year of free everything, and the difference is entirely in whether the definition gets written before you sign.

Is one year a normal warranty period for freelance work?

It is at the long end for most knowledge and digital work, where defect windows of thirty to ninety days are common because genuine delivery defects surface fast in normal use, and it is unremarkable in trades where work is seasonal or inspected on a slow cycle. Judge it against discoverability, not habit: how long until a real defect in this deliverable would plausibly show itself to a client using it as intended? A period matched to that answer is assurance. A period far beyond it mostly insures outside change and other people's edits, which are not yours to underwrite free. If the client wants the year anyway, give it on the narrow defect definition and price the extension as its own line. That combination, long period, tight definition, visible price, satisfies the honest version of the ask in almost every case.

What happens if the client claims under the warranty for something that is really a change?

Run the claim through the definition, in writing, without treating the client as an opponent. Name the test: was this fault inside the deliverable on delivery day, measured against the agreed work? If yes, correct it under the warranty and say so plainly. If the item is new scope, an outside change, or damage from later edits, say which exclusion it falls under, quoting the term both sides signed, and in the same message offer the work as a priced stage with a date. Most misdirected claims are honest confusion about what a warranty is, and a clear definition plus an immediate priced door resolves them without heat. The claims that turn into fights are the ones judged from memory under an undefined term, which is why the definition and the acceptance record do the heavy lifting: the argument, when it comes, is about a document, not about character.

Should the warranty restart when a defect is fixed?

For the corrected item, a fair and common shape is that the fix carries the remainder of the original period, with a short minimum window so a correction delivered near the end can still be checked in use. What should not happen is a full restart of the year across the whole engagement for every correction, which converts one defect into a rolling extension that never closes and makes the term unpriceable. State the rule in the warranty itself, one line, before any claim exists: corrections are covered for the balance of the period or a stated number of days, whichever is longer. Also record each correction as its own accepted stage, so the warranty history is a list of dated events either side can read, rather than a growing legend about how many times the work has been back.

How does a job record help run a warranty fairly?

It fixes the three facts every claim is judged on. 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 the warranty clock starts on a provable date, the covered scope is the accepted set of steps, and each correction lands as its own dated stage instead of blurring into the original delivery. 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, deliver your next warranted job on one record, so a claim eleven months later is checked against the accepted work in minutes, not rebuilt from email: 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