Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

README.md

Data

Source

All documents are synthetically generated by AI. No real company data, contracts, or proprietary content is used. No content was copied from any existing template or document.

Documents

The contract clause structure follows the standard components of a B2B SaaS/software service agreement (definitions, scope, term, fees, IP, confidentiality, data protection, warranties, liability, indemnification, dispute resolution, general provisions) as described in publicly available legal drafting guides.

Tasks

The 60 review tasks follow standard enterprise contract management workflows as described in:

Specific domain knowledge referenced per document type:

Document Type Domain Knowledge
Service Agreements Standard software service agreement clauses (scope, term, fees, IP, confidentiality, liability, indemnification, dispute resolution). Governed by Singapore law.
Amendments Standard contract amendment format: recitals, numbered amendments referencing original clauses, general provisions.
Master Service Agreement Multi-vendor governance framework with qualification requirements, steering committees, performance management, financial controls.
Vendor Assessments SLA performance scoring across delivery, security, financial, relationship, and innovation dimensions.
Information Security Policy Aligned with common information security frameworks: data classification (public/internal/confidential/restricted), access control with RBAC and MFA, encryption standards (AES-256, TLS 1.2+), incident severity classification.
Data Governance Policy Data quality dimensions (accuracy, completeness, consistency, timeliness, validity, uniqueness), lifecycle management, retention schedules, privacy requirements.
Board Minutes Singapore board meeting format: quorum, resolutions, management reports, risk committee updates.
Vendor Proposals Standard vendor proposal format: executive summary, company overview, requirements analysis, technical methodology (5-phase approach), team composition, timeline, pricing, references, terms. Shared governance, risk management, compliance, training, innovation, and sustainability sections across all proposals.
NDAs Standard mutual non-disclosure agreement with defined confidential information, exceptions, survival period.

Fictional Entities

All company names, vendor names, personnel names, contract IDs, and financial figures are fictional:

  • Company A Pte Ltd — fictional client company
  • Cloud Provider B Inc — fictional cloud vendor
  • AI Lab C Ltd — fictional AI vendor (not affiliated with Google AI Lab C)
  • Security Firm D Pte Ltd — fictional security vendor
  • Data Services E Pte Ltd — fictional data vendor

Document Statistics

File Size Type
contract_alpha_cloud.txt 45 KB Service Agreement
contract_beta_ai.txt 46 KB Service Agreement
contract_gamma_security.txt 46 KB Service Agreement
contract_delta_data.txt 45 KB Service Agreement
amendment_alpha_cloud_a1.txt 5 KB Amendment
amendment_beta_ai_a1.txt 5 KB Amendment
amendment_gamma_security_a1.txt 5 KB Amendment
amendment_delta_data_a1.txt 5 KB Amendment
master_service_agreement.txt 9 KB MSA
vendor_assessment_alpha_cloud.txt 4 KB Assessment
vendor_assessment_beta_ai.txt 4 KB Assessment
vendor_assessment_gamma_security.txt 4 KB Assessment
vendor_assessment_delta_data.txt 4 KB Assessment
policy_information_security.txt 7 KB Policy
policy_data_governance.txt 6 KB Policy
board_minutes_2024_q4.txt 8 KB Board Minutes
proposal_cloudnine_cloud.txt 60 KB Vendor Proposal
proposal_deepmind_ai.txt 60 KB Vendor Proposal
proposal_cybershield_security.txt 60 KB Vendor Proposal
proposal_datastream_data.txt 60 KB Vendor Proposal
nda_001_cloudnine.txt 6 KB NDA
nda_002_deepmind.txt 6 KB NDA
Total 490 KB 22 files

Content Overlap

The four service agreements share Articles 1-16 and Schedules A-B (common legal template), differing only in:

  • Article 17 (vendor-specific terms)
  • Contract headers (parties, dates, amounts)
  • Payment schedules

This ~70% content overlap across contracts is representative of real enterprise contract portfolios where a standard template is used across vendors.