Issue Log

What is an Issue Log?

An issue log is a project management tool used to document, track, and manage problems that arise during a project. It records issues that could affect project performance, timelines, or outcomes. These issues may include unexpected delays, resource shortages, technical difficulties, or stakeholder concerns. The log clearly records each problem, its impact, the person responsible, and the resolution status. This tool helps teams stay organized, supports accountability, and improves communication by making all known issues visible and traceable.

The project manager typically maintains issue logs and updates them regularly throughout the project life cycle. Depending on the project’s complexity and the team’s preferences, teams may manage the log through spreadsheets, project management software, or collaboration tools.

Key Points

• An issue log lists all current and past problems identified during a project.
• Each entry typically includes a description, date identified, priority, owner, and resolution status.
• It supports problem-solving by assigning accountability and tracking resolution efforts.
• The log helps identify recurring issues and trends that could affect project delivery.
• Keeping an up-to-date log improves transparency and helps manage stakeholder expectations.

Related Terms

• A risk register documents potential future problems, whereas an issue log tracks problems that have already occurred.
• A project status report often includes a summary of open issues from the issue log to update stakeholders.
• A change log may be used alongside an issue log when resolving problems resulting in project scope, schedule, or resource changes.
• The responsibility assignment matrix can help determine who should be assigned to resolve each entry in the log.
• Referencing project documentation provides context for analyzing entries in the log.

Issue Log: Example

A software development team encounters a testing delay due to a missing quality assurance resource. The project manager logs the issue, notes its high priority, assigns it to the resource manager, and records the discovery date. Two days later, a backup tester resolves the issue. The team updates the log to reflect the resolution and closes the entry.

Issue Log: Best Practices

• Record issues as soon as the team identify them to avoid overlooking problems.
• Assign clear ownership to ensure accountability for resolution.
• Prioritize issues based on their potential impact on project goals.
• Update the log consistently to maintain accuracy and relevance.
• Review the log regularly in team meetings to monitor progress and support timely decisions.

Additional Resources

Preparing for a PMI certification?

• Exam Prep Courses: PMP^®, CAPM^®, and PMI-ACP^®
• Exam Simulators: PMP^®, CAPM^®, PMI-ACP^®, PMI-PBA^®, PMI-RMP^®, PMI-SP^®, PgMP^®, and PfMP^®
• Professional Development Units (PDUs): 15, 30, and 60 PDU Bundles