Software & SaaS

Designing a weekly progress check-in template

A weekly check-in works when it is short, repeatable and tied to decisions. This guide walks through building one template, using a worked example, that individuals, teams or coaches can adapt without extra tooling.

Step one: choose what counts as progress — AddProgressA useful path from inputto understanding

01

Step one: choose what counts as progress

Start by naming two or three measures that matter for the period. Vague targets like get fitter produce vague updates, so convert them into countable or observable items. Worked example: a student preparing for a certification exam sets three measures: practice questions completed, topics reviewed and one mock test score. Each measure has a weekly target, such as sixty questions and two topics. Limiting the list keeps the check-in under five minutes. If a measure cannot be updated from memory or a quick note, replace it with something simpler, because friction at this stage is why most check-ins quietly stop.

Step two: add fixed prompts and a time — AddProgressPeople connected by aclear purpose

02

Step two: add fixed prompts and a time

Pick one day and a consistent window, then write the same prompts every week. A useful set has four lines: what moved, what stalled, what changed in the plan and what the next step is. In the exam example, the student records sixty-five questions done, a weak area in networking topics, a decision to swap one review session for practice and a next step of scheduling the mock test. Keep each answer to a sentence or two. Fixed prompts make entries comparable across weeks, so patterns appear without extra analysis or special formatting.

Step three: review the trend and decide — AddProgressPeople connected by aclear purpose

03

Step three: review the trend and decide

A check-in only matters if it changes something. After each entry, spend a minute comparing against the last three weeks and choose one adjustment: keep, increase, reduce or drop a target. In the example, three weeks of low scores in networking leads the student to shift ten questions per week into that topic and move the mock test later. Record the decision beside the entry so the reason survives. If a coach or teammate is involved, share the entry before the next conversation, letting the meeting focus on the decision rather than reporting numbers.

Build brief

Explore AddProgress

Held for potential development. Acquisition inquiries may be considered.

Domain options ↗