Mercor vs. Outlier vs. TELUS: audit work and pay by record type

“Mercor vs. Outlier tracking” and “TELUS pay verification” sound like questions about which platform has the best timer or clearest report. But without verified, current documentation for each project’s reporting setup, a feature-by-feature verdict would be guesswork. Contractors should check what their own account and project actually record.

A more dependable comparison starts with three records: your work sessions, your task activity and the platform’s report of work or pay. Those records may describe different things. A timer can measure active time; a task record can count completed items; a pay report can cover a different period or status. None should be treated as a substitute for the others.

Compare the records, not platform reputations

For Mercor, Outlier and TELUS, make a small audit for each active project rather than assuming the same fields or rules apply everywhere. Note what the project makes available: dates, task counts, duration, rate, reported amount and payment status, if shown. Leave a field blank when it is not supplied. Do not infer a timer policy from another project, or from another contractor’s account.

Then align the boundaries before comparing numbers. Use the same date range and time zone. Decide whether your session starts when you begin the work or when a platform timer begins, and use that definition consistently. Separate time spent on setup, breaks or waiting if the platform’s report does not include it. A difference may reflect mismatched boundaries rather than missing pay.

This is the practical answer to a “RLHF platform comparison”: compare like with like. For each period, record your own task count and work duration, the platform’s corresponding figures where available, and any amount it reports. Mark estimates separately from confirmed payments. If a figure changes, preserve the earlier record and note when you checked it.

A repeatable payment check

1. Save the source. Keep a copy or dated note of the platform report available to you. Record the project and covered period.
2. Match the period. Align report dates with your own log; account for time zones and work that crosses midnight.
3. Compare units. Check tasks against tasks, hours against hours, and reported amounts against amounts. Do not treat a task count as proof of duration.
4. Label the result. Mark each figure as tracked, platform-reported, estimated or paid. “Estimated earnings” is not the same as money received.
5. Follow up with evidence. If figures differ, describe the period and the specific discrepancy using records you are permitted to retain. Do not copy confidential prompts, answers or ratings into a personal log.

This approach also helps when one account presents detailed work history and another gives only a summary. Your audit should reflect the evidence available, not fill gaps with assumptions. For a closer look at why personal timers and platform timers can diverge, see how to interpret timer drift.

Choose a logging method that fits the gap

A platform’s own records are the right starting point for its report, but they may not give you one view across several contracts. A spreadsheet offers control and portability, but it depends on timely manual entry. A cross-platform tracker can reduce that entry work, though its own totals still need to be checked against source reports. No personal log changes a platform’s rules or establishes that a disputed amount is owed.

RaterSidekick is one option in that last category. Its Chrome extension tracks work sessions, tasks and estimated earnings on websites the user explicitly designates, including Mercor, Outlier and TELUS. It detects task completion through a user-selected keyboard shortcut. The company says the extension does not capture screenshots, keystrokes, screen recordings or task content. Users can also import history from spreadsheets or platform exports instead of relying on extension tracking.

Its Pay Checker compares a user’s records with platform reports. That makes it a comparison aid, not an independent confirmation of a platform’s calculation or a payment. Contractors should still check the source report, preserve their own dated records and distinguish estimated earnings from amounts actually received. If the mismatch needs a formal follow-up, a clear, content-free session record is more useful than a recollection assembled weeks later.

The decision is about your workflow

If you work on only one project and its reports answer your questions, a separate tracker may add little. If you move among platforms, a consistent personal log can help you compare periods and spot gaps, provided you keep each project’s rules and reporting format distinct. The right routine is the smallest one that lets you explain where each number came from.

For Mercor, Outlier and TELUS alike, verify the account-level evidence before drawing conclusions about tracking or pay. Record what the platform reports, record what you observed, and keep estimates, reports and payments in separate columns. That is a better comparison than assuming every contractor sees the same dashboard.