Guidelines For Completing The Issue Log
Guidelines For Completing The Issue Log
Issue #: Assign a unique number to each issue sequentially. This helps keep track of the order in which
issues arise.
Issue Description: Provide a clear, concise description of the issue. Focus on what the issue is, how it
affects the project, or any specific details that are relevant to understanding the problem.
Impact on Project: Describe how the issue affects the project. This might include delays, additional
costs, resource constraints, or impact on project quality.
Date Reported: Indicate the date when the issue was first reported.
Reported By: Enter the name of the person who reported the issue.
Assigned To: Specify the person or team responsible for resolving the issue.
M (Medium) for issues that should be resolved soon but are not critical, or
Due Date: Set a target date by which the issue should be resolved.
Status: Indicate the current status of the issue, such as “Open,” “In Progress,” “Resolved,” or “Closed.”
Comments: Add any additional information or context, including updates on progress, changes in
impact, or decisions made.
Sample Entry
Supplier
Project
Delay in informed;
timeline 2023-09- 2023- In
1 resource A. Smith Logistics H tracking
may extend 01 09-05 Progress
delivery expedited
by 1 week
order.
Issue Issue Impact on Date Reported Assigned Priority Due
Status Comments
# Description Project Reported By To (M/H/L) Date
Potential
Reviewing
Limited resource
2023-09- 2023- schedules to
3 availability constraints C. Tanaka HR L Open
04 09-15 find additional
of personnel for next
support.
phase