Logs and registers
The six records the project keeps to track risks, issues, quality, products, lessons and day-to-day notes.
Scene 1
Logs and registers
The six records the project keeps to track risks, issues, quality, products, lessons and day-to-day notes.
Caption 1 of 3
Name the PRINCE2 logs and registers
Read all scene text
- Name the PRINCE2 logs and registers
- Describe what each one records
- Explain when each is created
Scenes animate with GSAP. Use pause or replay at any time.
In this session
- Name the PRINCE2 logs and registers
- Describe what each one records
- Explain when each is created
It's time to look at where the York project keeps its records.
Let's say a new project assurance reviewer joins in Stage 3 and asks, "Where can I see what's happened so far?" Ellie opens one folder with six files. Within half an hour, the reviewer knows the project's story.
What's in the folder?
Select the arrow to learn more
1 of 4
What might happen
The risk register lists every risk, from the damp (now closed) to the coffee chain (still open).
The six logs and registers
Each one has a different job:
- Daily log: the project manager's informal diary of notes, actions and informal issues
- Lessons log: lessons from previous projects and from this one
- Issue register: formal issues and their status
- Risk register: identified risks, their assessment and responses
- Quality register: planned and completed quality activities
- Product register: products, their versions and status
When they're created
The daily log and lessons log are created in starting up a project, because they're needed right from the beginning.
The issue, risk, quality and product registers are created in initiating a project, alongside the management approaches that describe how they'll be used.
Who keeps them
The project manager is responsible for the logs and registers, but project support usually keeps them up to date. Ellie updates the York registers after each meeting and each quality check.
Team managers and the board feed information in, and project assurance reviews them to check the project is being managed properly.
Keep them simple
York's logs and registers are tabs in one spreadsheet. The app team keeps its risks and issues in the same tool they use for the backlog.
What matters isn't the tool, but that the information is current, easy to find and used to make decisions.
Key points to remember
- PRINCE2 uses six logs and registers to track the project.
- The daily log and lessons log are created in starting up a project.
- The issue, risk, quality and product registers are created in initiation.
- Project support usually maintains them on behalf of the project manager.
Knowledge check
Choose one answer
Practices
In which process is the lessons log created?
Sign in to save your result. Knowledge checks can be retried any time.
PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.