Project issues log www.techrepublic.
com
Keep track of your problems with this project
issues log
It’s rare that an IT project is completed without any problems happening along the way. That’s why it’s so
important to make sure you document your project issues so that they don’t derail your goals. Use this
project issues log to summarize all of the issues that occur during your project. With this document, you
can view open issues and make sure that a resolution is forthcoming.
To help you understand how this log works, we’ve provided three sample issues for a ghost project. As
you will see, the log should contain enough information to ensure that issues are not overlooked, but it
should not be so detailed that scanning the document for trouble spots is difficult. To maintain this
readability, make sure that the information can fit across a single sheet of paper (either vertically or
horizontally) or can be displayed in a single window. Each problem should be represented on one line of
the issues log.
Directions for using the project issues log
1. Document an issue, including any pertinent details such as the date and who reported it.
2. Determine a priority for the issue. Label it as high, medium, or low.
3. Assign the issue to a project team member. The issue can be scheduled for resolution to better
manage the team member’s time and effort.
4. Track the status of the resolution. Label it as open, in progress, or closed.
5. Document the process by which the issue was resolved. This will help the team note any lessons that
can be learned from the problem’s solution.
This log was created by TechRepublic columnist Tom Mochal, who is a project manager mentor. It can be
used in conjunction with his issue submission form, which allows project managers to capture, screen,
prioritize, and evaluate issues. When using the issue submission form, each of the submissions can then
be mapped into one row on the project issues log.
©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.
Project issues log www.techrepublic.com
Issue Priority Date Reported Assigned Date
# Issue Description and Impact to Project (M/H/L) Reported By To Resolved Status Resolution/Comments
A pending acquisition has tied up the customers, who
asked to put their work on hold for two weeks. We have The sponsor has agreed to free up key individuals
other work to do, but this could delay the overall as needed. They have also agreed to an extension
1 schedule by up to two weeks. H 10/20/00 Anders Thornton 11/2/00 Closed of the due date by up to one week.
The vendor was able to replace the contractor
with another person. The impact to this portion of
A contractor quit the project unexpectedly. If we do not the project is a one-week delay as the new person
get the right replacement, this could result in a serious gets up to speed. The overall project timeline
2 delay. H 10/24/00 Monty Smith 10/31/00 Closed should still be okay.
The delivery of the test server was delayed by two
weeks. This may require a delay in the start of testing
3 for up to two weeks. H 11/10/00 Williams Thornton InProg We are currently looking for alternative servers.
©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.
Project issues log www.techrepublic.com
Issue Priority Date Reported Assigned Date
# Issue Description and Impact to Project (M/H/L) Reported By To Resolved Status Resolution/Comments
©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.
