ai training companies contract and sow checklist

# ai training companies contract and sow checklist

What should a busy buyer settle before signing?

Start with the purchase itself. Are you hiring a person to join your team, buying a labeled dataset, or paying for employee training? Give that answer a clear sentence in the statement of work, or SOW.

A role description cannot carry all the terms for a finished dataset. A course syllabus cannot define the quality of production labels. Each purchase needs its own proof that the agreed work was done.

Use the main agreement for terms that apply across the relationship. Put project details in the SOW. Ask counsel to set the order of precedence so conflicting terms have a clear answer.

Before signing, check that the documents answer these questions:

• Who signs the agreement, employs or contracts the workers, and manages their daily work?
• What work is included, and what needs a separate approval?
• What must the buyer supply before work can begin?
• How will the buyer review and accept the work?
• Who may access the data, and what tools may they use?
• What can change the bill?
• What happens when work fails review or a person leaves?
• How does either side end the engagement and recover its files?

Give each open item an owner. A sales email that says the team will handle something later leaves procurement with no clear term to approve.

Put acceptance beside the deliverable

For data labeling, specify the task, input format, label rules, and output format. Include examples of acceptable work and hard cases that require escalation. Name the person who can resolve an unclear label.

For model evaluation, define the rubric and test set. State how reviewers handle tied scores, conflicting judgments, and prompts that cannot be scored. Require approval before anyone changes the rubric during a batch.

For employee training, identify the audience and learning goals. Specify the exercises, attendance rules, and assessment. Decide whether acceptance means delivery of the sessions, completion by participants, or a demonstrated skill.

For an embedded hire, define the role and reporting line. Set an onboarding plan and review cadence. If you also want a guaranteed project outcome, ask for a separate term that assigns responsibility for that outcome.

Test the contract against a failed batch

Imagine a batch arrives on time but fails your quality check. Could your project lead find the correction deadline and billing rule without calling sales?

Then imagine your team changes the instructions after work starts. Could the provider show which version applied and who approved the change?

If either answer is unclear, revise the SOW before approving the purchase.

What do public rules tell you to check?

Worker status deserves a separate review from task quality. The US Department of Labor states: "Employers are responsible for determining whether a worker is an employee under the FLSA." Its guidance describes misclassification as treating an employee as an independent contractor. US DOL guidance

For a US-based engagement, ask counsel to assess how the work will run. Give them the planned supervision, schedule, and duties. Have them compare those facts with the proposed agreement.

For a worker based in Latin America, obtain a review under the law of the worker's country. Keep that review distinct from a US FLSA analysis. Ask the provider to identify the local entity and explain who carries each employment duty.

Put the resulting responsibilities into the contract. A broad promise to handle compliance leaves questions about payroll records, disputes, and exit costs unanswered.

Separate tax paperwork from employment review

The IRS describes Form W-8 BEN as a certificate of foreign status for individuals for US tax withholding and reporting. Its instructions address giving the form to the withholding agent or payer in the stated circumstances. IRS Form W-8 BEN guidance

Ask your tax adviser which forms apply to the actual payee. Record who collects them and where they are stored. Keep the employment review as its own approval task.

Avoid collecting sensitive worker records simply because they might be useful. Ask for the evidence your finance and legal teams need, with access limited to the people who review it.

Make schedule claims precise

Mexico City stays on UTC-6 without daylight saving time. Tijuana follows US daylight saving changes. A contract that promises only "Mexico business hours" leaves room for different schedules. IANA time zone data

Name the worker's time zone and the buyer's time zone. Specify whether the agreed overlap follows the buyer's clock when daylight saving time changes.

Also attach the holiday calendar that will govern coverage. State who approves leave and how the team handles a deadline that falls on a local holiday.

These details let a manager plan review sessions before a delivery slips. They also give finance a defined basis for checking charges for extra coverage.

How do nearshore and Latin American hiring models change the SOW?

Compare proposals by the work each party owns. The label "AI training" does not tell you who hires the people, manages quality, or accepts delivery risk.

Use this table to frame the proposed arrangement. Confirm the allocation in the signed documents.

Choose the model your team can manage

If your team will assign the daily queue and settle labeling disputes, budget time for that management. Name the internal owner in the SOW.

If you want the provider to run delivery, ask it to name the delivery manager. Define the reports that person sends and the decisions they can make without your approval.

When comparing AI recruitment companies, ask where recruiting ends and employment support begins. Request a responsibility table even when the proposal uses a single monthly fee.

Buyers comparing the best AI training companies should use the same workload and acceptance rules across proposals. A low price for unchecked output cannot be compared fairly with a price that includes review and correction.

Match payment to the purchase

For hourly work, state which activities are billable. Include training, meetings, waiting for access, and rework. Set an approval process for hours above the agreed limit.

For per-task work, define a billable item. Address duplicates, incomplete submissions, rejected labels, and tasks abandoned because the input was unusable.

For a monthly hire, ask when billing starts and how partial months work. State how leave, equipment, and replacement affect the invoice.

For a fixed project fee, tie payment stages to named deliverables. Specify how the parties handle a delay caused by missing buyer inputs.

Talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

What should you ask a provider to put in writing?

Send the questions below with your draft SOW. Ask for answers in the document that will govern the work.

Who owns the scope and its changes?

Name a decision-maker on each side. Identify who can approve extra cost and who can change task instructions.

Attach the current rubric with a version number. Require a written change record when a new label, language, or input type enters the queue.

Ask how the provider will estimate the effect on price and delivery. State whether work pauses while that change is under review.

Include buyer dependencies. Access, sample data, and subject-matter review should each have an owner and due date. Define how a missed dependency affects the schedule.

How will we accept or reject work?

Specify the review method before the first production batch. Define the sample selection, pass threshold, and treatment of serious errors.

Decide whether quality is measured by item, label, batch, or reviewer. A single accuracy figure can hide disagreement about what was counted.

Set a review window and rejection process. Require enough detail for the provider to reproduce the issue. Ask counsel to review any clause that treats silence as acceptance.

Define correction deadlines and repeat-failure remedies. State whether failed work is billable and whether corrected work receives a fresh review.

Use a paid pilot if the task rules still need testing. Give it its own scope and price. Require approval before it turns into a larger commitment.

Who may see our data?

List the approved work locations and systems. Ask whether subcontractors can access client material and require a clear approval process for them.

Specify account controls, device requirements, and access removal. Identify who can download files or export a dataset.

Require approval before client material enters an external AI tool. Name approved services and account types. Address retention settings and whether prompts or outputs may be used to train another model.

Set an incident reporting deadline and a named contact. Define what the initial report must contain and how later updates will reach your security team.

Who owns the outputs?

Ask counsel to cover labels, prompts, evaluation notes, code, and course materials as separate work products where needed.

Identify any pre-existing material the provider intends to use. State what rights your team receives and whether those rights survive termination.

Ask whether the provider may reuse examples, publish a case study, or retain data for internal testing. Make each permission explicit.

For a dataset handover, specify the file format and required fields. Include task identifiers, rubric versions, and review history so your team can trace disputed items.

What can change the invoice?

Request the full fee schedule and a sample invoice. Ask which costs require advance approval.

Cover tools, equipment, paid training, overtime, and travel where relevant. State the invoice currency and any exchange-rate adjustment method.

For employment arrangements, ask how the price treats benefits, statutory payments, leave, and termination costs. Have the provider identify what is included and what may be passed through.

Set a process for disputed charges. Name the contact, response period, and treatment of undisputed amounts. Avoid leaving invoice disputes to an informal chat.

What happens when someone leaves or work stops?

Separate replacement from project remedies. Ask what triggers a new search and what support continues while it runs.

Set handover duties for the departing person or delivery team. Cover unfinished tasks, open defects, credentials, and equipment.

For termination, state the notice process and final billing rules. Ask for a worked example using your proposed engagement.

Require a final data export before access closes. Assign responsibility for revoking accounts and confirming deletion. Address backup copies and any records retained under an agreed duty.

What evidence supports the promises?

Ask for a sample status report, an anonymized quality report, and the proposed escalation process. Review whether those documents answer the questions your team will ask during delivery.

For AI companies hiring remote workers, ask who trains new reviewers on your task. Request a plan for checking their work before they handle a full queue.

Treat worker reviews as prompts for diligence. If reviews raise concerns about unpaid work or unclear instructions, ask how the provider handles those situations.

Before signature, have the delivery owner walk through the SOW with procurement. A clause may be clear to a lawyer yet still leave the manager unsure who approves a rejected batch.

Where does Opus fit in this contract review?

Opus states: "The client chooses the finalist and manages day-to-day work." Use that allocation when deciding who owns task instructions, daily review, and acceptance.

If you need a provider to own a complete labeling project, ask whether the proposed engagement includes that duty. Put the answer in the SOW before treating a staffing quote as a delivery commitment.

Opus states that it charges one flat monthly rate per hire. The stated scope covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee, and the rate depends on role, seniority and location.

Dollar rates: Not published.

Request a written quote for the role you intend to fill. Ask how the contract treats the start date, partial months, and any charges outside the monthly rate.

Opus also states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Ask for that promise in the agreement. Review the request process, handover support, and billing during a replacement search.

A replacement clause answers a hiring question. Your SOW still needs to answer what happens to rejected work, an unfinished dataset, or access to client systems.

Bring a role description and a sample task to the conversation. Include the data restrictions and hours your manager needs. Ask for a proposal that assigns each duty to a named party.

Talk to Opus about a role

<!-- File not saved: this workspace is read-only. Contract terms still need legal review for the actual engagement. -->