The Risks and Assumptions column is the fourth column of the logical framework. The assumptions describe the situations, events, conditions or decisions which are necessary for the success of the project, but which are largely or completely beyond the control of the project's management. Risks are events that may have a negative impact on the project.
The fourth column and the first column have an if… then… relation. If the assumptions in column four are met, or if the risks do not occur, then we'll achieve what we've set out to do in column one.
Logframer allows you to use the RAID typology. RAID stands for:
Risks, assumptions, issues and dependencies exist in different parts of the project's time-line:
Use the Details pane to specify whether an item of the fourth column is a risk, an assumption or a dependency. Because issues only occur during the execution phase, you can’t identify an item as an issue in Logframer.
To identify an item as a risk, use the RAID type selector (first field) and select ‘Risk’ from the drop-down list.
Here you can:
The Risk Register is a report that you can either print or export to MS Word or MS Excel. The print version and the MS Word version give you an overview of the risks and what you will do in response; the objectives they may influence and the risk level at the onset of the programme.
You can select if you want to view all risks or the risks of a specific category (operational; financial; objectives; reputation risks)?
If you export the Risk Register to MS Excel, you will get an interactive tool to assess the likelihood and possible impact of each risk over the course of your project. This will allow you to see how each risk evolves over time and what measures you must take to deal with them.
To identify an item as an assumption, use the RAID type selector (first field) and select ‘Assumption’ from the drop-down list.
Here you can:
The Assumptions Table is a report that you can either print or export to MS Word. It provides an overview of the assumptions of each objective.
In print preview, you can select if you want to view all assumptions, or only the assumptions of a certain level (goals, purposes, outputs, activities).
To identify an item as a dependency, use the RAID type selector (first field) and select ‘Dependency’ from the drop-down list.
Here you can:
The Dependencies Table is a report that you can print. It provides an overview of the dependencies of each objective.
In print preview, you can select if you want to view all dependencies, or only the dependencies of a certain level (goals, purposes, outputs, activities).