Setting Communication Protocols With Vendors
Set vendor communication protocols that end the "I told the cleaner" problem: one intake channel, response times by priority, and a weekly written record.
Most vendor disputes are not really about the work. They are about a message that went to the wrong person, was never written down, or arrived after the moment when it could still have been cheap to fix. Vendor communication protocols exist to make that impossible, not to add process for its own sake.
The test of a protocol is simple: if the site supervisor, the contractor's area manager and the property manager all left tomorrow, could a new team reconstruct what was asked, what was answered and when? If not, the protocol needs writing.
Key takeaways
- Nominate one intake channel for requests and one for emergencies, and route everything through them.
- Set response times by priority, not by relationship — emergencies, safety issues, service failures and routine requests.
- Confirm every verbal instruction in writing within 24 hours, or it did not happen.
- Keep a site communication log with date, requester, issue, action and closure. This is the record that ends "nobody told us".
- Hold a monthly review with the contractor's supervisor, and escalate in defined steps with a clock.
What is the single biggest cause of vendor communication failures?
The single biggest cause is triangle communication: the tenant tells the property manager, the property manager tells the cleaner, and the contractor's supervisor never hears about it. Information travels, but accountability does not.
Three patterns account for most of it:
- No named contact. Requests go to whoever is on site, and whoever is on site cannot schedule equipment or approve overtime.
- Verbal-only instructions. A quick word in a corridor carries no date, no owner and no deadline.
- Split threads. Half the history is in email, half in text messages, and the newest staff member has none of it.
A written protocol fixes all three by answering four questions before anything goes wrong: who you contact, through which channel, by when they answer, and what happens if they do not. Put the answers in the contract, the site file and the vendor induction, so the protocol survives a change of site manager.
What channels should each type of message use?
Route each message type to a dedicated channel and hold that line. Mixed channels are how instructions get lost.
| Message type | Channel | Who sends | Who receives |
|---|---|---|---|
| Emergency (flood, power, security, biohazard) | Phone call, then written confirmation | Anyone on site | Contractor supervisor and property manager |
| Safety or hazard report | Written log entry plus phone if urgent | Site staff or inspector | Contractor supervisor, copied to manager |
| Service failure or complaint | Written request in the shared log | Property manager | Contractor supervisor |
| Routine request (extra bins, supply top-up) | Shared log | Site staff | Contractor supervisor |
| Scope change or added work | Formal variation in writing | Property manager | Account manager |
Two rules make this work. Emergencies are always phone-first — a written note nobody reads until Tuesday is not an emergency response. And every phone call about anything beyond a two-minute question gets confirmed in writing the same day.
Define what is included in the contract closely enough that "extra" is identifiable: frequencies, areas and equipment. Anything outside that definition needs written approval before the work starts, with a capped value for minor works and agreed rates for hourly labour, equipment, consumables and after-hours work. Record who approved it and when — an approval without a name is not an approval.
How quickly should a vendor respond?
Set response times by priority, and define each priority by example so nobody has to guess. A vendor cannot be held to a response time the contract never specified.
| Priority | Example | Acknowledge | Resolve or give a dated plan |
|---|---|---|---|
| 1 — Emergency | Water escape, power loss affecting cleaning, blood or body fluid spill in a public area | Within 30 minutes | Same day, or interim control in place |
| 2 — Safety | Blocked exit, wet floor without signage, chemical left unlabelled | Within 2 hours | Same day |
| 3 — Service failure | Restrooms unserviced, waste not cleared, floors not done to schedule | Within 4 business hours | Within 2 business days |
| 4 — Routine | Consumable top-up, minor damage report, scheduling request | Within 1 business day | Within 5 business days |
Write the table into the contract rather than a side letter, and state the consequence of a missed response. A response time with no consequence is a suggestion.
Blood and body fluid incidents deserve their own paragraph in the protocol, because they combine urgency with a specific method. CCOHS sets out the sequence for decontaminating blood and body fluid areas, including the 1:100 household bleach dilution and the handling of soiled materials, in its sanitation and infection control guidance for cleaning staff. Mirror that sequence in your protocol so the on-site response is not improvised at 11 p.m.
When should you escalate, and to whom?
Escalate automatically when a response time is missed — not when you have run out of patience. An automatic trigger removes the personal element and makes escalation routine rather than confrontational.
A four-step ladder works for most contracts:
- Step 1 — Supervisor. The issue is logged and the supervisor has the stated response window. Most issues end here.
- Step 2 — Area manager. Triggered by a missed response time, or the same issue logged three times in a rolling 30 days. A written action plan with dates is required.
- Step 3 — Account manager. Triggered by two missed action plans, or any critical item not closed within 5 business days.
- Step 4 — Formal notice. Triggered by a failure the contract defines as material. This is where the notice to perform process begins.
Keep a clock on each step and record it. Escalation that depends on someone's mood is escalation that gets applied inconsistently across a portfolio, which is exactly what contractors learn to work around.
What should a site communication log contain?
A communication log contains five fields per entry: date and time, who reported it, what was observed, what was requested, and when it closed. Keep it in one place both parties can see, and make these rules explicit:
- Every entry gets a reference number, so "the third time this month" becomes a checkable fact.
- Photos attach to the entry, and to the specific item where an inspection produced them.
- Closure requires confirmation, not silence. An entry closes when the requester accepts the fix.
- Nothing is deleted. A re-opened item gets a new entry referencing the original.
NeatScore records inspections against weighted items with a photo per item, and tracks deficiencies with an owner and a closure date, so the deficiency list and the communication log describe the same reality. The wider reporting picture — what goes to the owner and what stays operational — is covered in the vendor reporting format owners actually read. For where communication sits in the wider contract cycle, see the property management vendor management framework.
Not regulatory advice. Incident reporting duties vary by province and by the type of incident. Confirm your obligations with your provincial regulator and follow the facility's own procedures.
What meeting rhythm should the contract set?
Set three meetings and cancel none of them. The weekly touchpoint (15 minutes) covers open deficiencies and staffing gaps for the coming week, with no minutes beyond the log. The monthly review (45–60 minutes) covers inspection scores, item-level failures, complaint trends and dated actions, with minutes issued within 24 hours. The quarterly review (60–90 minutes) covers the quarter's trend, performance against thresholds, variation requests and seasonal work.
The monthly review is the one that changes behaviour, provided the data is shared in advance. Sending the report an hour before the meeting turns a review into a reading exercise.
How do you handle scope changes without a dispute?
Handle scope change in writing before the work starts, at a stated cost or rate. Verbal scope creep is the most common source of invoice disputes later, and the invoice side — matching work to evidence before paying — is where most of them surface. Paying vendors: invoices, variations and disputes sets out the three-way check that prevents it.
How do you keep the protocol alive across scope and staff changes?
Two habits carry it: scope change in writing before the work starts at a stated cost or rate, and the protocol stored where a new person will actually look. Include a one-page contact sheet at the front of the site file — names, roles, numbers, email, escalation order — and cover it in vendor induction with a signed acknowledgement before the first shift.
The cheapest test of whether the protocol is real is an annual desk check: pick three closed log entries at random and confirm each has a date, an owner and a confirmed closure. If three random entries cannot be traced end to end, the protocol is decoration.
Frequently asked questions
Should tenants contact the cleaning contractor directly?
No — route tenant requests through the property manager or the shared log so there is one record and one accountable owner. Where a tenant must reach someone directly, give them the intake channel rather than an individual's mobile number, and make sure requests raised that way still land in the log.
What if the contractor refuses to use our log?
Make the log the contractual reporting method, and state that requests outside it are not treated as instructions. Most resistance disappears once the contractor sees that the same log protects them when an accusation is unfounded.
How do we handle communication across multiple sites?
Use one protocol template with a site-specific contact sheet, so the rules are identical everywhere and only names and numbers change. A portfolio where each site invents its own escalation ladder cannot be managed or compared.
Are group chats a suitable channel for vendor communication?
Only for time-critical coordination within a single site, and never as the system of record. Chat threads are hard to search months later and leave no reliable trail. Move anything with a deadline into the log the same day.
How long should communication records be kept?
Keep log entries, inspection reports and closure confirmations for the contract term plus one renewal cycle — commonly three to five years. The value appears late, in a dispute or an insurance question about an event long before anyone currently on site started.
Write it down, then hold the line
A communication protocol turns a complaint into a dated request with an owner and a deadline. Write the four answers down — channel, contact, response time, escalation — and enforce them evenly across every site.
NeatScore gives property and facilities managers the record underneath those protocols: weighted item lists scored on the APPA 1–5 scale, critical items flagged, photos per item, offline inspections that sync when the device reconnects, branded PDF reports, deficiency tracking with owners and dates, and a multi-site dashboard. Start a free 14-day trial or see pricing.
