Combined Issue & Risk Log Management Template

Effective project governance requires that both issues and risks are identified, tracked, and resolved in a systematic way. While many organisations maintain separate logs for issues and risks, a combined template offers several practical advantages:

• Unified visibility stakeholders can see at a glance what could happen (risk) and what is already happening (issue).
• Reduced duplication the same fields (owner, status, mitigation) are reused, saving time.
• Simplified reporting a single source of truth for management dashboards.

Key Concepts

Issue

An issue is a problem that has already occurred and is affecting the project. It requires an immediate response to contain or resolve its impact.

Risk

A risk is a potential future event that may affect project objectives. Risks are managed through identification, analysis, and the planning of mitigation or contingency actions.

Structure of the Combined Log

The template is designed as a table with columns that apply to both issues and risks. Each row represents either an issue or a risk, distinguished by a Type column.

How to Use the Template

1. Identify & Classify When a new item is discovered, decide whether it is an issue (already occurring) or a risk (potential future event). Record Issue or Risk in the Type column.
2. Assign a Unique ID Use a simple sequential number or a coding scheme (e.g., R001, I002) to make referencing easy.
3. Describe Clearly Provide a concise title and a brief description that anyone can understand without additional context.
4. Allocate Ownership The Owner is responsible for monitoring, driving mitigation (for risks) or resolution (for issues), and updating the log.
5. Assess Impact & Likelihood
   • Impact rating (15) measures the effect on scope, schedule, cost, or quality.
   • Likelihood rating (15) is only relevant for risks; it estimates the probability of occurrence.
6. Calculate Priority For risks, multiply Impact Likelihood. For issues, use Impact alone. The resulting number determines the priority level (e.g., 15 low, 610 medium, 1115 high, 1625 critical).
7. Define Status Typical statuses: Open, In Progress, Closed, Deferred. Keep this column uptodate.
8. Plan Mitigation or Resolution Document the specific actions that will reduce risk probability/impact or resolve the issue.
9. Set Target Dates Provide realistic dates for when the mitigation or resolution should be completed.
10. Record Actual Dates & Comments Once an item is closed, fill in the actual resolution date and any lessons learned.

Best Practices

• Regular Review Cycle Hold a weekly or biweekly log review meeting. Update status, reassess priority, and adjust actions as needed.
• Keep it Simple Avoid overengineering. The template should be easy to fill out and understand for all team members.
• Link to Project Artefacts Where relevant, attach or reference related documents (e.g., risk analysis worksheets, issue tickets).
• Use Colour Coding Highlight highpriority items with a background colour (e.g., light red for critical). This visual cue speeds up triage.
• Document Lessons Learned The Comments column is a valuable repository for what worked and what didnt, feeding into future risk management processes.
• Integrate with Project Dashboard Export the log to your reporting tool so that executives can see a highlevel view without digging into the spreadsheet.

When to Separate the Logs

Although a combined log works well for most smalltomedium projects, there are scenarios where separate logs are preferable:

• Very large programmes where the volume of risks and issues overwhelms a single table.
• Regulatory environments that require distinct audit trails for risk registers and issue registers.
• Projects that employ specialised risk analysis techniques (MonteCarlo simulations, quantitative risk scoring) that need additional fields not relevant to issues.

Conclusion

The combined Issue & Risk Log template provides a streamlined, singlesource approach to tracking problems and uncertainties throughout a project lifecycle. By using consistent fields, clear ownership, and a simple priority calculation, project teams can quickly identify what needs attention, allocate resources efficiently, and keep stakeholders informed. Implement the template, embed it in your regular governance meetings, and continuously refine the process the result will be a more transparent, proactive, and resilient project environment.