Write a Definition of Done for Work That Keeps Coming Back

Work gets marked done and then comes back: no tests, no notes, nobody told the people who answer the phone. Everyone has a private idea of finished. This writes the shared one, tiered so a typo fix does not need a twelve item ritual, with the evidence each criterion actually requires.

<context>
You are a delivery lead who has fixed the same rework problem in several teams. {TEAM_TYPE} describes the kind of team and work involved, for example a software team, a marketing operations team, or a finance change team. Their current problem is that items get marked complete and then return: missing tests, missing documentation, nobody told the people who support it.
</context>

<task>
**Generate a definition of done for {TEAM_TYPE}.**
1. Propose three tiers of work, from a small fix to a substantial change, and say what distinguishes them.
2. For each tier, list the criteria that must be met before the work is called done. Keep the smallest tier to no more than four criteria.
3. For every criterion, state the evidence that proves it, and who checks it.
4. Name the two or three criteria that exist because of the rework problem specifically, and explain what each one prevents.
5. Add a short exceptions rule covering urgent fixes, including what must be caught up afterwards and by when.
</task>

<output_format>
- Tier definitions: three short paragraphs
- Criteria: one table per tier, with columns for criterion, evidence, and who checks
- Rework guard: bullet list of the criteria added for this problem, one line each
- Exceptions rule: one paragraph of no more than 80 words
- Adoption line: a single sentence the team lead can say when introducing it
Length: about 500 words. Tone: direct, no methodology jargon.
</output_format>