Promise Watch

Checks the promise behind every open line's date, and reads what the supplier has said about it by email.

ReadsERPSupplier email

You get · Table on screen

Problem: The ERP holds a date nobody has confirmed, while the truth about where the parts actually are is sitting in email.
Impact: The delay is not realized until the stale date finally comes due and production feels it, even though the supplier already said enough to see it coming.
Solution: Scans supplier email for anything that flags a PO and raises it against the order book, then names what to correct in the ERP so the dates you plan against stay true.

01 · What it looks like

The real screen, from a real run.

Nothing here is a mockup. These are captures of the working app against a live ERP, and the numbers in each caption are the numbers in the picture above it.

The Promise Watch output: 42 of 63 open lines flagged, 14 promises broken, 28 with no promise, each with the fix to make in the ERP. — 42 of 63 open lines flagged: 14 promises already broken, and 28 where nobody ever committed to a date at all. Every flagged line carries the correction to make in the ERP, written by rule rather than improvised run to run.

The same Promise Watch run filtered to the two lines the supplier wrote about, showing the supplier's message against a line with no promised date. — The two lines the supplier actually wrote about. The ERP holds no promised date on either, while the supplier's own message says 45 of 60 castings shipped. The order book looks quiet and the mailbox does not, and that gap is what this task exists to close.

See the other tasks How Ask Mack works →

Which of these is your Monday morning?

Book an assessment and we will map the repeating work in your plant, then show you what the first build looks like against your own systems.

Book an Assessment Explore Project Foundry →