Tracking how long event issues stay unresolved
Open issues keep piling up on the tracker and nobody can say which ones have been stuck the longest.
The short answer
Issue ageing means recording the date each issue was opened and showing how many days it has been open, sorted oldest first. Your team then agrees age bands that trigger a nudge, an escalation or a decision.
Age is a prompt to ask why, not a score. An old issue may be waiting on a supplier, a decision or a person, and the fix is different in each case.
What to record for each issue
- A one-line description that someone outside the team can understand.
- The date it was opened, not the date it was last discussed.
- One named owner, who may not be the person who fixes it.
- What it is waiting on: a person, a supplier, a decision, information or nothing.
- The next step and the date of that step.
- What it blocks, such as a milestone, a payment or another task.
Set age bands that fit your timeline
The same number of open days means different things six months out and three weeks out. Express bands relative to the event date or to the milestone the issue blocks, and let your committee choose the limits.
The table gives a structure. The day counts are left for you to set.
| Band | Meaning | Action |
|---|---|---|
| New | Opened within your first limit. | Owner confirms next step. |
| Ageing | Past the first limit with no movement. | Project lead asks what it is waiting on. |
| Stuck | Past the second limit, or it now blocks a milestone. | Escalate to the chair or approver with a decision request if a decision is the blocker. |
| Critical | Within a set distance of the event, or blocking a contract date. | Add to the leadership summary and decide an option. |
Ask the right question about each old issue
- Waiting on a decision: who decides, by when, and what happens if it is not made?
- Waiting on a supplier: when was the last request, and is there a second contact?
- Waiting on information: who holds it, and can an assumption be recorded meanwhile?
- Waiting on nothing: is this issue still real, or can it be closed or merged?
Review rhythm
- Before each weekly report, sort the issue list oldest first.
- Move any issue that crossed a band and note the date it moved.
- Ask owners of Stuck and Critical items for a next step in writing.
- Report the count by band and the two or three oldest items in the status report.
- Close issues only when the owner records what resolved them.
Pitfalls
- Resetting the date every time someone comments, which hides real age.
- Closing issues to improve the numbers rather than resolving them.
- Treating all issues as equal, so a minor one that is old crowds out a recent one that blocks the venue contract.
Worked example · Fictional example
A fictional forum team reads its issue list
Fictional organisation and figures, written to show the level of detail that is useful.
Persatuan Fiktif Jurutera Pengurusan has seven open issues. Sorted by age, the oldest is a catering allergen list requested from the venue 21 days ago, waiting on the venue's reply.
The project lead sees it blocks the final catering numbers milestone, moves it to Stuck, and asks the secretariat head to phone the venue's second contact. A younger issue about a speaker photo is Ageing but blocks nothing, so it stays with its owner. The report shows seven issues: three New, two Ageing, two Stuck.
Use this yourself
Issue ageing log
Copy this table into your tracker and add a row for each open issue. Days open is the report date minus the opened date.
| Issue | Opened | Days open | Owner | Waiting on | Blocks | Band | Next step and date |
|---|---|---|---|---|---|---|---|
| Example: venue allergen list not received | Date opened | Report date minus opened | Name | Venue reply | Final catering numbers | Stuck | Phone second venue contact by date |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The tracker already records opened dates and owners.
- Few issues are open at once and the team meets weekly.
- Owners respond when asked for a next step.
Outside planning help earns its fee when
- Issues sit with suppliers or committee members who are slow to respond and need chasing.
- Nobody has authority to escalate to the chair.
- The issue list mixes real blockers with old notes and nobody has time to clean it.
Need someone to chase the stuck issues?
A conference project lead can keep the issue list current, ask owners and suppliers what each old issue is waiting on, and bring stuck items to your chair with the decision needed. Your committee keeps authority over the choices. Send your current issue list and how many people are involved.
Questions organisers ask
How many days should trigger escalation?
Your committee should set this, relative to the event date and the milestone the issue blocks. A limit that suits a seven-month plan will be too slow in the last month.
Should we count weekends and public holidays?
Pick one rule, calendar days or working days, and use it every time. State the rule at the top of the log.
What if the issue belongs to a supplier?
Keep it on your list with a named person on your side as owner, and record what the supplier owes and by when.
Is this the same as a risk register?
No. An issue has already happened. A risk might. Track them separately and link an issue back to its risk if there was one.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.