How to identify risks and blockers in meeting notes
Risks and blockers require different responses: a risk may affect future work, while a blocker is already preventing progress. Extracting them separately helps the team choose a useful next action.
Start with the right material.
- What you provide
- an existing visible project-meeting transcript.
- The intended result
- Extract stated blockers, dependencies and impact without predicting unsupported risks.
How the workflow works.
Record the stated issue, affected work and any owner or mitigation discussed. Preserve uncertainty and distinguish an observed dependency from a speculative concern.
What to check in the result.
Check that the summary does not upgrade every concern into a confirmed problem. If impact, ownership or timing is missing, list it as information to clarify with the team.
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: Blocker, Dependency, Stated impact, Owner. 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.