Milestone progress log template
By Kivrelune Studio

Milestone progress log
Show which planned outcomes are complete, underway or waiting on another action.
Progress since baseline
Period: [dates]. Milestone: [target result]. Expected by today: [checkpoint]. Achieved: [evidence]. Remaining: [work or decision].
Explain variance
Delay or acceleration: [difference]. Cause within or outside the team: [reason]. Recovery option and cost: [choice].
Next checkpoint
By [date], produce [observable result]. Owner: [person]. If [dependency] is unresolved by [time], ask [decision maker] to choose [options].
Using this template
Compare each milestone's expected checkpoint with the result someone has actually accepted. Explain significant variance, distinguish remaining work from waiting time and define the observable result the team should produce before the next checkpoint.
Questions & answers
Looking for more help? Visit the Help center.
How should we express progress when completed effort is hard to estimate?
Use accepted outputs, completed tests or resolved dependencies as evidence. Describe the remaining checkpoint concretely and name its owner instead of relying on a speculative percentage.
What is included in this template?
Progress since baseline · Explain variance · Next checkpoint. Each section includes prompts you can adapt to your team.
How can the project team keep this current?
Give each open decision an owner and a due date. At the next checkpoint, update the milestone and record the work that changed since the last review.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.
