Issue logs and action trackers for small teams

What is the difference between an issue log and an action tracker?

Small teams often keep problems in chat messages and promises in memory. Then a delay is discovered late, or a task is forgotten because nobody owned it. Two simple lists fix this.

An issue log records something that has already happened and needs management action. The UK government project delivery guide defines an issue as a relevant event that has happened, was not planned and requires management action. An action tracker records tasks that people have agreed to do, from meetings or from issue responses. Many teams combine these in one sheet with a column for type.

Do not mix issues with risks. As PMI's PM Network explains, a risk has not happened yet, while an issue has. Issues need action now. Risks are reviewed less often. When a risk happens, move it to the issue log and let the person who owned the risk work on the issue.

What should each line in the log contain?

Keep it short. Too many columns means nobody fills them in.

The UK guide notes that an issue should be described at a level where it can be managed and assigned to a single owner. It also lists three elements of an issue: the cause, the event and the impact. If you can fill in those three, the line is useful.

How do you set up and run the log in five steps?

1. Create one shared sheet. Use a spreadsheet or table in your team workspace. Add the columns above. Share the link in the team chat.
2. Say who can add items. Anyone should be able to raise an issue. The project manager checks and assigns an owner within a day or two.
3. Write each issue in plain words. Say what happened and what it affects. Avoid blame and avoid personal data about community members.
4. Assign one owner and one date. The UK guide says the issue owner assigns actions to named individuals. "Team to follow up" means no one follows up.
5. Review weekly. Spend ten minutes at your team meeting going through open items. Ask: is it moving, is it stuck, does it need escalation? Our guide to running project meetings that end with decisions shows how to fit this in.

When should you escalate an issue?

Agree escalation rules in advance. A simple version:

• Owner solves it if the fix is within the team's budget, time and authority.
• Project manager decides if the fix needs a plan change inside the agreed tolerances.
• Sponsor or donor is informed if the fix needs a change to scope, budget or timeline.

The UK guide says responses can range from accepting the impact to corrective action, and that changes outside agreed limits should go through formal change control. Our article on how to manage changes to scope, budget and timeline explains that route.

How do you close an issue properly?

Do not close an issue because the owner says it is done. As good practice, ask a second person to confirm the fix before the issue is closed. Record the date and what was done. A short note of the cause helps your team learn.

How can the log help your reporting and learning?

The issue register is a main source of information for reports, according to the UK guide. When you write a monthly or donor report, you can read the log to see what went wrong, how you responded and how long it took. The guide also suggests looking at issues together to find common causes. If three issues in a quarter came from late partner reports, the real problem is the reporting calendar, not three separate events. Feed those patterns into your lessons learned.

Tips for low-connectivity teams

• Keep a simple offline copy and sync it at set times.
• Let field staff send issues by message in the format "what, where, impact". The project manager enters them.
• Use short codes for locations so the sheet stays readable on a phone.

How EMPO can help

EMPO is a reliable, trusted training and consultancy provider and one of Myanmar's leading names in practical NGO training, with 1,200+ people trained and 15 partner organisations. We are based in Yangon, work in English and Burmese, and train online and in person across Myanmar. Our project management courses include practical tools such as issue logs and trackers. See our training services or contact us.

Sources

• Chapter 21: Issue management — UK Government Project Delivery, 2024
• Risks vs. issues — Project Management Institute, PM Network, 2012