To define done for a project deliverable, agree on five things before work begins: who will use it, what result it should support, what it must include, who will review it, and how it will be handed off. A finish line should be visible in the work and its handoff, not inferred from the hours spent.
This can fit in a few lines. The goal is to make the next decision easier for the person doing the work, the person accepting it, and the people who depend on it.
A finished file is not the same as a finished handoff
People use the word done for several different states. Separate them before a deadline gets close:
- Prepared: the person doing the work has completed the agreed content and quality checks.
- Ready for review: the work is in the agreed place and the reviewer has the context needed to assess it.
- Accepted: the person with approval authority confirms that it meets the agreed criteria, or identifies what remains open.
- Handed off: the next owner can find the current version, understand its limits, and take the next action.
These states can happen on different days. If a report is complete but a sponsor has not reviewed it, call it ready for review. If a process guide is approved but the team cannot find it, the handoff is still open. Naming the state gives everyone a usable update without pretending the remaining step is complete.
How to define done for a project deliverable
Start with the person who will use the work. Name the decision, task, or understanding the deliverable should support. Then describe the output that will serve that use.
A simple sentence frame is: This [output] is ready for [person or team] to [use or decision] when [observable checks] are met, and [next owner] can find it at [location].
For example, “finish the onboarding guide” is hard to verify. A clearer agreement might say that a new team member can use the guide to locate the first-week schedule, find the right contact for access questions, and follow the approved setup steps. The named reviewer checks the links and confirms the guide is in the team’s shared location. This example is a starting point; the real checks depend on the people and work involved.
That sentence also reveals missing authority. If nobody knows who can accept the work, or what result it needs to support, ask before turning a guess into a deadline.
Write five checks you can verify
- Purpose and reader. Who needs this, and what should they be able to do, decide, or understand after receiving it? Avoid criteria like “looks good” unless you also name the audience and the observable standard.
- Required contents and boundaries. List the information, sections, files, or decisions that must be present. State important exclusions too. A short guide may need the approved steps and an owner for questions; it may not include a full policy history.
- Evidence and quality checks. Decide what needs to be checked before review: source facts, calculations, links, version, spelling, legibility, or another standard that matters for this work. Choose checks that can actually be observed. Do not add a review ritual that does not reduce a real risk.
- Reviewer and acceptance. Name who can accept the deliverable and what they are checking. A contributor can provide useful feedback without holding final approval. If review time affects the schedule, agree on a date or response window rather than assuming an approval will arrive.
- Handoff and next action. Say where the current version will live, who receives it, and what happens next. If another person needs to maintain it, name that owner. Include an open issue or known limitation when it affects use.
Keep the checks proportional to the work. A one-page internal note does not need the same approval path as a public launch or a change that affects customer commitments. The test is whether another person can assess the result without reconstructing the agreement from memory.
Keep acceptance criteria specific to the work
A team may already have shared quality standards, such as checking sources or storing approved files in a known place. Keep those baseline standards, then add the checks that apply to this particular output. A broadly reusable checklist cannot tell you whether this report answers this reader’s question.
Project acceptance guidance from Ohio’s Office of Budget and Management describes criteria from the user’s point of view and includes the deliverable, measures, format, quality review, and acceptance process. Use the parts that fit the work; the purpose is to make acceptance clear before delivery, not to create paperwork for its own sake. Read the Ohio acceptance criteria guidance.
If your team uses the phrase “Definition of Done,” preserve its shared standard and still write item-specific acceptance checks. Scrum.org’s Definition of Done explainer describes a shared quality baseline for a product increment. The useful distinction is simple: the baseline covers work in general; the acceptance criteria explain whether this deliverable meets its agreed use.
Use a short completion brief
Write the agreement where the work already lives. A small brief can use these lines:
- Deliverable and intended user: What is being made, and who needs it?
- Purpose: What should the user be able to do or decide?
- Must include: What content or evidence is required?
- Acceptance check: What can the reviewer verify?
- Reviewer and date: Who accepts it, and when is review needed?
- Handoff: Where is the approved version, who owns it next, and what remains open?
For a short equipment-return guide, the acceptance check might be that the intended team can identify the return location, the required record, and the person to contact when an item is missing. The reviewer can test those three points against the current process. If the actual process is unclear, the guide is not ready to promise a finish date; the missing decision needs an owner first.
When a check fails, make the choice visible
If a review finds a missing requirement, separate a correction from a new request. A correction brings the work back to the agreement. A new audience, extra deliverable, or different outcome may change scope, timing, or ownership. State the difference and ask the authorized person which version to complete.
When feedback points in opposite directions, summarize the shared goal and the actual tradeoff before editing. The Journal’s decision test for conflicting project feedback offers a way to separate constraints, evidence, preferences, and scope changes. The point is to get a decision the people doing the work can carry out.
Use status words that match the evidence. “Draft complete, review pending” is clearer than “done” when approval is still required. If the expected outcome no longer fits, take that change to the person with authority rather than quietly expanding the assignment.
Close the handoff with a clean record
At delivery, include the current version, its location, the reviewer or acceptance status, any known limit, and the next owner or action. A reader should not need to search several messages to learn which file is current or whether it is approved.
If you are joining work already in motion, the Journal’s project takeover checklist can help you confirm which outputs are accepted and who owns the next decision. For more practical work frameworks, visit The Self Made Journal.
A clear finish line protects the work from endless polishing and from premature closure. If you want an everyday tee built around discipline and repetition, see the Forged in Repetition Tee. The live product page has its current details and size chart.
0 comments