Vendor Coordination

Find Out Who Didn't Confirm Before the Day Starts

Twelve moving parts watched continuously, with only the exceptions reaching you.

It runs in the systems you already have

  • Slack
  • Notion
  • Google Drive
  • Microsoft Teams
  • Jira
What it looks like

Vendor Coordination, once it is built.

You ask in your own words. It does the work in the systems that already hold it, and tells you what it changed.

Where do we stand for Thursday?

Eleven of fourteen confirmed. Three are not:

  • Lighting — no reply since Monday, chase drafted
  • Catering — confirmed a different headcount than the brief
  • Transport — confirmed, but for the wrong load-in window

Everything else needs nothing from you. The three chases are written and ready to send.

How it gets built

Connect, describe, run.

The same three steps whatever the process is.

  1. 01

    Connect

    The agent is wired into the systems the work already lives in. Nothing moves and nobody learns a new tool.

  2. 02

    Build

    The rules are described rather than drawn, in the words you already use to make the call.

  3. 03

    Run

    It runs on its own and hands back the decisions that need a person. The handover is designed, not left over.

Questions

What people ask about vendor coordination

Do our vendors have to change anything?
No. It reads the threads that already exist. Asking a dozen suppliers to adopt a portal is a bigger change programme than the problem justifies.
Why exceptions rather than a dashboard?
A dashboard showing eleven greens and one red still needs somebody to look at it, and the morning it matters is the morning nobody has time. Silence meaning confirmed is a claim worth making.
What if a vendor confirms something different from the brief?
That is a mismatch, not a confirmation, and it is surfaced as one. Which mismatch actually matters today is a judgement.

Pick this one, or the one costing you more.