OpsGrid · PO approval alerts · Business Central · Live in beta

A purchase order has sat with one approver for four days. The buyer thinks it’s moving.

Business Central sent it to the right approver under the rules you set. OpsGrid puts every PO still waiting, the approver it sits with and the days it has waited into one Teams card, for the person who has to chase them.

The cost of a PO waiting on a signature

Supplier deliveries to US manufacturers were “slower in October for the 11th consecutive month”, and production-material lead times averaged 87 days (ISM October 2026 Manufacturing PMI Report). A PO that waits four days for a signature turns an 87-day lead time into 91.

What OpsGrid surfaces

Two purchasing signals, live in the beta today.

Purchase order approval status your team checks PO by PO today. OpsGrid checks Business Central on a schedule, every 6 hours as planned, and lists every PO still waiting on an approver.

  • POs stuck in approval Each PO waiting on an approval step, the approver it sits with, and the days it has waited
  • Open POs by vendor Every open purchase order, grouped by vendor

Card goes to: Procurement Lead · BC write: none. Approve alerts the stakeholders on that PO; BC’s own approval workflow decides who signs.

See all 28 decisions OpsGrid surfaces 17 live today, 11 on the roadmap, ranked by what the delay costs you
9 POs Stuck in Approval
9 POs Stuck in Approval Open Purchase Orders by Vendor

OpsGrid Beta · Dynamics 365 Business Central · sample data

How it works

Waiting POs surface in Teams, with a name on each.

OpsGrid checks your Business Central purchase orders on a schedule. Every 6 hours is the planned default; a configurable interval is on the roadmap.
OpsGrid sends one card in Microsoft Teams to the named Procurement Lead, listing each waiting PO, the approver it sits with and the days it has waited.
Approve on the card alerts the stakeholders on that PO, starting the chase without a single email. The approver still signs in Business Central, and OpsGrid changes nothing in BC’s approval rules. Automatic escalation when a PO waits too long is on the roadmap.
Decision Infrastructure

Business Central decides who signs. Nobody watches how long they take.

BC’s approval workflow already handles amount limits, the approver chain, due dates and delegation, and OpsGrid leaves those rules alone. It puts every waiting PO, its approver and its days waiting in front of one named person in Teams, and logs what happened next.

The approval step exists in BC. The wait inside it has no owner: a PO can sit with one approver for days while purchasing assumes it is moving. OpsGrid gives that wait a name.
Act from Microsoft Teams Predefined ownership, no ambiguity 0 BC writes without approval Full audit trail, automatic
1.2 hrs
time to decision: 2.3 days to 1.2 hours
2 to 3 wks
from BC connection to live signals
0
BC writes without a named person’s approval

From one active OpsGrid beta deployment · Dynamics 365 Business Central · mid-market manufacturer · baseline at project start, outcomes at 30 and 90 days. Decision latency: calendar time from the event’s record in Business Central to the owner acting on it.

What's next
30-minute call
Book a Decision Latency Audit

30 minutes. We identify the 3–5 operational decisions currently slowing your business and estimate what each delay costs. No slides. A number and a map.

Book the call →
LinkedIn
Connect with Christopher Wakare

Christopher leads IQ's deployment work. If you'd rather start with a message, connect on LinkedIn and send a note about what you're running into.

Connect on LinkedIn ↗