Set Up a Vendor Call Log With Decision Notes

Vendor calls disappear into personal notes

An executive assistant spends a surprising amount of time on the phone with vendors: software account managers, travel agencies, facilities contractors, couriers, and professional services firms. Each call produces a small agreement. A cost will be held, a delivery will move, a renewal will be paused, or a contact will send updated terms. Those agreements matter, but they often live in a notebook or an email thread that only one person can find.

When that person is on leave or leaves the company, the next assistant inherits a vendor relationship with no reliable history. The vendor remembers a promise that the office cannot confirm. The executive remembers approving something that never made it into the contract. A vendor call log prevents that drift by recording the call, the decision, and the next action in one shared place.

Capture the call before writing the summary

The log should be completed during or immediately after the call, while details are still accurate. Record the date and time, the vendor and product, the names of everyone on the call, and the reason the call happened. Add the current contract or renewal date if it is relevant. These fields seem obvious, but they are exactly what goes missing when a call is summarized from memory a day later.

Then write the substance in two parts. First, what the vendor said, stated as a claim rather than a fact. Second, what the office decided or still needs to decide. This separation matters. "Vendor says the new rate applies from April" is not the same as "We agreed to the new rate from April." Mixing the two creates commitments the executive never approved and makes it impossible to tell later which statements were verified.

Give every decision a named owner and a date

A call log without owners becomes a diary. Every action item needs one person who is responsible, a date by which it will happen, and a clear description of what "done" looks like. If the action is "send updated costs," say who will send it, to whom, and by when. If the action is "review the renewal terms," say who reviews them and what decision they are authorized to make.

The assistant is often the owner of the follow-up, but not always. Sometimes the vendor must send a document, finance must approve a purchase order, or legal must review a change. Record those handoffs explicitly and check them at the next weekly review. The decision log can hold the durable decision, while the call log holds the conversation that produced it. Linking the two prevents a decision from existing only in a phone note that nobody reads.

Separate information calls from approval calls

Not every vendor call needs the executive. A call to confirm a delivery window or update a contact is informational. A call that changes cost, scope, term, or liability is an approval matter. Write that distinction into the log so the assistant knows when to escalate and when to handle the matter directly.

For approval calls, prepare a one-page summary before the call: what the vendor is asking for, what the current terms are, what the alternatives are, and what happens if the office does nothing. Send it to the executive in advance, and record their response in the log. If the executive delegates the decision, note the limit of that authority. A verbal "handle it" is not a blank check, and the log should make the boundary visible to anyone who reviews the file later.

Connect the log to renewal and expiry dates

A vendor call often reveals a date the office did not have: a notice period, a cost lock, a contract anniversary, or a service termination window. Add that date to the document expiry review and to the calendar that tracks renewals. The call log should not become a second calendar. It should feed the calendar that already exists.

At the end of each month, scan the log for dates falling in the next ninety days. Confirm that the owner of each upcoming renewal knows what action is required and when. If a notice period is thirty days, the decision date is thirty days before the anniversary, not the anniversary itself. Recording that math in the log prevents the most expensive vendor mistake, which is missing a cancellation window because everyone assumed someone else was watching.

Review the log for patterns, not just tasks

Once a month, read the log as a whole rather than item by item. Look for vendors who call repeatedly about the same issue, discounts that were promised but never applied, and approvals that took longer than the service warranted. Those patterns are early warnings about a contract that no longer fits the office or a relationship that needs a different owner. Assign one person to review the monthly summary and bring the three most important findings to the next operations meeting.

The SBA's guide to managing a business treats vendor relationships as part of ordinary operations rather than a special project, which is the right frame here. Keep the log simple enough that people update it after every call, and review it often enough that the entries stay trustworthy. A log that is complete but never read is no better than a stack of sticky notes. Put the monthly review on the same calendar as the renewal check so the two routines reinforce each other.

Make the log part of the handover

The final test of a vendor call log is whether a new assistant can use it on their first day. Can they see which vendors are active, who the main contact is, what was last promised, and which decisions are still open? If the answer is no, the log is missing structure or the team is not maintaining it. Add a short index at the top with the active vendors and the owner of each relationship.

Include the log in the handover record for absences and role changes, and give the incoming assistant a fifteen-minute walkthrough. The goal is not perfect documentation. It is enough context to avoid repeating a negotiation, missing a renewal, or promising something the office cannot deliver. If you want help building vendor routines that survive staff changes, contact our team.