Move vendor calls out of the founder's inbox without losing control
A vendor directory and handoff checklist covering contact ownership, backup coverage, approvals, renewals and escalation rules.
Changing an email address is only one part of a vendor handoff. Transfer the context, the authority limits and the follow-up schedule so a coordinator can act without sending every question back to the founder.
Audit the relationships before redirecting calls
Review recent invoices, recurring charges, agreements and actual requests to find active providers. Include occasional providers used for repairs. A list assembled only from the founder's phone can miss a contract managed by accounting or a warranty held by the landlord.
For each vendor, distinguish the commercial owner from the day-to-day contact. Record which services are active, the locations involved and where the current agreement can be found. A vendor with multiple local branches may require a different dispatch contact for each site.
Create a directory that supports an action
The directory should answer what to do next, not simply identify a company. Keep contract references and service instructions with each relationship. Use approved shared accounts or controlled document access; do not place passwords in the contact record.
Assign someone to maintain the directory when a service changes or a contact leaves. Add a last-verified date and an owner for missing information. A small set of current records is more dependable than a large database nobody checks.
| Field | What to record |
|---|---|
| Service and site | Scope, exclusions and site-specific access instructions |
| Contacts | Dispatch, account contact, client owner and backup |
| Authority | Who can approve work and the written limit |
| Timing | Service hours, update expectations, renewal notice date |
| Evidence | Agreement location and latest service history |
Send a handoff with clear boundaries
Tell each provider which operational requests now go to the coordinator, when the founder remains involved and how urgent issues should be escalated. Ask for acknowledgment and confirmation that their records were updated. Inform employees at the same time, or they may continue directing vendors to the old contact.
Keep commitments separate from coordination. Receiving a quote does not authorize a purchase, and discussing renewal options does not authorize signing. Written approval limits should cover both the dollar amount and the type of commitment. The client's purchasing policies still apply.
Prepare a decision rather than forwarding a thread
When a vendor asks about a renewal, the coordinator should assemble current terms, the notice deadline, the proposed change and the options. The founder then has a decision to make, rather than a chain of messages to reconstruct. If a key document is missing, identify that gap and its owner.
Routine appointment scheduling can remain with the coordinator when it is within scope. A new recurring charge, a change in service level or access to a restricted area should follow the agreed approval path. A backup approver matters when the primary person is away.
Test the handoff on a real category
Choose one category, such as printer service, and walk through a routine request, a missing provider response and a quote requiring approval. Check whether a backup coordinator can identify the next action from the shared record. Do not test by sending live purchases or unnecessary service calls.
At review, count how often a request returned to the founder and why. Some returns are valid decisions. Others expose missing documents or unclear authority. Fix those gaps before adding more vendors. A remote partner can manage communication, but a named local contact is still needed for deliveries and site access.
Sources and reading limits
The workflow and templates are editorial proposals. External sources provide the context described below; they do not verify SFI results or delivery capabilities.
- City Wide — facility services management ↗
Official service description; competitor capabilities do not establish SFI capabilities. Accessed November 4, 2026.