Canadian HR policies for U.S. tech employers: Ontario, BC and Alberta

Assess duties—not a technology label

Start with actual work: engineering, support, sales, operations, management or another function. A company can employ people with different duties and different applicable rules. Do not import U.S. exempt classifications into a Canadian record.

Ontario has an IT-professional exemption from specified hours-of-work and overtime provisions. The definition is limited; specialized knowledge and professional judgment matter. It is not an exemption from the whole ESA. Ontario — exemptions for information technology professionals Ontario — interpretation of Regulation 285/01

BC has a separate high-technology-professional definition and exclusions from specified hours and holiday provisions under section 37.8. Basic operational technical support is expressly outside key parts of that definition. Do not treat every employee of a technology company as excluded. British Columbia Employment Standards Regulation — section 37.8

Do not export either province’s exception to Alberta. Arrange a separate assessment under Alberta’s rules for the actual role.

A three-province map—not a national exemption chart

The table organizes the review. It does not classify a developer, support technician, salesperson or manager. A title, salary or parent-company industry is not enough evidence to apply every exception. Where facts are uncertain, obtain a role-specific assessment before altering timekeeping or pay.

Use the same evidence format across provinces so payroll can see the differences. The local legal tests should remain distinct even when the internal worksheet looks the same.

What a useful role-exception file contains

Record the actual duties, examples of work, level of independent professional judgment, reporting structure and any facts relevant to the local definition. Include the source provision, which requirements are affected, who reviewed it and the date of the assessment. Keep a role description current enough to describe what the person really does.

For Ontario and BC, read the actual definition instead of relying on the phrase “IT exemption.” Ontario’s official material and BC’s regulation describe different categories. BC’s definition expressly excludes basic operational technical support from key parts of its high-technology-professional definition. Ontario — interpretation of Regulation 285/01 British Columbia Employment Standards Regulation — section 37.8

Schedule a reassessment when someone moves from development into first-line support, begins managing people, or changes location. Do not leave the original payroll exception in place solely because the employee ID stayed the same.

A helpful review record also identifies what the exception does not resolve. An exception concerning overtime is not a universal exemption from vacation, privacy, safety, human-rights or contractual obligations.

Ontario: record the right count and date

Ontario employers meeting the 25-or-more-employee threshold in Ontario on January 1 generally need the ESA written disconnecting-from-work and electronic-monitoring policies before March 1 of that year. The applicable counting rules and statutory scope matter; do not substitute global headcount or full-time equivalents. Ontario — written policy on disconnecting from work Ontario Employment Standards Act — section 41.1.1

The disconnecting-policy requirement does not itself create a general new right to ignore work communications. Explain your actual arrangements and preserve other applicable rights.

Keep a dated threshold worksheet. Separately review workplace violence, harassment, safety, accessibility and hiring obligations; their tests are not all the same 25-person test.

Ontario: three different headcount dates to track

Do not maintain one “25+ employees” checkbox and reuse it for every obligation. For Ontario, record the relevant date and counting method for each requirement.

Ontario — written policy on disconnecting from work · Ontario Employment Standards Act — section 41.1.1 · Ontario - publicly advertised job posting requirements · Ontario - mandatory information for employees

Ontario’s public-job-posting rules took effect January 1, 2026. Covered postings require compensation information, disclosure of AI used to screen, assess or select applicants, and vacancy status; Canadian-experience requirements are prohibited. The compensation rules include a $50,000 range-width limit and an exception where expected compensation, or the range’s upper end, exceeds $200,000 annually. Interviewed applicants have a 45-day decision-status notification rule, measured from the last interview when there is more than one. Posting/application records and interview-notification records have distinct three-year retention starting points. Check the official guidance for exclusions and details.

Assign recruiting an owner for the posting version and notification process. A handbook paragraph does not automatically update an external job board or your applicant-tracking system.

British Columbia: separate role analysis from company policy

Create a role inventory before changing timekeeping or holiday treatment. Record the source, facts and reviewer for any exception relied on. If a job changes, reopen that analysis instead of leaving a historic label in payroll indefinitely.

Use a policy manual that identifies the workplace and company procedures. Avoid writing that “all BC tech workers are exempt” or that a salary makes an exemption automatic.

For a shared U.S.–Canada product team, establish who reviews after-hours incident response and how employees report time. A global on-call procedure still needs local review.

BC: review a remote job posting before publishing

BC’s guidance requires wage or salary information in publicly advertised job postings by covered provincially regulated employers. It includes postings on employer and third-party sites, and jobs advertised outside BC that are open to BC residents and may be filled by someone living in BC, remotely or in person. Federal employers are excluded from that provincial requirement. BC - wage or salary information on job postings

Check whether the specific position and employer fall within the rule before using a U.S. job-ad template. State an actual expected wage or salary, or a bounded range; the guidance does not treat an unspecified minimum or maximum as an adequate range. A recruitment campaign that advertises no specific opportunity is different from a specific vacancy.

Operational check: compare the approved posting with the recruiter’s version, external job boards and the employer’s careers page. Give the recruiting owner a way to correct a stale version. Do not assume that publishing pay information also settles role classification, employment terms or any separate reporting obligation.

Alberta: build its own workplace record

For an Alberta employee, start a separate worksheet for applicable hours, overtime, holidays, vacation, leaves, termination and workplace procedures. Use Alberta's official employment-standards materials rather than copying an Ontario exception. Alberta - employment standards rules

Alberta's overtime guidance states that overtime rules apply to salaried as well as non-salaried employees, while listing specified occupational exceptions, including information systems professionals. Neither a salary nor employment by a software company is a complete analysis. Check the applicable category and actual duties before relying on an exception. Alberta - overtime hours and overtime pay

Assign a local-rule owner, a payroll owner and an escalation contact. Record the company's actual workplace practices: remote work, travel, on-call arrangements, employee concerns and relevant training.

Keep the manual, employment terms and payroll configuration aligned. If a Canadian employee moves to Alberta, reassess the implications before treating the move as an address-only change.

Five controls for a growing tech team

1. Role-change check: reassess any exception when duties change.
2. Location-change check: review moves before implementation.
3. Threshold check: keep dated counts for each applicable policy trigger.
4. Tool-change check: review new monitoring, AI and employee-data practices.
5. Version check: distribute the right local manual and record receipt.

These are suggested operational controls, not an exhaustive statement of legal obligations. Hiring disclosures, accessibility, occupational safety, workers’ compensation, immigration and industry-specific requirements may require additional review.

The handbook-gap checker helps organize these questions. It cannot classify a role, confirm an exemption or certify that every required policy is present.

Worked example: three roles in a software business

Fictional planning example: a U.S. software business employs an Ontario engineer, a BC first-line support technician and an Alberta operations coordinator. It begins with three role records, not one label saying “Canadian tech—all exempt.”

The Ontario review considers actual specialized duties and the particular provisions affected by any valid exception. The BC review considers the high-technology-professional definition and the support exclusion. The Alberta review uses Alberta’s rules for the actual role. The example does not decide whether any of these employees qualifies for an exception.

Recruiting separately checks the requirements for a new public posting. HR keeps the relevant Ontario headcount snapshots, while payroll receives the reviewed hours and time-off instructions. A new on-call arrangement triggers a schedule and role review, not simply a handbook update.

The business uses a shared issue tracker with workplace, question, evidence, owner and implementation status. This lets a global HR team coordinate without pretending that three provinces have the same legal tests. For the daily operating process, use the remote-team guide.

A release checklist for growing Canadian tech teams

• Match each employee to the actual workplace and reviewed employing arrangement.
• Confirm the role evidence and the exact provisions affected by any exception.
• Check the appropriate headcount dates rather than a worldwide total.
• Compare public hiring material with the reviewed local requirements.
• Align after-hours work, incident response and time recording with the local analysis.
• Inventory employee-data and monitoring tools, including changes to AI-enabled systems.
• Reconcile the manual, payroll setup, recruitment process and manager instructions.
• Distribute the correct version and test the employee’s reporting contacts.

These are recommended coordination checks, not a complete legal audit. The point is to close the gap between a rule in a document and the system or manager implementing it. Keep specialized questions assigned to the appropriate reviewer rather than marking them solved by a generic policy.

Use the handbook-localization guide for global/local document conflicts and the first-hire guide when the business expands into another Canadian workplace.