Vendor Communication Log
A log for vendor communications, agreements, and open actions.
Choose a design
The same document in 9 designs, same content and editable fields, different styling. Pick the design you like and download that version. Click any design to preview it larger before downloading. The Sample card shows a completed example, filled in with sample details.
Classic Navy
Executive Charcoal
Modern Minimal
Compact
Burgundy
Forest
Teal Professional
Warm Copper
Mono
Sample
Download this template
Choose the file you need, then download it. No sign-up, no payment.
What’s Included in This Resource
Every resource on The Office File provides a complete toolkit rather than an empty, unhelpful document shell:
- Editable Microsoft Word (.docx) template (41 KB)
- Printable PDF version (76 KB)
Sample included: Example: Vendor Communication Log in use. Logging vendor communications in one place: communication log, agreements made, open actions, and log review.
How to Use This Template
Follow these practical steps to customize and roll out this procedure with your team:
1. Log every contact
Record date, channel, parties, subject, and outcome for each contact.
2. Separate agreements from chat
Record agreements in their own table with written-confirmation status.
3. Keep open actions current
Update owners, due dates, and statuses at each review.
4. Review the log regularly
Carry open actions forward and file agreements.
About This Template
Memory fades; written logs do not. This template gives you a structured format for recording events as they happen, with timestamps, descriptions, and responsible persons. Make logging a habit and you will wonder how you ever operated without it.
Logging vendor communications in one place: communication log, agreements made, open actions, and log review.
When to Use This Template
- Handing over shift or project history without relying on memory
- Tracking maintenance, inspections, or checks with dated entries
- Identifying recurring problems by reviewing logged patterns over time
- Maintaining legally defensible records for compliance purposes
- Recording incidents or events as they happen for an accurate timeline
Key Sections Explained
Understanding what goes in each part of the document helps you fill it in correctly the first time:
Date and time
When each entry occurred, contemporaneous timestamps are what give a log its credibility.
Follow-up actions
What needs to happen next, who owns it, and by when, so the log drives action, not just archives history.
Event description
What happened, stated factually. Keep opinion out; record what was observed.
Log title and purpose
What events this log captures and why the record matters.
People involved
Who was present, who acted, and who was notified, names and roles, not just 'someone'.
Frequently Asked Questions
What should never go in a log?
Opinions, speculation, and blame. Record what was observed factually, logs get read in disputes, and editorialising undermines their credibility.
How detailed should entries be?
Enough that someone reading in six months understands what happened without needing to ask you. Names, times, and specific observations beat vague summaries.
Who can access the log?
Define this upfront, especially for sensitive logs like incidents or complaints. Controlled access protects both the subjects and the integrity of the record.
What if we missed logging something?
Add it as soon as possible, clearly marked as a late entry with the actual date of the event and the date of recording. A marked late entry beats a gap or a backdated fiction.