Skip to main content
After your organization invites a specialist, work appears in the portal from that org’s projects. Experts should know which task family they accepted before they start.

​
Where work appears

​
Task types

Judge model outputs: pairwise preferences, rankings, absolute grades, safety flags, and short rationales. Read RLHF evaluations before the first labeling session.
Author scenarios, goals, and success criteria in your specialty that become environment tasks. Read Domain writing before you draft.
Projects may include calibration items (gold questions) so your org can measure agreement. Treat them the same as live work.

​
Accept and submit

1

Read the brief

Check domain fit, format (RLHF vs writing), rubric or style guide, rate (if applicable), and deadline.
2

Accept only if in-domain

Decline if the specialty is wrong. That keeps your org’s banks clean.
3

Complete in the project UI

Follow the onboarding doc linked on the offer. Use only allowed references.
4

Submit for review

Submissions may be spot-checked by project leads or cross-raters before approval.
After you accept, finish by the deadline or release the task early. Repeated abandonments reduce future invitations on that engagement.