Many office tasks start with a verb and end with an argument. “Prepare the report.” “Update the deck.” “Review the proposal.” “Get the client file ready.” Everyone understands the words, but not necessarily the finish line. One person thinks the report is done when the analysis is complete. Another expects an executive summary, checked figures, approved formatting and a PDF ready to send. The gap often appears only near the deadline, when changing the work is most expensive.
A simple definition of done prevents that problem. Before you begin, write a short statement describing the observable conditions that must be true for the task to be considered complete. For ordinary office work, a useful definition of done may be three to seven checks that clarify the output, quality level, approval state and handoff.
Why “done” is often more ambiguous than it sounds
Work requests usually describe activity rather than completion. “Research three vendors” tells you what to do, but not whether the final output should be raw notes, a comparison table or a recommendation. “Update the budget” may mean replacing the latest figures, checking formulas, getting Finance approval and circulating the final version—or only the first of those steps.
This ambiguity creates two common failures: stopping before the recipient has something usable, or polishing beyond what the task requires. Both waste time.
A definition of done gives the task a stopping rule. It tells you what must be true before you can close the work, and it also tells you what does not need to be perfected.
Start with the final user of the work
Before listing checks, identify who will use the output and what they need to do with it. A spreadsheet prepared for your own analysis has a different finish line from one going to a director for approval. Meeting notes kept as a personal memory aid have a different standard from minutes that assign actions to six people.
Ask one practical question: “What should the next person be able to do immediately when I finish?” The answer often exposes missing requirements. If the next person must approve the proposal, the proposal needs enough context to make a decision. If they must send it to a customer, it needs final formatting and a recipient-ready version. If they must continue the task, it needs a clear handoff. The principles in how to hand off a task without losing context are useful when completion transfers responsibility to someone else.
Use four dimensions to define completion
Most office tasks can be clarified by checking four dimensions: output, correctness, approval and delivery. You will not need all four every time, but they provide a fast way to find hidden expectations.
1. Output: what exactly exists at the end?
Name the concrete deliverable. Instead of “research suppliers,” define the output as “a one-page comparison of three qualified suppliers with price, lead time, risk and a recommended option.” Instead of “prepare meeting notes,” use “a concise recap containing decisions, action owners and due dates.”
Include the required format only when it matters. A PowerPoint deck, editable spreadsheet, signed PDF and email summary are different outputs. If the recipient needs two of them, say so before work begins.
2. Correctness: what must be checked?
Not every detail carries equal risk. Identify the facts that would make the work unusable if wrong: totals, dates, names, formulas, contractual terms, version numbers or source data. Then define the minimum verification required.
For example: “All totals reconcile to the source sheet; customer names and delivery dates are checked; no unresolved comments remain.” This is more useful than saying “make sure it is accurate.” Before delivery, you can use a short final quality check to verify those conditions without reopening the entire task.
3. Approval: who must accept or decide?
Some work is not complete when the draft is finished. It is complete when the required reviewer has approved it. Other work is complete when you submit it for review because approval belongs to a separate process. Confusing those two states causes tasks to disappear into limbo.
Write the boundary explicitly: “Done when the revised copy is sent to Legal for review” or “Done when Legal approval is received and incorporated.” If several people are involved, clarify the action owner and decision owner. The approach in clarifying ownership on shared work helps prevent a finished draft from becoming an ownerless next step.
4. Delivery: where does the finished work go?
A file sitting on your desktop may be finished technically but unfinished operationally. Define where the final version must live and who needs to receive it. That might mean uploading the approved file to a shared folder, updating the project tracker, sending the link to a manager or replacing an obsolete version.
Include access requirements when relevant. “Final deck saved in the client folder and shared with the account team with working permissions” is a clear finish line. It prevents the familiar situation where the work exists but nobody can find or open it.
Keep the definition short enough to use
A definition of done should reduce friction, not create another document to maintain. For a routine task, three lines may be enough. For a higher-risk deliverable, five to seven checks may be appropriate. If you have twenty-five checks, you are probably writing a procedure or quality-control checklist rather than defining completion.
A practical format is: “This task is done when…” followed by observable conditions. For example: “This task is done when the three vendor quotes are compared using the agreed criteria; the recommended vendor and reason are stated; pricing and delivery dates are verified; the operations manager has approved the recommendation; and the final comparison is saved in the procurement folder.”
Notice that each condition can be answered yes or no. Avoid vague standards such as “looks professional,” “is comprehensive” or “is basically ready.” If a subjective standard matters, make it more observable: “uses the current company template and contains no draft comments” is easier to verify than “looks polished.”
Agree on done before doing more work
If the task came from someone else and the finish line is unclear, confirm it early. You do not need to send a long requirements document. A short recap can be enough: “I’ll treat this as complete when I have updated the Q3 figures, reconciled the totals to Finance, added a three-bullet summary and sent you the PDF for approval. No slide deck needed.”
That sentence does two things. It surfaces mismatched expectations while changes are cheap, and it protects you from expanding the task silently. If the requester adds another requirement, you can incorporate it deliberately rather than discovering it during final review.
Use different finish lines for different stages
Large assignments often have several legitimate “done” states. Research can be done before the recommendation is done. A draft can be done before approval is done. Separating these stages makes progress visible and prevents one enormous task from staying open for weeks.
For example, define “analysis done” as complete source data, checked calculations and documented findings. Define “decision pack done” as a recommendation, key tradeoffs and an approval request. Define “project closed” as approval recorded, final files stored and follow-up actions assigned.
This also improves prioritization. When a large task competes with other work, the 15-3-2-1 method can help identify the most important next result. A clear stage-level definition of done then tells you when that result is genuinely finished.
Watch for scope changes after work starts
A definition of done is a baseline, not a weapon. Requirements can change for good reasons. New data arrives, a customer changes direction or a manager needs a different format. When that happens, update the finish line consciously.
The important distinction is between a changed requirement and unnoticed scope growth. If a five-page analysis becomes a fifteen-slide presentation plus a data appendix, acknowledge that the task has changed. Recheck the deadline, priority and ownership rather than pretending the original estimate still applies.
Close the task with a two-minute done check
Before marking the task complete, read the definition once and verify each condition. Do not rely on the feeling that you have worked on it long enough. Check the actual finish line.
If one condition is not met, decide whether the task is still open, the requirement has changed or the missing item belongs to someone else. If another person owns the remaining step, record that dependency instead of mentally treating the work as finished.
This final check should be fast because the important thinking happened at the beginning. You already know what output is required, which facts matter, whose approval counts and where the finished work goes.
A clear finish line makes work easier to start
Defining done is not only about closing tasks correctly. It makes starting easier. Ambiguous work feels larger because your brain has to imagine every possible expectation. A visible finish line turns a vague assignment into a bounded piece of work.
Before your next substantial office task, spend two minutes completing one sentence: “This is done when…” Name the deliverable, the critical checks, the approval boundary and the final handoff. Then work toward those conditions instead of an undefined idea of perfection.
The result is less rework, fewer last-minute surprises and a more defensible stopping point. You know when to keep going, when to ask for clarification and, just as importantly, when the work is complete enough to move on.