DELIVERY CHECKPOINTS
Name the moments that matter in a project
Use milestones to describe a delivery checkpoint, associate the relevant tasks and explicitly record when the checkpoint has been reached.
A checkpoint is a shared decision
A project can contain dozens of tasks while the customer and delivery lead care about a handful of meaningful outcomes. A milestone names one of those outcomes: a reviewed concept, a prepared launch or a completed installation phase. Tsumira gives that checkpoint a record of its own, so its description, date and reached state can be discussed without mistaking every small task for a major delivery event.
Define what the checkpoint means
Create the milestone inside the project with a name, an optional description and a due date where one has been agreed. Associate tasks through their milestone field to make the work behind the checkpoint understandable. The date can also appear with the project timeline milestones, giving the planning conversation a clear named reference rather than an unexplained marker.
- Name and explanatory description
- Optional agreed due date
- Task association within the project
Record reaching it deliberately
A milestone distinguishes upcoming from reached and records the time at which it was marked reached. A permitted colleague performs that transition; the saved revision is checked to avoid overwriting a newer change. Finishing a task and reaching a milestone are distinct actions, so the team can review whether the overall outcome really meets the intended checkpoint.
- Upcoming and reached states
- Recorded reached time
- Explicit action with current-record checks
Connect the conversation and commercial context
A milestone record supports the project communication context, making it possible to discuss the specific checkpoint instead of hiding the decision in an unrelated chat. Supported milestone billing plans can reference milestones, but reaching one does not itself send an invoice. Charge acceptance and financial document creation remain separate steps with their own permissions and review.
- Conversation attached to the checkpoint
- Connection to supported milestone charges
- Separate delivery, charge acceptance and invoicing
A concrete workflow
Define the outcome
Describe the result the team will recognize as this checkpoint and choose a meaningful name.
Connect the work
Assign the relevant project tasks to the milestone and add a realistic due date.
Review the result
Discuss the task outcomes and remaining questions in the milestone or project context.
Mark the checkpoint reached
An authorized colleague records the reached state; any commercial follow-up proceeds through its own workflow.
An illustrative working example
Example: an installation readiness checkpoint
A technical services team defines “Ready for installation” with a description covering the approved site information and prepared materials. The preparation tasks point to that milestone. When the work is reviewed, the project lead records the milestone as reached. If the contract uses a milestone charge, the billing owner separately checks and accepts the charge. Delivery progress and the commercial decision are therefore visible without being conflated.
Questions about this topic
Is a milestone the same as a task?
No. A task describes work to perform. A milestone names a checkpoint that can bring several pieces of work together.
Does completing all tasks automatically reach the milestone?
Do not assume that. Reaching the milestone is an explicit supported action, allowing the responsible team to judge the overall result.
Can a milestone exist before its date is known?
Yes. The due date is optional. Add it when the team has a useful commitment rather than filling in an arbitrary date.
Does reached status automatically invoice the customer?
No. A supported milestone plan may use the milestone as delivery evidence, but charge acceptance and financial documents remain separate controlled actions.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Asana
Workflow concept: Review named checkpoints before mapping them to project milestones.
DocuSign
Workflow concept: Identify reviewed acceptance evidence relevant to a delivery checkpoint.
Google Docs
Workflow concept: Prepare a checked milestone outcome without treating a document draft as acceptance.