Quick Start
Get from zero to your first compliance findings in under 10 minutes. No integration required.
Prerequisites
- A Contract-as-Code account (sign up or request access via sales)
- A PDF collective agreement, CBA, or enterprise agreement
- A CSV export of employee payroll data from your HRIS
Step 1: Create your organisation
After signing in, you'll be prompted to create an organisation. This is your workspace — all contracts, rules, validation jobs, and team members belong to your organisation.
- Organisation name (e.g., "City of Toronto HR")
- Primary jurisdiction (you can add more later)
- Your role (admin, reviewer, or viewer)
Step 2: Upload a collective agreement
Navigate to Contracts → Upload contract.
- Select or drag your PDF file (max 200 pages, 50 MB)
- Enter a display name (e.g., "CUPE Local 79 — 2024–2027")
- Select the applicable jurisdiction
- Click Upload & Extract
The AI extraction pipeline runs in 1–3 minutes depending on document length. You'll receive an email when extraction is complete.
Supported formats
PDF is the primary supported format. Scanned PDFs with OCR text layers are supported. Image-only scans without an embedded text layer will produce lower-quality extractions — use a PDF with selectable text when possible.
Step 3: Review rule candidates
Once extraction completes, navigate to Contracts → your contract → Rule Candidates.
Each rule candidate shows:
- Source clause: the exact text from the agreement, with page number
- Rule type: the family (overtime, shift premium, vacation, etc.)
- Structured interpretation: the AI's structured version of the rule (thresholds, rates, conditions)
- Confidence score: the extraction pipeline's confidence in its interpretation
For each candidate, you can:
| Action | What it does |
|---|---|
| Approve | Adds the rule to the active rule set for validation |
| Edit | Modify parameters before approving (e.g., correct a threshold) |
| Reject | Exclude this candidate from the active rule set |
| Flag for review | Mark for a colleague or legal counsel to review |
WARNING
No rule becomes active without an explicit approve action. Rejected and unreviewed candidates are never used in validation.
Step 4: Upload employee data
Navigate to Validation → New validation run.
- Select the contract(s) to validate against
- Upload your CSV employee dataset
- Select the as-of date (the pay period you're validating)
- Click Run validation
CSV format
The column-mapping engine automatically recognises exports from ADP, Dayforce, Workday, Kronos, Sage, and Micropay. For other formats, you'll be prompted to map columns manually.
Required fields:
| Field | Description | Example |
|---|---|---|
| Employee ID | Any unique identifier | EMP-4471 |
| Date | Pay period or shift date | 2025-01-15 |
| Hours worked | Total hours for the period | 42.5 |
| Hourly rate | Rate paid | 35.00 |
| Classification | Job title or classification code | RN-2 |
Optional fields (improve finding accuracy):
| Field | Description |
|---|---|
| Shift start / end | Enables shift premium validation |
| Overtime hours | Enables overtime rule validation |
| Years of service | Enables vacation/seniority validation |
Employee PII
Employee identifiers are hashed (SHA-256) before any external processing. Raw names, SINs, SSNs, NI numbers, or TFNs are never stored on our infrastructure.
Step 5: Review findings
Validation runs complete in seconds for typical datasets (under 10,000 records). Each finding shows:
- Employee (hashed reference)
- Date / pay period
- Rule violated (with link to the approved rule and source clause)
- Expected value (what the agreement says should happen)
- Actual value (what your data shows)
- Estimated financial impact
- Severity (error, warning, review needed)
Step 6: Export your report
Navigate to Reports → select your validation run → Export.
Available formats:
- PDF — structured audit report with clause references, suitable for compliance teams and legal counsel
- CSV — raw findings data for further analysis in Excel, Google Sheets, or your BI tool
Next steps
- Core Concepts: Contracts & Versions — managing multiple agreements
- Core Concepts: Rule Families — what types of rules the platform extracts
- Core Concepts: Jurisdictions — how region and jurisdiction affect validation
- Integrations: CSV Data Ingestion — detailed CSV schema reference
- Security: Data Privacy — how employee data is handled
- API Reference — programmatic access to the platform