Know which vendor commitments need attention before the review.
Collect service evidence, compare it with documented commitments, and prepare a review packet that clearly separates facts from assumptions.

A vendor-by-vendor SLA review with evidence, gaps, and proposed owner actions.
Human sign-off requiredA vendor-by-vendor SLA review with evidence, gaps, and proposed owner actions. Prepared for review, never posted.
How this composition works.
This workflow turns a scattered weekly vendor check into a repeatable evidence packet. The agent retrieves current service records and prior decisions, calculates observed performance, and highlights gaps. Account owners decide how to interpret exceptions and what to communicate externally.
Load the vendor register
Read the current owners, review dates, and commitments from the approved register.
Collect supporting files
Find service reports and contractual reference documents in the approved folder.
Trace open correspondence
Collect relevant vendor updates without sending or changing messages.
Route the review
Post the packet to owners and flag missing evidence for follow-up.
A human signs off
The agent prepares evidence; account owners approve any vendor-facing claim or escalation.

A vendor-by-vendor SLA review with evidence, gaps, and proposed owner actions.
Human sign-off requiredA vendor-by-vendor SLA review with evidence, gaps, and proposed owner actions. Prepared for review, never posted.
Composed from the tools operations already uses.
Optional skills add method and verification.
Put your operations workflow under policy. Tell us what your team repeats today.
More for operations.
Morning operations brief
Review overnight incidents, group recurring signals, check the approved runbook, and deliver a source-linked morning handover.
See the workflowAccess review
Read current access across approved systems, compare it against the recorded roster, and prepare a review list of accounts that no longer match.
See the workflowRunbook drift check
Compare approved runbooks against the systems they describe, flag steps that reference something that has since changed, and prepare a correction list.
See the workflow


