Product Update - September 08, 2026

Product Update — September 8, 2026

---

Frontline Passdown Follow-ups and Blocker Rechecks — AI-assisted shift handover and blocker resolution tracking

Shift passdowns now close the loop on two problems that previously fell through the cracks. When a supervisor writes a passdown note, the platform generates AI-drafted follow-up task suggestions for the incoming team — the supervisor reviews each one, edits the title and due date, assigns it to an eligible employee at the same location, and it becomes a real tracked task with an assignment notification. Separately, when a campaign item is blocked and that block is linked to a Service Desk ticket, a recheck round fires automatically once the ticket closes: the frontline worker is prompted to confirm whether the blocker is actually resolved or still present, keeping campaign item status accurate without requiring manual follow-through from the manager.

Use case: A store manager writing the closing passdown flags a display fixture that needs repositioning. The platform drafts a follow-up task; the manager assigns it to the opening supervisor with a 9 a.m. due time, and the opening shift starts with the task already in their day sheet.

Available in: Frontline Execution → Day Sheet → Passdown and Blockers · Settings → Frontline Execution → Passdown Follow-ups

---

SOP Version Change Summaries — Show employees only what changed in a procedure since they last completed it

When an employee opens a procedure they have completed before and the procedure has been updated since their last run, they now see a step-by-step diff alongside the current text — added steps, removed steps, and modified steps highlighted in context. Employees who completed an older version can see at a glance what is different without re-reading every step, and managers no longer need to send a separate communication every time a procedure is revised.

Use case: A safety coordinator updates a chemical handling SOP to add a new PPE step. Employees who previously completed the SOP open it for their next run and immediately see the new step highlighted as added — no need to read through the unchanged steps or check a separate change log.

Available in: SOP Hub → Procedure → Version Change Summary

---

Service Desk Parts Requests Through the Warehouse Fulfillment Queue — Proper parts fulfillment workflow for field service and IT operations

Parts added to a service ticket are now a fulfillment request rather than an immediate inventory deduction. The request appears in the warehouse pick queue — the same queue material requests and supply orders already use — where a storekeeper reviews it, picks the item, and confirms fulfillment. Inventory only decrements at the moment of physical pick, so stock counts on screen stay in sync with stock counts on the shelf. If a request cannot be fulfilled, the storekeeper can decline it and the technician is notified. Multiple parts added to the same ticket while the request is still open append to a single pick row rather than generating separate trips.

Use case: A field technician adds three parts to an open service ticket from a remote site. The warehouse storekeeper sees a single consolidated request, picks all three items on one trip to the shelf, confirms fulfillment, and the ticket's parts cost and inventory records update simultaneously — no manual reconciliation needed at the end of the week.

Available in: Service Desk → Ticket → Parts · Field Service Suite → Warehouse → Fulfillment Queue