How to assess eor companies for compliance, IP and data access

What should a busy buyer check before hiring?

Ask for the proposed employment agreement and data-access plan before you approve a candidate's start date. For an AI training role, include the work itself in that review. Someone who writes evaluation prompts may need different permissions from someone who labels customer conversations.

Give your reviewers a concrete description of the job. State who assigns tasks, sets working hours and approves leave. List the systems the person will use and the files they will produce. Ask the provider to explain how its proposed arrangement fits those working conditions.

Use that description to resolve four questions:

• Which entity will employ or contract with the worker?
• Who will handle local payroll and employment obligations?
• How will rights to the worker's output reach your company?
• Who will approve, monitor and remove access to your systems?

Require names and contract terms in the answers. A sales statement about compliance leaves too much open when your team needs to approve an actual hire.

For example, consider a trainer who will review support tickets and correct model responses. Before that person starts, decide which tickets they may see. Specify whether they can download records or paste text into another tool. Assign someone on your team to approve exceptions.

Keep the employment review and the security review connected. If the proposed worker changes country, uses a subcontractor or requests a different device, revisit the affected approvals. Avoid treating the original hiring decision as permission for every later change.

When comparing the best eor companies for your shortlist, use the same job description and access requirements. Otherwise, one quote may cover a different arrangement from another. A lower monthly price means little until you know which duties and costs each proposal includes.

Set a clear approval point before live work begins. Legal should review the signed terms, finance should accept the cost schedule, and security should approve the requested access. Name the hiring manager who checks that those decisions are recorded. A candidate's availability should not become the reason to skip an unresolved item.

You can still prepare onboarding while those checks run. Draft task instructions, choose approved practice data and arrange meetings with the manager. Keep access to customer records pending until the people responsible have cleared it.

What do employment rules tell you about the decision?

Start with the worker's location and proposed relationship. The US Department of Labor defines misclassification as treating an employee under the FLSA as an independent contractor. Its guidance concerns that law; do not apply it as a classification test for a Latin American resident working abroad. US Department of Labor

For a hire abroad, ask local counsel to review the actual working arrangement. Provide the schedule, supervision plan and contract together. Ask whether changes are needed before work begins, and record who will carry them out.

Separate tax paperwork from worker status

The IRS describes Form W-8BEN as a certificate of foreign status for US tax withholding and reporting. Its instructions address giving the form to a withholding agent or payer in the stated circumstances. Use the form for its intended tax purpose. Keep a separate review of how the worker will be engaged. IRS

A useful procurement question is: "What assessment supports the proposed status for this role in this country?" Request the answer before signing. Do not let a completed onboarding form substitute for that discussion.

Give the reviewer the working plan your manager intends to use. If the contract describes project work but the manager expects an ongoing role with fixed hours, point out that difference. Ask for advice on the arrangement you will actually run. Keep the final decision with the hiring record so a new manager can understand it later.

Build local benefits into the cost comparison

Annual benefits affect what you should ask about a monthly quote. The following examples give you specific items to discuss with a provider. Request a calculation for the proposed salary, start date and employment terms.

Ask about other obligations separately. Colombia's article 249, for example, describes cesantías at one month of salary per year of service, proportionate for a partial year. Request the applicable payment and funding schedule for the hire. Código Sustantivo del Trabajo

Paid leave also belongs in the review. Mexico's law states a minimum annual vacation period of 12 working days and a vacation premium of at least 25%. Ask how leave entitlement, accrual and coverage will work for the proposed employee. Ley Federal del Trabajo

Use these obligations to test the quote. Ask the provider to show an ordinary month's invoice and explain what changes around benefit payments or departure. Have finance record which costs are included, prepaid or billed later.

Request the same calculation for a hire who starts partway through the year. Ask how the provider treats a salary increase and whether it changes amounts already accrued. Specify the currency used for the quote and invoices. If currency conversion affects your payment, ask which rate applies and when it is set.

Do not turn an isolated statutory formula into a universal exit estimate. Request a country-specific termination calculation for the circumstances you want to plan for. Separate that estimate from any promise to find a replacement worker.

How should you compare nearshore hiring models?

Choose the model around the responsibility you need someone else to take. Finding a candidate, employing that candidate and delivering a finished dataset are different purchasing decisions.

Before comparing proposals, write down who will manage the work. If your lead assigns tasks and reviews each person's output, make that explicit. If you want a completed labeling project, define the acceptance criteria and ask who supervises delivery.

Use this comparison to ask for a written division of duties. Model names alone will not tell you whether a provider handles a particular task.

An EOR proposal should receive the same IP and security review as any other route. Ask who signs the worker's agreement and how your company receives rights to the resulting work. Have counsel examine the full chain of agreements.

For AI training work, define the output in plain terms. That may include labels, ranking decisions, evaluation prompts, scripts and written guidance. Ask how the agreement treats work created during onboarding or a paid trial. Record any pre-existing materials that the person expects to bring.

If you choose a managed service, ask whether its staff may change during the project. Specify how new workers receive approval and whether they can access the same records. Require the proposal to address subcontractors if the provider intends to use them.

For a long-term hire, discuss manager responsibilities before onboarding. Who records leave? Who raises a performance concern? Who tells the worker about a contract change? Put these duties beside the provider's duties so your managers know when to involve it.

Consider how you will handle disputed work, too. For a managed labeling project, define who decides whether a batch meets your instructions and who pays for corrections. For a hire your team directs, name the manager who reviews mistakes and teaches the task. Ask the provider which performance issues require its involvement.

When reviewing global eor companies, repeat these questions for the actual country and employing entity. Ask who handles the hire if a local partner changes. Require a contact and a process for that event before accepting a general promise of country coverage.

What should you ask a provider before granting access?

Send the questions with your role description. Ask for written answers that your legal, security and finance reviewers can use. Keep unresolved items visible in the hiring checklist, with an owner and a decision date.

Confirm the employer and working arrangement

Request the legal name of the entity signing with the worker. Ask whether the provider uses a local partner and which agreement governs that relationship.

Then describe how your team plans to manage the person. Include fixed meetings, expected hours and any on-call duties. Ask the provider to review that plan against the proposed employment terms.

Confirm who maintains employment records and handles worker questions. Your managers should know where to send a payroll issue or leave request. Ask how disputes reach the right person and who can approve a change.

Trace ownership of the work

Ask counsel to review the worker agreement alongside your service agreement. Request a clear explanation of how rights pass to your company and which provisions need local review.

Define the materials that the worker will create. For an AI trainer, "work product" should prompt a discussion about annotations and evaluation sets as well as code. Ask about prompts, task instructions and revisions to existing datasets.

Address prior materials before they enter your project. Have the worker identify templates, scripts or other assets they expect to reuse. Decide who reviews any license terms and records approval.

Keep confidentiality and ownership as separate review items. Ask what each clause does, who is bound by it and what happens after the engagement ends. Require the signed documents before releasing proprietary work.

Also ask whether the provider may retain examples of completed work for training, demonstrations or internal quality reviews. State your decision in the agreement. If any use is permitted, define which material it covers and who must approve it. Include rejected drafts and sample tasks in that discussion.

Set a usable data-access plan

Give security a list of the data the role needs. Identify whether it includes customer messages, personal information or unreleased product details. Approve access for the task rather than granting the same permissions as an internal engineer by default.

Ask the provider and your own IT owner to resolve these points:

• Will the person use a company-managed device?
• Which accounts need multifactor authentication?
• Can files be downloaded, printed or copied to personal storage?
• Are external AI tools allowed for any part of the task?
• Who can approve a new dataset or working location?
• Which logs will your team review, and who responds to alerts?

For labeling work, consider whether the task can use a restricted view or approved sample. If the job requires live records, document that decision and the access conditions.

Have the data owner approve the material for the stated purpose. Ask legal to review any customer terms that affect who may handle it or where work may occur. Give the worker a short, usable rule for each restriction. "Use only this approved workspace" is easier to follow than an unexplained link to a long policy.

Before launch, test the account with the permissions you intend to grant. Check whether it can export records, invite another user or reach unrelated projects. Record any exception and its expiry date. Repeat the review when the person's task changes, especially when a trainer moves from sample data to live records.

Ask how an incident reaches your team. Put the contact route and expected notice terms in the agreement. Confirm who can suspend access while the issue is reviewed.

Walk through an accidental upload to an unapproved tool. Ask whom the worker should contact and what details your team needs. Assign someone to preserve relevant logs and coordinate the response. Make the reporting route easy to find during the workday.

Test the departure process before the start date

Walk through a resignation and a client-requested end to the engagement. Ask who coordinates the employment steps and how your IT team receives the timing.

Name an owner for each account, device and shared folder. Decide how work moves to a replacement without copying it into personal storage. Ask how retained copies and backups will be addressed under the agreed terms.

Include accounts outside your main sign-in system. Ask the manager to check labeling tools, shared links and any credentials created for the task. Agree on who confirms that access has ended. Keep the completion record with the employment handover.

Request an example final invoice. Have the provider explain any notice costs, accrued benefits or other charges that may apply. Your budget owner should understand those terms before approving the hire.

The same checklist can support a provider discussion about a specific AI training role. Talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

How should you assess Opus for your role?

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

For a buyer, the next step is a role-specific written quote. Ask how the stated coverage applies to the proposed country and working arrangement. Request the agreement that defines each party's duties.

Published dollar rates: Not published.

Ask for the monthly rate for your role, seniority and location. Have finance review how the quote treats benefit accruals, salary changes and departure. Do not substitute a general description of coverage for the terms you will sign.

Opus also states: "The client chooses the finalist and manages day-to-day work." Plan for that management responsibility. Assign someone to teach the task, review output and handle access requests.

For an AI training hire, give that manager an approved sample task. Use it to discuss how the candidate handles unclear instructions or questionable data. Keep customer records out of the assessment unless your team has approved their use.

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Review that promise alongside the employment and offboarding terms. Ask how a replacement search interacts with the departing worker's final pay, file handover and access removal.

Keep the decision tied to the role you are filling. If you need help with employment, review the proposed employer and duties. If you need someone to run the work, ask who will supervise daily output and accept completed tasks.

Before approving a start date, gather the signed agreements, accepted quote and access plan in one hiring record. Assign owners for the items still requiring approval. The worker's first task should use only the systems and data your team has cleared.

Talk to Opus about a role.

<!-- File not saved: the workspace is read-only. Live legal updates were not checked; country-specific terms need review before use. -->