Free Tool

Decision Log

Document team decisions with context, options, rationale, and next steps. Export a clean PDF record to share with stakeholders.

Example

An engineering team documents their CI/CD platform choice.

Decided2026-03-15·Sarah Chen, Tech Lead

Context

Our current Jenkins setup requires constant maintenance and does not support our move to containerized deployments. Build times have increased 40% over the last quarter.

Options Considered

  • GitHub Actions: native integration, marketplace, per-minute billing
  • GitLab CI: built-in registry, self-hosted option, included in license
  • CircleCI: fast builds, good caching, separate vendor

Decision

Migrate to GitHub Actions. Start with non-critical services, complete migration by end of Q2.

Rationale

GitHub Actions integrates directly with our repository workflow, eliminates the maintenance overhead of self-hosted Jenkins, and the per-minute pricing model fits our burst-heavy usage pattern.

Need to decide with your team?

DecTrack helps teams make structured, transparent decisions together, from defining options to reaching consensus.

Frequently Asked Questions

A decision log (also called decision record or decision journal) is a structured document that captures why a decision was made, what alternatives were considered, and what happens next. It creates an audit trail so the team can revisit decisions without relying on memory.
The person who owns the decision or facilitated the discussion. In practice, this is often the project lead, product manager, or tech lead. The important thing is that one person takes responsibility for documenting it while the context is still fresh.
Detailed enough that someone reading it six months later understands why this choice was made. Include the key trade-offs, constraints, and assumptions. Two to four sentences is usually enough.
An Architecture Decision Record (ADR) follows a specific template for technical/architecture choices and lives in the codebase. A Decision Log is broader: it covers any type of team decision (hiring, process changes, vendor choices, strategy) and can be stored anywhere.
At least quarterly, or whenever circumstances change significantly. Review decisions whose assumptions may no longer hold. Mark outdated decisions as deprecated and link to the replacement decision.