The Daily Log is a fundamental management product within PRINCE2 7 that serves as an informal repository for recording and tracking various project information that does not warrant formal documentation in other registers or logs. It functions as a practical tool for the Project Manager to capture …The Daily Log is a fundamental management product within PRINCE2 7 that serves as an informal repository for recording and tracking various project information that does not warrant formal documentation in other registers or logs. It functions as a practical tool for the Project Manager to capture day-to-day events, actions, and information throughout the project lifecycle.
Within the Progress Practice, the Daily Log plays a crucial role in supporting effective project monitoring and control. It provides a flexible mechanism for the Project Manager to document informal issues, required actions, significant events, and comments that arise during project execution. This information helps maintain awareness of project activities and supports decision-making processes.
The Daily Log typically contains entries related to informal discussions, minor problems encountered, actions agreed upon during meetings, and general observations about project progress. Unlike formal registers such as the Issue Register or Risk Register, the Daily Log does not require structured approval processes, making it an efficient tool for capturing information quickly.
Key characteristics of the Daily Log include its informal nature, continuous maintenance throughout the project, and its role as a memory aid for the Project Manager. It helps ensure that important details are not forgotten and can be referenced when needed. The log may also capture information that could potentially escalate to formal issues or risks if circumstances change.
In terms of progress monitoring, the Daily Log supports the Project Manager in tracking day-to-day activities, understanding team dynamics, and identifying patterns that might affect project delivery. It complements more formal reporting mechanisms by providing context and background information that enhances understanding of project status.
The Daily Log is created during the Initiating a Project process and maintained throughout the project until closure, when it is archived along with other project records for future reference and organizational learning.
Daily Log - PRINCE2 Foundation v7 Complete Guide
What is the Daily Log?
The Daily Log is an informal repository used by the Project Manager to record information that does not need to be captured in formal project registers or logs. It serves as a personal notebook or diary for the Project Manager to track day-to-day events, actions, and decisions that occur throughout the project.
Why is the Daily Log Important?
The Daily Log is essential for several reasons:
• Captures informal information: Not everything that happens on a project warrants a formal entry in the Issue Register or Risk Register. The Daily Log provides a place for these smaller items.
• Supports smaller projects: On smaller or less complex projects, the Daily Log can be used instead of maintaining separate formal registers, reducing administrative overhead.
• Creates an audit trail: It provides a record of informal conversations, minor problems, and ad-hoc decisions that might otherwise be forgotten.
• Flexibility: The format is entirely at the discretion of the Project Manager, making it adaptable to different project environments.
How Does the Daily Log Work?
The Daily Log functions as follows:
• Created during Initiating a Project: The Project Manager establishes the Daily Log at the start of the project.
• Maintained throughout: Entries are added continuously as events occur during the project lifecycle.
• Types of entries: The log can contain informal issues, minor risks, notes from conversations, action items, reminders, and any other relevant information.
• Escalation path: If an item in the Daily Log becomes significant enough, it can be transferred to the appropriate formal register (Issue Register, Risk Register, or Lessons Log).
• Owned by the Project Manager: Unlike other registers that may involve multiple stakeholders, the Daily Log is solely managed by the Project Manager.
Key Characteristics to Remember:
• It is informal in nature • It is a repository rather than a formal management product • It belongs to the Project Manager • It can be used to reduce formality on smaller projects • Items can be promoted to formal registers when necessary
Exam Tips: Answering Questions on Daily Log
1. Remember the owner: The Daily Log is always owned and maintained by the Project Manager. If a question asks who is responsible for this log, the answer is the Project Manager.
2. Focus on informality: When questions describe scenarios involving minor problems, informal notes, or day-to-day tracking, think Daily Log. Formal issues go to the Issue Register.
3. Think small projects: Questions about tailoring PRINCE2 for smaller projects often reference using the Daily Log as an alternative to multiple formal registers.
4. Distinguish from other logs: Know the difference between the Daily Log (informal, personal to PM), Issue Register (formal issues), Risk Register (formal risks), and Lessons Log (lessons learned).
5. Watch for escalation scenarios: If a question describes a minor item becoming more significant, the correct approach is often to transfer it from the Daily Log to the appropriate formal register.
6. Creation timing: Remember that the Daily Log is created during the Initiating a Project process, not during Starting Up a Project.
7. Format flexibility: Questions might test whether you understand that the Daily Log has no prescribed format - it is whatever works best for the Project Manager.