Issue Log
An issue log is a project document used to record and monitor all issues — problems, gaps, inconsistencies, or conflicts — that arise during the project and require resolution.
Explanation
The issue log is first created during the Direct and Manage Project Work process and is maintained throughout the project. An issue is a current problem or condition that may impact project objectives, as opposed to a risk, which is an uncertain future event. Issues require attention and resolution, and the issue log provides the structured tracking mechanism.
Each entry in the issue log typically includes a unique identifier, a description of the issue, the date identified, the person who raised it, the assigned owner, the priority, the target resolution date, the current status, and the resolution. Issues may be technical (a component does not meet specifications), organizational (resource conflicts), or interpersonal (stakeholder disagreements).
The project manager is responsible for monitoring the issue log and ensuring that issues are addressed in a timely manner. Unresolved issues can escalate and negatively impact the project. Some issues may lead to change requests if their resolution requires modifications to the project management plan or baselines. The issue log is an input to multiple processes, including Manage Stakeholder Engagement and Monitor and Control Project Work.
Key Points
- •Records current problems requiring resolution, not uncertain future events (those are risks)
- •Created during Direct and Manage Project Work and updated throughout the project
- •Includes ID, description, owner, priority, target date, status, and resolution
- •Unresolved issues may escalate into change requests or risks
Exam Tip
Issues are current problems; risks are uncertain future events. If the exam describes a problem that is happening now, it belongs in the issue log. If it might happen, it belongs in the risk register.
Frequently Asked Questions
Related Topics
Direct and Manage Project Work
Direct and Manage Project Work is the process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project objectives.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Change Requests
A change request is a formal proposal to modify any document, deliverable, or baseline on a project. Change requests include corrective actions, preventive actions, defect repairs, and updates.
Assumption Log
An assumption log is a project document used to record all assumptions and constraints identified throughout the project lifecycle.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Part of
Integration Management
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.