Social Task Proof Checklist
Strong social-task proof lets a reviewer confirm the requested action without guessing. Before submitting, verify five things: the evidence matches the instruction, is readable, identifies the relevant account or content, shows the completed action, and includes the requested reference. CLEAR is a memory aid created for this guide, not an industry standard; each task’s instructions always take priority.
Read the task before you act
Read the complete instruction before completing the action. Confirm the platform, target account or content, deadline, required wording and accepted proof format. Stop if a task asks for a password, recovery phrase, private key, two-factor code or payment to unlock a reward.
Use the CLEAR check
C means Condition: the evidence matches the exact instruction. L means Legibility: important text and interface states are readable. E means Entity: the relevant account, post or channel is identifiable. A means Action: the requested completion is visible. R means Reference: the required URL, task or context is present.
Build useful screenshot proof
Show enough context to connect the account, content and completed action. Keep the username or channel visible when required, and capture the interface state that demonstrates completion. Crop only irrelevant space, never alter the meaning, and check readability on a smaller screen.
Use direct links and exact references
Submit the direct URL requested by the task, not a homepage or search result. Test it while signed out when possible so you know what a reviewer can see. Never share private session URLs, authentication links or account-management pages.
Protect sensitive information
Reveal only what is needed to verify the action. Hide unrelated email addresses, phone numbers, private messages, notifications, wallet details and browser tabs. Passwords, recovery phrases, private keys and authentication codes must never appear in task evidence.
Run the final check and handle revisions
Open every attachment, test every link and compare the evidence with the original instruction. If revision is requested, address the specific missing element with a new screenshot, link or explanation; do not resubmit the same unclear evidence or fabricate proof.
- What counts as good social-task proof?
- Good proof clearly connects the required account or content with the completed action. It is readable, task-specific and contains the screenshot, link or context requested by the task.
- Is a screenshot or a link better?
- Follow the task instruction first. Screenshots preserve a visible state, while direct links let the reviewer inspect live content. When permitted, using both can reduce ambiguity.
- Can I crop a proof screenshot?
- Yes, if cropping removes only irrelevant or sensitive space. Keep all details needed to identify the account, content and completed action.
- What should I do if my proof link is private or broken?
- Check visibility and replace the link if possible. Add a readable screenshot when the task permits it, and explain any access limitation instead of asking the reviewer to guess.
- Should proof contain passwords or wallet credentials?
- No. Never submit passwords, recovery phrases, private keys, two-factor codes or authentication links as task proof.
Sources
- How to spot and avoid task scams — U.S. Federal Trade Commission