# Order Promise Date Slip Tracker Worksheet > Source: https://netray.co/tools/order-promise-date-slip-tracker-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Track how far each open order line has slipped from its original promise, see value at risk, and decide whom to call first. ## Category supply-chain ## Audience - Customer service rep - Production planner - Customer service manager ## Tool **Kind:** worksheet **Mode:** editable **Currency:** $ **Columns:** #### Order / line **Key:** order **Type:** text #### Customer **Key:** customer **Type:** text #### Part number **Key:** part **Type:** text #### Line value **Key:** value **Type:** number **Format:** currency #### Original promise (days from order) **Key:** orig_days **Type:** number **Unit:** days #### Revised promise (days from order) **Key:** new_days **Type:** number **Unit:** days #### Slip **Key:** slip **Type:** number **Expr:** new_days - orig_days **Format:** days #### Value slipped **Key:** late_value **Type:** number **Expr:** value * if(gt(new_days - orig_days, 0), 1, 0) **Format:** currency #### Cause **Key:** cause **Type:** select **Options:** - Material - Capacity - Quality - Outside process - Customer change - Carrier #### Customer informed **Key:** informed **Type:** select **Options:** - Yes - No **Rows:** #### Material **Order:** SO-104522 / 2 **Customer:** Delta Hydraulics **Part:** HP-4410 **Value:** 6200 **Orig days:** 30 **New days:** 44 **Informed:** Yes #### Capacity **Order:** SO-104530 / 1 **Customer:** Kestrel Marine **Part:** KM-118 **Value:** 3150 **Orig days:** 21 **New days:** 21 **Informed:** Yes #### Outside process **Order:** SO-104544 / 3 **Customer:** Northwind Aerostructures **Part:** B-2210 **Value:** 18900 **Orig days:** 45 **New days:** 52 **Informed:** No #### Quality **Order:** SO-104551 / 1 **Customer:** Sato Components **Part:** SC-77 **Value:** 2400 **Orig days:** 14 **New days:** 19 **Informed:** No **Totals:** #### Total open value **Key:** value **Agg:** sum **Format:** currency #### Value slipped **Key:** late_value **Agg:** sum **Format:** currency #### Average slip (days) **Key:** slip **Agg:** avg **Format:** decimal #### Maximum slip (days) **Key:** slip **Agg:** max **Format:** number **Summary:** #### Share of value slipped **Key:** pct_slipped **Expr:** sum_late_value / sum_value * 100 **Format:** percent **Primary:** true #### Lines tracked **Key:** lines **Expr:** count **Format:** integer **Notes:** Enter promise dates as days from order date to keep the math simple. Sort by Customer informed, then by slip, so the lines you must call about today are first. ## Content **Intro:** Customers forgive a late order faster than a surprise. This worksheet shows which lines have slipped, by how much and for what reason, and whether the customer has been told. It is meant for the daily stand-up between customer service and planning. **Sections:** #### How to use the tracker **Body:** List each open line that has moved or is at risk. Enter the original and revised promise as days from the order date, and the line value. The sheet computes slip in days and the value of lines that moved. Mark whether the customer has been informed. Before each stand-up, filter for lines marked No and make those calls first. #### What the numbers tell you **Body:** Share of value slipped shows how much of your open book has moved. Average slip tells you whether delays are a few days or a few weeks. Group by cause to see the pattern: mostly Material points at purchasing and supplier performance, Capacity points at scheduling and quoting, Quality points at the shop floor. **Bullets:** - Material causes: review supplier lead times and safety stock - Capacity causes: check promise logic against finite capacity - Customer change causes: tighten the change request process - Uninformed customers: fix the notification habit first #### Linking to the ERP **Body:** Your ERP holds the promise date, but it rarely keeps a history of how many times it moved. Capture the original promise here, or in a user-defined field, so you can measure slippage. A repeating pattern of two or three promise changes per line is a sign that promise dates are guesses. #### Common mistakes **Body:** Resetting the original promise every time it moves, which hides the real slip. Not recording the cause, which makes the data useless for improvement. Only tracking lines already past due, instead of lines that will be late. **Cta:** Netray can read promise date history and open order lines from your ERP, so this tracker is filled from data and the at-risk list is ready each morning. **Faq:** #### Should the original promise ever change? **Answer:** No. Keep the first confirmed promise fixed and record every revision against it. If you overwrite it, the slip always looks like zero and you lose the signal that something is wrong with how dates are set. #### How is this different from an on-time delivery report? **Answer:** On-time delivery measures against the final date after shipment. This tracker works earlier, on open lines, so you can warn customers before the date is missed. #### What counts as a slip? **Answer:** Any revision that moves delivery later than the date the customer was given. Customer-requested moves are logged with the cause Customer change, so they do not count against your own performance in review. #### Can I use dates instead of days? **Answer:** Yes, but the worksheet formulas expect numbers. Convert dates to days from order date, or compute the difference in Excel after export and keep the days columns for the summary. ## Search terms promise date tracker, order slip tracker excel, late order tracking spreadsheet, customer order delay tracker, open order past due report excel, order promise date change log, late sales order tracker --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json