From notification to completion: the five places where maintenance orders get stuck On Monday, an operator reports a leaking seal on a circulation pump. The repair itself takes four hours. Yet the order doesn't reach TECO (technically completed, the SAP status that closes the work) until six weeks later. Nobody did anything wrong: the notification waited for review, the order for approval, the part for a purchase order, the job for a suitable window, and the paperwork for someone with time.Most maintenance organizations will recognize this. The lead time of a maintenance order is mostly waiting, not working. And that waiting rarely shows up in reporting. Backlog overviews show where an order stands today, not how long it took to get there. KPIs such as MTTR (mean time to repair) average everything out. And each queue has a different owner: planning, approval, purchasing, operations, administration. Everyone sees their own piece; nobody sees the whole chain.The good news: the data to make this visible is already in your ERP system, such as SAP. Every status change, pur