---
title: "How to track progress across sessions: a simple working template"
description: "Keep goals, experiments, outcomes, and changing priorities in one dated view, without turning people into scores."
canonical: "https://tamloot.cc/en/blog/how-to-track-progress-across-recurring-sessions"
---

# How to track progress across sessions: a simple working template

Keep goals, experiments, outcomes, and changing priorities in one dated view, without turning people into scores.

Tamloot Editorial | Published: 2026-02-15 | Updated: 2026-10-16

![A winding path of colorful stepping stones beside a notebook.](https://tamloot.cc/images/blog/coaching.webp)

## The short answer

Agree on what progress would look like, record a starting point, and review dated examples together. Track changed goals and blocked actions as well as completed ones.

“Things are better” can be true and still leave you wondering what actually changed. A lightweight progress record gives that conversation something concrete to stand on.

The useful unit is not a score you invent about someone. It is an agreed goal, an observable experiment, and a dated account of what happened.

## Agree on the destination in ordinary language

Ask what the person wants to be different. Replace a broad phrase such as “better communication” with an example they would recognize: “raise a concern before the deadline, rather than after it.”

Write the person's definition down. If your setting uses formal outcome measures, follow that process; this working template does not replace it.

## Copy this progress table

| Field | What to record |
|---|---|
| Goal | The change the person wants |
| Starting point | A dated example of the current situation |
| Experiment | One agreed action or question to explore |
| Result | What happened, in the person's account |
| Next review | When you will return to it |
| Status | Active, revised, paused, or complete |

Keep the table with the relevant session history. A coach may track a leadership experiment. A consultant may track a new handoff process. An advisor may track whether an agreed document was provided. Use a separate row for each distinct goal.

## A fictional example

A coaching goal is “delegate one recurring task with a clear handoff.” The starting point is that the person currently does it themselves. The experiment is one handoff with written success criteria. At the next review, they report that the task moved, but follow-up questions still came back to them.

That is useful information. It is not a failed person or a successful percentage. The next conversation can explore which criteria were missing.

## Make room for a changed goal

A goal can stop being relevant. Mark it revised or paused and record why, rather than silently deleting it or counting it as a failure.

Likewise, distinguish “not attempted,” “attempted and blocked,” and “attempted with a mixed result.” Those lead to different questions. Keep uncertainty visible when the source note is incomplete.

## Use the history to prepare a question

Before the next conversation, review the active rows and choose one question. “What happened when you tried the handoff?” is more useful than “How is everything?” when that experiment was the agreement.

Tamloot helps keep session notes, tasks, and preparation connected. You can use the same routine with a document or notebook. Start with the method, then choose the tool that makes it easy to maintain.

For a ready-made session structure, try the [coaching notes template](https://tamloot.cc/en/blog/coaching-session-notes-template).

## A few good questions

### What if the goal changes between sessions?

Keep the earlier goal with a revised or paused status, note the reason, and create a dated version of the new goal. This preserves the history without treating a change of direction as failure.

## Where to look next

- [Home](https://tamloot.cc/en)
- [Pricing](https://tamloot.cc/en/pricing) — also as markdown at [/pricing.md](https://tamloot.cc/pricing.md)
- [Documentation](https://tamloot.cc/en/docs)
- [Journal](https://tamloot.cc/en/blog)
- [Developer resources](https://tamloot.cc/en/developers)
- [Public API documentation](https://tamloot.cc/en/docs/api)
- [MCP server setup](https://tamloot.cc/en/docs/mcp-server)
- [Agent auth guide](https://tamloot.cc/auth.md)
- [llms.txt](https://tamloot.cc/llms.txt)
- [OpenAPI description](https://tamloot.cc/openapi.json)
- [API catalog](https://tamloot.cc/.well-known/api-catalog)
- [Sitemap](https://tamloot.cc/sitemaps/sitemap.xml)