How to finish tasks: completion criteria and the final step

Find exactly what remains unfinished

How do you finish tasks when the main work is already done? Often the problem is neither starting nor a lack of motivation. A document is written but not sent; an item is chosen but the order is unconfirmed; a project is ready but a mandatory condition is unchecked. These tasks need different final steps, although they all look the same on a list: ‘almost done’.

Choose one task and ask who or what must confirm its completion. If the answer is ‘I will feel that it is enough’, the boundary is too uncertain. If someone else accepts the result, you need their criteria. For a personal task, record an observable fact: sent, installed, checked, agreement received. This does not make every completion easy, but it shows exactly where progress stopped.

Define completion before making another improvement

A completion criterion answers what must be true at the end. For a report: required data for the selected period, checked calculations, a clear conclusion, and delivery to the recipient. For an application: mandatory fields, attached materials, submission, and confirmation. Attractive formatting may be a requirement or a wish; distinguish the two.

The Scrum Guide uses the Definition of Done to establish a shared understanding of the quality of a completed result in team development. Here we borrow only the idea of explicit conditions; this does not turn a personal list into Scrum. Make the conditions clear in advance and avoid changing them whenever the result is nearly achieved. Otherwise, the latest version will always be insufficient simply because another has been imagined.

Separate four kinds of remaining work

Check the remaining work: is it a required correction, delivery of the result, waiting for a reply, or an additional improvement? You cannot hide a correction in a future version if the result fails requirements without it. Delivery is easy to forget when the main process has already tired you out. Waiting does not end with your own check mark. An improvement can be separated if it does not prevent acceptance of the current result.

This distinction protects against both endless improvement and premature closure. ‘I want one more example’ does not always mean the article is unfinished; ‘the total is unchecked’ may mean it is. The basis is the criterion and consequences, rather than the desire to remove the task from the list quickly.

Example: the report is written, but the task is still open

An illustrative situation: Dasha has written a report but has spent three days changing its formatting. She must give it to her manager by Friday for a decision. She lists the requirements: data for the right month, a checked final table, conclusions on two questions, and a sent file. It turns out there are no special formatting requirements, while one amount remains unchecked.

Dasha stops changing colors, checks the amount, reviews the document against the criteria, and sends it with a short message about the period and conclusions. She saves the additional chart idea separately. If the manager must accept the report, ‘obtain acceptance’ remains open until the reply. If the original task was only to send it, it is complete after delivery. The distinction depends on the promised result, rather than a desire to close the whole project with one mark.

Make the final step executable

‘Finish the project’ is still too broad. Replace it with a precise action: check two points, assemble final files, send a link, confirm delivery. Prepare the required information before the work block. If you need someone else’s reply, send a specific question stating exactly what is being checked and when the answer is needed.

For a handoff, specify the version, location of the result, and what you need from the recipient. ‘I have done everything’ often creates new uncertainty: where is the file, which version is final, and is a reply needed? A good handoff saves another round of clarification. But do not invent an elaborate ritual for a household task. Confirming an appointment or putting away tools after a repair may be a sufficient final step.

When an honest cancellation is better

Not every old commitment needs to reach its original form. If the goal has disappeared, conditions changed, or another route was chosen, cancellation may be needed instead of completion. Check the consequences: who expects the result, which materials are needed later, and what must be communicated. Quietly forgetting leaves uncertainty for you and others.

For example, an obsolete home project can be closed with ‘abandoned; materials put away’. A work agreement cannot simply disappear from the list: first agree on cancellation or handoff. Leave a short reason and the next responsible action, if any. Attention is then freed through a real decision, rather than a hidden promise to return someday.

A checklist for closing one task

Apply the list to a result that is actually ready for completion. If the main work is still ahead, you first need an execution plan. This checks the final part, so the checklist is short. In Sinqly, you can make the specific finishing step a task and mark the original work complete only after its conditions are met.

• The promised result is recorded in one sentence.
• Mandatory conditions are known and kept separate from new wishes.
• Remaining corrections are completed and checked.
• The final version is in a clear location.
• The result has been delivered to the person expecting it.
• Waiting for a reply is explicit if it forms part of the commitment.
• New improvements have been separated or declined.
• The decision to complete or cancel is recorded.

If the list reveals several more hours of work, do not call that a small loose end. Review the estimate and deadline. This is an important result of the check: you now know exactly what is unfinished, rather than merely retaining a sense of endless incompletion.

Mistakes that keep work open

Common mistakes are raising the standard near the finish, forgetting delivery, treating your own completed work as an accepted result, and starting the next version before closing the required one. Another is choosing ‘never return to it’ as a criterion. Some results naturally require maintenance; that is separate future work, rather than proof that completion is impossible now.

Difficulty starting and maintaining progress toward a large goal require other solutions. The practical outcome here is more specific: choose one nearly finished task, name the closing condition, and perform the last step without adding a new version on top of the old one. After completion, decide separately whether a next version is needed at all. Closed work does not forbid future improvements; it makes them a new, deliberate choice.

Sources

• Scrum Guides: the official Scrum Guide 2020

Frequently asked questions