Issue Log

Phase: Execution | Audience: Internal | Project: WEB-2026-01 Corporate Website Development

Understand it first

In simple words: The Issue Log records problems that have already happened, their impact, who is fixing them and by when.

Think of it like: On a trip, the train is cancelled. That is no longer a risk; it is an issue. You note it and decide to take a bus.

When is it created?	Execution, updated whenever an issue arises
Who prepares it?	Project Manager
Who approves or uses it?	Internal; serious issues escalated
What happens next?	Issues are tracked until resolved

How it connects to other documents

Many issues start as risks in the Risk Register.
Serious ones appear in the Weekly Status Report.
Lessons from them go into the Lessons Learned Register.

The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Problems that have already happened, their impact, and the action to resolve them. A risk that occurs becomes an issue.

Item	Detail
Document no.	WEB-2026-01/IL
Version	1.0
Date	30 Oct 2026
Owner	Project Manager
Audience	Internal
Phase	Execution

1. Log

ID	Raised	Issue	Impact	Priority	Owner	Action	Target	Status
I-01	9 Oct	Logo supplied only as low-resolution JPG	Blurry logo on high-resolution screens	Medium	Designer	Requested vector file from client's agency	12 Oct	Resolved
I-02	16 Oct	Content for 4 services pages not received (risk R3)	Content upload in week 7 at risk	High	PM	Escalated to Head of Marketing; new date 6 Nov; placeholder text used meanwhile	6 Nov	Open
I-03	26 Oct	MD asked for a new home page layout in round 2 (risk R1)	20 extra designer hours; cost overrun	High	Designer	Absorbed within round 2 to protect sign-off date; lesson recorded	30 Oct	Resolved
I-04	28 Oct	Temporary staging server blocks outgoing email	Contact form cannot be tested	Medium	Backend	Switch to transactional email service early	13 Nov	Open
I-05	22 Oct	Designer on unplanned leave for 1 day	Inner page designs 1 day late	Low	PM	Designer worked Saturday 24 Oct	24 Oct	Resolved

Note: Risk vs issue: a risk is something that might happen (in the Risk Register); an issue has already happened and needs action now. I-02 and I-03 started life as risks R3 and R1.

WEB-2026-01/IL · v1.0 · Internal. Bracketed items such as [Client Name] are placeholders.

Key takeaways

Risk = might happen; issue = has happened.
Every issue needs an owner, an action and a target date.
Escalate early when an issue threatens a milestone.

Common mistakes to avoid

Confusing risks and issues.
Leaving issues 'open' with no action.
Hiding issues from the sponsor.

Next lesson: 28. Decision Log