Run a Recurring Vendor Call Agenda for the Executive Office
by ExecutiveAssistantAgency Editorial Team · 4 min read
A repeatable agenda that turns recurring vendor calls into short, decision-focused sessions with clear owners and follow-up.
In this article
Vendor calls drift without an owner
A recurring call with a facilities vendor or a software supplier can become a status meeting that never resolves anything. The vendor describes activity, the executive listens, and the same open issue returns four weeks later. The assistant who schedules the call can also shape it, and that is where the value sits. A fixed agenda turns a vague check-in into a short working session.
The agenda should serve the executive's decision load rather than the vendor's reporting habits. Every item needs a purpose, a time box, and a named owner. Anything that does not need a decision can move to a written update. The assistant's job is to protect the meeting from becoming a reading of the vendor's dashboard.
Build one agenda that repeats
Start with a standing template that covers the same four blocks: performance, open issues, changes ahead, and decisions needed. Keep the template to one page and send it to the vendor two days before the call. Ask the vendor to add evidence under each block rather than a separate slide deck. A consistent structure lets the executive compare this month with last month without hunting for context.
Set a default length and defend it. A thirty-minute call with four blocks leaves roughly six minutes per block, which is enough for a short update and one decision. If a topic needs more time, schedule a separate working session with the right specialists. Do not let a routine call expand because nobody agreed on an end time.
Put performance evidence on the page
Ask for the same three or four measures every cycle, such as response time, unresolved tickets, delivery dates, and service interruptions. The measures should be defined in plain language and tied to the contract or the statement of work. A vendor that changes the definition of a measure mid-year is hiding a trend rather than reporting one. Keep a simple chart in the agenda pack so the executive sees direction, not just a snapshot.
Record the source of each measure and the date it was pulled. A number without a source invites an argument about method instead of a decision about service. When a measure moves sharply, ask the vendor for the cause before the call and include the answer in the notes. The NIST Cybersecurity Framework is a useful reference for structuring supplier risk conversations around outcomes rather than slogans.
Keep decisions and owners visible
Add a decision log to the bottom of every agenda. Each entry should show the question, the options, the owner, the due date, and the status. Review the log at the start of the call so old items cannot quietly disappear. A decision that is deferred three times needs a different owner or a smaller scope.
Separate a decision from a discussion. If the executive is not ready to choose, record what information is missing and who will supply it. Do not let the call end with a vague agreement to revisit the topic. A written follow-up sent within a day is more useful than a longer meeting next month.
Separate escalations from routine updates
Create a short escalation path for issues that affect the executive's calendar, the security of the floor, or a live client commitment. The vendor should know whom to call and what response to expect. Routine issues stay in the written update and do not consume call time. This distinction keeps the meeting calm while still giving urgent problems a route.
Give the vendor a single point of contact on your side and ask for the same in return. When the contact changes, update the agenda template and the contact list in the same week. A call that starts with two strangers introducing themselves has already lost its first ten minutes. The vendor management workload review looks at how those relationships accumulate across an executive office.
Rotate the evidence each cycle
Do not let the vendor choose the same favorable measure every month. Rotate at least one measure so the call examines a different part of the service. Compare the current result with the prior three cycles rather than with a single month. A trend line is harder to explain away than a one-off number.
Ask the vendor to bring one improvement proposal and one risk for the next cycle. The proposal should name the cost, the owner, and the expected effect on service. The risk should include the vendor's plan to reduce it. This small requirement turns a passive update into a forward-looking conversation.
Close with a written follow-up
Send a short summary after every call with the decisions, the owners, and the next dates. Keep it under one page and put the decision log first. Ask recipients to reply only if a line is wrong, which reduces the reply traffic. File the summary with the agenda so the next cycle starts with the prior record.
Review the agenda format every quarter. Drop any block that has produced no decision or useful evidence for three cycles. Add a block only when a recurring problem needs a standing place. For teams that need help running these routines, contact us to discuss assistant support. The meeting room release rule shows the same discipline applied to another shared resource.
Related Articles
blog
Build a Decision Memo Template for the Executive Approval Queue
A one-page decision memo template that turns a crowded approval queue into clear choices, stated risks, and a recorded outcome the executive can act on quickly.
blog
Build an Executive Reading Folder for Long-Form Briefings
A reading folder structure that gives the executive one place for long-form briefings, a stable naming rule, and a short index that makes the queue easy to enter.
blog
Prepare a Same-Day Visitor Brief for the Executive Suite
A same-day visitor brief that gives the executive the name, purpose, sensitivities, and expected outcome of each visit without exposing unnecessary personal detail.