What a contractor of record does
A contributor program brings together several different jobs. Someone must establish the contributor’s identity, agree the work and compensation, document the right to use the deliverables, approve payments, and retain the records that explain each transaction. A contractor of record brings a contracting party into that workflow. The provider’s specific responsibilities should be written into the service agreement rather than inferred from the product name.
For example, an annotation startup may recruit contributors and operate its own task platform while a provider signs the contributor agreements and administers payouts. The startup still defines the dataset, evaluates quality, and decides what work it accepts. This separation can make operations easier to manage, but only if the agreements and day-to-day process describe the same arrangement.
Before selecting a provider, trace one contributor from invitation to their first completed payment. Identify who answers questions at each step, who can make changes, and where the evidence lives. A clear division of responsibilities matters more than a long feature list.
CoR, AoR, and EOR compared
These labels describe different arrangements, and providers do not always use them consistently. Ask to see the contract structure. A contractor of record typically acts as the contracting counterparty. An agent of record administers agreed activities for a principal, with the precise authority set out in the contract. An employer of record employs the worker and handles the relevant employment administration.
Direct contractor management is another option: your company signs the contributor agreement and uses software or a provider to manage records, invoices, and payouts. It may fit a team that already has the contracting process it needs. It should not be confused with buying a different allocation of contractual responsibility.
| Arrangement | Relationship | What to establish |
|---|---|---|
| Direct management | Your company contracts with the contributor | Agreement, classification, approvals, and payment responsibilities |
| Contractor of record | Provider acts as contracting counterparty | Scope of obligations, IP transfer, and any liability limits |
| Agent of record | Provider acts within the authority granted by the principal | Who is principal, who signs, and what the agent can do |
| Employer of record | Provider employs the worker | Employment terms, statutory obligations, and operational responsibilities |
Start with the actual working relationship
Paying someone for completed tasks is a way of calculating compensation. It does not, by itself, decide whether that person is an independent contractor. Review how the work is organized, what control the business exercises, and the local requirements that apply to the contributor. A signed contractor agreement is part of that review, not a substitute for it.
In the United States, the IRS describes behavioral control, financial control, and the relationship of the parties as relevant categories for federal employment tax analysis. That is a US framework, not a global checklist. A program recruiting in several countries needs a country-specific assessment rather than a single score applied everywhere.
For an AI data team, useful facts include whether contributors can decline tasks, whether fixed shifts are required, how instructions and quality reviews work, and whether the relationship is ongoing or tied to a particular project. Performance bonuses also belong in this assessment. Review changes in the operating model when a contributor moves from occasional tasks to regular responsibilities.
Follow the rights from contributor to customer
The output may be a set of labels, a written explanation, a ranking, a recorded conversation, or code for a test environment. Your downstream agreement may require rights to distribute, sublicense, modify, or use that output for training and evaluation. Those rights need a documented path from the contributor to your company and, where appropriate, to your customer.
Ask how the agreement defines deliverables, deals with pre-existing material, and records the contributor’s acceptance. Keep the relevant agreement version alongside the assignment and acceptance record. If a provider is a party in the chain, establish how rights move through that provider to you.
An IP assignment does not answer every data question. Consent to a recording, rights in third-party material, confidentiality, and personal-data processing can require separate treatment. Review these together before collecting a new type of data, especially when expanding from text annotation into audio, video, or specialist software contributions.
Connect accepted work to a payment record
The operational unit is often an accepted task rather than a monthly salary. Keep task identifiers, the rate version, accepted quantities, and any bonus approval in a record that finance can reproduce. The contributor should be able to understand how the amount was calculated without needing access to internal customer information.
Separate work acceptance from payment execution. A task may be complete while the associated payment is awaiting approval, funding, a corrected bank detail, or confirmation from the payment route. Treating all of those states as “paid” makes support and reconciliation harder. Agree which system supplies each status before launch.
For frequent small payments, compare the expected payment size with fixed transaction costs, currency conversion, and the administrative work of exceptions. A weekly batch may be simpler than a separate transfer for every task, even when earnings are calculated per task. The appropriate schedule should be agreed with contributors and reflected in the contract.
Decide which onboarding records your platform needs
An embedded onboarding experience describes where contributors complete the process. It does not, by itself, explain who stores identity evidence or which systems can access it. Draw that data flow separately from the contributor journey. Your product might need an onboarding result and an agreement reference while another party needs the underlying evidence for a defined purpose. Confirm the actual arrangement before telling a customer that your company never receives identity documents.
List the records that each operating team needs. A task coordinator may need eligibility and agreement status. Finance may need an invoice and payment reference. A support specialist may need to identify the unfinished onboarding step. Those needs are different from broad access to identity documents or tax forms. Review exports and support attachments as well as the main application, because a carefully designed onboarding flow can still produce unnecessary copies through routine troubleshooting.
Keep responsibility for maintenance explicit. If a contributor changes residence, updates a receiving account, or signs a revised agreement, decide which system captures the change and which team assesses its consequences. A current status without a dated history may be insufficient to explain why a payment or engagement was approved at an earlier point. Ask the provider what records remain accessible during the engagement and after it ends.
Compare the service and the billing unit
A quote is only useful when it identifies what is being counted. Registered contributors, active contributors, paid contributors, transactions, and total payment volume are different billing units. A network of 500 registered people with 200 active contributors can produce very different costs under those models.
Talk to Toku about volume-based pricing. When your program needs an AoR arrangement and IP protections, the price must reflect that scope. Higher volume does not remove the minimum pricing needed to provide those services; the specific terms are agreed in your quote.
Ask for the full calculation: the service fee, any minimum, payout costs, currency conversion, and implementation or additional support. Use an example month from your actual operating plan. Show both the number of people and the number of payments so that a low-activity network is not mistaken for a conventional recurring payroll.
Questions to ask before signing
Choose a sample contributor in each launch country and walk through the proposed arrangement. The discussion should produce an agreed operating process and a list of records, rather than a general assurance that compliance is covered. Ask who handles a failed onboarding check, an unsigned agreement, a contested task, and a returned payment.
Also review what happens when the relationship ends. Determine how outstanding work is accepted, how final payments are approved, how access is removed, and how required records remain available. If you change providers later, you should understand which records can be exported and how ongoing obligations are handled.
The best fit is the arrangement that matches both the legal relationship and the way your network actually works. Some teams need direct contractor management. Others need a provider in the contracting chain. Where the relationship is employment, evaluate an employment solution instead of trying to solve the issue by changing the payment method.
- Who signs with the contributor, and who is the principal?
- Which activities remain your responsibility?
- How are IP rights and agreement versions recorded?
- What is the process for classification changes and exceptions?
- Which countries and payment methods are supported for your arrangement?
- What does the price count, and what happens in an inactive month?
Validate the arrangement with a small pilot
Before expanding a contributor program, test the whole operation with a small authorized group. Include the work types, countries, and compensation rules that matter to your launch. Walk through an accepted task, a bonus, a correction, and an incomplete onboarding record. The purpose is to see whether the agreement, product, and finance workflow fit together, not just whether the application can send an API request.
At the end of the pilot, reconcile the approved earnings to the invoices and payment outcomes. Check that your team can locate the signed agreement and explain the rights attached to a sample deliverable. Ask support to describe an exception using the records available to them. Write down any manual step that would become difficult at a larger volume, then agree how it will be handled before recruiting more contributors.
Keep the initial service scope and the expansion plan together. A move into a new country, a different kind of expert work, or a new downstream customer requirement may change both the operating process and the quote. Treat those changes as part of managing the arrangement rather than assuming the first pilot establishes every future use case.
General information for teams planning contributor programs. Classification, tax, payment eligibility, and data obligations depend on the actual arrangement and applicable local requirements.