Skip to content
Blog

The open issues list in a project: structure, template and common mistakes.

Almost every project in machine and plant building has an open issues list, and almost every one is out of date after three weeks. Which columns an OPL needs, what a template looks like and the mistakes that usually make it fail.

Yanik YeganehfarCo-Founder & COO6 min read
Quick answer

An open issues list (OPL) collects everything still to be clarified or done in a project. Each item needs a clear description, one responsible person, a due date, a status and a source reference, such as minutes or an email. It stays useful if each project has exactly one, closed items get a date and the status meeting uses it.

Contents
  1. What is an open issues list in a project for?
  2. Which columns does an open issues list need?
  3. What does a template with sample rows look like?
  4. Why does the open issues list go out of date so quickly?
  5. How does the list stay current?
  6. How does KoAssist help with open issues?

The open issues list for the assembly cell has 74 rows. 31 of them are highlighted yellow, which according to the legend means "being clarified". On 12 rows it does not say who is clarifying the item. The last change is from 2 October, saved as "OPL_assembly_cell_v7_final_new.xlsx". The project folder also contains a v8 that someone from the electrical team created.

The list is not badly made. It simply shares the fate of most open issues lists. It gets created, filled and at some point no longer maintained.

What is an open issues list in a project for?

An open issues list collects everything in the project that has not yet been clarified or done. In machine and plant building that typically means:

  • questions to the customer about the specification
  • pending approvals of drawings, circuit diagrams or layouts
  • technical clarifications between mechanical, electrical and software
  • missing documents, such as data sheets for bought-in parts
  • defects from FAT or SAT that have to be fixed before acceptance

Its purpose is simple. No item should get lost, and everyone in the project should see what is still missing. How the overall project status becomes visible without long rounds of questions is described in the article on project status without status meetings.

Which columns does an open issues list need?

Fewer than most templates provide. These nine are enough for almost any project:

Column Content Why
No. sequential, never reused so that emails and minutes can refer to "OP 23"
Description one sentence, concrete "Clarify protection class of control cabinet" instead of "Control cabinet"
Category customer, mechanical, electrical, software, purchasing for filtering in the status meeting
Responsible one person, not a team nobody feels addressed by "Electrical"
Due date when it must be clarified by without a date the item stays open forever
Status open, being clarified, done three levels are enough
Closed on date shows what has moved since last week
Resolution how the item was clarified otherwise nobody will know in a year what was decided
Source minutes, email, specification with page so you can look up where the item came from

What does a template with sample rows look like?

No. Description Category Responsible Due date Status Closed on Resolution Source
21 Clarify protection class of control cabinet, specification says IP54, installation site in splash zone according to layout Customer Project management 8 Nov done 6 Nov IP65 confirmed, change order announced Specification p. 18, customer email 6 Nov
22 Data sheet for rotary table missing for load verification Purchasing Purchasing, Ms Berger 12 Nov being clarified Minutes of design review 29 Oct, item 4
23 Transfer height to existing conveyor contradictory (850 / 1,000 mm) Customer Design, Mr Aydin 15 Nov open Specification p. 7 and layout Rev. B

The examples show two habits that make the difference. The description says exactly what is unclear. And the source leads to the page, not just to the document.

Why does the open issues list go out of date so quickly?

There are several versions. Each department keeps its own copy, or the list is sent by email and maintained locally. After a few weeks nobody knows which one applies.

Settled items are not closed. The item was settled in an email, but nobody enters it. The list grows, and whoever opens it can no longer see what is really open.

Nobody feels responsible. "Electrical" or "Customer" in the Responsible column means nobody in practice.

Items without a due date. They stay open until they turn up again in assembly.

The list lives next to the project. Things are settled in emails, phone calls and meetings. The list only hears about it if someone updates it. The article on project status in Excel, OneNote and email describes this pattern in more detail.

How does the list stay current?

One list per project, in a fixed place. In the project folder or in SharePoint, not as an email attachment. If you send it, send a link.

Everyone closes their own items. The project manager checks, but does not enter everything.

The status meeting works with the list. New items are entered directly in the meeting, with an owner and a due date. Items that have not moved for two meetings are raised.

Closed items stay visible, but filtered. Do not delete anything. The resolution of a closed item is often the answer to a question in the next project. Why this knowledge is otherwise lost is shown in the article on lessons learned in machine building.

Send questions to the customer in batches. Once a week, with the numbers from the list. That saves the customer time and makes answers easier to match.

How does KoAssist help with open issues?

Project Memory in KoAssist, the AI agent for machine and plant builders, starts where the list goes out of date: between the email and Excel.

At the start, KoAssist reads the specification and fills in a project profile from it. Anything missing or contradictory goes onto a list as a question to the customer. During the project, KoAssist also reads emails and minutes. If an open issue is settled in an email, a proposal to close it arrives, with a reference to the email. The proposal only becomes valid once someone on the team accepts it. Project Memory is currently in pilot operation with existing customers.

If you would like to see how this looks on one of your own projects, you can book a demo.

Written by

Yanik Yeganehfar

Co-Founder & COO

On LinkedIn ↗

Frequently asked questions

Yanik Yeganehfar, co-founder of KoAssist

Find out with Yanik whether KoAssist fits your projects.

Request a demo