Contract Review Checklist
I. Performance Obligation Clause Review
- [ ] Service Scope Definition: Does the contract clearly specify the coverage scope, equipment models, installation locations, and functional boundaries of the security system in the form of a checklist or technical specification? Avoid ambiguous terms such as "full package" or "comprehensive responsibility."
- [ ] Delivery Standards and Acceptance Procedures: Are quantifiable acceptance criteria defined (image resolution, response time, storage duration, etc.), along with the acceptance process and objection period for system delivery?
- [ ] Performance Timeline Milestones: Are delivery timelines for each phase clearly defined, with corresponding milestone checkpoints and associated breach penalties?
- [ ] Defect Liability Period: Is a defect liability period specified following system installation and commissioning, including response time limits for remediation during this period?
- [ ] Breach Liability Calculation: Are the penalty or compensation calculation methods reasonable, and is there a liability cap clause in place?
II. Third-Party Liability Clause Review
- [ ] Personnel Injury Liability Attribution: In the event of personal injury or death during construction or maintenance, which party bears responsibility, and does this comply with labor protection regulations in the project's country of operation?
- [ ] Property Damage Compensation Scope: Is the compensation scope clearly defined for property damage to the client caused by security equipment failure or construction operations?
- [ ] Liability Transfer to Third Parties: When subcontractors or suppliers cause damage to third parties outside the project scope, is the liability chain clearly defined, and is the client protected from improper exposure?
- [ ] Data Security and Privacy Liability: When video data collected by the security system is leaked or misused, which party bears responsibility—the system integrator or the client—and is there a clear agreement in place?
III. Insurance Coverage Obligation Clause Review
- [ ] Mandatory Insurance Types: Does the contract explicitly require the contractor to procure specific insurance types (such as contractor's all risks insurance, third-party liability insurance, etc.), and do these coverage types match the project type?
- [ ] Insurance Certificate Submission Requirements: Does the contract require the contractor to submit valid policy copies to the client before commencing work as an entry condition?
- [ ] Insurance Coverage Continuity: Does the contract require insurance to remain effective throughout the entire contract duration and defect liability period, with clear obligations for renewal upon expiry?
- [ ] Insurance Claim Cooperation Obligations: Are the contractor's cooperation obligations following a claim (such as notification deadlines, evidence preservation, site protection) clearly stated in the contract?
- [ ] Insurance Exemption Scenarios: Are scenarios where insurance does not provide coverage disclosed to and confirmed by the client?
IV. Force Majeure and Exemption Clause Review
- [ ] Force Majeure Definition Scope: Are force majeure event types explicitly enumerated (natural disasters, war, civil unrest, government actions, etc.), and does the definition include specific risk types common in the project's country of operation?
- [ ] Notification Obligations and Documentation Requirements: Are the notification deadlines and required documentation reasonable and feasible following a force majeure event?
- [ ] Contract Suspension and Termination Rights: Do both parties have the right to suspend or terminate the contract after force majeure persists for a specified duration, and how are associated costs settled?
- [ ] Liability Exemption Boundaries: Which scenarios do not constitute force majeure (such as supplier delivery delays, market price fluctuations, etc.), and does the contract include explicit exclusions?
V. Dispute Resolution and Governing Law Clause Review
- [ ] Governing Law: Which country's laws govern the contract—is it the law of the project's country of operation or a third country agreed upon by both parties?
- [ ] Dispute Resolution Method: Is negotiation, mediation, arbitration, or litigation preferred, and is the arbitration institution or competent court clearly specified?
- [ ] Language Version Precedence: When discrepancies arise between contract versions in different languages, which version takes precedence?
Comparative Analysis of Common Liability Clause Approaches
| Dimension | Approach A: Integrator Full Responsibility | Approach B: Segmented Liability Allocation | Approach C: Client Self-Insured Risk |
|---|---|---|---|
| Performance Obligation Entity | Integrator assumes responsibility for the complete system | Equipment suppliers, installers, and maintenance providers each fulfill their respective roles | Client independently bears system operation risks |
| Third-Party Liability | Integrator procures unified insurance and handles compensation | Liability propagates through the contract chain layer by layer | Client procures independent insurance and handles matters |
| Insurance Cost Proportion | Insurance premium included in total contract price | Each segment procures independent insurance with transparent costs | No insurance premium, but full risk self-assumption |
| Applicable Scenarios | Packaged campus-wide security system deployment | Large-scale projects with multiple suppliers | Entities with limited budgets but strong operational capabilities |
| Risk Controllability | Relatively high—centralized authority and responsibility | Moderate—dependent on contract chain clarity | Relatively low—dependent on client's own capabilities |
FAQ
Q: Is it sufficient for the contract to simply state that insurance is "the contractor's own responsibility"?
A: No. Further clarification is needed regarding insurance type names, minimum coverage thresholds, proof submission deadlines, and remedial measures if insurance lapses. Otherwise, the client may face a situation where no coverage is available when a claim occurs.
Q: Must Southeast Asian project contracts use local laws?
A: Not necessarily. Most Southeast Asian countries permit parties to agree on foreign laws or international practices. However, mandatory provisions related to real estate, construction permits, and similar matters typically take precedence under local regulations. It is advisable to reach agreement on dispute resolution mechanisms and governing law before contract execution.
Q: Can a subcontractor's insurance directly cover the main contract project?
A: This depends on the specific insurance type and policy terms. Insurance types such as contractor's all risks insurance typically allow the main project to be insured as a whole. However, coverage types such as third-party liability insurance have limitations on the insured party scope defined by policy terms. It is not advisable to assume by default that subcontractor insurance directly covers the main project.
Q: Do force majeure clauses apply to supply chain disruptions?
A: Generally not. Under mainstream contract practices, supplier delivery delays constitute commercial risk and do not fall within the scope of force majeure. If coverage for such risks is required, a separate delivery delay liability clause should be included in the contract.
Q: If the contract does not specify a defect liability period, what is the default treatment?
A: If no provision is made, the defect liability period may default to statutory requirements in the project's country of operation or relevant industry practices. It is advisable to proactively negotiate and clarify these terms during the contract execution stage to avoid being placed at a disadvantage when disputes arise.
This checklist serves as a reference for contract review. The validity and interpretation of specific provisions should be governed by the current laws and regulations of the project's country of operation and the actual contract text executed by both parties.