A regional manager fires the landscaping contractor on a Friday afternoon. The email is short and, after eight months of missed mowing cycles and two ignored warnings, deserved. On Monday morning three things surface. The irrigation controllers at four properties run on a cloud account the contractor set up in its own name, and nobody at the operator has the password. The gate codes the contractor's crews used are the same codes the residents use, and the contractor still knows them. And the accounting team finds a $9,000 prepaid order for spring mulch, placed through the contractor in February, of which $3,400 has been delivered. The contractor, now unpaid and unhappy, is not returning calls.
None of that was a surprise the operator could not have seen. All of it was in the vendor file, the contract and the purchase ledger. It surfaced on Monday because terminating a vendor was treated as an email, and it is not: it is a project with a start date, a sequence, and one rule that governs the sequence. The vendor's last invoice is the one thing you still hold. The vendor's passwords, keys and prepaid balances are theirs. So access is transferred before the final payment is released, never after.
This post covers when to terminate and the evidence to have first, what to read in the contract before writing anything, a 30-day off-boarding plan you can run as a table, two annotated letters (for cause and for convenience), the access and credentials checklist, how warranties survive the exit, what to tell tenants and staff, and how to close the vendor file so the next manager does not rehire the same contractor by accident.
Definition
Terminating a vendor in property operations is the planned exit of a maintenance contractor or service provider from a property or portfolio: ending the contract on its terms (or at expiry), transferring access, credentials, keys, records and warranties back to the operator, settling open work orders, prepaid balances and the final invoice, and lining up the replacement so service does not lapse. RIOO describes this as the eighth stage of the vendor lifecycle, and its governing rule is that access is transferred before the final payment is released. Vendor off-boarding is the operational half of that exit; the termination notice is only its first document.
At a glance
| Question | Answer |
|---|---|
| When can you terminate? | For cause after a documented breach and an expired cure period; for convenience on the notice the contract gives (commonly 30 to 90 days); or at expiry by not renewing |
| What is termination for cause vs convenience? | Cause: the vendor breached, you can end it faster and usually without a fee, but you need evidence and must follow the cure step. Convenience: no breach needed, but you serve the full notice and pay any early-termination fee |
| What do you read first? | Notice period, cure period, termination fee, prepaid and deposit terms, retention or holdback, warranty survival, return-of-property and transition clauses |
| How long does off-boarding take? | Plan on 30 days from the decision, with the notice served around day 5 and the final payment released around day 30 |
| What is the sequence rule? | Replacement lined up, then notice, then access and records transferred, then open work reconciled, then the final invoice released |
| What is at risk on the Friday email? | Notice fees you still owe, a prepaid balance you cannot recover, emergency replacement at a premium, and credentials you have to reset at your cost. In the example: about $18,950 avoidable |
When to terminate, and the evidence you need
There are three doors out of a vendor relationship and they are not interchangeable.
1. Termination for cause: is available when the vendor has breached the contract: missed SLA clocks past the termination trigger, lapsed insurance, safety violations, unauthorised subcontracting, billing for work not done, or whatever else the contract names. It is faster and usually carries no fee, but it has to be earned. Almost every contract requires written notice of the breach and a cure period (typically 10 to 30 days) before the termination takes effect, and a for-cause exit that skips the cure step converts into a wrongful termination the vendor can claim damages for. The evidence has to exist before the notice is written: scorecard history, SLA measurements, dated warnings, photographs and the tenant complaints, all in the vendor file. The vendor scorecard post sets out what that evidence file needs to contain before you act, and this post does not repeat it.
2. Termination for convenience: needs no breach. You serve the notice the contract specifies (30, 60 or 90 days is common), pay any early-termination fee, and the relationship ends on the date the notice runs out. It is the cleaner exit when the vendor is adequate but you have found better, when you are consolidating trades, or when the for-cause evidence is thinner than you would like. The cost is the notice period, during which the vendor is still entitled to the work or the fee.
3. Non-renewal at expiry: is the quietest exit. Most maintenance contracts renew automatically unless one party gives notice before a deadline, often 60 or 90 days before the anniversary. Missing that deadline commits you to another term. If the annual review has decided to replace a vendor, the non-renewal notice is a calendar entry, not a confrontation.
Related reading: Vendor Performance Review Cadence: Weekly, Monthly, Quarterly, Annual
The decision of which door to use is a comparison of two numbers: what the for-convenience notice costs you, and what the for-cause route risks if the evidence does not hold. When the scorecard file is thin, convenience is usually cheaper than a dispute.
Before any of the three, one question sits above the rest: can you replace them? If the vendor is the only licensed elevator contractor within two hours, or handles 40% of your work orders, the exit plan starts with the replacement, not the notice. The concentration risk post covers how to tell whether a vendor is replaceable; this post assumes you have checked.
Read the contract first
The termination clause is rarely the only clause that matters. Before the notice is drafted, someone reads the whole agreement with a highlighter and fills in a short table like this one. It takes an hour and it is the hour that saves the most money.
| Clause | What to record | Why it matters |
|---|---|---|
| Term and renewal | Start date, current term end, auto-renewal, non-renewal notice deadline | Expiry may be the cheapest exit, if you have not missed the deadline |
| Termination for convenience | Notice period, whether notice must be written and how it is served (email, recorded post, registered address), any early-termination fee | Sets the earliest effective date and the cost |
| Termination for cause | Named breaches, notice-of-breach requirement, cure period, whether repeated breaches shorten the cure | Defines what you have to prove and how long you must wait |
| Fees during notice | Whether the monthly fee is payable if you stop dispatching work during the notice period | You may owe the fee whether or not you use the vendor |
| Prepaid amounts and deposits | Any prepaid services, materials, retainers or deposits held by either party; refund terms | The $9,000 mulch order lives here |
| Retention or holdback | Any percentage held back on invoices and when it releases | What you still hold after the final invoice |
| Warranties | Workmanship warranty period, whether it survives termination, manufacturer warranties on installed equipment | Warranties on last year's roof do not end because the roofer did |
| Return of property | Keys, fobs, access cards, equipment, records, drawings, credentials; deadline; who pays for re-keying if not returned | The clause that makes the access checklist enforceable |
| Transition assistance | Any obligation to hand over records and cooperate with the replacement, and whether it is paid | Lets you require a handover meeting |
| Confidentiality and data | Tenant data, access codes, security information; obligation to delete | Governs what the vendor may keep |
| Subcontractors | Whether the vendor's subcontractors have separate rights or liens | A subcontractor unpaid by your vendor can lien the property |
| Insurance survival | Whether completed-operations cover continues after the contract | Claims for work done during the term can arrive after it |
| Dispute resolution | Mediation, arbitration, governing law, notice addresses | Determines where any argument goes |
If the contract is a one-page proposal signed years ago with none of these clauses, the exit is governed by the law of the jurisdiction and by whatever course of dealing has built up, which is a reason to involve counsel earlier rather than later. Our post on property maintenance contracts covers what the agreement should have contained; the vendor SLA template includes the termination-trigger clause that makes a for-cause exit provable.
The 30-day off-boarding plan
The plan below assumes a convenience termination with 30 days' notice, or a for-cause termination after the cure period has expired. Stretch or compress the days to match the contract's notice period; keep the order. Day 0 is the decision, not the notice.
| Day | Step | Owner | Done when |
|---|---|---|---|
| 0 | Decision recorded with the reason, the door being used (cause, convenience, expiry) and the evidence file reference | Ops director | Decision note filed in the vendor record |
| 0 to 3 | Contract read and the clause table above completed; counsel consulted if for cause or if the contract is silent on exit | Ops + legal | Clause table filed |
| 1 to 5 | Replacement vendor identified from the roster or a quick bid, and onboarding started (identity, insurance, banking, rate card) | Ops + accounting | Replacement at Day 0 readiness or a dated plan to reach it |
| 1 to 5 | Access inventory compiled from the vendor file: every key, fob, code, credential, account and portal login the vendor holds (see the checklist below) | Ops + property managers | Inventory signed by each property manager |
| 5 | Notice served in the form the contract requires, with the effective date, the return-of-property deadline and the handover request; a copy filed in the vendor record | Ops director | Proof of service on file |
| 5 to 7 | Open work orders listed; each marked complete-by-vendor, reassign-to-replacement, or cancel; the vendor told which is which in writing | Ops | Work order list agreed |
| 5 to 10 | Purchase ledger reviewed: open POs, prepaid balances, deposits, retention, unbilled work; a draft reconciliation prepared | Accounting | Draft reconciliation |
| 7 to 14 | Codes and credentials the vendor knows but does not own are changed: gate codes, alarm codes, key-safe combinations, shared passwords; residents notified of any code change | Property managers | Change log complete |
| 10 to 20 | Handover meeting: records, drawings, manuals, service histories, warranty documents, equipment serials and controller or cloud-account ownership transferred; keys, fobs and cards counted against the inventory | Ops + replacement vendor | Handover receipt signed by both sides |
| 10 to 20 | Accounts the vendor owns on the operator's behalf (irrigation, BMS, smart-lock, monitoring, supplier accounts) transferred to an operator-owned login, or rebuilt if the vendor will not cooperate | Ops + IT | Operator holds admin on every account |
| 15 to 25 | Replacement vendor shadows or takes over sites; site walk with both vendors where the contract allows | Ops | Replacement dispatched on live work orders |
| 20 to 28 | Final invoice received; reconciled against completed work orders, prepaid balances and deposits; disputes raised in writing | Accounting | Reconciliation agreed or disputed items listed |
| 25 to 30 | Access confirmed: inventory closed, unreturned items re-keyed at the vendor's cost where the contract allows, portal and system access deactivated | Ops + IT | Access sign-off filed |
| 30 | Final payment released, net of retention, deductions and undelivered prepaid items; retention held to the warranty or holdback date | Accounting | Payment scheduled; retention release date diarised |
| 30 | Tenant and staff communication updated; vendor record closed with reason code and do-not-rehire flag if applicable | Ops | Vendor file closed |
Two things about the order. The replacement is lined up before the notice goes out, because a vendor on notice has no reason to be responsive and your properties still need service. And the final payment is the last row, after the access sign-off, because it is the only lever you still hold once the notice has been served.
What the Friday email cost
Back to the landscaping contractor. Monthly fee $6,500; 60 days' notice for convenience; $9,000 prepaid for mulch, $3,400 delivered.
The Friday email. No notice served, so the contractor claims the 60-day fee anyway: $13,000, which the contract supports. The contractor disputes the prepaid balance and holds the $5,600 undelivered value for five months while the argument runs. A replacement landscaper is found on Monday at an emergency rate 35% above standard for the two months it takes to bid properly: $6,500 × 1.35 × 2 = $17,550 against $13,000, a $4,550 premium. Four irrigation controllers are reset and re-registered by a technician because the cloud account cannot be recovered: $1,400. The gate codes at four properties are changed, and 212 residents are notified. Avoidable cost: $13,000 + $4,550 + $1,400 = $18,950, plus the $5,600 tied up.
The 30-day plan. The notice is served on day 5 and the contractor works the notice period, so the $13,000 pays for two months of actual service rather than for nothing. The prepaid balance is reconciled in the final invoice: $5,600 credited against the last payment. The replacement is bid and onboarded during the notice period at the standard rate. The irrigation account is transferred at the handover meeting because the final payment has not been released. Avoidable cost: close to zero, and the $5,600 comes back as a deduction on day 30.
The difference is not cleverness. It is sequence.
The termination letter: two annotated samples
A vendor termination letter has one job: to end the contract on a date, in a way the contract recognises, without saying anything you would not want read aloud in a dispute. Both samples below are deliberately short. Everything about performance history belongs in the evidence file, not in the letter; the letter refers to it and stops.
Letter A: termination for cause
[Operator letterhead]
[Date]
[Vendor legal name, registered address, as stated in the contract]
Sent by [method the contract requires] and by email to [contract notice address]Re: Termination for cause. Maintenance Services Agreement dated [date], [property or portfolio name]
We refer to our notice of breach dated [date] (the "Breach Notice"), served under clause [x] of the Agreement, which identified the following breaches: [one line each, e.g. "failure to meet the P1 restore time on work orders 4471, 4502 and 4519"; "lapse of general liability cover between [date] and [date]"].
Annotation: this paragraph does the legal work. It ties the termination to a prior breach notice and to the clause that allows for-cause termination. If you have not served a breach notice and waited out the cure period, you cannot send this letter yet.
The cure period under clause [x] expired on [date]. The breaches identified in the Breach Notice were not remedied within that period. [If applicable: the further breach on [date], work order [number], is a repeat of a breach previously notified.]
Annotation: state the fact of non-cure and the date. Do not characterise it ("wholly inadequate", "unacceptable"). Adjectives invite argument; dates do not.
We therefore terminate the Agreement for cause with effect from [date] (the "Termination Date"), under clause [x].
Annotation: one sentence, one date. For cause, the Termination Date can usually be immediate or short; check the clause.
By the Termination Date you are required under clause [x] to return all keys, fobs, access cards, equipment and records belonging to [operator] or the properties, to transfer to us administrative control of [list any accounts: irrigation controllers, monitoring accounts, supplier accounts], and to delete access codes and tenant information in your possession. A schedule of items to be returned is attached. Items not returned by the Termination Date will be replaced or re-keyed at your cost under clause [x].
Annotation: this is the return-of-property clause turned into an instruction with a deadline and a consequence. Attach the access inventory as the schedule.
Open work orders [numbers] are to be completed by [date]. Work orders [numbers] are cancelled with effect from today and should not be attended. No further work is to be undertaken without written instruction from [named person].
Annotation: prevents the vendor from generating billable work during the wind-down and makes clear which jobs it may still invoice.
Please submit your final invoice by [date], itemised against work order numbers, together with a statement of any prepaid amounts, deposits and materials held. Payment will be made in accordance with clause [x] following reconciliation and confirmation of the return of property, less any amounts due to us under the Agreement.
Annotation: sets the final-invoice deadline and states, without threat, that payment follows reconciliation and return of property. This is the sequence rule in contractual language.
Warranties given under clause [x] in respect of work completed before the Termination Date continue in accordance with their terms, as do your obligations under clauses [confidentiality, insurance, indemnity].
Annotation: names the surviving clauses so the vendor cannot later argue they ended with the contract.
This letter is without prejudice to any other rights or remedies of [operator] under the Agreement or otherwise.
[Signature, name, title]
Attachments: Breach Notice dated [date]; Schedule of property and accounts to be returned
Letter B: termination for convenience
[Operator letterhead]
[Date]
[Vendor legal name, registered address]
Sent by [method the contract requires] and by emailRe: Notice of termination. Maintenance Services Agreement dated [date], [property or portfolio name]
Under clause [x] of the Agreement, we give notice that the Agreement will terminate on [date] (the "Termination Date"), being [number] days from the date of this notice.
Annotation: no reason is required and none should be given. A reason invites a reply about the reason. If the vendor asks, "a portfolio-wide review of contracted services" is a complete answer.
Until the Termination Date the Agreement continues in full effect and we expect services to be delivered in accordance with it. [If applicable: from [date] we will reduce dispatched work as the transition proceeds; the monthly fee remains payable under clause [x].]
Annotation: keeps the vendor working during notice and acknowledges the fee position so it is not disputed later.
We would like to arrange a handover meeting during the week of [date] to transfer records, service histories, manuals, warranty documentation and administrative control of [list any accounts], and to reconcile keys, fobs and access cards against the attached schedule. Clause [x] provides for your cooperation with transition, [and we confirm this will be paid at the rates in Schedule [x] / and this is included in the monthly fee].
Annotation: a convenience exit can be cordial, and the handover meeting is where the vendor's goodwill is worth the most. Say whether transition time is paid; unpaid handover requests get ignored.
Please submit your final invoice within [number] days of the Termination Date, itemised against work order numbers, with a statement of prepaid amounts, deposits and materials held. Payment will be made in accordance with clause [x] following reconciliation and confirmation of the return of property.
Warranties in respect of work completed before the Termination Date continue in accordance with their terms, as do clauses [confidentiality, insurance, indemnity].
We appreciate the service provided over the term of the Agreement.
[Signature, name, title]
Attachment: Schedule of property and accounts to be returned
A contractor termination notice sent to a sole trader or a small firm without a formal contract follows the same shape: the date the work ends, what is to be returned, which jobs may still be invoiced, and when the final invoice is due. Keep it as short.
Access, keys and credentials checklist
This is the list that should have been compiled at onboarding and updated at every review. If it was not, it is compiled now, property by property, and the property managers sign it, because they are the people who know which contractor has which key. The columns matter: an item is not closed until the last column is filled.
| Category | Items to inventory | Action at exit | Closed when |
|---|---|---|---|
| Physical keys | Master keys, sub-masters, unit keys, plant room, roof, riser, meter room, mailroom, bike store | Counted back against the issue log; unreturned keys trigger a re-key at the vendor's cost where the contract allows | Count matches or re-key completed |
| Fobs, cards and transponders | Building access fobs, car park cards, lift cards, vehicle transponders | Deactivated in the access-control system on the effective date, whether or not returned | Deactivation log shows each credential off |
| Codes the vendor knows | Gate codes, key-safe combinations, alarm codes, intercom bypass codes, lockbox codes | Changed at every property the vendor served; residents and other vendors notified | Change log complete |
| Accounts the vendor set up | Irrigation and lighting controllers, BMS and HVAC cloud portals, smart locks, CCTV and monitoring, leak-detection sensors, EV chargers | Ownership transferred to an operator-owned admin login; vendor user removed; recovery email and phone changed | Operator holds admin and has tested a password reset |
| Accounts in the property's name opened by the vendor | Supplier trade accounts, equipment rental, waste and recycling, parts suppliers | Statement obtained; account closed or the authorised signatory changed | Supplier confirms in writing |
| Operator systems | Vendor portal login, work order system, email aliases, shared drives, tenant portal admin rights, messaging groups | Deactivated on the effective date; mailbox or alias redirected to the replacement contact | Access log shows deactivation |
| Documents and data | Service histories, as-built drawings, equipment schedules, test certificates, permits, tenant contact lists, access lists | Delivered at handover; vendor confirms deletion of tenant and security information under the confidentiality clause | Handover receipt and deletion confirmation on file |
| Equipment and consumables | Operator-owned tools, spare parts stock, uniforms with the property's branding, signage, vehicles or trailers | Returned or bought out at agreed value | Return receipt or buyout in the final reconciliation |
| Third-party registrations | Vendor listed as emergency contact with the alarm company, fire authority, lift inspector, utility or council | Contact changed to the operator or the replacement | Confirmation from each third party |
The fourth row is where most exits go wrong and where the Friday email in the opening example did. Cloud-connected equipment is routinely registered by the installing contractor under the contractor's own email address, because that is the fastest way to commission it. The property owns the hardware; the contractor owns the login. The fix at exit is a transfer to an operator-owned account, tested by performing a password reset from the operator's side before the final payment is released. The fix at onboarding, for every future vendor, is a rule that every account is registered to an operator address from day one.
Warranties survive termination, if you keep them
The roof installed last year carries a manufacturer's warranty on the membrane and the contractor's workmanship warranty on the installation. Neither ends because you have ended the contract, but both can become unenforceable in practice if the paperwork leaves with the vendor.
At handover, collect for every installed asset the warranty certificate, the serial number, the installation date, the commissioning report and any registration reference. Check whose name the manufacturer's warranty is registered in; where it is the contractor's, ask the manufacturer to transfer it to the owner, which most will do with a letter from the installer. Record the workmanship warranty period from the contract and confirm in the termination letter (as both samples do) that it survives. Diarise the warranty end dates in the asset record so a failure inside the period is claimed rather than paid for. Where the contract provides a retention or holdback tied to the defects period, hold it to that date and release it against the calendar, not against the vendor's request. And note that a workmanship warranty from a contractor that has ceased trading is worth little, which is one more argument for manufacturer warranties registered to the owner.
Completed-operations insurance is the related point. A claim arising from work the vendor did during the term can arrive after the exit. Keep the certificates of insurance that were on file during the term in the closed vendor record; they are the evidence of what cover existed when the work was done.
Tenant and staff communication
Residents do not need to know why a vendor has gone. They need to know that service continues, who to contact, and whether anything they use has changed. A short notice through the tenant portal or by email on the effective date covers it: a new contractor is responsible for [service] from [date]; requests continue to go through the normal channel; [if applicable] gate or entry codes have been changed and the new code is [delivered separately]. Nothing about the previous vendor.
Staff need more. Site teams, concierge and security are told the effective date and instructed that the outgoing vendor's crews are no longer to be admitted after it, with the replacement's crew list and vehicle descriptions supplied in its place. Anyone who takes calls is told where to send the outgoing vendor's queries (accounts, for the final invoice; the ops director, for anything else) so that the vendor cannot re-open the relationship through a friendly caretaker. Other vendors that share access codes are told of the change. And the person who approves invoices is told the vendor is closed, so that a late invoice for "additional works" in the last week gets queried rather than paid.
The tone throughout is neutral. A vendor that is spoken about badly to residents or to other contractors has a defamation claim to add to whatever else it may be considering, and the operator's staff will work with that vendor's people again somewhere.
Recording the exit in the vendor file
The last step in the plan closes the vendor record, and how it is closed decides whether the same contractor is rehired at another property in two years by a manager who never heard the story. The hub post describes the vendor file as a record with a start date, terms, critical dates, a ledger and an expiry; the exit fills in the expiry.
| Field | What to record |
|---|---|
| Status | Terminated (cause), terminated (convenience), not renewed, or ceased trading |
| Effective date | The Termination Date from the letter |
| Reason code | A short standard code (performance, insurance, safety, billing, consolidation, cost, vendor request) plus a one-line note |
| Evidence reference | Where the scorecard history, breach notice, warnings and photographs are filed |
| Notice served | Date, method, proof of service, copy of the letter |
| Financial close | Final invoice amount, deductions, prepaid credit, retention held and its release date, final payment date |
| Access close | Date the access inventory was signed off; any items unreturned and how they were dealt with |
| Warranties | Assets with surviving warranties, registered owner, end dates |
| Rehire flag | Eligible, eligible with conditions, or do not rehire, with the approver's name |
| Reference policy | Whether the operator will give a reference, and what it will say |
A closed record with a do-not-rehire flag is a control. A closed record with nothing but a status is a gap that the next emergency will fill with the most familiar phone number.
Key facts
- Terminating a vendor is a 30-day project with a fixed sequence, not an email: replacement lined up, notice served, access and records transferred, open work reconciled, final payment released last (RIOO's sequence rule).
- The three exits are termination for cause (breach, notice of breach, cure period, then termination), termination for convenience (full notice period and any fee, no reason needed), and non-renewal at expiry (a calendar deadline, often 60 to 90 days before the anniversary).
- Before drafting anything, read the contract for notice, cure, fees during notice, prepaid amounts, retention, warranty survival, return of property, transition assistance and subcontractor rights.
- The termination letter states dates, clauses and instructions and nothing else; performance history belongs in the evidence file, which the scorecard post describes.
- Cloud accounts for irrigation, BMS, smart locks and monitoring are the most commonly missed access item because they are registered to the contractor's email; transfer them and test a password reset before the final payment.
- Workmanship and manufacturer warranties survive termination; collect certificates and serials at handover and re-register manufacturer warranties to the owner.
- In the worked example, the unplanned Friday exit cost about $18,950 in avoidable notice fees, emergency premiums and resets, plus $5,600 of prepaid materials tied up for months.
Running the exit from the system
Everything in the plan above is a read from a record that should already exist: the contract terms and critical dates, the open work orders, the purchase orders and prepaid balances, the invoices and retention, the documents and the access inventory. An exit run from memory, or from a folder of emails, is the one that finds the $9,000 mulch order on Monday.
In RIOO on NetSuite, work orders are created, prioritised, assigned to technicians or vendors and monitored to completion in service request and task management, which also centralises communication, documentation and task assignments for each vendor, so the open work order list at day 5 is a filter rather than a phone round. On the financial side, vendor management and accounts payable holds each supplier's profile with its purchase history, past payments and credit memos, matches invoices against purchase orders, flags duplicates before approval, and schedules payments, which is where the final invoice is reconciled against the ledger before it is released. For the checks that come after the exit, the vendor compliance post explains why the certificate on file is not the whole story.
Run the exit in order. Copy the 30-day table into your own tracker, fill the owner column with names, and do not release the final payment until the access row is signed off. To see how work orders, vendor records, purchase orders and payments sit in one system, book a walkthrough of RIOO's vendor management and accounts payable.
Frequently asked questions
Q1. What is the difference between termination for cause vs convenience?
Termination for cause ends the contract because the vendor breached it: you serve a notice of breach, wait out the cure period the contract gives, and if the breach is not remedied you terminate, usually without a fee and on a short effective date. Termination for convenience needs no breach: you serve the notice period the contract specifies (often 30 to 90 days), pay any early-termination fee, and the contract ends when the notice runs out. Cause is faster and cheaper but requires evidence and the cure step; convenience is slower but hard to dispute.
Q2. How much notice do you need to give a maintenance vendor?
Whatever the contract says, in the form it says. Convenience clauses commonly require 30, 60 or 90 days' written notice; for-cause clauses require a notice of breach and a cure period, often 10 to 30 days, before termination. Auto-renewing contracts usually require non-renewal notice 60 to 90 days before the anniversary. Where there is no written contract, the notice required is a matter of local law and past dealing, so take advice before sending anything.
Q3. What should a vendor termination letter include?
The contract it refers to; the clause relied on; for cause, the earlier breach notice and the date the cure period expired; the termination date; what is to be returned and by when, with the consequence for non-return; which open work orders are to be completed and which are cancelled; when the final invoice is due and that payment follows reconciliation and return of property; and which clauses survive, such as warranties, confidentiality and insurance. It should not include a narrative of the vendor's performance; that belongs in the evidence file.
Q4. How do you replace a vendor without a gap in service?
Line up the replacement before you serve notice. Use the emergency roster or a quick bid to identify the successor, start its onboarding (identity, insurance, banking, rate card) on day 1, have it shadow the outgoing vendor during the notice period where the contract allows, and dispatch it on live work orders from around day 15. The notice period is transition time; a vendor served notice on the day its replacement is chosen is the reason exits go smoothly.
Q5. What happens to warranties when you terminate a contractor?
They continue according to their terms. Workmanship warranties are contractual and should be named as surviving in the termination letter; manufacturer warranties attach to the equipment and should be checked for the registered owner and transferred from the contractor to the property owner if necessary. Collect the certificates, serials and commissioning records at handover, record the end dates in the asset register, and hold any defects retention to its date rather than releasing it with the final invoice.
