Published October 22, 2026
Vendor follow-up is a natural task to delegate. It is repetitive, time-bound, and mostly administrative. It is also a place where an assistant can accidentally commit the company to a price, a scope, or a delivery date.
The solution is not to keep every email with the owner. It is to separate coordination from commitment. The assistant coordinates the request, the owner makes the commitment.
Table of contents
- Define the boundary in verbs
- Build a vendor request record
- Chase without implying agreement
- Assemble the comparison
- Escalate the four commitment moments
- Sources
- Frequently Asked Questions
Define the boundary in verbs
Write the assistant's authority as a verb list.
May: request a quote, confirm receipt, ask for missing documents, schedule a call, restate the approved scope, and compile a comparison.
May with approval: share budget ranges, confirm a delivery window, introduce a legal contact, or disclose evaluation criteria.
May not: select a vendor, accept a price, change scope, sign an agreement, promise payment terms, or authorize work to begin.
The verb list goes in the task brief. It prevents a well-meaning assistant from interpreting "get this moving" as permission to agree.
Build a vendor request record
Use one record per vendor per request:
- vendor legal name and contact
- request ID and the internal owner
- scope summary and required deliverables
- approved budget range, if any
- deadline for the quote and the decision date
- evaluation criteria and their weights, if disclosed
- documents received and missing
- communications log
- current state: requested, received, clarifying, evaluated, selected, declined
Link the record to the approved scope document. If the scope changes, create a new request ID rather than editing the old one. Otherwise the comparison becomes impossible.
Chase without implying agreement
Follow-up messages should be factual and neutral.
Weak: "This looks good, can you start Monday?" Better: "Thank you. We have received the proposal. The evaluation is scheduled for October 27 and we will confirm next steps after that date."
The second message keeps the vendor informed without creating an expectation of award. It also avoids the common mistake of thanking a vendor in a way that sounds like acceptance.
If a vendor asks a question outside the approved scope, route it to the owner. Do not improvise a commercial answer to keep the conversation moving.
Assemble the comparison
The comparison should show the same dimensions for every vendor:
| Dimension | What to show |
|---|---|
| Scope coverage | Included, excluded, and assumed items |
| Price | Total, unit basis, taxes, and optional items |
| Timeline | Start date, milestones, and dependencies |
| Assumptions | What the vendor assumes the buyer will provide |
| Evidence | References, certifications, or samples |
| Risk | Missing information that could change the decision |
Do not add a recommendation unless the owner asks for one. If asked, separate the evidence from the recommendation and state the trade-off. The NIST Privacy Framework is a useful reminder that vendor data handling and access should be part of the evaluation when personal data is involved; it is not a vendor-selection scorecard.
Escalate the four commitment moments
Stop and route to the owner when:
- A vendor asks for a price commitment or a budget confirmation.
- A vendor asks to change scope, timeline, or payment terms.
- A vendor requests signatures, purchase orders, or access credentials.
- A vendor says work has started or an invoice has been issued.
Each escalation should state the request, the approved position, the consequence of delay, and the decision needed. The assistant can draft the response for approval.
Sources
- NIST Privacy Framework
- O*NET OnLine: Executive Administrative Assistants
- U.S. Department of Labor: Hiring
- Bureau of Labor Statistics: Occupational Outlook Handbook
Frequently Asked Questions
Can an assistant tell a vendor the budget?
Only if the owner has approved disclosing that range for that request. A budget shared in one deal is not permission to share it in another.
Should the assistant recommend a vendor?
The assistant can present criteria and evidence. A recommendation is acceptable only when the owner asks for one and the assistant states the basis and the uncertainty.
What if a vendor starts work before approval?
Record the date and what was communicated, notify the owner immediately, and do not confirm or expand the work. The owner decides whether to authorize, pause, or stop it.
Review cadence
Review the follow-up queue weekly. Separate vendors who are waiting on the business from those the business is waiting on, and record the next action for each. If a follow-up needs an approval the assistant cannot give, escalate it with the decision and the deadline. Do not let a polite check-in replace a decision.
A good follow-up queue has one next action, one owner, and one date per vendor, and a clear rule for when a follow-up becomes an escalation. Review the oldest items first and close the ones that no longer matter. A queue that only grows is a sign that the business has not decided what it wants from the vendor. The record should show the decision, not just the last contact date.