---
title: "The consulting decision log: stop reopening the same conversation"
description: "A decision-log template that captures the why, the owner, and what would make a decision worth revisiting."
canonical: "https://tamloot.cc/en/blog/consulting-decision-log"
---

# The consulting decision log: stop reopening the same conversation

A decision-log template that captures the why, the owner, and what would make a decision worth revisiting.

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

![Paper cards connected by a pencil line beside an open notebook.](https://tamloot.cc/images/blog/consulting.webp)

## The short answer

A consulting decision log records the decision, date, owner, rationale, dependencies, and review trigger. Keep proposals separate from approved decisions so a summary does not accidentally become authorization.

“We already decided that.”

“Did we? I thought we were still exploring it.”

There goes the first part of another project conversation. A decision log cannot make people agree, but it can make the state of the discussion visible.

## What belongs in a consulting decision log?

A decision log is a short record of what was decided and why. It complements the full conversation notes rather than replacing them.

| Field | What to capture |
|---|---|
| Decision | One sentence describing the choice |
| Status | Proposed, approved, superseded, or withdrawn |
| Date and source | When it happened and the relevant conversation |
| Decision owner | Who has authority to approve it |
| Rationale | Why this option was selected |
| Dependencies | What must be true for it to work |
| Review trigger | What would justify reopening it |
| Next step | Who does what next, and by when if agreed |

An action owner and a decision owner may be different people. Writing someone's name beside a task does not establish their authority to approve the project change.

## A fictional example: one workflow, two interpretations

A consulting team discusses piloting a new intake process with one department. One stakeholder hears “approved rollout.” Another hears “interesting idea.”

The log should say “Proposed: pilot with one department, pending operations lead approval,” until that approval exists. When approved, add the date and source. If scope later changes, create a new entry that supersedes the old one.

Useful rationale might be “limit disruption while testing the handoff.” A useful review trigger might be “revisit after the first pilot review, or if staffing assumptions change.” Both explain more than a lonely checkbox.

## Close the conversation with a read-back

Before everyone leaves, read back the proposed decisions and open items. Ask who can confirm each one and what remains pending. Capture corrections in the record.

Send the appropriate summary through the agreed channel, with sensitive material removed where necessary. Do not assume everyone attending a conversation should receive every underlying note.

## Turn the log into preparation

Before the next project conversation, review only the decisions affected by the agenda. Check dependencies and upcoming review triggers. The question becomes “has the staffing assumption changed?” rather than “can someone remind me why we chose this?”

For recurring goals alongside decisions, use the [progress-tracking template](https://tamloot.cc/en/blog/how-to-track-progress-across-recurring-sessions).

## Use AI to draft, then verify authority

AI can extract candidate decisions from notes, but a confident sentence is not evidence of approval. Check the speaker, the wording, and the source conversation. Mark anything ambiguous as pending.

Tamloot brings transcripts, summaries, tasks, and preparation into one workflow. A decision log gives that captured context a practical job: helping everyone understand what is settled and what still needs a conversation.

## A few good questions

### How is a decision log different from meeting notes?

Meeting notes preserve the wider discussion. A decision log highlights the choice, its authority, its rationale, and the conditions for revisiting it. Link the log to the source notes.

### What should I do when a decision changes?

Keep the earlier entry, mark it superseded, and add the new decision with its date and rationale. This preserves why the project changed direction.

## 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)