Checkboxes stay in this browser and are never sent to Specialist AI Work or a platform. These lists organize questions to verify; they do not decide whether you qualify or guarantee work.
Start with readiness Print checklists
Use this before opening a role-specific application. It helps separate evidence you can honestly present from requirements you still need to verify.
AI evaluator application readiness Read the current role page and confirm it still accepts applications. Match the required field to credentials or work samples you can substantiate. Prepare a concise example of reviewing, correcting, ranking, or explaining work. Confirm country, work-authorization, schedule, and equipment requirements. Record the advertised applicant pay and any variable-rate language. Remove confidential employer, client, patient, assessment, or project information from examples. Use AI Work Match Reset this checklist An assessment may be legitimate, but its scope and data handling should still be proportionate. Pause when the task looks like production work without clear limits.
Before an unpaid assessment Confirm the assessment belongs to the official platform or application domain. Read the expected time, format, scoring, retake, and accommodation information. Check whether the prompt requests confidential or personally identifying material. Save the role title and assessment date without copying protected test content. Decide in advance how much unpaid time you are willing to spend. Stop if payment, cryptocurrency, credentials, remote access, or unrelated software installation is requested. Recorded screening can involve voice, video, identity, and retention questions. Verify what is required before consenting or recording.
AI interview or recorded response Confirm whether voice, video, screen sharing, or a live interviewer is required. Read the platform notice about recording purpose, retention, and deletion. Use a quiet setting and test only the minimum required permissions. Do not reveal passwords, identity numbers, banking details, or confidential work examples. Prepare truthful, specific examples rather than scripted claims of qualification. Ask for an alternative or accommodation when the documented process permits it. Identity checks can be part of legitimate onboarding, but the request should come from the verified platform flow and explain who processes the data.
Identity verification safety Start from the platform’s official site rather than a message link. Confirm the processor name, purpose, requested document, and retention notice. Check that the request occurs at the expected onboarding stage. Never share one-time codes, banking passwords, or remote-device access. Avoid sending identity documents through ordinary email or chat. Contact official support independently if the domain, urgency, or request changes. Payment setup is easier to audit when you record the agreement and provider terms before completing work.
First payment setup Confirm worker classification and who is responsible for tax reporting. Record the rate, payable activity, approval rules, and payout threshold. Verify the payment provider from official platform documentation. Use a unique password and multi-factor authentication where supported. Keep invoices, approved task records, and payment dates without storing credentials. Escalate missing payment through the documented support path with non-confidential evidence. Acceptance often means access to a pool, not guaranteed assignments. Use a measured routine instead of repeatedly refreshing or assuming a technical problem.
Accepted but no tasks Check onboarding, profile, assessment, tax, and payment steps for incomplete items. Review the official dashboard and support status at reasonable intervals. Confirm whether country, language, specialty, or device filters affect task access. Record the last meaningful platform update. Avoid paying anyone who promises to unlock task volume. Keep applying elsewhere rather than treating one platform as guaranteed income. A short recurring review reduces missed follow-ups without turning unstable project work into an all-day refresh habit.
Weekly multi-platform routine Review new public roles that fit your actual field and location. Update saved and applied states in your local or optional cloud tracker. Check follow-ups due in the next fourteen days. Reconfirm changed pay, eligibility, or project wording before applying. Review platform messages through official dashboards. Export a tracker backup and remove stale notes containing unnecessary personal data. Follow up only through a documented channel and keep the message brief. Silence does not prove rejection, but repeated unsolicited contact rarely improves screening.
Application follow-up Confirm the application was submitted and note its date. Wait for the platform’s stated response window. Use the official support or recruiter channel attached to the application. Mention the role and submission date without sending identity documents. Ask one clear status or technical question. Record the response, next step, or decision to close the application. A referral may credit the referrer, but it should still lead to the normal platform process and never promise acceptance or work.
Before using a referral link Read the site’s referral disclosure. Confirm the destination uses the expected official platform host. Check that the role or program is still current. Compare the route with the platform’s direct application option. Do not proceed if the referrer requests payment, credentials, or private documents. Assume normal screening, eligibility, availability, and project terms still apply.