How to build a decision log from a meeting
A decision log records what was chosen and why, so later work does not reopen settled questions without context. It can also show which matters were deferred rather than resolved.
Start with the right material.
- What you provide
- a meeting transcript with proposals and decisions.
- The intended result
- Create a decision log distinguishing accepted choices from unresolved proposals.
How the workflow works.
Identify explicit decisions, record the available rationale and retain alternatives mentioned in the discussion when they explain the choice. Link each entry to its source passage or timestamp where available.
What to check in the result.
Check that the decision maker or group actually approved the outcome. A strong preference, proposed option or unanswered question should not appear as a completed decision.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Decision, Status, Evidence. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.