# Definition of done

> A definition of done is a signed list, agreed before work starts, of exactly what has to be true for a job to count as finished. If every item is met, the job is done. If not, it is not.

- URL: https://radkod.com/en/glossary/definition-of-done
- Publisher: RadKod
- Published: 2026-07-28

## What is a definition of done?

A definition of done is a list of the conditions under which a software job is finished. Each item is written so it can be checked: which pages exist, which connections work, which date it ships. Both sides sign it before work begins.

Here is an everyday case. You are having a website built. The list includes items such as "contact form messages reach the sales inbox" and "old URLs redirect to the new ones". On delivery day each item is tested. If all pass, the job is done. If one fails, it is not. There is no percentage in between.

## Why does it matter?

Software projects often stall because nobody ever defined what finished means. A definition of done removes "almost done" as an answer, and both sides know what to expect. We explain how we write one in [definition of done: why we write it on day one](/en/blog/definition-of-done). How to check quotes for one is covered in [how to compare software quotes](/en/blog/compare-software-quotes).

## Frequently asked questions

### What goes into a definition of done?

The pages or screens to deliver, the connections that must work, acceptance tests and the delivery date. Each item is written so it can be checked yes or no. What is out of scope is stated too.

### Is a definition of done the same as a quote?

No. A quote gives the price and general scope. A definition of done lists exactly when the work counts as finished. We sign both on day one, before work starts.

### What happens if a new request comes up mid-project?

It is not quietly added to the list. It is discussed, sized and priced, and added only once approved. That keeps the original delivery date clear.