Overview
A lightweight decision log SOP for consultants, covering stages, roles, notes, review rhythm, and workspace ownership. It turns the decision log workflow into a repeatable operating habit without forcing consultants into a heavyweight process.
Page-specific fit
Why this resource exists
SOP audience: independent consultants, fractional operators, advisors, and implementation partners.
Workflow object: decision memory.
Operating cadence: weekly client review with a short post-meeting action capture habit.
Trust signal: follow-up reliability, client status clarity, recommendation traceability, and time spent preparing updates.
Purpose of the SOP
This SOP exists to make decision log work repeatable for consultants. The goal is not to document everything. The goal is to reduce the specific failure mode where decisions are made repeatedly because teams cannot find the rationale, owner, or date of the original choice.
The SOP should help a teammate understand what stage the work is in, who owns the next move, which note explains the context, and when the next review happens.
Roles and ownership
The workspace needs a repeatable client operating layer that preserves context while keeping each engagement easy to brief and hand off. That means every SOP needs clear role boundaries without creating a governance layer nobody wants to maintain.
Use one accountable owner for each active item. Collaborators can contribute, but the workflow should never depend on a vague group owner.
- Workflow owner: maintains stages and review rhythm.
- Card owner: owns the next action and status accuracy.
- Reviewer: approves or requests changes by a visible date.
- Context owner: keeps notes, decisions, and references current.
Procedure
Start with Proposed, Discussing, Decided, Revisit, Archived. These stages are enough to describe the work without turning the board into an admin project.
The SOP should state what must be true before work enters each stage and what must be true before it leaves. If the rule cannot be explained in one sentence, simplify it.
- Proposed: define the owner, input, output, and review signal for this stage.
- Discussing: define the owner, input, output, and review signal for this stage.
- Decided: define the owner, input, output, and review signal for this stage.
- Revisit: define the owner, input, output, and review signal for this stage.
- Archived: define the owner, input, output, and review signal for this stage.
Workspace setup
In Kanvly, the board handles movement and the note layer handles durable context. Decision owner, options considered, rationale, affected work, date, and revisit trigger should be preserved.
For consultants, this is especially useful because client context, recommendations, delivery tasks, meeting notes, and follow-up can scatter across many client spaces. The SOP should tell people where to update status, where to write context, and where to review blockers.
Review and improvement
Review the SOP during weekly client review with a short post-meeting action capture habit. Use the review to inspect stale work, owner gaps, blocked items, and repeated exceptions.
Measure follow-up reliability, client status clarity, recommendation traceability, and time spent preparing updates. If the SOP reduces those issues, keep it. If it creates extra admin without better decisions, shorten it.
- Name the workflow owner.
- Define stage entry and exit rules.
- Clarify one owner per active item.
- Link the notes that explain decisions.
- Set a review cadence and improvement rule.