What is a project issue log?

A project issue log is a working record of problems that have already occurred and need an owner, action, due date, and follow-up through resolution.

What is the difference between an issue and a risk?

An issue is a problem or event that has happened. A risk is an uncertain event that might happen and could affect the project. When a risk occurs, record the active problem as an issue and update the risk history.

What should an issue log include?

Include an ID, date raised, factual description, impact or priority, category, reporter, accountable owner, next action, due date, status, escalation or decision, resolution, and date closed.

How often should a project issue log be reviewed?

Review open issues during the regular project delivery check-in and sooner when a deadline, impact, or escalation changes. Every open issue should have a current owner, next action, and due date.

Do I need a separate issue log if I already use a RAID log?

Usually not. A RAID log already includes issues alongside risks, actions, and decisions. Use one authoritative record unless a clear reporting or workflow need calls for an issue-only view.

Project issue log template: move problems toward resolution

When a project blocker gets buried in notes, the next action can disappear with it. Use an editable Excel issue log to record the impact, owner, next action, escalation, and eventual resolution, with a fictional worked example.