Event-Driven Controls

B.

Event-driven controls are a key aspect of PRINCE2 methodology, which is a project management framework used to manage and control projects. These controls are put in place to manage events that may occur during a project's lifecycle, ensuring that project managers are able to react quickly and effectively to keep the project on track.

To answer the question, we need to identify which option is NOT an event-driven control. Let's look at each option in turn:

A. Project mandate: This is not an event-driven control. A project mandate is a document that outlines the reason for a project and what it is trying to achieve. It is typically created before a project is initiated and is used to ensure that everyone involved in the project is clear on its purpose.

B. Checkpoint Report: This is an event-driven control. A checkpoint report is created at the end of each stage of a project to provide an overview of progress and to assess whether the project is still on track. This report can trigger corrective action if necessary.

C. Exception Report: This is an event-driven control. An exception report is created when there is a deviation from the plan, such as a change in scope or an overrun in budget. This report is used to trigger a formal review of the project and to decide whether to continue with the project or to stop it.

D. End of a stage: This is not an event-driven control. The end of a stage is a milestone in the project plan, but it is not a control that is put in place to manage events that may occur during the project.

Therefore, the answer to the question is A. Project mandate, as it is not an event-driven control.