Open Issues List Template Excel: What to Include

How-to basics · Updated November 20, 2026

An open issues list template in Excel is a structured tracker for recording unresolved problems, assigning an owner, setting a priority and due date, and documenting how each item is closed. Start with columns for Issue ID, Date Opened, Description, Category, Priority, Status, Owner, Due Date, Next Action, and Resolution; then turn the range into an Excel table and add dropdowns for fields such as Status and Priority.

What an open issues list is for

An open issues list, sometimes called an issue log or issue tracker, gives a team one place to see work that still needs a decision, investigation, repair, or follow-up. It is useful for project meetings, operations handoffs, product development, event planning, and other work where unresolved items could be forgotten or block progress. The list is not just a collection of complaints: it should show what happens next, who is responsible, and what evidence will count as resolution.

“Open” usually describes an issue that has not been fully resolved, but teams may use several lifecycle statuses. A reported concern might be New, then In Progress, then Blocked, and finally Closed. Keeping status separate from priority matters: priority says how urgently the team should respond, while status says where the work stands. A high-priority item can be blocked, and a low-priority item can be in progress.

Excel works well when a list is modest in size, a team needs flexible columns, or the tracker must be shared as a familiar workbook. It does not automatically provide the audit history, notifications, access controls, and linked workflows available in dedicated issue-management systems. Treat the workbook as a tracking tool, not as proof that a problem has been fixed.

Recommended template columns

Use one row per distinct issue and give each column one clear purpose. A practical starting set is:

  • Issue ID: A stable identifier such as ISS-001. It makes discussion and handoffs clearer than referring to a row number, which can change when the list is sorted.
  • Date Opened: The date the issue was first recorded. Use a real Excel date, not text such as “last Monday.”
  • Description: A concise, observable statement of the problem. Include relevant context, impact, or reproduction details where appropriate.
  • Category: A consistent classification such as Scope, Quality, Supplier, Safety, or Decision. Choose categories that help your team group and review work.
  • Priority: A small, defined scale such as High, Medium, and Low. State what each level means so different people do not apply it differently.
  • Status: A lifecycle value such as New, In Progress, Blocked, or Closed. Define whether a status like Deferred is still considered open.
  • Owner: One person accountable for coordinating the next step. Other contributors can be listed in a separate field or named in the notes.
  • Due Date: The date for the next meaningful milestone or expected resolution. If there is no agreed date, leave it blank rather than inventing one.
  • Next Action: A specific, verifiable step, such as “Confirm the delivery date with the supplier,” rather than “Follow up.”
  • Resolution and Date Closed: Record what changed, the outcome, and when the issue was closed. Keeping this history helps explain later decisions.

For a small team, those fields may be enough. Add a link to a document, a “Last Updated” date, an impact description, or a decision-maker field only when people will maintain and use it. Too many columns create empty cells and make updates feel like paperwork.

Create the tracker in Excel

In Excel for Microsoft 365 on Windows, type the headers into the first row and enter issues below them. Select the range and choose Insert > Table, confirm that “My table has headers” is selected, and choose OK. A table expands as new rows are added and provides filter buttons in the header row. You can also use Home > Format as Table to apply a table style. On Mac, the Insert tab also offers the Table command; labels and dialog placement can vary slightly by release.

Give the table a useful name from Table Design > Table Name, for example OpenIssues. Avoid merged cells, blank separator rows, and multiple issues in one cell: they make sorting, filtering, and summaries less reliable. Freeze the header row with View > Freeze Panes > Freeze Top Row if the list is long. Adjust column widths, wrap long descriptions, and use a consistent date format so the important details remain readable.

For example, a row might read: ISS-014; 3 Nov 2026; “Two test units fail to connect after restart”; Quality; High; In Progress; Sam Lee; 6 Nov 2026; “Collect logs from both units”; blank resolution. This example shows the level of detail to aim for: a reader can understand the issue and next step without needing to decode shorthand.

Use dropdowns and visual cues

Dropdowns reduce spelling differences that can split filters and summaries. To create one, select the cells under Status, then choose Data > Data Validation. In the settings, set Allow to List and enter a short source list, for example New,In Progress,Blocked,Closed. Repeat for Priority with a controlled list such as High,Medium,Low. For a list that will change, put the allowed values in a separate worksheet and use a named range as the validation source; this is easier to maintain than editing every validation rule.

Use conditional formatting to make exceptions visible, not to decorate every row. Select the relevant cells and choose Home > Conditional Formatting. For example, highlight overdue due dates with a rule based on a formula, or use text rules to distinguish Blocked and Closed items. If the workbook is shared, explain the colors in a small legend and do not rely on color alone; retain the written status so the meaning is accessible and clear when printed in grayscale.

Excel for Mac includes Data Validation and Conditional Formatting, though dialog details can differ. In Excel for the web, common table, filter, and validation tasks are available, but some advanced formatting or workbook features may have different controls or limitations. If people will edit the file in multiple versions, keep the template to standard table, validation, and formatting features.

Define a simple workflow

A tracker stays useful only if the team agrees how to maintain it. Set a small operating routine before adding many rows:

  1. Log: Write a distinct issue with enough facts to understand the impact. Avoid adding guesses as if they were confirmed causes.
  2. Triage: Agree on category, priority, and whether the item belongs in this tracker. Combine duplicates, but preserve links or notes to the original reports when needed.
  3. Assign: Name an accountable owner and agree on a next action and, where reasonable, a due date.
  4. Review: Filter for open statuses and check blocked items, approaching dates, and records with no owner or next action. Update the row during the meeting rather than keeping separate notes that soon diverge.
  5. Close: Change the status only when the agreed resolution or disposition is documented. If the item is deferred or accepted as a risk, record that decision rather than presenting it as fixed.

Agree on what counts as “open.” Some teams count every status except Closed; others treat Deferred or Accepted as a separate disposition. That definition affects summaries and meeting agendas, so make it visible in a notes area or a short instructions tab.

Optional formula for issue age

An age column can help a team notice items that have been sitting unresolved. For a plain worksheet with Issue ID in A, Date Opened in B, and Status in F, enter this in H2, labeled Age (days), then fill it down:

=IF(OR(B2="",F2="Closed"),"",TODAY()-B2)

With B2 containing 1 Nov 2026 and F2 set to In Progress, the formula returns 2 on 3 Nov 2026. A blank opening date or a Closed status returns a blank. The result changes as the current date changes because TODAY is recalculated by Excel; it is not a permanent record of the age at closure. If you need a historical duration, record the closing date and calculate from the two stored dates instead. Ensure Date Opened contains actual Excel dates and format the result as a number, not as a date.

Filter, review, and summarize the list

Table filters make the workbook useful during day-to-day review. Filter Status to exclude Closed, then sort by Priority or Due Date to put urgent work near the top. Filter Owner to prepare an individual’s follow-up list, or filter Category to review a particular workstream. Clear filters before concluding that an item is missing; it may simply be hidden by the current view.

A small summary area can show counts by status or priority, but it should not replace the underlying issue rows. A PivotTable is an option for grouping a larger list by Status, Owner, or Category: select the table and choose Insert > PivotTable. Refresh the PivotTable after new data is added if the displayed counts do not update. For a simple tracker, filters and a regular review may be more useful than a dashboard that nobody maintains.

Common problems and ways to prevent them

The most common failure is not a spreadsheet error but stale information. An owner changes, a due date passes, or a fix is attempted, yet the row remains unchanged. Set a review cadence appropriate to the work—weekly for an active project may suit some teams, while a daily operational queue may need more frequent review—and make updating the tracker part of the meeting or handoff.

  • Vague descriptions: Replace “system issue” with the observed behavior, where it occurs, and its effect. Do not put sensitive personal or confidential information in a broadly shared workbook.
  • No clear ownership: A group name can obscure accountability. Assign one coordinator, even when resolution requires several contributors.
  • Priority inflation: If everything is High, the scale cannot help people sequence work. Define priority using agreed impact and urgency criteria.
  • Inconsistent statuses: Free-typed values such as “working,” “started,” and “in progress” create fragmented reporting. Use a controlled list and a short definition for each value.
  • Rows used as records: Do not delete closed items simply to make the sheet look current. Archive them in a planned way if the file becomes unwieldy, and retain whatever history the team needs.
  • Accidental edits: Shared workbooks can be changed or sorted in ways that confuse users. Keep a backup or version history, limit editing to appropriate collaborators, and document the table’s intended fields.

When Excel is enough—and when to use another tool

Excel is a reasonable choice when the tracker is straightforward, the team is small, reporting needs are modest, and collaborators can agree on one authoritative file. It is easy to adapt columns and create a printable meeting view. A shared workbook stored in a collaboration location can reduce conflicting copies, but users still need to agree which file is authoritative and how changes are communicated.

Consider a dedicated project, service-desk, or software issue system when items need automated assignment, notifications, permissions by role, a detailed change history, links to code or service tickets, or workflows that span many teams. A shared list or database tool may be more suitable when multiple people need controlled forms and views without editing a spreadsheet grid. These alternatives are not automatically better for every small tracker; choose based on collaboration, governance, and reporting needs rather than on the number of features alone.

Frequently Asked Questions

Where can I get an open issues list template for Excel?
Excel does not require a special template to make an issue log. You can create one from the headers and setup steps above, or search Excel’s template gallery for a project or issue-tracking workbook and adapt its fields. Check that any downloaded workbook has the columns and sharing controls your team needs before entering sensitive information.

What is the difference between an issue log and an action item list?
An issue log describes unresolved problems, risks, or decisions and tracks their status and resolution. An action list focuses on tasks someone has agreed to complete. A single issue may generate several action items, so a larger project may track the issue in one place and link its actions separately.

Should closed issues stay in the workbook?
Usually, retaining closed rows helps preserve decisions and prevents repeated reports from being treated as new. If the list becomes difficult to use, define an archive process and keep an accessible record; do not remove history without considering team, organizational, or retention requirements.

How do I mark overdue issues in Excel?
Use a real due date and a status field, then apply conditional formatting to due-date cells or filter the list by date. Decide whether an item marked Blocked or Deferred should still be highlighted as overdue. A visual rule is a reminder, not proof that the owner has been notified.

Can several people update the same Excel issue tracker?
Yes, when the workbook is saved in a supported shared location and collaborators have suitable access, Microsoft 365 can support co-authoring. Avoid distributing separate emailed copies as if each were the master. Confirm that everyone knows where the authoritative workbook is stored and how to handle conflicting or unclear updates.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.