Most condo boards sign security service agreements without fully reading them. The decision was made (vendor evaluated, references checked, scope agreed), and the contract feels like paperwork. So it gets passed around for signatures and filed.
This is where corporations expose themselves. The differences between a strong security contract and a weak one rarely show up during the sales process. They show up two years later when a problem requires the contract to do something — limit liability, define performance, allow termination, transfer records. Nine clauses determine whether the contract actually protects the corporation when it matters. Here’s what each one does, what good language looks like, and what to push back on before signing.
| Note: This article is contract education, not legal advice. Every condo board signing a security service agreement should have the document reviewed by the corporation’s legal counsel before execution. The framework below helps you ask the right questions of that counsel — it doesn’t replace them. |
1. Scope of Services
This is the most important and most overlooked clause. It defines what the vendor is actually contracted to do — and what they aren’t. Vague scope language (“general security services,” “protection of the premises”) creates ambiguity that always resolves in the vendor’s favour when something goes wrong. Strong scope language specifies posts, shift hours, patrol frequency, supervisor visit cadence, reporting deliverables, and incident response protocols. If you can’t read the scope clause and visualize exactly what the vendor delivers each day, it’s too weak.
2. Performance Standards and Service Level Commitments
The clause that defines what “good” looks like. Strong contracts include measurable standards: response times for incidents, patrol completion rates, supervisor visit frequency, daily report delivery deadlines, officer training documentation requirements. Weak contracts say things like “vendor will provide reasonable security services in accordance with industry standards.” That language is unenforceable. Push for specifics that can be audited — and a defined process for raising and resolving performance concerns.
3. Termination and Cure Provisions
Two scenarios matter here: termination for convenience (the corporation simply wants to end the relationship) and termination for cause (the vendor isn’t performing). Both should be explicit. Standard notice for convenience runs 30 to 90 days. Termination for cause should require written notice of the specific deficiency, a defined cure period (typically 30 days), and the right to terminate immediately if the cure isn’t delivered. Watch for clauses that require lengthy notice for cause or that include early-termination penalties — these protect the vendor at the corporation’s expense.
4. Insurance Requirements and Indemnification
This clause defines what coverage the vendor must maintain and who bears responsibility when things go wrong. Strong language specifies minimum insurance limits, names the corporation as additional insured, requires certificates of insurance to be provided annually, and includes mutual indemnification — the vendor covers losses caused by their actions or omissions; the corporation covers losses caused by its own. Beware of one-sided indemnification clauses that obligate the corporation to indemnify the vendor for the vendor’s own conduct.
5. Liability Limitations
Almost every security contract limits the vendor’s liability — the question is by how much. Common limitations cap damages at the value of fees paid in some prior period. The cap should be high enough that it doesn’t render the contract toothless when a serious incident occurs. A cap equal to one month of fees is too low; closer to a year is more reasonable. Some contracts attempt to exclude liability entirely for certain categories of loss. Have counsel review these carefully.
6. Officer Assignment and Replacement
Less common in standard contracts, but increasingly important. This clause defines whether specific officers are assigned to the building or whether the vendor can rotate staff freely. The corporation’s interest is in continuity — officers who know the building deliver better service. The vendor’s interest is flexibility. A reasonable middle ground: the vendor commits to maintaining a defined number of regular officers, with rotation only with prior notice and the right of the corporation to reject specific replacements for cause.
7. Records, Reporting, and Data Ownership
Determines what the vendor must deliver and who owns it. Daily reports, incident reports, patrol logs, visitor records, and CCTV footage (if the vendor operates it) should all be specified. Ownership should explicitly assign these records to the corporation. Retention obligations should be defined — typically 24 to 36 months minimum. On termination, the vendor must transfer all records and certify deletion of any copies they retained. Without explicit data ownership language, the corporation can find itself unable to access its own incident history.
8. Price Escalation and Adjustment Mechanisms
Multi-year contracts almost always include some mechanism for annual price increases. The clause should specify what triggers an increase (minimum wage changes, CPI thresholds, scope changes), how much advance notice the corporation receives, and any cap on annual increases. Watch for open-ended language allowing the vendor to raise rates “as necessary” — this is essentially a blank cheque. Tying increases to specific, documented triggers protects the operating budget from surprise renewal demands.
9. Confidentiality and Dispute Resolution
Confidentiality clauses are standard but should be mutual — the vendor protects the corporation’s information, and the corporation protects the vendor’s pricing and operational details. Dispute resolution clauses define what happens when the parties can’t agree. Mediation as a first step is reasonable; mandatory binding arbitration with a vendor-selected arbitrator is not. The corporation’s preferred position is mediation followed by litigation in the local courts under provincial law — not arbitration in a jurisdiction the vendor chose.
The Final Check Before Signing
Run through this short sequence before any board member signs:
- Has the corporation’s legal counsel reviewed the agreement?
- Does the scope clause describe daily operations clearly enough to enforce?
- Are performance standards measurable, not vague?
- Does the termination clause include a cure period and a reasonable notice term for convenience?
- Is the liability cap proportional to the corporation’s risk exposure?
- Does the corporation explicitly own the operational records?
- Are price escalation triggers specific and capped?
If any answer is unclear, the right move is to ask the vendor to clarify in writing — before the contract is signed, not after.
The Bottom Line
A condo security contract is one of the higher-stakes vendor agreements the corporation signs. The clauses above are where the contract earns its keep when problems arise — or fails to. A board that understands what each clause does gets better outcomes from disputes and exits cleanly when it needs to.
Falcon Security’s standard service agreement is structured around these clauses by default — every section above is written into the contract clearly and reviewable before signing. [Request a contract walkthrough] Or download the Vendor Evaluation Checklist to score any vendor before reaching the contract stage.
Frequently Asked Questions
Q1. Should a condo board have a lawyer review a security service agreement?
Ans. Yes, especially for multi-year contracts or buildings with significant insurance exposure. The cost of legal review is small relative to the operational and liability exposure the contract creates. The corporation’s regular legal counsel can usually handle this without specialist involvement.
Q2. What’s a reasonable term length for a condo security contract?
Ans. One to three years is the standard range. One-year terms maximize the corporation’s flexibility and pressure on the vendor to perform. Three-year terms sometimes offer modest concessions in exchange for the commitment. Anything longer than three years rarely benefits the corporation.
Q3. Can we negotiate the standard contract a vendor provides?
Ans. Almost always, yes. Vendor standard contracts are first drafts, not final terms. Reputable vendors expect and accept reasonable revisions. The clauses most commonly negotiated are termination terms, liability caps, performance standards, and price escalation mechanisms.
Q4. What happens if the security vendor breaches the contract?
Ans. Most contracts specify a notice-and-cure process: the corporation provides written notice of the breach, the vendor has a defined period (typically 30 days) to remedy it, and the corporation can terminate if remedy isn’t delivered. Serious or repeated breaches may justify immediate termination — but the contract language determines the available options.
Q5. Are auto-renewal clauses normal in condo security contracts?
Ans. Common but not mandatory. Auto-renewal clauses typically extend the contract for another full term unless either party provides written notice within a defined window (usually 30–90 days before renewal). If your contract has auto-renewal, calendar the notice deadline well in advance — missing it locks the corporation in for another full term.
Q6. Should the contract specify which officers will work at our building?
Ans. Naming specific officers in the contract is unusual and impractical (officers leave, get promoted, change schedules). What’s reasonable is a clause requiring the vendor to maintain a defined number of regular officers, to provide notice of personnel changes, and to give the corporation the right to reject replacements for cause.
Q7. How do we handle disputes that arise under the contract?
Ans. Most contracts include an escalation path — concerns raised in writing to the vendor’s account manager, then to senior leadership if unresolved. Mediation is a reasonable next step before litigation. Be cautious about contracts mandating binding arbitration in a jurisdiction or under rules the vendor selected — these often favour the vendor in disputes.
Q8. What documents should accompany the main contract?
Ans. Common attachments include the scope of services, post orders, insurance certificates, the vendor’s proof of provincial licensing, the resident communication template, and any service-level definitions. These should be referenced in the main contract as integral parts of the agreement, not standalone documents.